We ended up using a transport filter and a bit of python code to do our rewriting. It checks all the headers that just about any email software might be using..
# Disposition-Notification-To: # Receipt-Requested-To: # Confirm-Reading-To: # MDRcpt-To: # MDSend-Notifications-To: # Smtp-Rcpt-To: # Return-Receipt-To: # Read-Receipt-To: # X-Confirm-Reading-To: # X-Acknowledge-To: # Delivery-Receipt-To: # X-PMrqc # Errors-To -Andy- -----Original Message----- From: Clive McDowell [mailto:[EMAIL PROTECTED] Sent: 25 October 2007 08:17 To: [email protected] Subject: Re: [exim] The dreaded disposition-notification-to header Tony Finch wrote: > So it doesn't. I think you'll have to delete and re-insert the header > then. I feared so. > The real way to solve the problem is to ensure that the Exchange > system uses globally valid email addresses, so that you don't have to > do any rewriting. Of course but that isn't possible with our current setup. My preferred solution was to strip them out but PHBs seem to like read receipts for some reason. Thanks anyway, Clive McDowell Information Services The Queen's University of Belfast -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
