public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Macek <david.macek.0@gmail.com>
To: cygwin@cygwin.com, fche@redhat.com, overseers@sourceware.org
Subject: Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
Date: Mon, 12 Dec 2016 07:58:00 -0000	[thread overview]
Message-ID: <f5970db5-84b6-7fc8-ba91-36ce9e91ceb5@gmail.com> (raw)
In-Reply-To: <20161210203947.GA434@ednor.casa.cgf.cx>

[-- 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 --]

  reply	other threads:[~2016-12-12  7:58 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 [this message]
2016-12-14 14:16             ` cyg Simple
2016-12-14 15:28               ` Christopher Faylor
2016-12-14 21:40                 ` cyg Simple
     [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=f5970db5-84b6-7fc8-ba91-36ce9e91ceb5@gmail.com \
    --to=david.macek.0@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).