Spamassassin Correct ?

[Glen Turner]

Brian wrote:
> Anyway I found the emails concerned. They were caught by Spamassassin, this
> system. Spamassassin reported the two emails thus. 
> 
> Does this seem ok ?

After a long time I've worked out how to make SA behave.

Have it add headers and do nothing else.  Get procmail to deliver suspected
spam into the IMAP Junk folder.

Set up a cron job to run sa-learn -- spam is in Junk, all other folders
except Trash are good.

Tell your users to move spam to the Junk folder (lots of e-mail clients
have a button for this). Tell them to retrieve real messages from Junk
and move them to another folder.

Once every month purge Junk more than three months old (that's a complicated
script as you need to use the last Received header, not the Date).

This seems to be the best fit to the current IMAP mail clients, gets
the feedback loop into SA working and lets people search for misclassified
mail.

Garry wrote:
> My grizzle is that SA government, local government, plus at least one ISP,
> have spam filters that eat things in some remote place that I have no way
> to access or interact with, and don't tell me about it.

If that's your only grizzle you're doing well. On my list are:

 - mail servers that don't support IMAP over SSL and AuthSMTP over the Submission
   port, forcing me to run a tunnel rather than use the same configuration
   everywhere.

 - mail servers that don't support IMAP/SSL and AuthSMTP/Submission at all.

 - corporate mail servers with small mailbox sizes. Corporate disk is <1.30/GB.
   Spend more than $5 you cheapskate.

 - local councils who think it is OK for the council CEO to read the e-mail
   of the elected councilors. That's a step worse than companies which think
   it is OK to read employee's e-mail.

 - mail servers which add disclaimers. Breaks encryption and you can't get rid
   of the disclaimer. The classic being the e-mailed tender response I got
   in a mail which said it wasn't an "official communication" and the mail I
   get which "may be privileged" (like I'm going to pay my lawyers to work
   out if it is or not) -- well both of those are going straight into the bin.

 - networks which stop IMAP/SSL and AuthSMTP/Submission except to their
   own servers.  SMTP, fair enough, but blocking SMTP/Submission is evil.