Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com

Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com

[Ian Lambert]

On Sat, 12/10/16, Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org> wrote:

 Subject: Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
 To: ...
 Date: Saturday, December 10, 2016, 3:39 PM
 
 
 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:
 
... 
 Please send any
 errors or issues encountered to overseers@sourceware.org.

 = = = 

It seems to have done away with the auto-signature helpful 
links, and References, at least for my last reply.

Problem reports: 
FAQ:                  
Documentation:   
Unsubscribe info: 
and 
References
 

Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com

[Christopher Faylor]

On Mon, Dec 12, 2016 at 12:07:19PM +0000, Ian Lambert wrote:
>On Sat, 12/10/16, Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org> wrote:
> 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:
> 
>... 
> Please send any
> errors or issues encountered to overseers@sourceware.org.
>
> = = = 
>
>It seems to have done away with the auto-signature helpful 
>links, and References, at least for my last reply.
>
>Problem reports: 
>FAQ:                  
>Documentation:   
>Unsubscribe info: 
>and 
>References

Should be fixed now.

cgf

Fwd: Re: DMARC - gmail.com or is it yahoo.com

[cyg Simple]

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@gmail.com>
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?

Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com

[Frank Ch. Eigler]

Hi -

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.


- FChE

Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com

[Christopher Faylor]

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.

fche, I read overseers.  No need to clutter my personal inbox with this.

I started looking at this when it came in.  No ETA yet.

cgf

Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com

[Christopher Faylor]

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@sourceware.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@sourceware.org.

cgf

Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com

[David Macek]

[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]

On 10. 12. 2016 21:39, Christopher Faylor wrote:
> 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.

FWIW, I received a message on [Thu, 8 Dec 2016 21:14:41 -0800 (PST)]:

> I'm going to use start using a new version of ezmlm-send on Friday.  It will
> rewrite the From addresses of any domain which wants to use DMARC.  From what
> I've read, that should stop yahoo and gmail from complaining.

> 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@sourceware.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.

Thanks. By the way, does that include domains with SPF?

> Please send any errors or issues encountered to overseers@sourceware.org.

-- 
David Macek


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3715 bytes --]

Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com

[cyg Simple]

On 12/10/2016 3:39 PM, Christopher Faylor wrote:
> 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@sourceware.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@sourceware.org.

The issue continues.

Here are the message numbers:

   206020
   206062

--- Enclosed is a copy of the bounce message I received.

Return-Path: <>
Received: (qmail 128079 invoked for bounce); 2 Dec 2016 17:38:50 -0000
Date: 2 Dec 2016 17:38:50 -0000
From: MAILER-DAEMON@sourceware.org
To: cygwin-return-206020-@cygwin.com
Subject: failure notice

Hi. This is the qmail-send program at sourceware.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<cygsimple@gmail.com>:
User and password not set, continuing without authentication.
<cygsimple@gmail.com> 173.194.203.26 failed after I sent the message.
Remote host said: 550-5.7.1 Unauthenticated email from yahoo.com is not
accepted due to domain's
550-5.7.1 DMARC policy. Please contact the administrator of yahoo.com
domain if
550-5.7.1 this was a legitimate mail. Please visit
550-5.7.1  https://support.google.com/mail/answer/2451690 to learn about the
550 5.7.1 DMARC initiative. e85si746691pfj.218 - gsmtp


-- 
cyg Simple

Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com

[Christopher Faylor]

On Wed, Dec 14, 2016 at 09:15:46AM -0500, cyg Simple wrote:
>On 12/10/2016 3:39 PM, Christopher Faylor wrote:
>> 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@sourceware.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@sourceware.org.
>
>The issue continues.
>
>Here are the message numbers:
>
>   206020
>   206062

I sent the above on 12/10.  Those messages were sent on 12/1 and 12/7
respectively.  The change was not retroactive.