From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Salil Mehta <salil.mehta@opnsrc.net>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, richard.henderson@linaro.org,
Peter Maydell <peter.maydell@linaro.org>,
Vishnu Pajjuri OS <vishnu@os.amperecomputing.com>,
Vishnu Pajjuri <vishnu@amperemail.onmicrosoft.com>
Subject: Re: FWD: [ATTENTION] Mails on qemu mailing list are disapapearing making communication unreliable
Date: Thu, 11 Dec 2025 09:31:36 +0000 [thread overview]
Message-ID: <aTqPeGHQBhmyFxXF@redhat.com> (raw)
In-Reply-To: <CAJ7pxebQnOYkMyFUwucn+VL-xasJ559SjcONtAYw+NvfZkd-fQ@mail.gmail.com>
On Wed, Dec 10, 2025 at 05:58:40PM +0000, Salil Mehta wrote:
> Hi Daniel,
>
> Many thanks for your reply.
>
> On Wed, Dec 10, 2025 at 4:54 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > On Wed, Dec 10, 2025 at 01:20:26AM +0000, Salil Mehta wrote:
> > > If there are SPF/DKIM/DMARC logs on the list side, would it be
> > > possible to see whether DKIM validation is failing for my messages?
> >
> > We have no access to anything in the mailman service - we're just
> > using the nongnu.org service for QEMU, run by the GNU project.
>
> Understood, thanks for clarifying.
>
> If you happen to know who maintains the nongnu.org Mailman service,
> or where I should direct questions about mail logs and DMARC handling,
> a pointer would be very helpful.
I'm afraid I don't know any contact there, but someone else on
CC might.
> I am following up with our IT/mail team about DKIM and the correct
> SMTP relay configuration for mailing lists. If it is easy to see
> from the list side whether my recent missing patch mails were
> rejected or filtered due to SPF/DMARC (as opposed to never
> arriving at all), that information would be very helpful for that
> discussion.
FWIW, when I first investigated DMARC/DKIM/SPF in the context of
mailing lists years ago, the following blog was a good explainer
to refer people to:
https://begriffs.com/posts/2018-09-18-dmarc-mailing-list.html
TL;DR: if DMARC is used by a sender's domain, then the best
situation is for the sender domain to have DMARC + DKIM enabled,
AND for mailing lists to NOT modify the message text, nor any of
the headers covered by DKIM.
We believe qemu-devel does the latter part correctly, as we
turned off modification of the Subject header, and stopped
appending a footer to the message text.
Unfortunately I don't know any way to trace the cause of your
problems without info from the mail system logs on the mailing
list server, which only the sysadmins have access to :-(
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2025-12-11 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ7pxeY8dpK53ePE6YcXqHpmxD9B7e9tY49ij6HzgU450OgYLA@mail.gmail.com>
2025-12-09 7:24 ` FWD: [ATTENTION] Mails on qemu mailing list are disapapearing making communication unreliable Michael S. Tsirkin
2025-12-09 9:17 ` Daniel P. Berrangé
2025-12-10 1:20 ` Salil Mehta
2025-12-10 16:54 ` Daniel P. Berrangé
2025-12-10 17:58 ` Salil Mehta
2025-12-11 9:31 ` Daniel P. Berrangé [this message]
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=aTqPeGHQBhmyFxXF@redhat.com \
--to=berrange@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=salil.mehta@opnsrc.net \
--cc=vishnu@amperemail.onmicrosoft.com \
--cc=vishnu@os.amperecomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).