So a human _should_ be periodically reviewing the bounces to make sure there isn't a problem anywhere.
I totally agree. What I meant with not wanting to see the bounces is I don't want to see them in MY inbox. As list owner, there is enough mail coming in there that needs immediate attention. I would like to re-route bounces to another address so that I may automatically move them to another folder using mail message rules. Andreas
At 11:40 AM -0500 11/7/01, Andreas Huttenrauch is rumored to have typed:
I would like to re-route bounces to another address so that I may automatically move them to another folder using mail message rules.
Like I said, I'd think the simplest way to do it would be using the .procmailrc of the receiving user to do pretty much whatever you wanted; so long as you periodically checked the folder, you could easily transfer anything containing an X-Diagnostic: header field to that folder, or something like: * ^X-Diagnostic: Mail to.*bounced.*time ...to only move bounce messages. (See, I'm lazy...I could see defining a new variable like bounce_recipient, and then reworking rc.request and .bin/procbounce to honor it, but given a choice between that and writing one recipe in a .procmailrc file, I'll take the easy way out every time.) Charlie
participants (2)
-
Andreas Huttenrauch
-
Charlie Summers