[Mailman-Users] list automatically removing users
I do not have bounce processing enabled but yet one morning I have a list of about 15 users unsubscribed from the list. According to logs, they all look like this, [EMAIL PROTECTED] auto-unsubscribed [reason: BYBOUNCE] This obviously says it was removed because of some measure of bounces were exceeded. But once again, I do not have bounce processing enabled. Any explanation would be nice .. Thanks, LDB -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] list automatically removing users
Lawrence Bowie wrote: I do not have bounce processing enabled but yet one morning I have a list of about 15 users unsubscribed from the list. According to logs, they all look like this, [EMAIL PROTECTED] auto-unsubscribed [reason: BYBOUNCE] This obviously says it was removed because of some measure of bounces were exceeded. But once again, I do not have bounce processing enabled. Is bounce processing turned off for the list and not just DEFAULT_BOUNCE_PROCESSING = No in mm_cfg.py? Did these unsubscribes occur at the time that cron/disabled runs (default 9:00 a.m. server time)? Was bounce processing ever enabled for the list? If so, once a member is disabled for bouncing, cron/disabled will continue to send warning messages and eventually remove the member, even if bounce processing is turned off for the list. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] list automatically removing users
Mark Sapiro wrote: Lawrence Bowie wrote: I do not have bounce processing enabled but yet one morning I have a list of about 15 users unsubscribed from the list. According to logs, they all look like this, [EMAIL PROTECTED] auto-unsubscribed [reason: BYBOUNCE] This obviously says it was removed because of some measure of bounces were exceeded. But once again, I do not have bounce processing enabled. Is bounce processing turned off for the list and not just DEFAULT_BOUNCE_PROCESSING = No in mm_cfg.py? Does not exists anywhere in my config. Did these unsubscribes occur at the time that cron/disabled runs (default 9:00 a.m. server time)? Yes, it did. Was bounce processing ever enabled for the list? If so, once a member is disabled for bouncing, cron/disabled will continue to send warning messages and eventually remove the member, even if bounce processing is turned off for the list. Bounce process was not enabled at all. -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] list automatically removing users
Lawrence Bowie wrote: Mark Sapiro wrote: Is bounce processing turned off for the list and not just DEFAULT_BOUNCE_PROCESSING = No in mm_cfg.py? Does not exists anywhere in my config. So new lists are created with bounce_processing on and you manually turn it off. Did these unsubscribes occur at the time that cron/disabled runs (default 9:00 a.m. server time)? Yes, it did. So presumably, it was cron/disabled that did the unsubscribes. If Mailman's bounce log (or logs if rotated) goes back a month ago, check for any occurrences of entries for the involved users. Also, try bin/list_members --nomail=bybounce listname and see if you currently have any members disabled by bounce. Was bounce processing ever enabled for the list? If so, once a member is disabled for bouncing, cron/disabled will continue to send warning messages and eventually remove the member, even if bounce processing is turned off for the list. Bounce process was not enabled at all. As I note above, when the list was first created, bounce_processing was on by default. Are you sure you turned it off immediately after creating the list? -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] list automatically removing users
Mark Sapiro wrote: Lawrence Bowie wrote: Mark Sapiro wrote: Is bounce processing turned off for the list and not just DEFAULT_BOUNCE_PROCESSING = No in mm_cfg.py? Does not exists anywhere in my config. So new lists are created with bounce_processing on and you manually turn it off. This is an old list. I am referring to and it explicitly turned off via the web interface. Did these unsubscribes occur at the time that cron/disabled runs (default 9:00 a.m. server time)? Yes, it did. So presumably, it was cron/disabled that did the unsubscribes. If Mailman's bounce log (or logs if rotated) goes back a month ago, check for any occurrences of entries for the involved users. Also, try bin/list_members --nomail=bybounce listname and see if you currently have any members disabled by bounce. There were not any users revealed after this command was executed. Was bounce processing ever enabled for the list? If so, once a member is disabled for bouncing, cron/disabled will continue to send warning messages and eventually remove the member, even if bounce processing is turned off for the list. Bounce process was not enabled at all. As I note above, when the list was first created, bounce_processing was on by default. Are you sure you turned it off immediately after creating the list? Cannot be sure all I know it turned off now and it was NOT recently turned off. -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
