XP is just a number | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I have about 12 web sites hosted on my server. 4 of them are pretty
hefty web applications with multple users. There are a few community
sites with mailing lists. YOU know, how it is. Well, because many of
these applications have the capability of sending emails, bounce
messages have become a real issue.
Most mail servers don't send a bounced message back to whoever is in the 'reply-to' field (for good reason!). All of those messages get bounced back to the server itself. But it is useless to sift through the 6000 or so double-bounces and spam bounces that come back to the server for those 2 or 3 'real' bounce messages that happen per week. I was just dropping them to /dev/null and explaining to my frustrated customers that there was nothing I could do about it. I stumbled across this post Detecting bounced mails and thought to myself, "Hey, I already have some experience with POP3 handling (Oakmailer) and that Mail::DeliveryStatus::BounceParser module looks like just the thing I need to make my customers happy campers." So, without further ado, this is what I came up with:
I went through each of my sites and created a bunch of messages that I
knew would bounce (phyllis_diller_is_my_hero@xxxxx.xxx) and sent them
to a wide variety of domains. This gave me a corpus to run the script
against, any messages that weren't detected meant I needed to do some
rewriting.
In the end, I spent about an hour and a half writing a script that saves me about 10 times that amount of time per month in handling complaints and trying to track down, "Why didn't my candidate get that email?" questions. This script processes roughly 1000 messages in 30 seconds on a 1.8 Ghz machine. I was thinking it might be useful to others in a similar situation. In reply to Dealing with Bounced email in multi host server by oakbox
|
|