Antispam software
home
spam is growing >>
advice >>
tools >>
downloads

Created and maintained
by Jacek Olszewski

Menu software by
PHP Layers Menu System

No Software Patents

Personal Email Filter

Installation

Files in the compressed tarball

README
INSTALL
CHANGELOG
gpl.txt
pef.inc
pef-down.php
pef1.php
pef2.php
pef3.php
.forward
.procmailrc
s.lst
c.lst
w.lst
b.lst
r.lst

Where to put them

All pef* files should be put into a directory accessible by the web server but only for those who have been authenticated. In the configuration of apache it may be specified like this: 
# fepclients
<Directory /web/fep>
allow from all
AuthType Basic
AuthUserFile /usr/local/fepclients
AuthName fepclients
require valid-user
</Directory>
where /web/fep contains all the pef* files, and /usr/local/fepclients is a file with user names and passwords of the clients.

If mod_php is used in safe mode, the pef* files should have the same group as all fepclients, and in php.ini the following directives should be placed: 

safe_mode = On
safe_mode_gid = On
The files .forward, .procmailrc and all *.lst should be replicated in client mail directories. The *.lst files should be owned by the clients, and made group readable and writeable, with the same group as the php scripts.

Configuration

There are only a few items that need to be modified at the beginning of pef.inc and .procmailrc, so that the domain name, the administrator's email address, etc., are all correct for the server where pef runs.

Log file

In .procmailrc you will find the line

LOGF=$HOME/mail.log

Its effect is a growing log of messages in the user directory. The line should either be commented out or the log should be rotated daily or weekly, and perhaps made available to the user through a web interface.

Warning

Pef has been tested on sendmail, procmail and apache with mod_php. However, the author takes no responsibility for any effects, good or bad, of running pef on any server whatsoever.

next