From: Lee <ler762@gmail.com>
To: overseers@sourceware.org
Subject: DMARC-aware version of ezmlm-send
Date: Mon, 20 Jan 2020 22:20:00 -0000 [thread overview]
Message-ID: <CAD8GWsterGFpRuXceRVwyHn4a-diD2FHWFSdBt0Y_X9YjTPnAQ@mail.gmail.com> (raw)
Wasn't this fixed in 2016 by cgf?
> Messages to you from the cygwin-announce mailing list seem to
> have been bouncing.
> ...
> Remote host said: 550-5.7.26 Unauthenticated email from epa.gov is not accepted due to domain's
> 550-5.7.26 DMARC policy.
ezlm-send fix notification:
---------- Forwarded message ----------
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
Date: Sat, 10 Dec 2016 15:39:47 -0500
Subject: Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
To: eblake@redhat.com, cygsimple@gmail.com, "Frank Ch. Eigler"
<fche@redhat.com>, overseers@sourceware.org, cygwin@cygwin.com
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
---------- Forwarded message ----------
From: cygwin-announce-help@cygwin.com
Date: 20 Jan 2020 21:15:09 -0000
Subject: ezmlm warning
To: ler762@gmail.com
Hi! This is the ezmlm program. I'm managing the
cygwin-announce@cygwin.com mailing list.
Messages to you from the cygwin-announce mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.
If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the cygwin-announce mailing list,
without further notice.
I've kept a list of which messages from the cygwin-announce mailing list have
bounced from your address.
Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per request),
send an empty message to:
<cygwin-announce-get.123_145@cygwin.com>
To receive a subject and author list for the last 100 or so messages,
send an empty message to:
<cygwin-announce-index@cygwin.com>
Here are the message numbers:
9379
--- Enclosed is a copy of the bounce message I received.
Return-Path: <>
Received: (qmail 51626 invoked for bounce); 8 Jan 2020 18:08:16 -0000
Date: 8 Jan 2020 18:08:16 -0000
From: MAILER-DAEMON@sourceware.org
To: cygwin-announce-return-9379-@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.
<ler762@gmail.com>:
User and password not set, continuing without authentication.
<ler762@gmail.com> 64.233.180.27 failed after I sent the message.
Remote host said: 550-5.7.26 Unauthenticated email from epa.gov is not
accepted due to domain's
550-5.7.26 DMARC policy. Please contact the administrator of epa.gov domain if
550-5.7.26 this was a legitimate mail. Please visit
550-5.7.26 https://support.google.com/mail/answer/2451690 to learn about the
550 5.7.26 DMARC initiative. g4si273934oia.179 - gsmtp
next reply other threads:[~2020-01-20 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 22:20 Lee [this message]
2020-01-21 2:04 ` Christopher Faylor
2020-01-21 3:46 ` Lee
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=CAD8GWsterGFpRuXceRVwyHn4a-diD2FHWFSdBt0Y_X9YjTPnAQ@mail.gmail.com \
--to=ler762@gmail.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).