[Mailman-Users] subscribers being unsubscribed at wrong time based on bounce settings.

[Mark Sapiro]

On 11/30/2016 04:22 PM, Christopher Adams wrote:
> 
> I have done some fairly extensive examination of logs and list settings for
> one of the lists hosted here, and I can't come up with a sensible
> explanation to tell a customer.


What is in the logs. In particular, the entire 'bounce' log from 11/1
thru 11/24.


> The list is set to not send messages when a person unsubscribes.


Do you mean admin_notify_mchanges is No, bounce_notify_owner_on_removal
is No or something else. When cron/disabled removes a member, it always
tries to notify the member. There's no setting for that.
	

> The bounce settings are set so that 2 warning messages are sent after the
> address is disabled and those messages should be 7 days apart.
> 
> A message was sent to the list on 11/1. I see in the logs that a
> substantial number of addresses reached the bounce limit and were disabled.
> So, based on the bounce settings, many of these should have been
> unsubscribed 14 days later. They were not.
> 
> However, on 11/24, there was a mass unsubscribe of addresses that had been
> disabled. Additionally, many (including some that turned out to have valid
> addresses) received unsubscribe notices.


Was cron/disabled running between 11/15 and 11/24?

Were changes made to the list's bounce settings after 11/1. In
particular, the number of notices (bounce_you_are_disabled_warnings) is
set in the user's bounce info when deliverry is first disabled and
subsequent changes to the list setting won't affect the number of
notices for that user.

	
> I tend to think that these are not related, but are two issues that I have
> not been able to explain.


Also what's in the subscribe log on 11/24. Where the 'unrelated'
unsubscribes all done at the time cron/disabled ran (default 09:00)?


-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan