I'd do your filtering at the gateway level, NOT in the client (PHP web
page). While squirrelmail CAN look at various DNSBL lists, its more
appropriate to deny the spam before it gets into the box. I use a
combination of qmail+rblsmtpd and spamassassin (with the "web bugs"
score turned up to 3.5 or so) and procmail, and I get about 1 spam a
day. I see in my server logs that my SMTP server is denying about 30
connections a day. I haven't yet seen how many spamassassin cleans up
after that, but like I said, its all done pre-squirrelmail.
THAT being said, if you have many non-savvy users, assassind or a very
basic procmail/spamassassin setup might be your best way to go. Set up
an MTA "sandwich" like so:
MTA1 on port 25 (does antirelay), force delivers all mails to assassind
|
assassind on port 7025 (or something), relayhost=localhost:8025
|
MTA2 on localhost:8025, does final delivery to maildirs.
Ed
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
--
squirrelmail-users mailing list
List Address: [EMAIL PROTECTED]
List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
