From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: cygwin@cygwin.com, overseers@sourceware.org,
"Frank Ch. Eigler" <fche@redhat.com>,
cyg Simple <cygsimple@gmail.com>
Subject: Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
Date: Wed, 14 Dec 2016 15:28:00 -0000 [thread overview]
Message-ID: <20161214152804.GA2077@ednor.casa.cgf.cx> (raw)
In-Reply-To: <472618a5-9cab-5573-f77e-0e3177557732@gmail.com>
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.
next prev parent reply other threads:[~2016-12-14 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <90156ed9-3ba3-3563-5f90-b6424041acca@gmail.com>
[not found] ` <24dbf7dd-8c45-b5cc-ad31-198ab61128ce@gmail.com>
[not found] ` <CACoZoo29vXpb0MzUri+NPJiZ5GSF+VZAykLa+JjS=g0VDEP7Pg@mail.gmail.com>
[not found] ` <CANnLRdiajEiXJ3JgUOwx2XhAMxS7ngHd8PSFLMkmNvc_FH2+ug@mail.gmail.com>
[not found] ` <20161130110601.GH14074@calimero.vinschen.de>
2016-11-30 14:09 ` Eric Blake
2016-11-30 15:25 ` Fwd: " cyg Simple
2016-11-30 15:55 ` Frank Ch. Eigler
2016-11-30 16:00 ` 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 [this message]
[not found] <860417281.1051305.1481544439039.ref@mail.yahoo.com>
2016-12-12 12:10 ` Ian Lambert
2016-12-12 14:54 ` 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=20161214152804.GA2077@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=cygsimple@gmail.com \
--cc=cygwin@cygwin.com \
--cc=fche@redhat.com \
--cc=overseers@sourceware.org \
/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).