Michelle Konzack wrote:
in short, if someone declares you as their MX (without your
authorization), you should not start listing clients that try to send
mail to such domains.
Are there ANY leagal reasons to declare someons MX as there MX?
You miss mouss' point.
If someone (maliciously or by mistake) declare your system as
their MX, innocent third party mail servers may through no fault
of their own connect to your system in order to send mail to
addresses for wich your system is not a MX.
If you allow the connecting system to get as far as RCPT TO: you
could check if someone has set the MX for the recipient
address(es) to point at your system before listing the client
(and that would also give the opportunity to contact whoever is
responsible for the bad MX record).
For a well known connection trap, this might well be a very
important precaution as spammers might otherwise try to poison
the list.
Regards
/Jonas
--
Jonas Eckerman, FSDB & Fruktträdet
http://whatever.frukt.org/
http://www.fsdb.org/
http://www.frukt.org/
