Eric Jahn wrote:
> Thanks for the advice, everyone. I've decided to go the route of using
> my ISP's mail server. So I changed my configuration file's line to
> read: define(`SMART_HOST',`outgoing.verizon.net')
> and now I get the following feedback from verizon (see below). I've
> played around with the config file, since, but I can't seem to make it
> work. Thanks for helping me with this. I know this isn't the most
> exciting stuff to discuss. -eric
>
>
> The original message was received at Wed, 19 Feb 2003 12:06:32 -0500
> from localhost.localdomain [127.0.0.1]
>
> ----- The following addresses had permanent fatal errors -----
> <eric@ejahn.net>
> (reason: 550 relaying mail to ejahn.net is not allowed)
>
> ----- Transcript of session follows -----
> ... while talking to outgoing.verizon.net.:
>
>>>>DATA
>>>
> <<< 550 relaying mail to ejahn.net is not allowed
> 550 5.1.1 <eric@ejahn.net>... User unknown
> <<< 503 No recipients specified
>
>
> Reporting-MTA: dns; tamqfl1-ar10-4-47-104-178.tamqfl1.dsl-verizon.net
> Received-From-MTA: DNS; localhost.localdomain
> Arrival-Date: Wed, 19 Feb 2003 12:06:32 -0500
>
> Final-Recipient: RFC822; eric@ejahn.net
> Action: failed
> Status: 5.1.1
> Remote-MTA: DNS; outgoing.verizon.net
> Diagnostic-Code: SMTP; 550 relaying mail to ejahn.net is not allowed
> Last-Attempt-Date: Wed, 19 Feb 2003 12:06:32 -0500
> _________________________________________________________________________
>
>
I have Verizon also and they have a really hatd to get along with mail
system. It requires verification and does not play well with Netscape
without a hassle.
But on the up side, they have no problem with their users hosting
websites etc. as long as our bandwidth is not excessive. Have to work
around dynamic IP addresses though.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:32:50 EDT