From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: RE : SOT Annual Meeting - Attendees List
Date: Fri, 02 Mar 2018 15:28:00 -0000 [thread overview]
Message-ID: <4d864792-798e-875d-4e27-05c7425131e3@gmail.com> (raw)
In-Reply-To: <pximrcowi9sftvnqgvn7pr4o.1520003532110@email.android.com>
On 02/03/2018 16:12, Jeff Lightner wrote:
>
>
> Cygwin continues to pass these spam messages about selling email and other lists. In the meantime it refuses legitimate emails simply due to corporate legal disclaimers that senders don't control.
> No doubt I'll get banned but I can't help pointing out such ludicrous disparities.
cool down. No one here is managing the spam filter
that is common to a lot of mailing lists
https://sourceware.org/lists.html#faqs
You can highlight the issue at the address mentioned here
https://sourceware.org/suggestions.html
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-03-02 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 15:11 Jeff Lightner
2018-03-02 15:28 ` Marco Atzeri [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-02 14:42 Ivana Cooper
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=4d864792-798e-875d-4e27-05c7425131e3@gmail.com \
--to=marco.atzeri@gmail.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).