The post from bmcgrathPIX seems to be the resolution to this message that we were getting when we tried to email anyone at earthlink.net:
There was a SMTP communication problem with the
recipient's email server. Please contact your system administrator.
<our_server.com #5.5.0 smtp;550-EarthLink does not recognize your computer (xxx.xxx.xxx.xxx) as connecting from an EarthLink connection. If this is in error, please contact technical support.>
Earthlink Tech support responded with the following canned message:
Hello,
The information below is of a technical nature and you may wish to forward
this to your mail server administrator in the event that you do not fulfill
that role yourself.
The following error message:
550-EarthLink does not recognize your computer ([IP]) as connecting
from an EarthLink connection. If this is in error, please contact
technical support. or 5.5.0 Relaying Denied
..is due to an improper MTA configuration with the host that is
responsible for delivering outbound mail on your network. In a nutshell,
the mail server which attempted to deliver mail to the earthlink.net e-mail
address was initially unable to successfully deliver the mail to the
earthlink.net MX (more than likely due to high load on our end, no
Earthlink MX host was available to accept the transaction at the moment of
the delivery attempt), and so the Earthlink A record was attempted by
the sending mail server. The earthlink.net A record, however, forwards
port 25 connections to our outbound SMTP servers. Unless the mail server
attempting the transaction maintains IP connectivity through the Earthlink
network, delivery attempts through the A record will consequently fail
and the above quoted error message will be returned.
The behavior exhibited by the sending mail server, in this case, is not
standard. According to RFC 2821, "Address Resolution and Mail Handling":
"If one or more MX RRs are found for a given
name, SMTP systems MUST NOT utilize any A RRs associated with that
name unless they are located using the MX RRs; the "implicit MX" rule
above applies only if there are no MX records present. If MX records
are present, but none of them are usable, this situation MUST be
reported as an error."
Currently, the earthlink.net MX records are as follows:
mx4.earthlink.net
mx5.earthlink.net
mx6.earthlink.net
mx7.earthlink.net
mx8.earthlink.net
mx9.earthlink.net
mxa.earthlink.net
mxb.earthlink.net
mxc.earthlink.net
mx1.earthlink.net
mx2.earthlink.net
mx3.earthlink.net
You may wish to verify that you are able to successfully resolve this
record through your name servers, and that you can successfully route
to these hosts.
It has been reported that some Windows-based mail servers behind
firewalls which do not allow transfer of UDP packets larger than 512
bytes may not be able to return the MX record for earthlink.net. For
more information, please see:
However, the byte size of our MX record is under the 512 byte limit and
is within an RFC compliant range. If your firewall restricts UDP packet
transfers though, you may want to verify that it will allow transfer of
a MX record within the size limitations specified by RFC1035:
Assuming that the earthlink.net MX is resolvable, if the sending mail
server cannot immediately establish a connection to deliver the intended
e-mail, the MTA should attempt to retry a connection to the Earthlink
MX, rather than defaulting to the earthlink.net A record.
Anyway, just wanted to thank bmcgrathPIX for his reply. It seems like my mail is getting out to Earthlink now.