X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient: geda-help AT delorie DOT com
Message-ID: <20150503101117.32144.qmail@stuge.se>
Date: Sun, 3 May 2015 12:11:17 +0200
From: "Peter Stuge (peter AT stuge DOT se)" <geda-help AT delorie DOT com>
To: geda-help AT delorie DOT com, geda-user AT delorie DOT com
Subject: Re: [geda-help] listserv changes
Mail-Followup-To: geda-help AT delorie DOT com, geda-user AT delorie DOT com
References: <201505030357 DOT t433vTkx008899 AT envy DOT delorie DOT com> <201505030358 DOT t433wE7q008928 AT envy DOT delorie DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201505030357.t433vTkx008899@envy.delorie.com> <201505030358.t433wE7q008928@envy.delorie.com>
Reply-To: geda-help AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-help AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

DJ Delorie (dj AT delorie DOT com) wrote:
> There's not much else I can do given the strict rules

There is: The mangling can (and should, arguably) be applied only for
senders whose hosts actually publish a DMARC policy, not for everyone.

The RFC, 7489, explains the DMARC background:

"Over time, one-on-one relationships were established between select
senders and receivers with privately communicated means to assert
policy and receive message traffic and authentication disposition
reporting."

So large providers embraced and extended the email system, optimizing
for their proprietary interests. And now it's an RFC. Not a standard.


> mailing lists must now operate under.

I see that very differently. Every list operator decides whether she
wants to apply list-hostile restrictions or not.

It's one thing that large providers only offer crippled email service
to their customers.

It's a completely different thing that a list operator chooses to
implement the large provider policy for a whole list, when there are
subscribers who have a completely different policy.

I disagree with choosing the lowest common denominator, because it
makes the mailing list experience worse for everyone, without a very
compelling reason.


I am of course willing to help improve your listserv, so that it only
mangles email from hosts which actually publish a DMARC policy. Let
me know.


Thanks

//Peter