Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Patrick Ben Koetter (pstate-of-mind.de)
Date: Wed Aug 25 2010 - 16:21:33 CDT
* Stan Hoeppner <stanhardwarefreak.com>:
> Would anyone happen to have an example guide showing the proper
> master.cf and main.cf parameters for setting up daemonized spamassassin
> to run super selectively via FILTER?
> I've reached the point that I'm killing about 98% of my spam load but
> I'm tired of the few phish/419 that make it into my inbox due to "zero
> day" attacks from compromised Hotmail, Yahoo, Squirrelmail, Horde,
> Exchange accounts and the like. I plan on configuring SA to be very
> lean, focusing on body content, bayes, and uribl hits.
> All the config examples I find on the Spamassassin site are geared
> toward a "heavy" setup running ALL mail through SA. I absolutely will
> not do this. I need very selective use of SA, one reason being that I
> have spamtrap mailboxen. Running SA "globally" would probably cause
> problems with this. It should only fire on one or two emails a day,
> which are the ones getting through, and these are to a single recipient
> address, mine. I'm using Dovecot LDA, not procmail etc, so I can't just
> run the spamassassin script (which would actually be much easier to
> implement for what I want to do).
Check out spampd <http://www.worlddesign.com/index.cfm/rd/mta/spampd.htm>:
"(...) It uses an excellent program called SpamAssassin (SA) to do the
actual message scanning. spampd acts as a transparent SMTP/LMTP proxy
between two mail servers, and during the transaction it passes the mail
through SA. (...).
All technical questions asked privately will be automatically answered on the
list and archived for public access unless privacy is explicitely required and
saslfinger (debugging SMTP AUTH):