[quote user="KSQR"]

When I activated SpamHalter I ran into a major problem, namely a 250KB file attached to a message got trimmed to under 10KB  Got the file by having the sender resend it and using web mail to retrieve it.  Also noticed that my mail filter to move files with ***SPAM*** prepended to Subject to a separate folder also moved some messages without the ***SPAM*** prefix.

    POP3 serverside filtering rules (if any)
    Global whitelist (if any)

[/quote]

After rerunning the PM install file (v4,70), the problem went away.  :-)

After many years of using PM, I finally edited my global whitelist file, white.pm.  To make editing easier. started by sorting.  The file went from over 500 entries to 383.

KSQR

I am using Pegasus mail and NOT Mercury Mail.

Could someone provide me with step by step instructions to start/implement the Spamhalter option?

I have seen how to setup with Mercury mail but not pegasus. Looks to be a great idea

and I'd just like a step by step process to set up for this old-timeer. Should would appreciate

Start by reading the Help files at:  Tools | Spam and content controls | Spamhalter | Help.

Everything you need is there.

[quote user="caisson"]

Start by reading the Help files at:  Tools | Spam and content controls | Spamhalter | Help.

[/quote]

Excerpt from: Getting started with Spamhalter

"You should not enable Spamhalter until you have a total of around 100 messages of each type that you can use as your initial corpus..."

Most of the spam I get is from addresses in two domains.  This mail is filtered by my web host using Spam Assassin; likely spam is marked with ***SPAM*** prepended to the Subject.  Probably a
little over 90% of all spam is detected with rare false positives.

Will Spamhalter be negatively affected by including spam with ***SPAM*** prepended to the Subject?

KSQR
 

If the message has already been examined and flagged as Spam by your web host, all you need to do is set up a new mail filtering rule (click the Filter button), that detects the string ***SPAM*** in the subject line and code an Action of Delete, then save the rule.  If you want to be a little cautious then change the Action of the rule to Move , and select a folder reserved for suspicious mails.  If you are confident that SpamAssasin is doing a good job for you in flagging suspicious mail, you don't need SpamHalter as well.

Martin 

Thanks everyone for the info

[quote user="irelam"]

If the message has already been examined and flagged as Spam by your web host, all you need to do is set up a new mail filtering rule (click the Filter button), that detects the string ***SPAM*** in the subject line and code an Action of Delete, then save the rule.  If you want to be a little cautious then change the Action of the rule to Move , and select a folder reserved for suspicious mails.  If you are confident that SpamAssasin is doing a good job for you in flagging suspicious mail, you don't need SpamHalter as well.

Martin 

[/quote]

When I activated SpamHalter I ran into a major problem, namely a 250KB file attached to a message got trimmed to under 10KB  Got the file by having the sender resend it and using web mail to retrieve it.  Also noticed that my mail filter to move files with ***SPAM*** prepended to Subject to a separate folder also moved some messages without the ***SPAM*** prefix.

Found that Pegasus Mail works through the anti-spam / filterrule features  in the following order:

    POP3 serverside filtering rules (if any)
    Global whitelist (if any)
    Spamhalter (if the sender is not on the global whitelist and  spamhalter is activated)
    Content control sets in order of occurrence including each black/whitelist (if the sender is not on the global whitelist and content control is activated)
    New Mail filter rules (if any)

KSQR