From: "Gregg C Levine" <obiwanthejediknight@worldnet.att.net>
To: Linux-8086 - ELKS <Linux-8086@vger.kernel.org>
Subject: Spam from a supposed Yahoo Groups moderator
Date: Sun, 6 Oct 2002 13:56:56 -0400 [thread overview]
Message-ID: <002f01c26d61$c36310e0$1aa2580c@who> (raw)
Hello from Gregg C Levine
Folks, ignore that invitation from that fraud of a supposed Yahoo Groups
moderator. He had no right to spam our group doing that, and I have
contacted Yahoo's crappy abuse desk with the notion that he should be
investigated by then, As far as what happens next, that'll depend on Yahoo.
More on that subject later. Can the list manager contact me, off list,
regarding what steps are being taken to prevent spam from landing on our
group? Also, that includes that kind of garbage as well. I'm not saying we
should make it difficult for folks who use their Yahoo mail accounts for
this list, only garbage that comes from people like the subject.
Gregg C Levine obiwanthejediknight@att.net
<This signature will be replaced, pending an approval from the Jedi Council.
>
next reply other threads:[~2002-10-06 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-06 17:56 Gregg C Levine [this message]
2002-10-07 9:16 ` Spam from a supposed Yahoo Groups moderator jb1
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='002f01c26d61$c36310e0$1aa2580c@who' \
--to=obiwanthejediknight@worldnet.att.net \
--cc=Linux-8086@vger.kernel.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