Re: FWD: [ATTENTION] Mails on qemu mailing list are disapapearing making communication unreliable

["Daniel P. Berrangé" <berrange@redhat.com>]

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.

This guarantees DMARC fail for any @huawei.com sender using any mailing
list, however, the @huawei.com DMARC policy is only set to 'quarantine'.

That should not block delivery to list subscribers, merely suggest
that MTAs put the mails in the Spam/Junk folder *if* DMARC fails.

mailam is cautious and thus applying DMARC countermeasures to huawei.com
addresses due to he missing DKIM records, in order to reduce the chance
that the mails end up in Spam/Junk folders for list subscribers.


This does not explain why messages might never appear in the list to
begin with though.

It is notable, however, that messages from salil.mehta@huawei.com
do arrive if they are non-patch mails. Presumably those are via a
normal email client 

I wonder how Salil is sending patches ? Some tool like git send-email
or git-publish ?

If so I then wonder if the tool is NOT correctly configured to use an
official huawei.com outbound SMTP relay ?

While you can have git send-email deliver directly to lists.nongnu.org,
the huawei.com SPF policy will almost certainly result in the mails
getting either rejected or dropped, *UNLESS* they are relayed via one
of the officially designated huawei.com SMTP relays.


> For example, the attached .eml file is a message from Vishnu (Ampere) which
> was sent to the list but later disappeared. This is starting to raise serious
> concerns about the reliability of the mailing list, and the broken communication
> is creating confusion for everyone involved.


In terms of mails from Vishnu, I see nothing in my INBOX from Vishnu.

The mail quoted below has a From address of vishnu@amperemail.onmicrosoft.com,
while people seem to sending to/cc for vishnu@os.amperecomputing.com

Is that From address correct ? It seems like the latter is more likely to be
the canonical address for Ampere accounts.

If not, perhaps that is triggering some rule that discards the mails when
sending is amperemail.onmicrosoft.com



> From: Vishnu Pajjuri <vishnu@amperemail.onmicrosoft.com>
> Date: Mon, 27 Oct 2025 13:58:59 +0530
> To: Igor Mammedov <imammedo@redhat.com>, salil.mehta@opnsrc.net
> Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org, mst@redhat.com,
>  salil.mehta@huawei.com, maz@kernel.org, jean-philippe@linaro.org,
>  jonathan.cameron@huawei.com, lpieralisi@kernel.org,
>  peter.maydell@linaro.org, richard.henderson@linaro.org, armbru@redhat.com,
>  andrew.jones@linux.dev, david@redhat.com, philmd@linaro.org,
>  eric.auger@redhat.com, will@kernel.org, ardb@kernel.org,
>  oliver.upton@linux.dev, pbonzini@redhat.com, gshan@redhat.com,
>  rafael@kernel.org, borntraeger@linux.ibm.com, alex.bennee@linaro.org,
>  gustavo.romero@linaro.org, npiggin@gmail.com, harshpb@linux.ibm.com,
>  linux@armlinux.org.uk, darren@os.amperecomputing.com,
>  ilkka@os.amperecomputing.com, vishnu@os.amperecomputing.com,
>  gankulkarni@os.amperecomputing.com, karl.heubaum@oracle.com,
>  miguel.luis@oracle.com, zhukeqian1@huawei.com, wangxiongfeng2@huawei.com,
>  wangyanan55@huawei.com, wangzhou1@hisilicon.com, linuxarm@huawei.com,
>  jiakernel2@gmail.com, maobibo@loongson.cn, lixianglai@loongson.cn,
>  shahuang@redhat.com, zhao1.liu@intel.com
> Subject: Re: [PATCH RFC V6 00/24] Support of Virtual CPU Hotplug-like Feature
>  for ARMv8+ Arch
> Message-ID: <c2462372-f797-47f3-a96e-4872f9cedde5@amperemail.onmicrosoft.com>
> In-Reply-To: <20251006160027.20067fe4@fedora>


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 :|