From: Digby Tarvin <digbyt@acm.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] INVESTMENT & ASSISTANCE
Date: Sun, 16 Jun 2002 22:12:51 +0100 [thread overview]
Message-ID: <200206162112.WAA22193@cthulhu.dircon.co.uk> (raw)
In-Reply-To: <20020616170512.14978199BB@mail.cse.psu.edu> from THOMAS EDWARDS at "Jun 16, 2002 07:05:20 pm"
I normally feel obliged to report this sort of blatant fraud when
I receive it directly, but there isn't enough header information
when it comes via a list. Is someone taking care of it?
It always seems a little irresponsible to me to just install filters
and leave inexperienced net users to the mercy of the con men....
I would imagine that with the formidable combined expertise of the
subscribers on this list, you would have to be pretty stupid to spam
it.
Anybody got any good tips for effective ways to deal with spammers?
I am fequently frustrated by NICs that allow IP registrants to privide
false (or no) e-mail address with which to report abuse.
DigbyT
THOMAS EDWARDS:
> From 9fans-admin@cse.psu.edu Sun Jun 16 21:38:46 2002
> Delivered-To: 9fans@cse.psu.edu
> From: "THOMAS EDWARDS" <thomyeddy@yahoo.co.uk>
> To: 9fans@cse.psu.edu
> Subject: [9fans] INVESTMENT & ASSISTANCE
> STRICTLY CONFIDENTIAL & URGENT.
>
> I am Mr, Thomas Edwards a native of Cape Town in
> South Africa and I am an Executive Accountant with
> the
etc.
--
Digby R. S. Tarvin digbyt@acm.org
http://www.cthulhu.dircon.co.uk
next parent reply other threads:[~2002-06-16 21:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020616170512.14978199BB@mail.cse.psu.edu>
2002-06-16 21:12 ` Digby Tarvin [this message]
2002-06-17 0:49 ` Scott Schwartz
2002-06-18 5:23 ` Lucio De Re
2002-06-17 1:28 presotto
2002-06-17 1:45 Russ Cox
2002-06-18 6:06 Russ Cox
2002-07-19 0:52 [9fans] useful language extension, or no? David Gordon Hogan
2002-07-19 12:53 ` Digby Tarvin
2002-07-19 15:41 ` Mike Haertel
2002-07-19 18:09 ` Digby Tarvin
2002-07-19 18:38 ` Scott Schwartz
2002-07-19 19:07 ` Digby Tarvin
2002-07-29 16:01 ` Ralph Corderoy
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=200206162112.WAA22193@cthulhu.dircon.co.uk \
--to=digbyt@acm.org \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).