From: Lee <ler762@gmail.com>
To: overseers@sourceware.org
Subject: Re: DMARC-aware version of ezmlm-send
Date: Tue, 21 Jan 2020 03:46:00 -0000 [thread overview]
Message-ID: <CAD8GWssCMvfGotNhmm0n2Edgtqt1tFkhZhwdJn0xDfe8tKwLpA@mail.gmail.com> (raw)
In-Reply-To: <20200121020413.GA4481@cgf.cx>
On 1/20/20, Christopher Faylor
<cgf-use-the-mailinglist-please@sourceware.org> wrote:
> On Mon, Jan 20, 2020 at 05:20:19PM -0500, Lee wrote:
>>Wasn't this fixed in 2016 by cgf?
>>
>>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
>
> So, are you saying it took you 3+ years to notice that it wasn't fixed
> or that something stopped working recently?
I'm saying this was the first cygwin bounce warning message I've seen
in ... I don't remember how long. So it seems like a recent thing,
but it's possible that I just haven't been paying enough attention
Lee
prev parent reply other threads:[~2020-01-21 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 22:20 Lee
2020-01-21 2:04 ` Christopher Faylor
2020-01-21 3:46 ` Lee [this message]
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=CAD8GWssCMvfGotNhmm0n2Edgtqt1tFkhZhwdJn0xDfe8tKwLpA@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).