Personally I don't like using Mail::Spamassassin. Its just a resource hog.

Really, the most efficient way is to just talk to spamd directly using perl sockets. The most basic, and thus most impervious to different versions of spamassassin is to use spamc. And, the most feature rich way to go is to use Mail::Spamassasin.

You choice depends on your needs (speed, compatibility, or features?). I meant to write a new spamassassin plugin that has the capability to work in any one of these 3 ways, not just one. One day when there is time growing on trees...

Aran


Skaag Argonius wrote:
Hi Andrew,

You'r right. I didn't think about that. Aran did write a replacement plugin
called spamassassin_direct.
However, I was under a lot of pressure to make it all work as smoothly and
quickly as possible.
This is why the plugin looks like it does. I will however try to make
another version which uses Mail::SpamAssassin.

Thanks for the comment! :)

Aric






-- Aran Clary Deltac http://www.arandeltac.com/ [EMAIL PROTECTED] Intergalactic Camel Coder




Reply via email to