All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen-Yu Tsai <wenst@chromium.org>
To: Geraldo Nascimento <geraldogabriel@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, Mark Brown <broonie@kernel.org>,
	alsa-devel@alsa-project.org,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	sound-open-firmware@alsa-project.org
Subject: Re: DMARC (Was: Re: [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe])
Date: Wed, 10 May 2023 11:01:04 +0800	[thread overview]
Message-ID: <CAGXv+5Eu8Y6PPwJ0iwfSvYMV9TkKqm1G+J=ZM1fw0jZyXUpOBg@mail.gmail.com> (raw)
In-Reply-To: <ZFqIGCliFRJ3W/ap@geday>

On Wed, May 10, 2023 at 1:52 AM Geraldo Nascimento
<geraldogabriel@gmail.com> wrote:
>
> On Tue, May 09, 2023 at 09:12:55AM +0200, Jaroslav Kysela wrote:
> > I am open to any suggestions, but the default mailman settings (do not do
> > anything) causes that some (mostly gmail) users do not receive their e-mails
> > because the ALSA's mail server has a bad reputation. Many companies are using
> > the google mail service for their domains nowadays.
> >
>
> As a GMail user, I can confirm that I'm not seeing any more bounces
> after mangling started. Usually it'd bounce and I'd have to login to the
> web interface to turn back on my subscription, a real pain.

FWIW the dri-devel mailing list seems to implement an alternative strategy
for dealing with Gmail and co. bouncing messages. If it gets bounces it will
send a separate "bounce probe" email including details about what bounced.
It will not just deactivate a subscription due to bounces.

Also, ALSA's mailing list now requires a subscriber to register a user
account to resume delivery is a bit annoying.


ChenYu

  reply	other threads:[~2023-05-10  3:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  1:09 [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe] Mark Brown
2023-05-04  7:35 ` Takashi Iwai
2023-05-04  7:58   ` Takashi Iwai
2023-05-08  7:52     ` Takashi Iwai
2023-05-09  7:12       ` DMARC (Was: Re: [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe]) Jaroslav Kysela
2023-05-09  9:37         ` Mark Brown
2023-05-09  9:54           ` Jaroslav Kysela
2023-05-09 14:35             ` Mark Brown
2023-05-09 18:03               ` Jaroslav Kysela
2023-05-09 18:26                 ` Konstantin Ryabitsev
2023-05-10  2:05                 ` Mark Brown
2023-05-10  3:33                   ` Chen-Yu Tsai
2023-05-10  3:58                   ` Geraldo Nascimento
2023-05-10  6:17                     ` Jaroslav Kysela
2023-05-10 15:13                       ` Konstantin Ryabitsev
2023-05-10 17:15                         ` Geraldo Nascimento
2023-05-09 18:22             ` Konstantin Ryabitsev
2023-05-10  7:50               ` Jaroslav Kysela
2023-05-10 15:34                 ` Konstantin Ryabitsev
2023-05-10 16:19                   ` Jaroslav Kysela
2023-05-10 16:43                     ` Konstantin Ryabitsev
2023-05-10 18:38                       ` Jaroslav Kysela
2023-05-11  5:58                         ` Mark Brown
2023-05-09 17:51         ` Geraldo Nascimento
2023-05-10  3:01           ` Chen-Yu Tsai [this message]
2023-05-10  6:46             ` Jaroslav Kysela
2023-05-05 20:38 ` [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe] Geraldo Nascimento
2023-05-06  0:13   ` Mark Brown
2023-05-06  2:17     ` Geraldo Nascimento
2023-05-07 23:33       ` Mark Brown
2023-05-07 23:38         ` Geraldo Nascimento

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='CAGXv+5Eu8Y6PPwJ0iwfSvYMV9TkKqm1G+J=ZM1fw0jZyXUpOBg@mail.gmail.com' \
    --to=wenst@chromium.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=broonie@kernel.org \
    --cc=geraldogabriel@gmail.com \
    --cc=sound-open-firmware@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.