From: Salil Mehta <salil.mehta@opnsrc.net>
To: "Daniel P. Berrangé" <berrange@redhat.com>
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: Wed, 10 Dec 2025 17:58:40 +0000 [thread overview]
Message-ID: <CAJ7pxebQnOYkMyFUwucn+VL-xasJ559SjcONtAYw+NvfZkd-fQ@mail.gmail.com> (raw)
In-Reply-To: <aTmlzlAWK8BcGaEp@redhat.com>
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:
> > Hi Daniel & Michael,
> >
> > Many thanks for replying.
> >
> > On Tue, Dec 9, 2025 at 9:18 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
> > >
> > > On Tue, Dec 09, 2025 at 02:24:44AM -0500, Michael S. Tsirkin wrote:
> > > > Hi guys,
> > > > who has ability to contact the list admins? Can help Salil?
> > >
> > > I'm not a list admin, but I have some observations below
> > >
> > > > ----- Forwarded message from Salil Mehta <salil.mehta@opnsrc.net> -----
> > > >
> > > > From: Salil Mehta <salil.mehta@opnsrc.net>
> > > > Date: Tue, 9 Dec 2025 00:44:04 +0000
> > > > To: "Michael S. Tsirkin" <mst@redhat.com>
> > > > Subject: [ATTENTION] Mails on qemu mailing list are disapapearing making communication unreliable
> > > > Message-ID: <CAJ7pxeY8dpK53ePE6YcXqHpmxD9B7e9tY49ij6HzgU450OgYLA@mail.gmail.com>
> > > >
> > > > Hi Michael,
> > > >
> > > > I hope you are doing well.
> > > >
> > > > I’ve noticed that some emails are going missing from the qemu-devel mailing
> > > > list. This has now happened multiple times, both with emails I have sent from my
> > > > official address and with emails from other contributors.
> > > >
> > > > Over the past three months, I have consistently observed emails disappearing
> > > > from the qemu-devel archives, which makes the mailing list communication highly
> > > > unreliable.
> > >
> > > I can see patches arriving in my INBOX via qemu-devel from salil.mehta@opnsrc.net
> > > but no patches from salil.mehta@huawei.com
> > >
> > > I do see some (non-patch) emails from salil.mehta@huawei.com, but the
> > > mailing list is re-writing this From address for DMARC countermeasures
> > >
> > > Salil Mehta via <qemu-devel@nongnu.org>
> > >
> > >
> > > Recapping mail delivery policies, DMARC requires a pass for *either*
> > > SPF or DKIM checks.
> > >
> > > SPF checks will always fail for mails forwarded via any mailing list.
> > >
> > > DKIM checks should still succeed *provided* the mailing list does not
> > > modify the message content, or certain headers. QEMU mailing list
> > > behaves in this respect generally, and applies countermeasures when
> > > appropriate.
> > >
> > > I see no DKIM records huawei.com, but I do see SPF records.
> >
> >
> > Thanks for identifying this.
> >
> > When you say there are no DKIM records for huawei.com, do you mean
> > that my @huawei.com mails do not contain any DKIM-Signature header,
> > or that a DKIM-Signature is present but cannot be validated against
> > a published key?
>
> I see no DKIM-Signature, and not DKIM DNS records with the
> default selector.
This is definitely a problem then — thank you for checking that so
clearly.
I’m still trying to get a hold of our IT team, and I’ll share this
information with them so they can look into enabling DKIM
properly for @huawei.com. Once I hear back from them or have any
concrete update, I’ll report it here so others aren’t hit by the
same issue.
Many thanks again for your help.
>
> > 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.
>
> > > This guarantees DMARC fail for any @huawei.com sender using any mailing
> > > list, however, the @huawei.com DMARC policy is only set to 'quarantine'.
> >
> > Agreed. I will check with the IT department here about the DKIM
> > headers and whether the public key is being published correctly.
>
> I should have checked before, but I see there are other people
> using @huawei.com email addresses that are posting to qemu-devel
> successfully.
Yes, that matches my observation as well. Messages from my
@huawei.com address do sometimes reach qemu-devel, but others
(particularly some patch series) appear to vanish. A couple of
colleagues have also mentioned similar intermittent issues in the
past, although it now seems to be affecting me more consistently.
What makes this confusing is that I have been using the same
git-send-email configuration and the same Outlook setup as before,
and earlier mails sent with these settings are present in the
qemu-devel archives. This suggests that something in the delivery
path, authentication checks, or domain policy may have changed
recently, even if not all @huawei.com senders are impacted in the
same way.
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.
Many thanks again for your help in digging into this.
>
> That seems to suggest that the huawei mail is able to work with
> QEMU lists and nothing about SPF/DKIM/DMARC is a blocking problem
>
> > > I wonder how Salil is sending patches ? Some tool like git send-email
> > > or git-publish ?
> >
> > Mails disappear or not appear in the mailing list even when I reply
> > via outlook and the same happens when I sometimes use git-send-mail.
> >
> > check these:
> > https://lore.kernel.org/qemu-devel/20251001010127.3092631-1-salil.mehta@opnsrc.net/
> >
> > AND
> >
> > https://lore.kernel.org/qemu-devel/CAJ7pxea721f4EwqpDdcztgRoN-rsB2tqthf-_Kb+mmsRkK1GyQ@mail.gmail.com/
> >
> > I'm replying to this broken link which existed but disappeared later.
> > [not found] <20250930224037.224833-1-salil.mehta@huawei.com>
>
>
> > > If not, perhaps that is triggering some rule that discards the mails when
> > > sending is amperemail.onmicrosoft.com
> >
> > Could be. Do we have access to the logs to verify the reason?
>
> Unfortunately we have no insight into operation of the mailman service
> as that's not run by QEMU.
Got it, thanks for clarifying.
If you happen to know who is responsible for administering the
mailman service or whom I should contact to request more detailed
mail logs, that would be very helpful.
Many thanks!
Best regards,
Salil
>
> 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 :|
>
next prev parent reply other threads:[~2025-12-10 17:59 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 [this message]
2025-12-11 9:31 ` Daniel P. Berrangé
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=CAJ7pxebQnOYkMyFUwucn+VL-xasJ559SjcONtAYw+NvfZkd-fQ@mail.gmail.com \
--to=salil.mehta@opnsrc.net \
--cc=berrange@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--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).