Hello all,
Apparently, the mail server used to test out certification for an ipv6 enabled e-mail address doesn't follow RFC standards when sending mail, and gets rejected by my server:
2009-07-27 01:55:50 SMTP protocol synchronization error (next input sent too soon: pipelining was
advertised): rejected "DATA" H=ipv6.he.net [2001:470:0:64::2] next input="To: \r\nFrom: ipv6@he.net\r
\nMessage-ID: <4a6d5d86d0209.1248681350@ipv6.he.net>\r\nSubject: IPv6 Certification Mail Test\r
\n\r\nPlease insert the following code"
Basically, our mail server located at 2001:470:e867::2 uses a simple way of breaking alot spambots - it inserts a 2 second delay before showing the first '220-' line. This won't break RFC compliant mail servers, but will break mail servers (mostly spam bots) that dump out the entire conversation without bothering to check to see if its okay to do so yet.
Unfortunately, it seems to affect the HE ipv6 testing mail server as well. Any way this could get fixed? :)
Brielle
Interesting..
I also filter pipelining and I did not encounter this problem with them.
Postfix (which I use) handles it differently than Sendmail though.
I believe its the initial delay thats causing the problem. I'm going to have to sniff packets later on to get the exact idea on whats happening, but from observation, it looks like its either not waiting for the final '220' (without the - at the end) before sending the initial EHLO/HELO then pipelining, or its trying to pipeline without telling my end to pipeline.
I think its the former rather then latter personally. I've seen Exchange servers do the exact same thing in the past.
It's actually not a mailserver, but the certification script you're interfacing with that's sending the mail.
We wait for data back from the server before sending the next line, and ensure we see a valid status number before moving on. The one thing I do see that probably tripped up our script on your server is the very long banner and command delays likely got what we were sending out of sync from what you were expecting. I've made some changes and it should be smarter.
Quote from: kcochran on July 27, 2009, 02:48:28 PM
It's actually not a mailserver, but the certification script you're interfacing with that's sending the mail.
We wait for data back from the server before sending the next line, and ensure we see a valid status number before moving on. The one thing I do see that probably tripped up our script on your server is the very long banner and command delays likely got what we were sending out of sync from what you were expecting. I've made some changes and it should be smarter.
Cool. :) Thanks for checking this out!
Brielle
I spoke too soon - getting the following error:
"Didn't get expected welcome"
From the test now.
Brielle
Blargh, the code really didn't handle multi-line banners well. This time for sure!
What's it written in BTW, Perl?
Quote from: kcochran on July 27, 2009, 04:01:17 PM
Blargh, the code really didn't handle multi-line banners well. This time for sure!
No '220 ' found in welcome banner :P
I didn't realize my mail server could be this troublesome. heh.
Brielle
It's in PHP.
I this doesn't do it, I'm going to beat up a penguin. A small foam one, mind you, but a penguin nonetheless.
Quote from: kcochran on July 27, 2009, 04:42:53 PM
It's in PHP.
I this doesn't do it, I'm going to beat up a penguin. A small foam one, mind you, but a penguin nonetheless.
Worked! :) Awesome!
Thank you
Brielle
Glad to hear that.
Penguin, you get a reprieve.
I'm also getting the error
Didn't get expected welcome
error message
My domain is theclements.info
thanks
Tim
I figured out the problem on my end.
the hmailserver requires a new "ip range" for it to accept connections from ipv6
RE - Reply #9: Oh, No! Not a penguin, let alone "Tux."
Anyone want to start a "save the penguin" fund here? ;)
Save the penguin, save the world! The penguin must survive.
:D
I'm sure I read that book, and wasn't it the little red devils that saved the penuins and let them go on to live a healthy life...
:)
same here I get "Didn't get expected welcome"
I tried everything,
the domain is bot.ipduh.com
g@g0:~$ dig +short mx bot.ipduh.com
10 hermes.ipduh.com.
g@g0:~$ dig +short AAAA hermes.ipduh.com
2a01:4f8:140:94a1::3
root@n ~ # telnet hermes.ipduh.com 25
Trying 2a01:4f8:140:94a1::3...
Connected to hermes.ipduh.com.
Escape character is '^]'.
220 hermes.ipduh.com ESMTP Postfix
ehlo g0.gr.trar.gr
250-hermes.ipduh.com
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
mail from:testing@g0.gr.trar.gr
250 2.1.0 Ok
rcpt to:f@bot.ipduh.com
250 2.1.5 Ok
data
354 End data with <CR><LF>.<CR><LF>
Subject:tcejbuS
testing
.
250 2.0.0 Ok: queued as C389140C0FE
quit
221 2.0.0 Bye
Connection closed by foreign host.
It worked, thank you very much :)
Quote from: sosdg on July 27, 2009, 01:07:14 AM
2009-07-27 01:55:50 SMTP protocol synchronization error (next input sent too soon: pipelining was
advertised): rejected "DATA" H=ipv6.he.net [2001:470:0:64::2] next input="To: \r\nFrom: ipv6@he.net\r
\nMessage-ID: <4a6d5d86d0209.1248681350@ipv6.he.net>\r\nSubject: IPv6 Certification Mail Test\r
\n\r\nPlease insert the following code"
I may have a similar problem with Exim version 4.76 #1 built 29-May-2011 18:23:23 on Debian: the test mail doesn't come through, but other regular emails are OK.
I have the following entries in /var/log/exim4/mainlog:
2011-09-15 17:43:19 H=ipv6.he.net [2001:470:0:64::2] F=<ipv6@he.net> temporarily rejected RCPT <ltp@serveur.LT-P.net>
2011-09-15 17:43:20 SMTP protocol synchronization error (next input sent too soon: pipelining was advertised): rejected "To:" H=ipv6.he.net [20
01:470:0:64::2] next input="From: ipv6@he.net\r\n"
I don't know what cause this.