New mailing list server deployed.

[gkeller]

Hello,

Lists.sonic.net has been moved to new hardware, and update to a newer version of the mailman software. In addition to improved performance, the new version of mailman has allowed us to enable dmarc_moderation_action. What this does is change the from address of the original sender of the message when a list email is sent to a domain that has a DMARC policy of reject, allowing the user to receive the message. This fixes a problem that was introduced as mail providers started enabling the stricter DMARC policy to cut back on spam sent to their users. Domains that this is known to be a problem for include yahoo.com and aol.com. If you experience any problems with this new setting, or any other list related issues, please let us know.

[cgarch]

Ya Hoo, so to speak. Thanks so much for getting this done. It has been a complete headache. Looking forward to testing this out.

[Mark Sapiro (MM dev)]

What this does is change the from address of the original sender of the message when a list email is sent to a domain that has a DMARC policy of reject, allowing the user to receive the message.

Actually what it does is change the From: address in outgoing posts when a list email is sent originally From: a domain that has a DMARC policy of reject, not "to a domain". You can't munge the From: header based on the DMARC policy of the recipient domain because many domains will honor a sender's DMARC p=reject even if their own DMARC policy is none.

[cgarch]

I'm having an issue with one of my lists not generating a digest on a daily basis since the Mailman software change. The threshold for triggering a digest is at 102K, which seems low enough, but the daily digest send is not happening. Other than changing the anonymous and munging settings, no other changes were made. Suggestions?

Craig

Edit: 1. anyone watching this thread?
2. quote from Mark Sapiro.
On 06/13/2014 02:05 PM, Craig Gaevert wrote:
Now however, in spite of what I am
fairly sure are the correct settings, since nothing else changed,
digests are not triggering on a daily basis. AFAICT, the setting
Digest_Send_Periodic is set to ‘Yes’ but nothing happens. As I don’t
have access to the logs, it is difficult for me to figure out what’s
going on. I do have a support ticket in with Sonic but thought
perhaps posting here might lead to a pointer as to what the issue
might be and I can refer same to them. Thanks much.


The most likely explanation is that Mailman's cron/senddigests is not
being run or it is encountering some problem.

Their upgrade shouldn't have affected this, but they need to see that
there is a crontab (either system or user) to run Mailman's cron jobs
and that they aren't throwing exceptions or errors.

One issue with cron errors is that often they are mailed by default to
the crontab owner which is usually 'mailman' which in turn is usually
the site list which doesn't accept the 'non-member post' or if it does,
no one sees it.

The site list should always accept non-member posts and the site mailman
admin should be a member of the site list and receive them.

--
Mark Sapiro <[email protected]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan

[cgarch]

Problem fixed - digests being delivered. Thank you Grant.

Craig

[isis]

Initially the original post said "the new dmarc_moderation_action has been set to “Munge From” for all lists on the server", but that part has apparently been deleted without explanation.

This is causing some confusion. I've been sending other list hosts to this forum for instructions on how to fix the problem on their end, mentioning to them the 'munge from' setting.

Is there some issue with that setting that people should know about? What should they be doing instead? Just updating to the newest version of Mailman did not fix the problem for others.

[cgarch]

It did not appear to be set at that on my lists. Here's the configuration I'm using that appears to be working.
Under Privacy/Sender Filters, set dmarc_moderation_action to "Munge from"
Under General Options, set from_is_list to "No"
Under General Options, set anonymous_list to "No"

What this does is that for everyone except the DMARC domains, the emails post as the original sender. For the DMARC domains, their posts are 'munged' to read as "John Doe via SRCC-C". If you set from_is_list to "Yes" then all posts to the list will be 'munged' - rather ugly but it works.

In all cases where you want the list to "reply to Sender" this now functions correctly and avoids many subscribers the embarassment of posting back to the list. Note too that Sonic has corrected a problem with digest delivery and that now works correctly.

This works for me except for one domain and thus affects only one subscriber. He can get another email account . . .

Craig

[isis]

Thank you for clarifying those steps.

[thomasb]

Hi,

I run a GNU mailman on a small (non-sonic.net) server. I recently upgraded to 2.1.18 in order to get around the DMARC problem. Messages to yahoo.com subscribers are now getting through but AOL.com is still rejecting messages. I set

dmarc_moderation_action = Munge From
dmarc_quarantine_moderation_action = Yes

anonymous_list = no
from_is_list = no

in the web interface.

Should I also add "REMOVE_DKIM_HEADERS = Yes" in mm_cfg.py?

(is sonic using REMOVE_DKIM_HEADERS ?)

Thanks,

Thomas

[cgarch]

You might want to check out the Mailman list at https://mail.python.org/mailman/listinfo/mailman-users. Lot of good help available there.

cg