Hello guys! :-)

I've taken the time with all the versions of the spamassassin plugins that I
found on this mailing list, and came up with a version that works real well
for me.

Here's a list of the problems that I've managed to fixed, with my barely
minimal perl knowledge:

* Some versions died with large emails, resulting in loss of mail
* Some versions did not parse the result of spamassassin correctly
* Some versions did not use spamc, resulting in unessecary overhead
* One version disregarded the threshold parameters altogether (reject and
munge)
* More various problems with parsing and calling spamassassin
* I've updated documentation in the pod

I'm sure this version still has a long way to go, and is in no way
perfect!!!
Please keep in mind, I am NOT a perl developer. I can write php, c++,
java... but definitely not perl.

With all this said, it really does work great on my setup, customers no
longer complain about loss of mail or false rejects, and that makes me
really happy. I've been looking for this solution for a while now, but
eventually had to sit down and write my own. I hope this helps others, as
i've noticed many unanswered questions about this issue on the list.

I have one more question. The documentation (the file README.plugins) does
not list 'DECLINED' as a possible result code with the 'data_post' hook.
However, I noticed the original spamassassin plugin returns it when it wants
to do nothing. Please confirm that this is correct, and that I don't have to
return the OK result code.

You can find my version here:

    http://gw.nsa.co.il/qpsmtpd/spamassassin

I would greatly appreciate if perl developers on this list looked at it and
gave me their suggestions, corrections, tips & tricks.

Thanks go to the following people for the various versions, which helped me
get to this version that I am now using: Ask Bjorn Hansen, Devin Carraway,
Aran Deltac.

Thanks a lot!!

    Skaag (Aric)
    NSA Internet
    & Security Ltd.


Reply via email to