Why can I get mail to some places, but instead always get the error “reply: read error from name.of.remote.host”?
This is usually caused by a bug in the remote host’s mail server, or Mail Transport Agent (MTA). The “EHLO” command of ESMTP causes the remote server to drop the SMTP connection. There are several MTAs that have this problem, but one of the most common server implementations can be identified by the “220 All set, fire away” greeting it gives when you telnet to its SMTP port. To work around this problem, you can configure sendmail to use a mailertable with an entry telling sendmail to use plain SMTP when talking to that host: name.of.remote.host smtp:name.of.remote.host Sites which must run a host with this broken SMTP implementation should do so by having a site running sendmail or some other reliable (and reasonably modern) SMTP MTA act as an MX server for the problem host. There is also a problem wherein some TCP/IP implementations are broken, and if any connection attempt to a remote end gets a “connection refused”, then *all* connections to that site will get closed.
Related Questions
- When I try to mail something, I get the following error message: "Cannot read frozen config file: not a typewriter". Whats wrong?
- Why can I get mail to some places, but instead always get the error "reply: read error from name.of.remote.host"?
- Why do I get an error message when trying to retrieve mail using Outlook Express?
