From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: Re: Mailing list subscription problems
Date: Mon, 19 Dec 2022 17:24:52 -0800 [thread overview]
Message-ID: <9c22b0d4-bf92-269b-82e9-a9e7e9121dc1@jhmg.net> (raw)
In-Reply-To: <Y6C+vKi8WBgsiUB4@calimero.vinschen.de>
On 12/19/22 11:42, Corinna Vinschen via Cygwin wrote:
>>
> Actually, Google hasn't relaxed their filtering, rather the DNS record
> of the cygwin.com domain was the culprit. It didn't have the required
> (by Google) DKIM/SFP records. This has been rectified last week,
> fortunately, so this shouldn't happen again. I re-enabled mail for
> all accounts having been disabled due to bounces.
Off-topic but I can't resist :-) The real irony here is that
while Google has draconian anti-SPAM filtering for _incoming_
mail, they are now one of the leading senders of SPAM, and
emails to their abuse address bounce. Sigh!
(I'll shut up now)
--
Jim Garrison
jhg@acm.org
prev parent reply other threads:[~2022-12-20 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 15:08 Kyle Marek
2022-12-19 17:50 ` David Standish
2022-12-19 19:27 ` William Deegan
2022-12-20 9:00 ` Csaba Raduly
2022-12-19 19:42 ` Corinna Vinschen
2022-12-19 19:45 ` Kyle Marek
2022-12-20 1:24 ` Jim Garrison [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=9c22b0d4-bf92-269b-82e9-a9e7e9121dc1@jhmg.net \
--to=jhg@jhmg.net \
--cc=cygwin@cygwin.com \
--cc=jhg@acm.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).