From: geda-user-bounces AT delorie DOT com
X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Sun, 3 May 2015 14:09:59 -0400
Message-Id: <201505031809.t43I9xKG012331@envy.delorie.com>
To: geda-user AT delorie DOT com
In-reply-to: <20150503101117.32144.qmail@stuge.se> (geda-user@delorie.com)
Subject: Re: [geda-user] Re: [geda-help] listserv changes
References: <201505030357 DOT t433vTkx008899 AT envy DOT delorie DOT com> <201505030358 DOT t433wE7q008928 AT envy DOT delorie DOT com> <20150503101117 DOT 32144 DOT qmail AT stuge DOT se>
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


You do realize that the changes I made do not affect the geda lists at
all, as they're already subscriber-only, right?

So despite your obvious bias against these new security measures, I've
decided to try to detect when one of the many security features is in
use (dmarc is not the only one) and apply the new changes only when
needed.

Hopefully that doesn't cause *more* problems.