From: Lars-Peter Clausen <lars@metafoo.de>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] DMARC & gmail & cirrus.com
Date: Mon, 17 Feb 2020 13:17:30 +0100 [thread overview]
Message-ID: <ce896073-df9e-7504-6c37-c611dd750936@metafoo.de> (raw)
In-Reply-To: <4fafa55a-acd0-8a64-2ebe-0ed38b306678@ti.com>
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@ti.com;ruf=mailto:dmarc-for@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
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2020-02-17 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 8:46 [alsa-devel] DMARC & gmail & cirrus.com Jaroslav Kysela
2020-02-17 9:07 ` Takashi Iwai
2020-02-17 9:33 ` Lars-Peter Clausen
2020-02-17 11:35 ` Charles Keepax
2020-02-17 11:56 ` Peter Ujfalusi
2020-02-17 12:17 ` Lars-Peter Clausen [this message]
2020-02-17 12:41 ` Jaroslav Kysela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ce896073-df9e-7504-6c37-c611dd750936@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=peter.ujfalusi@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.