From: Duncan Sinclair <sinclair@dis.strath.ac.uk>
To: Mads Martin Joergensen <mmj@suse.de>
Cc: zsh-workers@sunsite.dk
Subject: Re: {SPAM?} Important! Please don't delete.
Date: Fri, 31 Jan 2003 07:36:38 +0000 [thread overview]
Message-ID: <BB9529DC-34EE-11D7-AB82-0003931123E4@dis.strath.ac.uk> (raw)
In-Reply-To: <20030131013551.GA29518@suse.de>
Hi,
On Friday, January 31, 2003, at 01:35 am, Mads Martin Joergensen wrote:
> * Duncan Sinclair <sinclair@dis.strath.ac.uk> [Jan 30. 2003 22:51]:
>> Hi,
>>
>> Did someone say the spam problem had been fixed???
>
> Yes. A spam problem being fixed does not necessarily mean that 100% of
> the spam is gone. These lists have no spam problem anymore. If you're
> that sensitive you would probably have to start learning how to
> spamfilter yourself.
I do have a spam filter - SpamAssassin put the "{SPAM?}" into the
subject of the original message for me.
SpamAssassin scored the message at 23.5, almost 5 times the score of 5
it needs to flag the message as spam.
X-Spamcheck: SpamAssassin (score=23.5, required 5, AS_SEEN_ON,
BULK_EMAIL, CASHCASHCASH, COPY_ACCURATELY, DATE_IN_PAST_12_24,
FINANCIAL, FREE_MONEY, INITIAL_INVEST, JODY, LINES_OF_YELLING,
LINES_OF_YELLING_2, LINES_OF_YELLING_3, MLM, NOT_INTENDED,
NO_REAL_NAME, ONLY_COST, OPT_IN, PARA_A_2_C_OF_1618, READ_TO_END,
RISK_FREE, SECTION_301, SENT_IN_COMPLIANCE, SPAM_PHRASE_21_34,
SUPERLONG_LINE, USER_AGENT_OE)
So I couldn't help wondering why sunsite.dk's spam filter thought the
message was OK...
Sorry for the noise...
Cheers,
Duncan.
prev parent reply other threads:[~2003-01-31 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001600c2ab76$ced38003$51514332@ruivcgh.yfw>
2003-01-30 21:51 ` Duncan Sinclair
2003-01-31 1:35 ` Mads Martin Joergensen
2003-01-31 7:36 ` Duncan Sinclair [this message]
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=BB9529DC-34EE-11D7-AB82-0003931123E4@dis.strath.ac.uk \
--to=sinclair@dis.strath.ac.uk \
--cc=mmj@suse.de \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).