Re: [Mailman-Users] bounce notifications
Andrew wrote: When mailman returns notification of a bounce to an administrator, the content always comes within an attachment. Is there any way of telling it to send the details within the body of the e-mail, because when you have lots there's a great deal of extra clicking involved, and it's more difficult to automatically process the information with code (e.g. within Outlook) The only ways to change that would be modifying the source code or using an MUA that displays attached messages inline. The bounce notice is sent as an attached message in order to preserve its headers and MIME structure exactly as Mailman received it. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Bounce notifications.
Thank you very much Mark. I'm sure that we'll be able to enact one of those options. Sincerely, Tim On Fri, May 29, 2009 at 9:18 AM, Mark Sapiro m...@msapiro.net wrote: Timothy Park wrote: I'm sorry in advance if I'm not understanding Mailman's bounce notification process, but here's my issue: I've noticed that when a message bounces, there are no notications to list owners. I only stumbled upon this error when we created a mailing list for a small group of developers, and one wasn't receiving any email due to a problem with his mail server. I had no idea until he told me that he wasn't receiving our messages about a week into the project. When I checked Mailman's bounce log (/var/log/mailmain/bounce), the erorr was there, and his bounce score was 1.0. Is this the normal action of Mailman's bounce system? That is, to hold off notifying the list owner of a bounce until the bounce score passes the defined threshold? If so, is there any way I can force bounce errors to be delivered? I tried disabling bounce processing, but that seems to just discard bounced messages without a notification. Some of our mailing lists are mission critical where one person not receiving a message could be a big deal, so if mailman could let us know when there is a delivery failure, that would be wonderful (we wouldn't mind the extra email). Thanks for your help! Your observations are correct and that's the way bounce processing is designed to work. If you want to be notified of every bounce, you have a few choices: 1) Be sure bounce_processing is Yes and bounce_notify_owner_on_disable is Yes, and set bounce_score_threshold = 1.0. This will cause a notice to be sent to the list owner containing the bounce message on the first bounce. The downside is the member's delivery will also be disabled, and the owner will then need to re-enable it, unless the address is truly undeliverable. 2) Change the alias for LISTNAME-bounces to deliver to owner instead of bounces. This will direct all bounces to the owner, but requires delivery to Mailman to be via alias and to be truly effective requires aliases to not be automatically generated. 3) Create a cron to run a few times a day and go through the bounce log looking for entries like May 28 05:06:04 2009 (12757) LISTNAME: u...@example.com bounce score: with timestamp than the last run and mail a notice to LISTNAME-owner. 4) Modify the code to do what you want. -- Mark Sapiro m...@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Bounce notifications.
Timothy Park wrote: I'm sorry in advance if I'm not understanding Mailman's bounce notification process, but here's my issue: I've noticed that when a message bounces, there are no notications to list owners. I only stumbled upon this error when we created a mailing list for a small group of developers, and one wasn't receiving any email due to a problem with his mail server. I had no idea until he told me that he wasn't receiving our messages about a week into the project. When I checked Mailman's bounce log (/var/log/mailmain/bounce), the erorr was there, and his bounce score was 1.0. Is this the normal action of Mailman's bounce system? That is, to hold off notifying the list owner of a bounce until the bounce score passes the defined threshold? If so, is there any way I can force bounce errors to be delivered? I tried disabling bounce processing, but that seems to just discard bounced messages without a notification. Some of our mailing lists are mission critical where one person not receiving a message could be a big deal, so if mailman could let us know when there is a delivery failure, that would be wonderful (we wouldn't mind the extra email). Thanks for your help! Your observations are correct and that's the way bounce processing is designed to work. If you want to be notified of every bounce, you have a few choices: 1) Be sure bounce_processing is Yes and bounce_notify_owner_on_disable is Yes, and set bounce_score_threshold = 1.0. This will cause a notice to be sent to the list owner containing the bounce message on the first bounce. The downside is the member's delivery will also be disabled, and the owner will then need to re-enable it, unless the address is truly undeliverable. 2) Change the alias for LISTNAME-bounces to deliver to owner instead of bounces. This will direct all bounces to the owner, but requires delivery to Mailman to be via alias and to be truly effective requires aliases to not be automatically generated. 3) Create a cron to run a few times a day and go through the bounce log looking for entries like May 28 05:06:04 2009 (12757) LISTNAME: u...@example.com bounce score: with timestamp than the last run and mail a notice to LISTNAME-owner. 4) Modify the code to do what you want. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Bounce notifications.
Jerry Feldman wrote: We run about 30 different listservs on the BLU server using Mailman 2.1.4. We recently upgraded from an ancient release of mailman. Some of our listserv admins are complaining about Uncaught bounce notification messages. It appears that most of these result from delayed email notification to hotmail or msn subscribers. There is a recent thread on this beginning at http://mail.python.org/pipermail/mailman-users/2004-November/040837.html Personally, I just ignore them. While I have not tried this, if we disable Should Mailman send you, the list owner, any bounce messages that failed to be detected by the bounce processor?, would that eliminate those messages. But, by disabling this, would the list owners lose some other important notification. Yes, it would eliminate delivering those unrecognized delayed notifications to the list owner, but it would also eliminate delivering all other unrecognized bounces, some of which may be SPAM or even desired messages sent to the list-bounces address and some of which may be real bounces in a non-standard format which should be seen. If this is a concern, you can set VERP_DELIVERY_INTERVAL to some non-zero value in mm_cfg.py so every nth post is VERP'd and real bounces will eventually be detected. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/