
Hi all,
I recently updated my server from Mac OS X 10.4 to 10.5, with the attendant upgrade of Mailman.
Following that, the server suddenly unsubscribed some 300 subscribers from various lists. Is that to be expected or should I resubscribe them?
Thanks,
Allan

Allan Hansen wrote:
I recently updated my server from Mac OS X 10.4 to 10.5, with the attendant upgrade of Mailman.
Following that, the server suddenly unsubscribed some 300 subscribers from various lists. Is that to be expected or should I resubscribe them?
It's not "expected", but in order to know whether to resubscribe them, you need to know why they were unsubscribed.
Here are some possibilities. Presumably the actual unsubscribes were of bouncing members by cron/disabled. Possibly cron/disabled was not being run before and the server/Mailman upgrade installed a new crontab for Mailman.
Prior to Mailman 2.1.10, if bounce_score_threshold for a list was reduced, members with stale bounce info with scores >= the new threshold would be disabled and/or unsubscribed. This wouldn't explain your situation unless you happened to reduce some bounce_score_threshold settings.

Closer examination has revealed that most if not all of these unsubscriptions are valid. The 'cron' explanation appears correct, because when I upgraded, I also found that the password reminders were suddenly being sent out, which they had not before. Looking at crontab, I found the cron job to do just that.
I wonder if this is something Apple bungled when they stopped using cron jobs for their own scheduled tasks. In any case, the jobs are now running again.
Thank you for the hint.
Allan
At 3:56 PM -0800 12/15/08, Mark Sapiro wrote:
Allan Hansen wrote:
I recently updated my server from Mac OS X 10.4 to 10.5, with the attendant upgrade of Mailman.
Following that, the server suddenly unsubscribed some 300 subscribers from various lists. Is that to be expected or should I resubscribe them?
It's not "expected", but in order to know whether to resubscribe them, you need to know why they were unsubscribed.
Here are some possibilities. Presumably the actual unsubscribes were of bouncing members by cron/disabled. Possibly cron/disabled was not being run before and the server/Mailman upgrade installed a new crontab for Mailman.
Prior to Mailman 2.1.10, if bounce_score_threshold for a list was reduced, members with stale bounce info with scores >= the new threshold would be disabled and/or unsubscribed. This wouldn't explain your situation unless you happened to reduce some bounce_score_threshold settings.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Allan Hansen
-
Mark Sapiro