[TOOLS-DEVELOPMENT] Fwd: DMARC for IETF lists

[Russ Housley <[e-mail]>]

Thoughts?

Begin forwarded message:

> From: Michael Richardson <[e-mail]>
> Date: February 3, 2015 10:57:49 AM EST
> To: [e-mail]
> Subject: DMARC for IETF lists
> 
> 
> Just after the DMARC occured, I asked what the IETF as an *organization* was
> going to do.  The DMARC situation has significantly affected the ability of
> the NOMCOM to communicate, forcing us to introduce mailman into what
> previously was a much lighter weight (which you should read: fewer opportunities
> for accidental confidentiality disclosures) /etc/aliases reflector.
> 
> In the late summer/fall, I was told that the the DMARC WG suggest something,
> and I should wait.  Are we approaching a point where we might be ready for
> running code?  It seems that we need this across the board.
> 
> {BTW: I don't have a problem with rejecting all email to lists with p=reject.}
> 
> 
> 
> From: Daniel Kahn Gillmor <[e-mail]>
> Date: February 3, 2015 10:07:29 AM EST
> To: "Eggert\, Lars" <[e-mail]>, "tools-discuss\@ietf.org" <[e-mail]>
> Cc: David Leon Gil <[e-mail]>
> Subject: Re: [Tools-discuss] DMARC
> 
> 
> On Tue 2015-02-03 06:04:28 -0500, Eggert, Lars wrote:
>> Begin forwarded message:
>>> PS. Sending via Gmail because the CFRG mailing list software attempts
>>> to forge @yahoo-inc.com <http://yahoo-inc.com/> FROM addresses. And
>>> Yahoo sets a DMARC p=reject. Could a list admin please configure the
>>> IRTF listserv to not blatantly violate the IETF DMARC standard?
>> 
>> Forwarding from CFRG. IIRC there is nothing that can be done, but forwarded just in case.
> 
> http://yahoomail.tumblr.com/post/82426900353/yahoo-dmarc-policy-change-what-should-senders
> 
> suggests:
> 
>>> If you are a mailing list owner, what should you do?
>>> 
>>> Mailing lists are a special case of sending mail on behalf of
>>> individuals. The most common option is to use the mailing list’s
>>> address instead of the sender’s on the From: line. This will change
>>> the reply behavior. Some mailing lists also choose to act as pure
>>> forwarders and resend the mail without breaking DKIM signatures. As
>>> of this publication, no common mailing list packages provide
>>> straightforward configuration options that produce DMARC
>>> compatibility, although Mailman has relevant features starting in
>>> 2.1.16. If you are a developer of mailing list software and would
>>> like help adding features to allow participants from domains with
>>> DMARC p=reject, please contact us at [e-mail].
> 
> mailman's "relevant features" don't appear to provide many good
> alternatives, even if we're running a newer version:
> 
> http://wiki.list.org/DOC/What%20can%20I%20do%20about%20members%20being%20unsubscribed%20by%20bounces%20of%20Yahoo%20user%27s%20posts%20for%20DMARC%20policy%20reasons%3F
> 
> But in 2.1.18, there is a dmarc_moderaction_action configuration value:
> 
>  http://wiki.list.org/DEV/DMARC
> 
> If we're running that version or later, i recommend setting
> dmarc_moderaction_action to "Munge From".
> 
>         --dkg
> 
> -- 
> Tools-discuss mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
> Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
> send email to [e-mail]
> 
>