#FILE
#	$Id: HOWTO,v 1.3 2004/01/20 14:04:50 ggw Exp $
#	HOWTO
#PURPOSE
#	Examples on how to use this alpha system.
#
#IMPORTANT
#	General info in the README file in this dir.
#NOTES
#	mysqlSendmail 1.2 now can handle and automate...all it needs is the
#	notifier.pl in the right place and it and realted files setup correctly.


---
New mysqlSendmail (cluster) uMailFilter automated method

Explanation:
eMail arrives to mail.isp.net, there it is processed via spamc/spamd with all
the cool community based real-time fuzzy hashed spam mail id lists.
Once spamd is done per user .procmailrc continues processing and marks email with
points >min and <max but this mail stays in regular mail drop. Mail >=max is
sent to another mysqlSendmail controlled server (hence the cluster term used 
herein.)
User only gets one spam-isolation message per day courtesy of the dbm hash
data base notify.pl script.
Here the user can pick-it up and/or bulk erase. That server admin can easily
implement a system for automatically deleting the unchecked more than ex. 
30 days old most likely 100% spam trash.

How it was implemented:
We hacked tConfiguration to provide procmail templates. procmail-default or a 
user specific (user by their login) procmail-login template
When adding a new user if uMailFilter points to a tMailFilter.cLabel called 
procmail, then the user is added with her own .procmailrc based on the 
tConfiguration template.
You still must have setup all the needed spam-system items in the correct places.
And you also must have a spam isolation mysqlSendmail controlled server running.
This last server is specified in the tConfiguration.cValue as 
server=server.isp.net.
This server.isp.net usually will have a webmail to access the isolated spam 
mail drop via localhost imap. Squirrelmail works fine.
More info in ../docs/tutorial.html and README



---
Old manual non mysqlSendmail.cgi method

---
Adding new users to server1/server2 spam isolation system


1-. Edit users_list.txt and add one per line all the NEW users only.
2-. Run #./procmailrc.pl newusers.txt
3-. Add user to easily read allusers_list.txt: #cat newusers.txt >> allusers.txt
4-. Run #cat /dev/null > newusers.txt to prep for 1-.


---
Testing

Use the user added above -for example tester1 and the spam.txt file like so:

#mail -v -s testing123 tester1 < spam.eml

then

#tail -20 /var/mail/tester1

Also send a non spam message

#mail -v -s testing123 tester1 < ham.eml

then again

#tail -20 /var/mail/tester1


And also check the external spam system (server2 etc.) Repeat and check for only one spam 
quarantine msg per day.

---
Notes

We need more spam.txt files with known points and rules for better testing.
The AWL rule needs to learn what is spam and what is not...so the notspam.txt
must be sent several times with current version of spamd.

Make sure that the isomsgsent.db and isomsgsent.log are chmod 666, since all 
user procmails must be able to write to them. Security risk: low, since all they
could possibly do would be mess up the per day control of iso messages sent.