Robert Schetterer wrote:
Eh?? Mail _from_ a large multinational company arrives via a dyn ip?
no the orginal mail is comming from there ( bigcompany) and wishes a
notify being delivered after recieve,
the bigcompany IP address is the one you put in the
smtpd_discard_ehlo_keyword_address_maps table.
But as Ralf suggested, maybe it's a header triggering the DSN.
I don't know what Outlook uses, maybe a header_checks
something like:
# header_checks
# don't allow delivery notice requests
/^return-receipt/ IGNORE
/^Return-view-to:/ IGNORE
/^notice..*deliver..*to:/ IGNORE
/^Notice-Requested-Upon-Delivery-To: / IGNORE
/^Disposition-Notification-To:/ 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.
Nah, it sucks. And it won't work anyway. Forget I posted it.
maybe the best solution is to just throw the mail away...
# transport
<>@bigcompany.example.com discard:
nice idea *g
And this won't ever work. Don't know what I was thinking...
Dear google: please delete this crap from your archives.
The solution is to prevent the DSN from being generated in the
first place.
--
Noel Jones
