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:subject:references:to:from:cc:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=XCjJM0SpOyttivu3
	i/lPFyDTAdARzyXCHrwc5IjAdtkZazeg56Y4uPP/AstKwPfGYykh0jm8MGb9EYn1
	Pbq4aISyw+ys9ncCBUOyE9nZuo2Ye3gL4lz5QXMi5MpfZiIrpMyEm6g3ZpF9S8qe
	juoZc7ze51TpD36+VzohC+kPKew=
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:subject:references:to:from:cc:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=3PfvxwzV1iE5nLAY4ZLfc5
	aGkOk=; b=mLwqEapvAKuyiBsNE7r7yr+6/OvQMlsYXmFM+Dx8iwSQn6Vl9laQeJ
	D6QCf/IFTb/Dqz9NnxcJSDl1Tbwze6PcqmrSzc7qIskMgr6uYugbUsojbwN8ww8N
	LdYJNWMHrMOz4y76KrI+dAfZutSu5r39wdoG4zL4O12J7XA9ugIIw=
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.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, H*M:9992, HCc:U*cygwin, subscribed
X-HELO:	mail-io0-f178.google.com
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=kTCdAiY0LM60xwgEd+MMGX8WO9qiPBNBDA5NRt/NLEzwGQCpxMmPrLrUxOACvKSkwi Piup/PEzJNg3bMDw25EkAPKD3lqjiq9rt78ibXEScyvtagIg+qwQLif4M/kfHqfZhWoR 0xtZP9F4+zSJLnqUHMA7QlnCCCCuBw53yix4GNG2R0p3IcisvmEdXMn2eqKHgzRrxqiO KzoHvTdcNdpHgRCPZm3xcqY3pPB5tyBFAVhipQ5IqFCgC8jYkdQ/R7UlypPwYdd8qs8u kYHetr7gF0KbkTN6c+2D243AUH1axPAN1slaQMpSkaPnCN62pLpAuPZZUL0XN1Dfx1Db pWVw==
X-Gm-Message-State:	AKaTC00JBaRrjOQf5uJqVLVp1iTgUCfbLpPF3auPLKHndEdxt5HhT+IARnfDi3wZTXHL7A==
X-Received:	by 10.36.181.88 with SMTP id j24mr28545100iti.34.1480519494996; Wed, 30 Nov 2016 07:24:54 -0800 (PST)
Subject:	Fwd: Re: DMARC - gmail.com or is it yahoo.com
References:	<CACoZoo29vXpb0MzUri+NPJiZ5GSF+VZAykLa+JjS=g0VDEP7Pg AT mail DOT gmail DOT com>
To:	overseers AT sourceware DOT org
From:	cyg Simple <cygsimple AT gmail DOT com>
Cc:	cygwin AT cygwin DOT com
X-Forwarded-Message-Id:	<CACoZoo29vXpb0MzUri+NPJiZ5GSF+VZAykLa+JjS=g0VDEP7Pg AT mail DOT gmail DOT com>
Message-ID:	<6d23d97b-98b3-f501-9992-b0e3b6b0d263@gmail.com>
Date:	Wed, 30 Nov 2016 10:24:33 -0500
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:	<CACoZoo29vXpb0MzUri+NPJiZ5GSF+VZAykLa+JjS=g0VDEP7Pg@mail.gmail.com>
X-IsSubscribed:	yes

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 <ErikSoderquist AT gmail DOT com>
To: cygwin AT cygwin DOT 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?


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -