-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stephen Ronan wanted us to know:
>> ----- Transcript of session follows -----
>>553 5.3.5 abc.org.org. config error: mail loops back to me (MX problem?)
>>554 5.3.5 Local configuration error
Best way to describe this is a sample.
Let's say my mail server is named mail.mrball.net. By default, the mail
server will accept mail for username@mail.mrball.net. But if you
notice, I send all my mail to and from username@mrball.net. If you look
at my dns records, you'll see that the MX for the domain mrball.net
points to mail.mrball.net.
If you put all that together, you see that *@mrball.net will be
delivered to the machine named mail.mrball.net. That machine has to
know that it needs to receive emails destined for *@mail.mrball.net
(default) _AND_ *@mrball.net.
The error that you're seeing is what happens when someone's mail server
is listed in dns as being authoritative for a domain, but the mail
server says "I'm not configured to accept mail for that domain."
At one time RedHat had a DNS setting that said "If DNS says that I'm the
MX for a domain, then relay the email." The only problem with that is
that spammers quickly figured out they could abuse that.
- --
Blue skies... Todd Public key: http://www.mrball.net/todd.asc
The question is for how long that network would be around before it falls
due to the same problem (dclue/dt < 0 on the part of those who run it)
--Alex on NANOG
Linux kernel 2.4.19-16mdk 4 users, load average: 0.35, 0.73, 0.47
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+VaBwIBT1264ScBURArTxAKDbyeShIYxSrfoIYCVxL7sv//JlUgCfZiJ9
XiX0GqtMhFUsH6KBKaDLmhU=
=dLIQ
-----END PGP SIGNATURE-----
References:
|
|
