On 2/18/2005 2:33 PM, Matt Kettler wrote:
> At 02:21 PM 2/18/2005, Eric A. Hall wrote:
> 
>>That's not mutually exclusive, and is actually somewhat inclusive. I mean,
>>if people are using the spamassassin script on a low-volume basis, then
>>there's a low volume of SQL/LDAP lookups, so the complaint is nulled.
> 
> True, but it's also intended for users who aren't sophisticated enough to 
> run a daemon, in which case they aren't sophisticated enough to run SQL.

At least we're making some progress here... As to the argument about
sophistication, the same could be said for any number of other things in
the spamassassin kit. Seems kind of arbitrary to draw the line here when
we've got more complexity in the various plugins, whitelist and blacklist
maintenance, bayes maintenance, etc. And in a lot of ways, allowing for
per-user SQL/LDAP configs and providing a nice hosted GUI front-end to
their settings removes a lot of that complexity. So from that perspective,
adding it to the spamassassin script would reduce some complexity.

> However, you don't appear to be using the spamassassin command line anyway.
> 
>>I'm using a third-party script for the in-line proxy, and it daemonizes
>>spamassassin on its own.
> 
> at which point the addition to the spamassassin command-line becomes 
> irrelevant, because you aren't using spamassassin. (it's impossible to 
> daemonize the spamassassin command line tool.)
> 
> You need it added to your third-party script, as, based on your 
> description, it's invoking the SA perl API's directly.

http://www.worlddesign.com/index.cfm/rd/mta/spampd.htm is what I'm
currently using. It doesn't provide any additional parameters over regular
spamassassin configs, and whatever I do to spamassassin is picked up
transparently. I'm having a couple problems with some of it (SPF errors
are being picked up and causing problems for it, apparently) but I haven't
found anything else that fits into the postfix->sa->postfix->cyrus model
in a better way so I'm inclined to keep using it.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/

Reply via email to