From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] DMARC & gmail & cirrus.com
Date: Mon, 17 Feb 2020 10:07:12 +0100 [thread overview]
Message-ID: <s5hd0adbn0f.wl-tiwai@suse.de> (raw)
In-Reply-To: <77884bad-81fd-f876-3f72-1f96a39d6329@perex.cz>
On Mon, 17 Feb 2020 09:46:22 +0100,
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?
If the number of such dead subscribers isn't too rapidly growing, the
manual bounce check and unsubscribing would work?
Takashi
>
> Jaroslav
>
> SMTP error:
>
> (host alt1.gmail-smtp-in.l.google.com[173.194.73.26] said: 550-5.7.26
> Unauthenticated email from cirrus.com is not accepted due to domain's
> 550-5.7.26 DMARC policy. Please contact the administrator of
> cirrus.com domain 550-5.7.26 if this was a legitimate mail. Please
> visit 550-5.7.26 https://support.google.com/mail/answer/2451690 to
> learn about the 450 4.7.26 DMARC initiative. m14si10079981ljg.84 -
> gsmtp (in reply to end of DATA command))
>
> DMARC settings for cirrus.com:
>
> v=DMARC1; p=reject;
> fo=1;rua=mailto:dmarc_rua@emaildefense.proofpoint.com;ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com
>
> --
> Jaroslav Kysela <perex@perex.cz>
> Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
_______________________________________________
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 9:08 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 [this message]
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
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=s5hd0adbn0f.wl-tiwai@suse.de \
--to=tiwai@suse.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.