On 12/01/2016 09:13 AM, Christopher Adams wrote: > I tracked one of the disabled addresses that was unsubscribed. It is the > same for all that were unsubscribed. > > bounce.log-20161101:Oct 31 16:16:36 2016 (32252) oebbmembers: > recipi...@wherever.com <mailto:recipi...@wherever.com> current bounce > score: 2.0 > bounce.log-20161107:Nov 06 15:21:38 2016 (24109) oebbmembers: > recipi...@wherever.com <mailto:recipi...@wherever.com> current bounce > score: 3.0 > bounce.log-20161107:Nov 06 15:21:38 2016 (24109) oebbmembers: > recipi...@wherever.com <mailto:recipi...@wherever.com> disabling due to > bounce score 3.0 >= 3.0 > bounce.log-20161112:Nov 11 15:56:41 2016 (11544) oebbmembers: > recipi...@wherever.com <mailto:recipi...@wherever.com> residual bounce > received > bounce.log-20161117:Nov 17 09:04:35 2016 (58403) Notifying disabled > member recipi...@wherever.com <mailto:recipi...@wherever.com> for list: > oebbmembers > bounce.log-20161123:Nov 22 10:11:14 2016 (60465) oebbmembers: > recipi...@wherever.com <mailto:recipi...@wherever.com> residual bounce > received > bounce.log-20161125:Nov 24 09:16:14 2016 (35874) Notifying disabled > member recipi...@wherever.com <mailto:recipi...@wherever.com> for list: > oebbmembers > bounce.log-20161125:Nov 24 09:16:14 2016 (35874) oebbmembers: > recipi...@wherever.com <mailto:recipi...@wherever.com> deleted after > exhausting notices > > > > The cron/disabled ran every day during November at 9.
So, if those are the only bounce log entries for recipi...@wherever.com, that member had delivery disabled by bounce on Nov 6 and was sent the first notice at that time. Then, I'm guessing, the delivery attempts on that message "timed out" after 5 days and the notice bounced on Nov 11. The second notice was sent on Nov 17 and that timed out and bounced on Nov 22. Then on Nov 24, the member was deleted after exhausting notices. This can be explained if the list's bounce_you_are_disabled_warnings_interval was initially > 10 days and was subsequently reduced to 7 days. This would account for the second notice not being sent until Nov 17. The only other possibility I can think of is cron/disabled encountered some error. One issue around this is that those errors are never seen because they are mailed by cron to the 'mailman' user, but the 'mailman' user address is the site list and if the site list is configured to discard or reject non-member posts, the error report is lost. There are two things here: 1) For various reasons, the site list should accept or at least hold (not reject or discard) non-member posts. 2) Mailman's crontab should include a 'MAILTO=' to mail any output to the site admin. -- 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 https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
