As a follow up to this.... Is it possible that the Verizon mail server is not relaying these because of an empty envelope header?
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of David Vrona > Sent: Tuesday, December 30, 2003 3:24 PM > To: [EMAIL PROTECTED] > Subject: Anybody having problems with Verizon mail relay? > > > Hi All, > > I have a problem that developed on December 23rd. > > I have a Linux server running qmail/tmda and I'm connected > via Verizon DSL. > > I route all outbound mail through Verizon's mail servers > (outgoing.verizon.net). > > On the 23rd, my TMDA confirmation requests started bouncing > with the following message from the Verizon mail server: > > <[EMAIL PROTECTED]>: > 206.46.170.8 does not like recipient. > Remote host said: 550 relaying mail to XXXX.com is not > allowed Giving up on 206.46.170.8. > > PLEASE NOTE: [EMAIL PROTECTED] is a valid e-mail address and I > can send e-mail > directly to [EMAIL PROTECTED] without any trouble. Also, > 206.46.170.8 > is Verizon's mail server (outgoing.verizon.net). > > > Is there something about the e-mail header in the TMDA > confirmation request that would cause a problem with a mail > relay? Verizon does require sender authentication and I am > doing that with the qmail remote-auth patch. > > Again, I can send e-mail to these addresses with no problem. > It is only the TMDA confirmation request messages that are > bouncing in this way. > > Thanks for any ideas on this. > > Dave > > > _____________________________________________ > tmda-users mailing list ([EMAIL PROTECTED]) > http://tmda.net/lists/listinfo/tmda-users > _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
