On 17 Nov 2009, at 17:28, W B Hacker wrote:
> Ed Singleton wrote:
>> I'm trying to work out how to add useful headers to the bounce
>> messages that Exim generates in order to assist automatic processing
>> of error messages. I've googled quite a bit, and read through the
>> Exim book, but can't find anything on it.
>>
>> Any information on how to add more information such as the error
>> message or error code to the headers, would be greatly appreciated.
>> Even if people can suggest terms to search for, that would be good.
>>
>> Thanks
>>
>> Ed
>>
>
> go ogle PVRS/BATV and/or search this list archives for BATV.
>
> (Bounce Address Tag Verification)
>
> Here is a decent explanation from an external-to-exim source;
>
> http://www.ironport.com/company/pp_eweek_07-27-2006.html
>
> There are many threads in archives here as to how-to, pros, cons,
> benefits,
> complications, etc.
Thanks for this. Sorry for my slow follow up; I have been away from
the internet for a while.
The BATV stuff seems to be about confirming that bounces are genuine.
I'm looking more for trying to find out why things bounced. EG Is it
a hard bounce or a soft bounce? Is the MTA that we were trying to
deliver to claiming that the account doesn't exist?
I understand that a lot of MTAs give false information, but I'm
willing to work with that. We send out a lot of marketing emails and
I want to automatically remove anyone who hard bounces. I'm not
entirely sure what to do with soft bounces, particularly as that
involves some negotiation with the marketing department.
I'm currently looking to only deal with the bounce messages that are
generated by the version of Exim under my control. Bounce messages
generated by other MTAs I'll deal with later.
AFAICT It will be easiest to parse the message body and try and
extract the information that way. I've googled quite a bit but can't
currently find anything that already tries to do this (I'm mainly
looking for Python related stuff as that's what I'm most comfortable
with). Lamson (
http://lamsonproject.org/) has some useful stuff that
parses the headers, but nothing that parses the bodies.
Anyway, I guess I should have been clearer in my initial email, but
I'm fumbling around in the dark quite a bit here.
Thanks
Ed
