[alsa-devel] DMARC & gmail & cirrus.com

[Lars-Peter Clausen]

On 2/17/20 12:56 PM, Peter Ujfalusi wrote:
> Hi,
> 
> On 17/02/2020 13.35, Charles Keepax wrote:
>> On Mon, Feb 17, 2020 at 10:33:55AM +0100, Lars-Peter Clausen wrote:
>>> On 2/17/20 9:46 AM, Jaroslav Kysela wrote:
>>>>      I can enable the "Replace the From: header address" in the
>>>> mailman config to "Munge From" like in the above example, but it
>>>> will mean that From: will be altered (see the explanation).
>>>
>>> The way I understand the option to replace the From: header is that
>>> it will only happen for those that have a reject policy, for
>>> everybody else nothing changes. So if the mailinglist is supposed to
>>> stay useful for those with a reject policy the only option is to
>>> rewrite the from header for them.
>>>
>>
>> Rewriting seems like the best option really, I doubt there
>> is much chance of me managing to get the IS guys to change
>> cirrus.com's DMARC policy and I guess we might not be the only
>> people who cause trouble on this front.
> 
> ti.com also had issues caused by DMARC policy. We have extensively
> nagged our IT department over this and it got resolved?
> Probably. Not sure, but I have not been unsubscribed lately from lists
> and no complaints on people not receiving my mails... it could be that
> they do not indeed receive the mails which makes them happy ;)
Its not that you get unsubscribed, but everybody else who is rejecting 
your mails ;)

_dmarc.ti.com.		3600	IN	TXT 
"v=DMARC1;p=quarantine;sp=none;rua=mailto:dmarc-aggr at ti.com;ruf=mailto:dmarc-for at ti.com;fo=0"

The p=quarantine means that your messages forwarded by the ALSA 
mailinglist will probably go to spam for people using gmail.

Some other mailinglists btw don't have this problem, since they forward 
the signed content of the mail unmodified. But since alsa modifies the 
subject as well as adding the info footer the original signature is no 
longer valid.

- Lars