MAIL FROM: BODY=8BITMIME SMTPUTF8 SIZE=443 This works: 220 mx. ESMTP welcomes you.Ģ Hello dude ĪUTH PLAIN AHRodW5kZXJiaXJkQGZhbWlsaWUtbGVpbmluZ2VyLmF0AG9ubHk0dGVzdA=ģ54 Enter message, ending with "." on a line by itselfīut this fails: 220 mx. ESMTP welcomes you. However, this is only successful if I leave off the "SMTPUTF8" from the "mail from:" string.
When I manually send the email using the tether, the "rcpt to:" works OK and I can sent the message successfully via openssl command line. I then setup my wifi so it is tethered to my cell phone so my ISP's network is out of the picture. I then tried sending using just openssl and see exactly the same thing, i.e., fails on "rcpt to:" The easyname server must have Spectrum blacklisted since it responds to "rcpt to:" with "Sorry, you are spamming" and the actual message is never even sent. My original test in comment 60 with claws and tb clients was using my ISP (Spectrum). Just mentioning as I observed it and it might be related. Has anyone else noticed that when going through the account creations wizard using the 202009xx 82.0a and plugging in the info from comment 39 that it takes a REALLY long time for it to respond? 89.0b4 seems a lot snappier with the process but it has the newer SMTP client. The "This is spam!" certainly puts the ball in easyname's court as it could be a blacklist or SPF if it's being farmed out to some 3rd party service provider. If bug 1563891 is the only thing that was different between the two but I was using the same IP, then some other very subtle part of this issue is at play. I cannot explain why 20200915 worked for me and 20200916 didn't. It would be great to get these folks involved here and have them watch in real-time what's happening on their end. Seeing as how it can be repro'ed using 78.x, as Gene said, it's got to be some weird syzygy of things such that, when just right, it fails. If your theory is right about blacklist checking, it could explain some of this behavior. I agree there certainly is something more to this than bug 1563891. So it seems that the provider goes off checking the blacklists and maybe in some cases gets a timeout, in which case they make an arbitrary decision. The only reliable IP not rejected was in fact the one from Mexico -) - Go figure!Īs Gene stated, there is a delay in the sending process which I also noticed visually. Five people from different countries tried (me: Mexico and others via VPN, Ping(?), Gene: US, reporter: Austria(?), Arthur(?)) and it failed in most cases, and three people (me + Arthur + reporter) did observe different behaviour on the 15-09 vs. Not sure is this might be something that an "easyname" user might need to configure to get email to send: Others TB logs attached above seem to successfully send the message but the server responds with little delay with "Sorry, this is spam". Could that be what the problem is? Also, note that there is a 23 second delay between sending RCPT TO and the "Sorry, you are spamming" response. What is the "correct" parameter for "EHLO"? Above it is my hostname. *** Error occurred while sending the message: Here's the claws SMTP log that looks very much like the TB SMTP log: * Account Connecting to SMTP server: :465. (I just installed Claws for testing this since the reporter(s) claim there is no problem sending with other random clients.) Also, see it with "Claws Mail 3.17.5" which also doesn't support SMTPUTF8 it appears. I see the "you are spamming" even with TB 78 which doesn't have SMTPUTF8 support. I used as the username as using 113289mail2 failed to complete the new account creation steps. Please verify that your Outgoing server (SMTP) settings are correct and try again., exitCode=2153066725, originalMsgURI= MessageSend.jsm:321:27ġ1:28:07.865 Prompter: internal dialogs not available in this context. The message could not be sent using Outgoing server (SMTP) for an unknown reason. Prompter.jsm:1084ġ1:28:07.864 mailnews.smtp: Command failed: 550 Sorry, this message is spam! currentAction=_actionStream SmtpClient.jsm:483:19ġ1:28:07.865 mailnews.smtp: Message sending failed.
I tried to send using info from comment 39 and using 89.0b4.ġ1:28:04.002 NS_ERROR_NOT_AVAILABLE: 2 ActivityManager.jsm:129ġ1:28:04.976 Prompter: internal dialogs not available in this context.
0 kommentar(er)
