Re: [Mailman-Users] many Subscription disabled messages after movinglist to new server
Andrew Watson wrote: I recently moved a list to a new host, but retained the domain name. After many travails, and help from this list, I got my list working. After about a week of function, I am suddenly getting many Subscription disabled messages (about 10% of the 4411 subscribers, so far, but still growing as I write). It is possible that these are legitimate, and these really are bad addresses, and that in the move of the list my bounce processing options changed to be more stringent. Current they are: bounce_processing=Yes bounce_score_threshold= 5.0 bounce_info_stale_after=7 bounce_you_are_disabled_warnings=5 bounce_you_are_disabled_warnings_interval=7 bounce_unrecognized_goes_to_list_owner=no bounce_notify_owner_on_disable=yes bounce_notify_owner_on_removal=yes But it seems likely that this is bogus, and good addresses are being disabled (especially if this grows to 100% of subscribers!) Has anyone experienced a similar problem? bounce_notify_owner_on_disable=yes so you should get a notice for each disable containing a copy of the triggering DSN. What does it say? Does it look legitimate? Also, what if anything do you see in Mailman's smtp-failure log? -- 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] many Subscription disabled messages after movinglist to new server
The bounce notices I get look legitimate. They typically include something like: Reason: Remote SMTP server has rejected address Diagnostic code: smtp;550 alb...@cvc.uab.es... User unknown Mailman's smtp-failure log contains many instances of lines like this (edited, vsad...@mysite.com is the list administrator) Jan 12 20:48:44 2010 (70977) Low level smtp error: Connection unexpectedly closed, msgid: mailman.1063.1263328366.70976.visionl...@mysite.com Jan 12 20:48:45 2010 (70977) delivery to vsad...@mysite.com failed with code -1: Connection unexpectedly closed There are also a few like this: Jan 12 20:02:54 2010 (70977) Low level smtp error: (48, 'Address already in use'), msgid: mailman.561.1263325634.70976.visionl...@mysite.com Jan 12 20:02:54 2010 (70977) delivery to visionlist-ow...@mysite.com failed with code -1: (48, 'Address already in use') These log messages commenced on Jan 12 (today). -Andrew On Jan 12, 2010, at 1:23 PM, Mark Sapiro wrote: Andrew Watson wrote: I recently moved a list to a new host, but retained the domain name. After many travails, and help from this list, I got my list working. After about a week of function, I am suddenly getting many Subscription disabled messages (about 10% of the 4411 subscribers, so far, but still growing as I write). It is possible that these are legitimate, and these really are bad addresses, and that in the move of the list my bounce processing options changed to be more stringent. Current they are: bounce_processing=Yes bounce_score_threshold= 5.0 bounce_info_stale_after=7 bounce_you_are_disabled_warnings=5 bounce_you_are_disabled_warnings_interval=7 bounce_unrecognized_goes_to_list_owner=no bounce_notify_owner_on_disable=yes bounce_notify_owner_on_removal=yes But it seems likely that this is bogus, and good addresses are being disabled (especially if this grows to 100% of subscribers!) Has anyone experienced a similar problem? bounce_notify_owner_on_disable=yes so you should get a notice for each disable containing a copy of the triggering DSN. What does it say? Does it look legitimate? Also, what if anything do you see in Mailman's smtp-failure log? -- 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] many Subscription disabled messages after movinglist to new server
PS: I independently tested one of the offending addresses, and it bounced. So perhaps they really are bad. I looked in the bounce log on the old server, and this same address bounced many times, but bounce info got reset often. The new bounce log has many messages, largely about resetting stale bounce info, and then about bounces. Consistent with bounce processing for a list starting out with many bad addresses. Are the configuration data stored in a readable file? I could go back to the old server and find out what bounce options I used there. -Andrew On Jan 12, 2010, at 1:23 PM, Mark Sapiro wrote: Andrew Watson wrote: I recently moved a list to a new host, but retained the domain name. After many travails, and help from this list, I got my list working. After about a week of function, I am suddenly getting many Subscription disabled messages (about 10% of the 4411 subscribers, so far, but still growing as I write). It is possible that these are legitimate, and these really are bad addresses, and that in the move of the list my bounce processing options changed to be more stringent. Current they are: bounce_processing=Yes bounce_score_threshold= 5.0 bounce_info_stale_after=7 bounce_you_are_disabled_warnings=5 bounce_you_are_disabled_warnings_interval=7 bounce_unrecognized_goes_to_list_owner=no bounce_notify_owner_on_disable=yes bounce_notify_owner_on_removal=yes But it seems likely that this is bogus, and good addresses are being disabled (especially if this grows to 100% of subscribers!) Has anyone experienced a similar problem? bounce_notify_owner_on_disable=yes so you should get a notice for each disable containing a copy of the triggering DSN. What does it say? Does it look legitimate? Also, what if anything do you see in Mailman's smtp-failure log? -- 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] many Subscription disabled messages after movinglist to new server
On 1/12/2010 3:38 PM, Andrew Watson wrote: The bounce notices I get look legitimate. They typically include something like: Reason: Remote SMTP server has rejected address Diagnostic code: smtp;550 alb...@cvc.uab.es mailto:alb...@cvc.uab.es... User unknown In that case, they are probably real, legitimate bounces of bad addresses. The hard failures have probably all been disabled by now. Mailman's smtp-failure log contains many instances of lines like this (edited, vsad...@mysite.com mailto:vsad...@mysite.com is the list administrator) Jan 12 20:48:44 2010 (70977) Low level smtp error: Connection unexpectedly closed, msgid: mailman.1063.1263328366.70976.visionl...@mysite.com http://mysite.com Jan 12 20:48:45 2010 (70977) delivery to vsad...@mysite.com http://mysite.com failed with code -1: Connection unexpectedly closed There are also a few like this: Jan 12 20:02:54 2010 (70977) Low level smtp error: (48, 'Address already in use'), msgid: mailman.561.1263325634.70976.visionl...@mysite.com http://mysite.com Jan 12 20:02:54 2010 (70977) delivery to visionlist-ow...@mysite.com http://mysite.com failed with code -1: (48, 'Address already in use') These log messages commenced on Jan 12 (today). If they only started today, I don't know what the issue might be. There is a bug in the Python email library that can cause problems if you have a lot of bad addresses. See http://bugs.python.org/issue5713. But that shouldn't be the issue here. I don't have a clue what the 'Address already in use' message means. Check your MTA's logs. Also see the FAQ at http://wiki.list.org/x/-IA9. -- 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] many Subscription disabled messages after movinglist to new server
On 1/12/2010 4:07 PM, Andrew Watson wrote: Are the configuration data stored in a readable file? I could go back to the old server and find out what bounce options I used there. If you still have the installation on the old server except for web access, you can do bin/config_list -o - LISTNAME There are a couple of possibilities. If the old server was Mailman 2.1.5, that release had bounce probes enabled by default. Thus, when an address bounced, it wasn't disabled immediately, but a VERPed prob was sent and the address wasn't disabled until the probe bounced. It the MTA wasn't handling the VERPed return address properly, no-one would ever get disabled. It's also possible that bounce_info_stale_after was too short. -- 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] many Subscription disabled messages after movinglist to new server
The old server had essentially the same bounce options as the new. It was mailman 2.1.5, and I see many probe messages in the bounce log. Maybe you are right about the VERPed probe. On Jan 12, 2010, at 4:19 PM, Mark Sapiro wrote: On 1/12/2010 4:07 PM, Andrew Watson wrote: Are the configuration data stored in a readable file? I could go back to the old server and find out what bounce options I used there. If you still have the installation on the old server except for web access, you can do bin/config_list -o - LISTNAME There are a couple of possibilities. If the old server was Mailman 2.1.5, that release had bounce probes enabled by default. Thus, when an address bounced, it wasn't disabled immediately, but a VERPed prob was sent and the address wasn't disabled until the probe bounced. It the MTA wasn't handling the VERPed return address properly, no-one would ever get disabled. It's also possible that bounce_info_stale_after was too short. -- 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] many Subscription disabled messages after movinglist to new server
Andrew Watson The old server had essentially the same bounce options as the new. It was mailman 2.1.5, and I see many probe messages in the bounce log. Maybe you are right about the VERPed probe. If there weren't any disabling due to probe bounce received messages in the log, only sending LISTNAME list probe to messages, then the bounced probes weren't being properly returned to the list-bounces address, and members were never getting delivery disabled and never getting removed. Their scores just got incremented to threshold and were then reset when the probe was sent to start the process all over again. -- 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
