1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
README for "filter v2.6", the email filtering program originally from ELM
This program is designed to look at each piece of email you get "locally",
and separate it off into different "mail folders".
It relies on you being able to create a $HOME/.forward file, or equivalent,
that lets you "pipe" incoming email to a filter program.
It takes action based on rules you put in $HOME/.filter/filter-rules.
(NOTE: UNIX-style 'mail folders' are actually text files!!!)
Those "folders" can normally then be read by the same program you normally
read your email with.
Why use 'filter', not 'procmail' ? Because procmail is too arcane.
It's kind of a "why use pico, when there's emacs?" thing.
I like to use actual english in config files whenever possible, so filter
is definately MY choice of email filtering programs.
See the manpage, or other stuff in the 'doc' subdirectory, for more details.
Philip Brown
filter@bolthole.com
October 2003
It only gets better, if YOU ask for stuff!
------------------------------------------------------------
------------------------------------------------------------
Safety note: If you are unsure of what you are doing, or just paranoid, you
should hook filter into your email, by creating the file $HOME/.forward
and putting in it
/path/to/safetymbox,"|filter"
"normally", you would just put "|filter", to pass all email to the filter
program. But this also saves all email you receive, to whatever safetymbox
you define. Be sure to clean it out regularly!
Also, you should periodically clean out your filter logfile. It keeps a log of
all email it sees, in $HOME/.filter/filter-log
"filter -S" will summarise the logfile for you.
"filter -c -s" will clean out the logfile.
YOU MUST HAVE -s with -c !!!
You might want to glance at the BUGS file, also.
|
