OK guys... this certainly qualifies as "most broken SMTP implementation ever".
Will the protocol police please send out a squad car to pick up the suspects? (at least now we know how they intend to only do this for HTTP. Blargh).
--- Begin Message ---
Patrick W. Gilmore wrote:
Worse than that - it's a fixed sequence of responses...
-- On Tuesday, September 16, 2003 00:56 +0200 -- Niels Bakker <[EMAIL PROTECTED]> supposedly wrote:
A wildcard A record in the net TLD.
$ host does.really-not-exist.net does.really-not-exist.net has address 64.94.110.11
$ host 64.94.110.11
11.110.94.64.IN-ADDR.ARPA domain name pointer sitefinder-idn.verisign.com
It even responds on port 25 (says 550 on every RCPT TO). Gah.
No, it accepts if the from domain exists - but only if it *REALLY* exists.
[...] rcpt to: [EMAIL PROTECTED] 250 OK mail from: [EMAIL PROTECTED] 550 User domain does not exist. mail from: [EMAIL PROTECTED] 250 OK
Nice that their spam filters still work. :(
And I love the 221 close message:
data
221 snubby1-wcwest Snubby Mail Rejector Daemon v1.3 closing transmission channel
Connection closed by foreign host.
$ telnet akdjflasdf.com 25
Trying 64.94.110.11...
Connected to akdjflasdf.com.
Escape character is '^]'.
220 snubby4-wceast Snubby Mail Rejector Daemon v1.3 ready
sdfg
250 OK
sdfgsdfgsdfgsdf
250 OK
sdfgdfgaegqaergqaergvav
550 User domain does not exist.
asdfgasdfgasdf
250 OK
sdfasdfadsfasdf
221 snubby4-wceast Snubby Mail Rejector Daemon v1.3 closing transmission channel
Connection closed by foreign host.
/ Mat
--- End Message ---
pgp00000.pgp
Description: PGP signature