Dear Maintainer,

When I submit a Debian bug using reportbug, I receive many DMARC
reports with failures in them.  It appears that the Debian BTS
forwards emails without changing the original sender.  This makes DKIM
and SPF fail in many cases.  It would be better to rewrite the sender
to, say, <owner@bugs.debian.org> before forwarding the message.

It is hard to judge the severity of this, since I don't know how many
recipients' SPAM filtering might have rejected the message based on
DMARC/DKIM/SPF failures.  Therefore, I'm marking it as important.

Here are some example outputs from dmarc-cat, for DMARC reports
relating to email forwarded by the Debian BTS (it is difficult for me
to provide attachments because of my local machine email config):

$ dmarc-cat gmx.net\!meltin.net\!1740787200\!1740873599\!cf6fcf3b8bb843b6acd2385e77dd2f5b.xml.gz
dmarc-cat 0.15.0,parallel/j12 by Ollivier Robert

Reporting by: GMX — noreply-dmarc@sicher.gmx.net
From 2025-03-01 11:00:00 +1100 AEDT to 2025-03-02 10:59:59 +1100 AEDT

Domain: meltin.net
Policy: p=none; dkim=r; spf=r

Reports(1):
IP                 Count   From       RFrom      RDKIM   RSPF
bendel.debian.org. 4       meltin.net meltin.net fail    none

$ dmarc-cat yahoo.com\!meltin.net\!1740787200\!1740873599.xml.gz
dmarc-cat 0.15.0,parallel/j12 by Ollivier Robert

Reporting by: Yahoo — dmarchelp@yahooinc.com
From 2025-03-01 11:00:00 +1100 AEDT to 2025-03-02 10:59:59 +1100 AEDT

Domain: meltin.net
Policy: p=none; dkim=r; spf=r

Reports(1):
IP                 Count   From       RFrom      RDKIM     RSPF
bendel.debian.org. 1       meltin.net meltin.net permerror none

$ dmarc-cat google.com\!meltin.net\!1737158400\!1737244799.zip
dmarc-cat 0.15.0,parallel/j12 by Ollivier Robert

Reporting by: google.com — noreply-dmarc-support@google.com
From 2025-01-18 11:00:00 +1100 AEDT to 2025-01-19 10:59:59 +1100 AEDT

Domain: meltin.net
Policy: p=none; dkim=r; spf=r

Reports(10):
IP                              Count   From       RFrom        RDKIM   RSPF
mitropoulos.debian.org.         36      meltin.net meltin.net   fail    none
mail.tryninja.io.               29      meltin.net meltin.net   fail    none
i-bif.cloudflare-email.net.     2       meltin.net meltin.net   fail    none
bendel.debian.org.              2       meltin.net meltin.net   fail    pass
smtp-mx-ubuntu-0.canonical.com. 1       meltin.net meltin.net   fail    softfail
bendel.debian.org.              1       meltin.net meltin.net   fail    none
mail-sor-f69.google.com.        1       meltin.net meltin.net   fail    pass
smtp-mx-ubuntu-1.canonical.com. 1       meltin.net meltin.net   fail    softfail
mail-sor-f41.google.com.        1       meltin.net mokyokit.com pass    pass
yw-1204.doraji.xyz.             1       meltin.net meltin.net   fail    none

Thanks...

Not really a bug in reportbug, but in the bug system in general, but I can confirm
that I replied to a bug using reportbug and received a bounce when bugs.debian
forwarded my message to the original reported as I have DKIM/DMARC setup for my
domain.

I would guess most mail servers are now bouncing on invalid DMARC since Google
and Yahoo implemented it a few years ago (I implemented it on my own mail servers
once the "big guys" started bouncing, so presumably everyone has to fall in line...

See this link for the original bug report + problem:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754809