On 03/20/2016 08:44 AM, Rafael Salasnik wrote:

On one of my lists 18 subscribers were deleted yesterday at the same time with no apparent reason. All the messages were in the format of:

"xxxxx@xxxxx.xxx has been removed from xxxxxx."

I'm guessing the time was 09:00. In any case, this was almost certainly automatic removal by bounce processing after exhausting notices. Mailman's bounce log will have more info.

Note that if you enable all the notices in the lists' Bounce processing section, you won't be quite so surprised. In particular, if bounce_notify_owner_on_disable is Yes, you will get a notice including the actual triggering bounce message when the member's delivery is first disabled by bounce. With default settings, this is 3 weeks prior to the eventual removal.

All addresses are aol, yahoo or hotmail/live. However other users with those accounts weren't removed For this group I have two lists. Some (but not all) belong to both lists but their subscriptions to the other list was not removed.

It sounds like DMARC is the root issue. See <http://wiki.list.org/x/17891458>.

Any thoughts/suggestions?

Suggestions depend on your Mailman version (in the case of DMARC). See the above link.

Also, check the web admin membership list for members whose delivery is disabled with a 'B'. These will be removed eventually and maybe should be reenabled.

If you have shell access, Mailman's

bin/list_members --nomail=bybounce LISTNAME

will list the members with delivery disabled by bounce, and the script at <https://www.msapiro.net/scripts/reset_bounce.py> can help reenable their delivery.

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

On 03/20/2016 08:44 AM, Rafael Salasnik wrote:

On one of my lists 18 subscribers were deleted yesterday at the same time with no apparent reason. All the messages were in the format of:

"xxxxx@xxxxx.xxx has been removed from xxxxxx."

I'm guessing the time was 09:00. In any case, this was almost certainly automatic removal by bounce processing after exhausting notices. Mailman's bounce log will have more info.

Note that if you enable all the notices in the lists' Bounce processing section, you won't be quite so surprised. In particular, if bounce_notify_owner_on_disable is Yes, you will get a notice including the actual triggering bounce message when the member's delivery is first disabled by bounce. With default settings, this is 3 weeks prior to the eventual removal.

All addresses are aol, yahoo or hotmail/live. However other users with those accounts weren't removed For this group I have two lists. Some (but not all) belong to both lists but their subscriptions to the other list was not removed.

It sounds like DMARC is the root issue. See <http://wiki.list.org/x/17891458>.

Any thoughts/suggestions?

Suggestions depend on your Mailman version (in the case of DMARC). See the above link.

Also, check the web admin membership list for members whose delivery is disabled with a 'B'. These will be removed eventually and maybe should be reenabled.

If you have shell access, Mailman's

bin/list_members --nomail=bybounce LISTNAME

will list the members with delivery disabled by bounce, and the script at <https://www.msapiro.net/scripts/reset_bounce.py> can help reenable their delivery.

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