Serge, >Anyway, if you want to be tracking bounces, you really should look into >VERP. James doesn't have an out-of-the-box ability to do this for you, >but you can write a mailet to track VERP bounces. >(http://cr.yp.to/proto/verp.txt)
Thanks for the info. We are trying to do something like that. All emails that we sent out through James have an unique ID and an associated status in a database. This ID is part of both the From: and Reply-to: fields. We have modified RemoteDelivery to set the status of an email to 'delivered' in our database if the email was succesfully delivered to the outside world. Any incoming messages on this domain are examined for the recipient. We have set different prefixes in the From: and Reply-To: headers to make a rude distinction between bounces and replies. If we detect a bounce or reply, the status of the associated email is updated in the database. My basic problem is that we assumed anything that is sent back to the From: address is a bounce. This assumption has been proven incorrect, at least by some of the out-of-office messages that I get back on my mail server. Right now I'm trying to work around this by writing a matcher that performs matches on the content of the mail, using a set of regular expressions. This could be quite expensive in terms of processing time, so all suggestions for a simple mechanism to identify out-of-office messages are welcome. -- Jeroen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
