detecting administrivia requests in "bounces"
For some reason, my users like to send emails to listname-bounces@listserver.com. I guess maybe because that is what is in the From: address on emails they recieve. Anyway, they will be emails with a single request in them like "help" or "subscribe" but they dome to me because the bounce filter couldn't filter them out. Is there anyway to have these checked for Administrivia?
On 5/17/07, James Dinkel jdinkel4@cox.net wrote:
For some reason, my users like to send emails to listname-bounces@listserver.com. I guess maybe because that is what is in the From: address on emails they recieve. Anyway, they will be emails with a single request in them like "help" or "subscribe" but they dome to me because the bounce filter couldn't filter them out. Is there anyway to have these checked for Administrivia?
No way without modifying the code, I think.
It looks like you'd have to modify maybe_forward in BounceRunner to send it along to CommandRunner instead of just forwarding it to the admin. Of course, if it's a genuinely unrecognized bounce, this would result in the sender getting a bounce BACK for the unknown command, which is bad.
--
- Patrick Bogen
On 5/17/07, James Dinkel wrote:
For some reason, my users like to send emails to listname-bounces@listserver.com. I guess maybe because that is what is in the From: address on emails they recieve. Anyway, they will be emails with a single request in them like "help" or "subscribe" but they dome to me because the bounce filter couldn't filter them out. Is there anyway to have these checked for Administrivia?
Check your list configuration. Those kinds of messages should already be filtered for Administrivia by default.
Check the main web admin page for your list, and scroll down to "administrivia". Make sure that the radio button is set to "Yes".
Beyond that, there's nothing that Mailman can currently do for you. If you like, you may be able to create some additional Python code to handle these kinds of requests, but you'd need to find the necessary source module and make your changes there.
If you go this route, please consider contributing your changes back to the project through the appropriate SourceForge "patch" page for Mailman.
-- Brad Knowles brad@shub-internet.org, Consultant & Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
participants (3)
-
Brad Knowles
-
James Dinkel
-
Patrick Bogen