1. Install SA on each machine in a central directory. Mine is "/usr/data/spamassassin"
In SA dist directory:
perl Makefile.PL PREFIX=/usr/data/spamassassin/usr SYSCONFDIR=/usr/data/spamassassin/etc
make
make install
2. Run spamd at system startup time for each machine. It's a good idea to do spamd/spamc for sitewide.
3. Use procmail for individual delivery preferences. For example, if a user wants to opt-in, place something like the
following in the .procmailrc file in the user's home directory:
:0fw
* < 256000
| /usr/data/spamassassin/usr/bin/spamc
:0:
* ^X-Spam-Flag: YES
${HOME}/.imap_folder/Blocked
Also, place something like the following in the .forward file in the user's home directory:
"|IFS=' '&&exec /usr/local/bin/procmail -f-||exit 75 #username"
Hope this helps,
Patrick
On Monday, November 25, 2002, at 05:50 PM, Ben M. VanWagner wrote:
Hi I am a newbie but couldnt find any relevant info on this subject
I would like to run a sitewide incoming mail server that is running spamassassin.
I have configured one for a customer to handle their mail just fine.
my problem is that I have 4 different mail servers with 4 different user lists and nearly 800 domains
I want customization of user settings (ie being able to opt out of it)
is there a way to do this ??
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
