Discuss 451: read error in the Mail Server Help forum on Dev Shed. 451: read error Mail Server Help forum discussing tips, tricks, techniques and Spam containment solutions. Topics include mail servers such as Sendmail and Qmail, webmail interfaces such as Squirrelmail and Horde and spam solutions such as SpamAssassin and Bayesian
The ASP Free website provides in-depth information on the latest developer tools available from Microsoft. Our cadre of writers, highly experienced industry experts, reveals the best ways to use established technologies as well as new and emerging technologies. Our coverage of Microsoft's development and administration technologies is among the most respected in the IT industry today.
ASP Free and Iron Speed Designer are giving away $5,500+ in FREE licenses. Iron Speed's RAD CASE toolset can save up to 80% of your coding time. One free license per week, one perpetual license per month! Download and Activate to enter!
Intel® Graphics Performance Analyzers is a powerful tool suite for analyzing and optimizing your games, media, and graphics-intensive applications. Used by some of the best developers on the planet, Intel GPA lets you maximize your app’s performance.
Posts: 67
Time spent in forums: 4 h 45 m 43 sec
Reputation Power: 10
451: read error
Hi all,
Kind of pulling my hair out with this one.
We have a customer who has recently transferred their domain to us. The server's running Qmail and requires SMTP auth.
The customer is on AOL broadband and are using MS Outlook 2003. They can receive mail but cannot send mail and get this error in a bounce message after sending mail:
Quote:
The original message was received at Mon, 16 Jan 2006 06:54:47 -0500 from smtp-los03.proxy.aol.com [195.93.24.41]
----- The following addresses had permanent fatal errors ----- <support@DOMAIN>
----- Transcript of session follows -----
451 4.4.1 reply: read error from mail.DOMAIN.
<support@DOMAIN>... Deferred: Connection timed out with mxbackup.DOMAIN.
Message could not be delivered for 2 hours Message will be deleted from queue
I've replaced the actual domain in the example above with DOMAIN for privacy.
The line "Deferred: Connection timed out" is fine as we have established the secondary MX is extinct, but the primary mail server is fine and I can send/receive messages from the same account without errors but the customer still can't.
Not sure if AOL don't allow their customers to use external SMTP servers or if they replace requests to use external servers with their own servers. The customer says he has "mail.DOMAIN" set as his outgoing mail server with outgoing authentication enabled, yet the error message indicates an AOL server...
Does anyone have any ideas? Short of going to the customer's office I am at a loss as to what to do and they are getting more and more aggravated as it was working before they transferred...
Posts: 67
Time spent in forums: 4 h 45 m 43 sec
Reputation Power: 10
Thanks for your suggestion.
Finally managed to work this one out - after lots of searching I found out that AOL use an SMTP proxy for any outgoing connections on port 25. So if he's got mail.domain.com set as his outgoing server in Outlook, AOL still intervene and replace it with their unreliable SMTP proxy.
I set up IPtables to forward connections on port 2525 to port 25, and the client now has his SMTP server set to mail.domain.com on port 2525 and it works like a charm.
A long way for a shortcut - but not impressed with AOL's thwarted approach to SMTP.
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
451: read error
Linear Mode
