Robert Schetterer wrote:
You add the IP of the ORIGINATING server; where the original message
comes from that triggers the DSN. This should prevent the DSN from
being generated in the first place.
Hi Noel, cant do that its a dyn ip
Eh?? Mail _from_ a large multinational company arrives via a
dyn ip?
OK, here's how to strip DKIM on output. This will affect all
mail going to that domain, not just DSNs.
I have no confidence this will fix the problem, good luck.
# main.cf
# (or use your existing transport_maps table)
transport_maps = hash:/etc/postfix/transport
# master.cf
#(this is a copy of the smtp...smtp line)
no-dkim unix - - n - - smtp
-o smtp_header_checks=regexp:/etc/postfix/strip-dkim
# transport
bigcompany.example.com no-dkim:
# strip-dkim
# remove DKIM and DomainKeys signatures so that
# badly broken clients don't choke.
/^DKIM-Signature: / IGNORE
/^DomainKey-Signature: / IGNORE
Seems more likely they are choking on the null sender address.
You can use the setup described above with smtp_generic_maps
to replace the null sender with something else. This breaks
RFCs - DSNs MUST be sent with the null sender.
-o smtp_generic_maps=regexp:/etc/postfix/replace-dsn
# replace-dsn
/^<>$/ [EMAIL PROTECTED]
# transport
[EMAIL PROTECTED] discard:
This solution sucks, but might allow the mail to be delivered.
maybe the best solution is to just throw the mail away...
# transport
<>@bigcompany.example.com discard:
--
Noel Jones
