|
|
Sample server- and client-side filters for X-Perlmx-Spam:
Since we will only be tagging spam with a header that indicates a likely
percentage that a given message is spam, dealing with that automatically
will be left up to the end user.
Should you want to have your mail server or client automatcially handle
mail that had been tagged as likely to be spam, here are some sample
user-contributed methods. To submit a suggestion, please send mail to <isf@listserv.tamu.edu>
.
Calypso 3.30
[Client filter] |
| Submitted by: Susan Cook |
Mailbox->Filters->New
Enter filter name (i.e.; Spam), then click [Add]
Pattern to search for: *Gauge=XXXXXX*
In: Message Header
Action: Move to Folder (select folder or create folder)
[Ok], then [Save]
Under your mailbox name, select Filter. Select the spam filter you
just created, right click on it, and assign it to your account. To
filter existing message in your Received Mail folder, right click
on it. Filter All Messages->Spam (or whatever you called it)
NOTE: For "Gauge=XXXXXX", each X equals 10%. Choose the percentage
that best meets your needs.
|
|
Eudora
[Client filter] |
| Submitted by: Pierce Cantrell to ISF |
Longer document describing the use of "Eudora Filters"
|
|
Exchange 2000
[Server side filtering] |
| Submitted by: Matthew Hudson to ISF |
Longer document describing the use of "Event Sinks"
|
|
| GroupWise |
| Submitted by: Kevin Davis to ISF |
'Not all mail clients have access to the "X-PerlMx-Spam" header info'
|
|
| Lotus Domino |
| Submitted by: Susan Cook |
Domino 6 has the capability for server-side spam filtering using
its own criteria.
|
|
Mercury/32 or Pegasus Mail
[Client filter] |
| Submitted by: David Kocmoud to ISF |
#To filter all messages containing the X-Perlmx-Spam header:
If expression headers matches "X-Perlmx-Spam:*" [your action goes here]
#To filter only messages containing the X-Perlmx-Spam header with a
#gauge of 90% or higher:
If expression headers matches "X-Perlmx-Spam:*Gauge=XXXXXXXXX*" [your action goes here]
#Mercury/32 also has its own anti-spam content control feature. If you
#wish to encoporate the X- Perlmx-Spam header score within your
#Mercury/32 content control filters, you can do the following (90% or
#above):
If header "X-Perlmx-Spam" contains "Gauge=XXXXXXXXX" weight 50
#For selectively picking out individual rules within the X-Perlmx-Spam
#header, us e the following:
If header "X-Perlmx-Spam" contains "NIGERIAN_SCAM" weight 50
|
|
Netscape Mail 7
[Client filter] |
| Submitted by: Susan Cook |
Tools->Message Filters New
Add a custom header of "X-Perlmx-Spam"
Choose "X-Perlmx-Spam" from the drop down
Choose "contains"
Enter: Gauge=XXXXXX
Choose "Move to Folder" from the drop down under "Perform this
action", and enter the folder or create a new Spam folder.
Click ok, then make sure it is enabled.
This filter will not handle existing messages; however you can
Search Messages with the same criteria as your filter to find and
move spam into the spam folder.
|
|
Outlook
[Client filter] |
| Submitted by: Kirk Hausman to ISF |
Within Outlook, select from the header: Tools -> Rules Wizard, then
click the New button to create a new rule.
Select to 'Apply this rule after the message arrives' then 'With
Probability=9 in the message header' (for a 90% score), then 'Move it
to folder' and apply the rule. I use separate rules for the
100% (Probability=100), 90% (Probability=9), 80% (Probability=8), and
all other (Probability=) to sort all of the potential-spam into
different folders.
It is not necessary in order to be as complex as this in your setup.
You may define a simpler set of rules, or put all above 80% into the
trash, or whatever else as desired.
|
|
procmail
[Server-side filtering] |
| Submitted by: ? |
Save to a spam folder for later reviewing:
:0
*^X-Perlmx-Spam:
spam
|
|
|
