Bob German writes on 11/3/2003 2:54 PM:
My understanding is that they started breaking the RFC by refusing mail with null <> senders last week.
Based on past experience, I wasn't too surprised.
Doesn't look like they are doing this. suresh@frodo 01:31:15 [~]$ dnsmx verizon.net 0 relay.verizon.net suresh@frodo 01:31:23 [~]$ telnet relay.verizon.net 25 Trying 206.46.170.12... Connected to relay.verizon.net. Escape character is '^]'. 220 sc011.verizon.net MailPass SMTP server v1.0.6 - 103003062626JY ready Mon, 3 Nov 2003 14:01:28 -0600 ehlo frodo.hserus.net 250-sc011.verizon.net 250-8BITMIME 250 SIZE 20971520 mail from: <> 250 Sender <> OK rcpt to: <postmaster@verizon.net> 250 Recipient <postmaster@verizon.net> Ok rset 250 Ok resetting state quit 221 sc011.verizon.net closing connection Connection closed by foreign host. Another thing - verizon is fairly responsive and does have some clued people in there. I have forwarded this thread to a friend in Verizon's postmaster desk. srs -- srs (postmaster|suresh)@outblaze.com // gpg : EDEDEFB9 manager, outblaze.com security and antispam operations