Difference between revisions of "Spam Mail Filter"

From CsWiki
Jump to: navigation, search
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Personal Spam Folder ==
+
== Personal spam folder ==
  
All the user's suspected spam is put in a personal mail file—''/cs/spam/'''login''' '' (e.g. ''/cs/spam/george'').
+
All the user's suspected spam is put in a personal mail file&mdash;''/cs/spam/'''login''''' (e.g. ''/cs/spam/george''). Note that each message in this file will have an extra header, <tt>X-Spam-Reason</tt>, explaining why it was caught.
  
In order to view the folder, the user can do:
+
Users that have their mail automatically forwarded to ''mail.huji.ac.il'' (see [http://wiki.cs.huji.ac.il/wiki/Mail#Mail.Huji.Ac.Il_Accounts mail.huji.ac.il accounts])
  pine -f /cs/spam/login
+
will not have their mail spam-filtered before forwarding.
 +
 
 +
In order to view the folder from any CSE Linux machine, the user can do:
 +
  pine -if /cs/spam/'''login'''
 
E.g.
 
E.g.
  pine -f /cs/spam/george
+
  pine -if /cs/spam/george
  
Note that each message in this file will have an extra header, <tt>X-Spam-Reason</tt>, explaining why it was caught.
+
== Legitimate mail in spam folder ==
  
== Legitimate Mail in Spam Folder ==
+
Sometimes the heuristic spam-catching algorithm errs and legitimate e-mail is caught in one's ''spam folder''. In such a case, you should put the ''sender address'' of the legitimate e-mail in your ''~/.nospam'' personal exception database described in the next section.
  
Sometimes the heuristic spam-catching algorithm errs and legitimate e-mail is caught in one's ''spam folder''. In such a case, one should either bounce ('b' in Pine) or forward the caught message to the address '''notspam@cs''' so that the spam database will correct itself. Note that this is an automated address so no human will read the contents of the message meant to you.
+
== Personal exception database ==
 
+
In addition to updating the global database, you should put the ''sender address'' of the legitimate e-mail in your ''~/.nospam'' personal exception database descibed in the next section.
+
 
+
== Personal Exception Database ==
+
  
 
Since legitimate e-mail can sometimes be caught in '' /cs/spam/'''login''' '', the user can create a personal exception database '' ~/.nospam '' with a list of sender addresses to pass through to the user's main mail inbox without being put in '' /cs/spam/'''login''' ''&mdash;note that the sender address can be extracted from the <tt>Return-path:</tt> header of the message (visible in full header mode).
 
Since legitimate e-mail can sometimes be caught in '' /cs/spam/'''login''' '', the user can create a personal exception database '' ~/.nospam '' with a list of sender addresses to pass through to the user's main mail inbox without being put in '' /cs/spam/'''login''' ''&mdash;note that the sender address can be extracted from the <tt>Return-path:</tt> header of the message (visible in full header mode).
Line 37: Line 36:
 
  echo '*' > ~george/.nospam
 
  echo '*' > ~george/.nospam
  
== Spam Folder Cleanup ==
+
== Spam folder cleanup ==
  
 
Any message left for more than 30 days in '' /cs/spam/'''login''' '' will be automatically deleted.
 
Any message left for more than 30 days in '' /cs/spam/'''login''' '' will be automatically deleted.
  
 
Hint: if you are going away for more than a month, it's a good idea to disable spam filtering (as explained above) during that time in order to avoid losing legitimate messages caught in the spam filter.
 
Hint: if you are going away for more than a month, it's a good idea to disable spam filtering (as explained above) during that time in order to avoid losing legitimate messages caught in the spam filter.
 
== Spam E-mail that Isn't Caught ==
 
 
Since the spam-catching algorithm is heuristic, it doesn't catch all spam and some spam e-mailings manage to get through. If spam reaches your regular mailbox (and, of course, you haven't turned off spam filtering in your ''~/.nospam'' file), then you should bounce ('b' in Pine) or forward the spam message to the address '''spam@cs''' to update the global spam database.
 

Latest revision as of 07:47, 16 August 2017

Personal spam folder

All the user's suspected spam is put in a personal mail file—/cs/spam/login (e.g. /cs/spam/george). Note that each message in this file will have an extra header, X-Spam-Reason, explaining why it was caught.

Users that have their mail automatically forwarded to mail.huji.ac.il (see mail.huji.ac.il accounts) will not have their mail spam-filtered before forwarding.

In order to view the folder from any CSE Linux machine, the user can do:

pine -if /cs/spam/login

E.g.

pine -if /cs/spam/george

Legitimate mail in spam folder

Sometimes the heuristic spam-catching algorithm errs and legitimate e-mail is caught in one's spam folder. In such a case, you should put the sender address of the legitimate e-mail in your ~/.nospam personal exception database described in the next section.

Personal exception database

Since legitimate e-mail can sometimes be caught in /cs/spam/login , the user can create a personal exception database ~/.nospam with a list of sender addresses to pass through to the user's main mail inbox without being put in /cs/spam/login —note that the sender address can be extracted from the Return-path: header of the message (visible in full header mode).

Example contents of ~/.nospam :

haim@eng.tau.ac.il
*@wildnose.com
*@*.huji.ac.il
jody@*
jay@natlib.com
melody@math.gmu.edu

The above ~/.nospam file allows both individual addresses such as jay@natlib.com and groups of addresses such as all users from the wildnose.com domain and all users in subdomains of HUJI plus the login jody from any domain.

An entry of '*' (asterisk) will cause all suspected spam to pass through to your regular mailbox effectively disabling spam filtering.

Example:

echo '*' > ~george/.nospam

Spam folder cleanup

Any message left for more than 30 days in /cs/spam/login will be automatically deleted.

Hint: if you are going away for more than a month, it's a good idea to disable spam filtering (as explained above) during that time in order to avoid losing legitimate messages caught in the spam filter.