Workaround for brain-dead BATV

[lst_hoe02]

Hello




Any comments?

Thanks

Andreas

we got problems with customers requesting MDN according to RFC-3798 with Disposition-Notification-To: header and using BATV on their gateways. On our side we honor read-request and sent MDNs with empty envelope sender to their Disposition-Notification-To: header which is unfortunately different form their BATV envelope sender and therefore dropped in many cases :-( As a workaround i had the idea to replace by Header check on our side the Disposition-Notification-To address by the return path but i'm not sure if this is doable or even a smart idea?

smime.p7s
Description: S/MIME Cryptographic Signature