From: Yuri D'Elia <wavexx@thregr.org>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Dealing with DMARC - any out-of-the-box solution in sight?
Date: Wed, 21 May 2014 12:32:56 +0000 [thread overview]
Message-ID: <537C9CF8.6020608@thregr.org> (raw)
In-Reply-To: <CAOPHaVTAVpbLN9OUyzG7NMWu4szaHCKgLbjE56wvL6tJpFY-2A@mail.gmail.com>
On 05/21/2014 01:19 PM, Christian Lohmaier wrote:
> Hi *,
>
> DMARC is in use by yahoo and others for a while, and gmail and others
> already respect the settings, causing many bounces....
>
> I wonder whether mlmmj will have some dmarc-compatible default soon or
> how other mailinglist admins deal with the topic.
>
> Disallow all mail from dmarc-policy using senders?
> Forward only (no footers, no list-tag, no body filtering... - and no
> real solution with some SPF)?
> Just replace from-address by "John Doe via <list-addresss>"?
> Replace From and add reply-to?
> Replace From by forwarder-address?
>
> What have other mailinglistadmins done?
> And what is the suggestion by mlmmj-devs?
I'm currently removing DKIM and some obvious headers (using delheaders):
DKIM-Signature:
Return-Receipt-To:
Disposition-Notification-To:
X-Confirm-Reading-To:
X-PMRQC:
in order to bypass DKIM checks. It works if there's no DMARC, but I had
no bounces from gmail users either.
If I read the spec correctly, the only solution would be to replace
From: with the list header (or a forwarder under the list domain) and
add a Reply-To:. And of course, you cannot modify the body/subject if
DKIM is in use.
I don't like neither. The ability to choose reply-to-author/list is lost.
Also, AFAIK there's no way to construct a Reply-To: automatically from
the From: address in mlmmj.
[sigh]
I don't understand why the keep breaking mailing lists....
Though DMARC with SPF *only* seems reasonable enough, the biggest
players all seem to use DKIM as well.
next prev parent reply other threads:[~2014-05-21 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 11:19 [mlmmj] Dealing with DMARC - any out-of-the-box solution in sight? Christian Lohmaier
2014-05-21 12:32 ` Yuri D'Elia [this message]
2014-05-21 13:04 ` Chris Knadle
2014-05-21 14:49 ` Chris Knadle
2014-05-21 22:06 ` Andreas Schulze
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=537C9CF8.6020608@thregr.org \
--to=wavexx@thregr.org \
--cc=mlmmj@mlmmj.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.