From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 102985 invoked by alias); 30 Nov 2016 15:25:08 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 101903 invoked by uid 89); 30 Nov 2016 15:25:06 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=H*MI:sk:g0VDEP7, HCc:U*cygwin, H*M:9992, subscribed X-HELO: mail-io0-f175.google.com Received: from mail-io0-f175.google.com (HELO mail-io0-f175.google.com) (209.85.223.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 30 Nov 2016 15:24:56 +0000 Received: by mail-io0-f175.google.com with SMTP id j65so354219766iof.0 for ; Wed, 30 Nov 2016 07:24:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:to:from:cc:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=9NFJ9mbE5tTGV/0fZh9tEWRkhIQg81o+g823dtcXc64=; b=C9ZiBfIKDKbl97trkD/IL7gydQyPzuyG7X2Zggz8GDa5SVEV2XoGwXx68b4yK8+7QL suwCI09WEDenVUoi2KteG/sila31MxTbq6BRifWM9f78mWhTlD0bvAp7+NhB6IyTWEXx LBga43eObW5hzv2e6Je43zKmKfdMokVRDKsC20L3q5ohvpDqJ3J11MPkSG7Yjp4UnhQf Xlaqf5t6KkVGbi0ug/0fILuMbt1GnIi3IqXwWh4EbH7r4hCVBIBHJRyTicpevWws2nGU 9oCsvhzL5pHenhTYxjiR1/V5NVmVmEIWt6lFG2mLMh79eCCRqELNsOLq1VsFMUaNlo4w m8fQ== X-Gm-Message-State: AKaTC030mC6h4hanF69Km1NKkIBRbU3EoB7QTJ61DcB/CfEjbHgNhdTN+Kcj+mIhZ46rLQ== X-Received: by 10.36.181.88 with SMTP id j24mr28545100iti.34.1480519494996; Wed, 30 Nov 2016 07:24:54 -0800 (PST) Received: from [192.168.0.6] (d27-96-48-76.nap.wideopenwest.com. [96.27.76.48]) by smtp.gmail.com with ESMTPSA id 19sm13968041ion.9.2016.11.30.07.24.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Nov 2016 07:24:54 -0800 (PST) Subject: Fwd: Re: DMARC - gmail.com or is it yahoo.com References: To: overseers@sourceware.org From: cyg Simple Cc: cygwin@cygwin.com X-Forwarded-Message-Id: Message-ID: <6d23d97b-98b3-f501-9992-b0e3b6b0d263@gmail.com> Date: Wed, 30 Nov 2016 15:25:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2016-q4/txt/msg00067.txt.bz2 Overseers, 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? Regards, cygSimple -------- Forwarded Message -------- Subject: Re: DMARC - gmail.com or is it yahoo.com Date: Tue, 29 Nov 2016 11:59:53 -0500 From: Erik Soderquist To: cygwin@cygwin.com On Tue, Nov 29, 2016 at 11:19 AM, David Macek wrote: > What happens is that ezmlm (the mailing list software) broadcasts this > message (after adding a bunch of links at the bottom) to everyone > subscribed, but with the sender unchanged. Yahoo has got a DMARC policy > set up that is supposed to ensure that only Yahoo servers can send > messages marked as "from ...@yahoo.com". As you can see, Google is > enforcing the policy and correctly rejecting the message as fake (it > really wasn't sent by Yahoo, but by Sourceware). This is only going to > happen more and more often as email providers up the battle against > spam. > > The best solution is to change the way ezmlm re-sends the messages, I > bet there's a big discussion about it somewhere on the Internet. Probably hundreds if not thousands of such discussions! Who is in charge of the list server configuration? Sourceware itself, or someone from Cygwin?