All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Jaroslav Kysela <perex@perex.cz>,
	ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] DMARC & gmail & cirrus.com
Date: Mon, 17 Feb 2020 10:33:55 +0100	[thread overview]
Message-ID: <d1d0be54-5bdb-0405-320a-d7e542fdbcde@metafoo.de> (raw)
In-Reply-To: <77884bad-81fd-f876-3f72-1f96a39d6329@perex.cz>

On 2/17/20 9:46 AM, Jaroslav Kysela wrote:
> Hi all,
>
>     today, all gmail users were unsubscribed from the mailing list, 
> because we have users who sends e-mails from domains with the DMARC 
> policy reject (like cirrus.com). The mailman counts those bounces and 
> unsubscribe users who do not receive those e-mails. The nice 
> explanation is here:
>
> https://www.linuxchix.org/content/mailing-list-changes
>
>     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).
>
>     Another option is to disable the bounce check in mailman, but it 
> will cause that the "dead" subscribers are not detected anymore.
>
>     Any opinions on this?
>
>                     Jaroslav 

The way I understand it option 2 would also mean that nobody at a 
service provider that implements DMARC checks on the receiver side would 
receive mail sent to the list by people using a service provider that 
has a reject policy for outgoing mails. E.g. in your example while gmail 
users would not be unsubscribed from the mailing-list, but they still 
wouldn't receive the mails sent from cirrus.com. Which kind of makes the 
mailinglist useless.

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.

- Lars

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2020-02-17  9:35 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 [this message]
2020-02-17 11:35   ` Charles Keepax
2020-02-17 11:56     ` Peter Ujfalusi
2020-02-17 12:17       ` Lars-Peter Clausen
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=d1d0be54-5bdb-0405-320a-d7e542fdbcde@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    /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.