public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@gcc.gnu.org>
To: gcc-help@gcc.gnu.org
Subject: Re: All Kinds Of High Quality Patches With Factory Rate+Fastest Turnaround Time
Date: Tue, 5 May 2020 16:00:26 -0400	[thread overview]
Message-ID: <20200505200026.GA1220@cgf.cx> (raw)
In-Reply-To: <CAH6eHdSpBp=SJmS+VmuMb0fvyPUu4aXfxm0OzB1VCkNe5nQKwA@mail.gmail.com>

On Tue, May 05, 2020 at 08:36:10PM +0100, Jonathan Wakely wrote:
>On Tue, 5 May 2020 at 19:24, Jeffrey Walton via Gcc-help
>Jeffrey Walton wrote:
>> Or better, change the mailing list ToS to include a $10,000 USD fee
>> for each solicitation or piece of spam. Then follow the money. Drag
>> them into court and bankrupt them.
>
>See https://gcc.gnu.org/spam.html
>
>By quoting his email in your reply you've just added another copy of
>it to the list archives, so another link to his site from gcc.gnu.org.

Yeah, imagine my surprise to see two new occurrences of this spam after
I'd blocked the original sender and trained the sapm filter with the
original content.

Now, Jeffrey Walton's email address is likely marked as less trusted
than it was before thanks to their having submitted something that was
previously identified as spam.  That's a side effect of posting spam to
a mailing list.


  reply	other threads:[~2020-05-05 20:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05 16:31 Mark Sloan
2020-05-05 18:13 ` Jeffrey Walton
2020-05-05 18:16 ` Jeffrey Walton
2020-05-05 19:36   ` Jonathan Wakely
2020-05-05 20:00     ` Christopher Faylor [this message]
2020-05-05 20:01       ` spam Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2020-05-01 20:35 All Kinds Of High Quality Patches With Factory Rate+Fastest Turnaround Time Mark Sloan

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=20200505200026.GA1220@cgf.cx \
    --to=cgf-use-the-mailinglist-please@gcc.gnu.org \
    --cc=gcc-help@gcc.gnu.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).