From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
Date: Wed, 14 Dec 2016 21:40:00 -0000 [thread overview]
Message-ID: <1449a24c-5f59-dc17-59da-f741140cf562@gmail.com> (raw)
In-Reply-To: <20161214152804.GA2077@ednor.casa.cgf.cx>
On 12/14/2016 10:28 AM, Christopher Faylor wrote:
> 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.
But I only received the reject notice today. Yes, I understand the delay
mechanism across multiple systems. Thanks for checking.
--
cyg Simple
--
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
next prev parent reply other threads:[~2016-12-14 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 16:19 cyg Simple
2016-11-29 17:00 ` Jack
2016-11-29 19:54 ` cyg Simple
2016-11-29 17:50 ` David Macek
2016-11-29 18:08 ` Erik Soderquist
2016-11-30 0:29 ` Stephen John Smoogen
2016-11-30 14:23 ` Corinna Vinschen
2016-11-30 21:13 ` Fwd: " cyg Simple
[not found] ` <20161130155549.GA29847@redhat.com>
[not found] ` <20161130160012.GA7318@ednor.casa.cgf.cx>
2016-12-09 5:13 ` Christopher Faylor
2016-12-10 20:40 ` Christopher Faylor
2016-12-12 7:58 ` David Macek
2016-12-14 14:16 ` cyg Simple
2016-12-14 15:28 ` Christopher Faylor
2016-12-14 21:40 ` cyg Simple [this message]
[not found] <860417281.1051305.1481544439039.ref@mail.yahoo.com>
2016-12-12 12:10 ` Ian Lambert via cygwin
2016-12-12 14:53 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1449a24c-5f59-dc17-59da-f741140cf562@gmail.com \
--to=cygsimple@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).