public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Mailing list subscription problems
Date: Mon, 19 Dec 2022 20:42:52 +0100	[thread overview]
Message-ID: <Y6C+vKi8WBgsiUB4@calimero.vinschen.de> (raw)
In-Reply-To: <CADX9Ks-xi2w5bsn_W3fyQp-uTkiQ3A-=Vs_=WaHyivJhGTpZHw@mail.gmail.com>

On Dec 19 12:50, David Standish via Cygwin wrote:
> On 12/19/22, Kyle Marek via Cygwin <cygwin@cygwin.com> wrote:
> > (CC'd the public mailing list for visibility of problems that may be
> > affecting others)
> >
> > Hello,
> >
> > Today I received an email from cygwin-bounces@cygwin.com with the
> > subject line of "You have been unsubscribed from the Cygwin mailing
> > list". I also just noticed that my Cygwin directory doesn't have any
> > emails since the email identified by the following headers:
> > [...]
> 
> I've experienced the same problem.  I reactivated my subscription a
> couple times.
> 
> More cygwin mail has been getting through to me that last few days.
> Hopefully google has relaxed their filtering,

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.


HTH,
Corinna

  parent reply	other threads:[~2022-12-19 19:42 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 [this message]
2022-12-19 19:45     ` Kyle Marek
2022-12-20  1:24     ` Jim Garrison

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=Y6C+vKi8WBgsiUB4@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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).