On 16/02/2012 15:26, Scappatura Rocco wrote:
Scappatura Rocco:
I would like that sender domain names for which is not
configured any MX record are not relayed from my MTA. I have
tried to use the
That would be a mistake. There is no RFC REQUIREMENT that a domain
has an MX record.
I have no doubt about the correctness of what you stated above, but
whenever a customer of mine sends a message through my MTA,
specifying a sender with a domain that has not a valid sender (and,
in particular, a domain sender with no MX defined and the message for
some reason is not delivered), I receive a DSN for the customer that
remain in deferred queue, just because it is destined to a recipient
for which the domain has no MX defined. :-(
For that to happen, the sending domain must be missing not only MX
records but also A records. In which case,
'reject_unknown_sender_domain' will block it.
If you have reject_unknown_sender_domain already configured and that
isn't blocking the mail, then missing MX records are not the reason why
you are unable to deliver the DSN to your customer.
What do your logs say when your server tries to deliver the DSN?
Mark
--
Sent from my Babbage Difference Engine 2
http://mark.goodge.co.uk
