Regular subscriber receiving both regular and digest delivery

Running Mailman 2.1.12 on CentOS 6.8. We have a regular-delivery subscriber who is somehow receiving both regular and digest delivery for the same list. She only wants regular delivery. Here’s what we’ve checked so far:
- Looked at Mailman’s web interface. Confirmed user is listed there as a non-digest, plain text subscriber
- Double-checked by running the # list_members –r <listname> command. Reran with the –d option. Output matched results above.
- Several people at her office are subscribers. Asked user if she receives mail on behalf of any current/former coworkers. She said no.
- In case user misunderstood what “digest” means, asked her to forward us a copy of a recent delivery. Sure enough, it’s the digest.
- Restarted Mailman via # sudo /etc/init.d/mailman restart
- Manually unsubscribed user via remove_members and re-added her for regular delivery
- Checked /var/log/mailman to see if anything useful there. Didn’t find anything relevant to the problem.
Going forward: It’s very possible I’ve overlooked something basic. Would be nice to see “under the hood” how Mailman is handling the user’s subscription. Am guessing there’s a way but am a fairly newbie sysadmin and am not familiar enough with Mailman to know.
Any suggestions on how to pin down and solve the problem? Thanks in advance for your time and advice.
Brian

On 12/08/2016 11:20 AM, Brian Austin wrote:
Running Mailman 2.1.12 on CentOS 6.8. We have a regular-delivery subscriber who is somehow receiving both regular and digest delivery for the same list. She only wants regular delivery. Here’s what we’ve checked so far: ... It’s very possible I’ve overlooked something basic. Would be nice to see “under the hood” how Mailman is handling the user’s subscription. Am guessing there’s a way but am a fairly newbie sysadmin and am not familiar enough with Mailman to know.
Any suggestions on how to pin down and solve the problem? Thanks in advance for your time and advice.
The digest is being sent to a different list member. If you look at the headers of the digest she receives, in particular, the chain of Received: headers, you may be able to figure out what address the digest is sent to. Or, if VERP is enabled, the headers like Return-Path:, Sender: and Errors-To: will have the address encoded as listname-bounces+user=her.domain@list.domain where her address is user@her.domain.
Alternatively, you can run
bin/list_members -d -f -n enabled <list name>
to get a list of the members receiving digests. You may be able to shorten the list with '-d mime' or '-d plain' instead of '-d' to match the format (mime or plain) of the digests she receives. You may be able to figure out from this list, particularly if the display name matches, which one goes to her.
The bottom line is Mailman will never send both individual messages and digests to the same address except for one final digest when a user switches from digests to individual messages. Mailman is sending these to two different subscriber addresses and something in the delivery chain after Mailman is getting them both into her inbox.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Hello Mark Sapiro. On Fri, 9 Dec 2016 09:24:52 -0800, you wrote:
The digest is being sent to a different list member.
To help Brian solve his problem: Some mailboxes have more than one single valid address. For example, name@domain.com and name@subdomain.domain.com are two different addresses for Mailman, but may be the very same mailbox. Or name@domain1.com and name@domain2.com might also end up in the same mailbox
Chrisitan
--
Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland)
Hilfe fuer Strassenkinder in Ghana: http://www.chance-for-children.org
participants (3)
-
Brian Austin
-
Christian F Buser
-
Mark Sapiro