From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Handling DKIM for nntp articles
Date: Fri, 05 Jun 2020 17:19:49 +0200 [thread overview]
Message-ID: <873679czfu.fsf@tullinup.koldfront.dk> (raw)
A while back I wrote a little on emacs-devel, and was a little dismayed
to see my articles munged:
From: =?UTF-8?Q?Adam_Sj=C3=83=C2=B8gren_via_=22Emacs_development_discussions=2E?= <emacs-devel@gnu.org>
One thing is the double encoding of the 'ø' in my last name, but why was
From: rewritten by Mailman at all?
Rereading "Actually, DMARC works fine with mailing lists"¹ today made me
realize why.
Here are the key sentences:
"A mailing list is going to have a hard time relaying messages for any
domain that uses DMARC and SPF but not DKIM."
"If the sending domain uses DKIM, it avoids the need for From-munging
or other hacks. It works under the condition that the list does not
modify the message."
I've got SPF and DMARC configured for my domain, and my MTA does DKIM
signing of all my outgoing emails.
So what's the problem?
I'm sending my messages to emacs-devel over nntp via Gmane!
So the article doesn't pass through my MTA, and thus not through
opendkim, so articles I send this way do not get DKIM signed!
Various mailing lists handle this in different ways - when I post to
ding via Gmane I usually get some reports about my emails being rejected
in various places - this is what emacs-devel avoid by rewriting From.
This also due to DKIM missing.
One solution would be not to post via Gmane, but to always post via
email instead.
That's doable, but kind of icky/finicky.
Could Gnus somehow do the DKIM signing and add the appropriate headers?
Best regards,
Adam
¹ https://begriffs.com/posts/2018-09-18-dmarc-mailing-list.html
--
"The light at the end of the tunnel Adam Sjøgren
Is nothing but the burglar alarm" asjo@koldfront.dk
next reply other threads:[~2020-06-05 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 15:19 Adam Sjøgren [this message]
2020-06-05 15:27 ` Emanuel Berg
2020-06-05 15:58 ` Adam Sjøgren
2020-06-05 17:18 ` Adam Sjøgren
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=873679czfu.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.org \
/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).