Spam detection software, running on the system "snow", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or block
similar future email. If you have any questions, see
[EMAIL PROTECTED] for details.
Content preview: Hi all. I just successfully got Spamassassin running on
my email server and wanted to share the news! In my case, I'm running
Postfix, Courier-Imap (for POP3), and MailDir. All the instructions
I've found are for other mail systems, or for systems using ProcMail
(instead of MailDir). I came across this URL tonight after looking
through the documentation on the Spamassassin web site:
http://www.geekly.com/entries/archives/00000155.htm. It details
configuration for ProcMail, but after looking through the document, I
realized I didn't need to care. The ProcMail part is for local
delivery, and I have Postfix/MailDir handling that. So, by following
the steps up to, but NOT including the ProcMail configuration things
seemed to work. [...]
Content analysis details: (84.2 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
1.3 PLING_PLING Subject has lots of exclamation marks
83 AWL AWL: Auto-whitelist adjustment
--- Begin Message ---
Hi all.
I just successfully got Spamassassin running on my email server and wanted
to share the news!
In my case, I'm running Postfix, Courier-Imap (for POP3), and MailDir. All
the instructions I've found are for other mail systems, or for systems using
ProcMail (instead of MailDir). I came across this URL tonight after looking
through the documentation on the Spamassassin web site:
http://www.geekly.com/entries/archives/00000155.htm. It details
configuration for ProcMail, but after looking through the document, I
realized I didn't need to care. The ProcMail part is for local delivery,
and I have Postfix/MailDir handling that. So, by following the steps up to,
but NOT including the ProcMail configuration things seemed to work.
Of course, I did some testing. Spamassassin has two sample files in the
/usr/share/doc/Mail-SpamAssassin folder for testing. One get's treated as
spam, and the other doesn't. I emailed the sample spam file to myself as
root. Well, the mail wasn't filtered, but that's normal because the mail
was sent from a trusted network (internal network). So, I forwarded the
email to my work address. Wow! Outgoing mail gets filtered too! The
message that came up in my work address had already been filtered, and I got
to see the filter report. Next, I forwarded the suspect message back to my
private address, and it too got filtered.
The key here is that your mail system should be fully functional before you
apply these instructions - otherwise you don't know why you're getting your
mail. So don't try applying SpamAssassin to a brand new mail server - wait
till it's been running reliably for a couple of days at least.
Anyways, I'm just all excited that I got it working... Next I need to
tackle the Antivirus problem... but that's a different project... <grins>
Shawn
--- End Message ---
