From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 92114 invoked by alias); 10 Dec 2016 20:40:01 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 92099 invoked by uid 89); 10 Dec 2016 20:40:00 -0000 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 Received: from external.cgf.cx (HELO cgf.cx) (107.170.62.102) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 10 Dec 2016 20:39:50 +0000 Received: by cgf.cx (sSMTP sendmail emulation); Sat, 10 Dec 2016 15:39:47 -0500 DKIM-Filter: OpenDKIM Filter v2.10.3 cgf.cx 83107400B0 Date: Sat, 10 Dec 2016 20:40:00 -0000 From: Christopher Faylor To: eblake@redhat.com, cygsimple@gmail.com, "Frank Ch. Eigler" , overseers@sourceware.org, cygwin@cygwin.com Subject: Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com Message-ID: <20161210203947.GA434@ednor.casa.cgf.cx> Reply-To: overseers@sourceware.org Mail-Followup-To: eblake@redhat.com, cygsimple@gmail.com, "Frank Ch. Eigler" , overseers@sourceware.org, cygwin@cygwin.com References: <6d23d97b-98b3-f501-9992-b0e3b6b0d263@gmail.com> <20161130155549.GA29847@redhat.com> <20161130160012.GA7318@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161130160012.GA7318@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2016-12/txt/msg00109.txt.bz2 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 " 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@sourceware.org. cgf