From: Backwoods BC <completely.and.totally.trash@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: cygwin.cygwin.narkive.com
Date: Mon, 13 Nov 2023 23:33:45 -0800 [thread overview]
Message-ID: <CAKwdsS_r-aREHf7+C9Gkx16GsscyNGDcxuB5r2QW+U-CBuiC-Q@mail.gmail.com> (raw)
In-Reply-To: <CAMQrdZ64J6s9mpf36yD1tvkahrOxyE09rvN0kRHfraTqJGh3fg@mail.gmail.com>
On Mon, Nov 13, 2023 at 10:17 PM Glenn Bogdan via Cygwin
<cygwin@cygwin.com> wrote:
> SPAMSPAMSPAMSPAMSPAMSPAM
Completely off topic here, but is there an automated way to have the
mail server report these spams to the US FTC? Or is it simply not
worth the effort?
next prev parent reply other threads:[~2023-11-14 7:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 6:16 cygwin.cygwin.narkive.com Glenn Bogdan
2023-11-14 7:33 ` Backwoods BC [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-16 23:06 cygwin.cygwin.narkive.com Alyssa Hoffman
2024-03-30 2:01 cygwin.cygwin.narkive.com Gregory J Miller
2024-02-27 22:23 cygwin.cygwin.narkive.com Ruth Bible
2024-01-13 19:50 cygwin.cygwin.narkive.com Evelyn Kanter
2023-12-19 6:53 cygwin.cygwin.narkive.com Edwards Beverly
2023-12-13 20:40 cygwin.cygwin.narkive.com Bethany Martinez
2023-11-15 20:54 cygwin.cygwin.narkive.com Crystal Stanley
2023-10-25 14:56 cygwin.cygwin.narkive.com Alicia Hogan
2023-10-21 6:30 cygwin.cygwin.narkive.com Harry Cox
2023-09-29 5:42 cygwin.cygwin.narkive.com Ethan Dixon
2023-09-26 8:51 cygwin.cygwin.narkive.com Samantha Harris
2023-09-18 18:33 cygwin.cygwin.narkive.com Kate Ross
2023-09-09 15:38 cygwin.cygwin.narkive.com Sylvia Wilson
2023-08-08 5:30 cygwin.cygwin.narkive.com Harry Cox
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=CAKwdsS_r-aREHf7+C9Gkx16GsscyNGDcxuB5r2QW+U-CBuiC-Q@mail.gmail.com \
--to=completely.and.totally.trash@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).