X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=e/eD7UwKKeJ1K4WxP4+xiRSE3PSmHG1KJNlvsa3O27cWEAxJjODJ9
	AzVjBLcCxUcL/swxkPGZb5LRqn5ZwJ9ecSAjAZszDDF2/iibkqlClC73fuLXFyqF
	d8vKVWqVIVzq8ONVKTvtor65ul1Lx+tdexBaImSAKigwrhbsbbXxCA=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=i6/JC9idInfU8sElWyhM0wP+EhI=; b=dJYXTr5YYbXukW/wjWz4TtlDY0Ao
	Fx0V8hHkV2LhZBu3xyzMKY/R1ihTSOe+AHxKbAngsNykjrMwslBCey6xxUeKNPpc
	qGUlHzvtEetHL7PoimubYUo5huF7RT4OCOZcckEFh0EKB5XWxldLAJv78XNqeMP/
	nUf4TNwWzXkzzWY=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.3 required=5.0 tests=AWL,BAYES_50,SPF_HELO_PASS,SPF_NEUTRAL autolearn=no version=3.3.2 spammy=frank, Frank, rusty, capabilities
X-HELO:	cgf.cx
DKIM-Filter:	OpenDKIM Filter v2.10.3 cgf.cx 83107400B0
Date:	Sat, 10 Dec 2016 15:39:47 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT sourceware DOT org>
To:	eblake AT redhat DOT com, cygsimple AT gmail DOT com,
	"Frank Ch. Eigler" <fche AT redhat DOT com>, overseers AT sourceware DOT org,
	cygwin AT cygwin DOT com
Subject:	Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
Message-ID:	<20161210203947.GA434@ednor.casa.cgf.cx>
Reply-To:	overseers AT sourceware DOT org
Mail-Followup-To:	eblake AT redhat DOT com, cygsimple AT gmail DOT com, "Frank Ch. Eigler" <fche AT redhat DOT com>, overseers AT sourceware DOT org, cygwin AT cygwin DOT com
References:	<CACoZoo29vXpb0MzUri+NPJiZ5GSF+VZAykLa+JjS=g0VDEP7Pg AT mail DOT gmail DOT com> <6d23d97b-98b3-f501-9992-b0e3b6b0d263 AT gmail DOT com> <20161130155549 DOT GA29847 AT redhat DOT com> <20161130160012 DOT GA7318 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version:	1.0
In-Reply-To:	<20161130160012.GA7318@ednor.casa.cgf.cx>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Wed, Nov 30, 2016 at 11:00:12AM -0500, Christopher Faylor wrote:
>On Wed, Nov 30, 2016 at 10:55:49AM -0500, Frank Ch. Eigler wrote:
>>cygsimple wrote:
>>> See the description below of a problem that is occurring because of
>>> DMARC rules in place by yahoo.com.  Is there anything you can do for this?
>>
>>cgf, any chance of updating our copy of ezmlm-toaster etc.?
>>Newer-than-2014 versions of ezmlm-idx seem to have some DMARC
>>capabilities.
>
>I started looking at this when it came in.  No ETA yet.

Huh.  I thought I sent an update about this but it vanished in the aether.

I just turned on a new DMARC-aware version of ezmlm-send which rewrites
the From address for any domain that is DMARC sensitive to something like:

"User name via mailinglist <mailinglist AT sourceware DOT org>"

when the mail is broadcast to the mailing list.  I would have done this
sooner but my ezmlm skills were really rusty and I almost ran out of
extremities to shoot.

Please send any errors or issues encountered to overseers AT sourceware DOT org.

cgf

- Raw text -