On Sun, Jan 16, 2005 at 09:15:31AM +0000, [EMAIL PROTECTED] wrote:
> I've been playing with this plugin off and on for some time, and I
> really find 'spamc' itself problematic. I'm wondering if others have found
> the same problems and what, if anything, they have done about it.
[...]
> Quite often, submitting the same file to 'spamc' can result in
> nothing, "0/0", or a complete score and breakdown of test hits. Because of
> this, the plugin essentially allows stuff through that should have been
> either tagged or deleted.
I look after spamc, and only recently did any real testing against SA 3.0,
once it reached Debian Sarge. I had one successs report against SA3 and let
myself get somewhat lulled. :)
Once I actually tried it myself, it didn't work at all, for the simple reason
that SA3 very slightly changed the wording of the X-Spam-Status header. I've
posted a slightly updated version of the plugin compatible with spamc from
both SA3 and SA2 in the usual place:
http://devin.com/qpsmtpd/spamassassin_spamc
Any further problem reports would be welcome.
Speaking to possible other causes besides a fault in the plugin itself, the
main thing I can suggest is that you check to see if you're hitting scan
timeouts -- there are a couple of levels of timeouts involved in a qpsmtpd
SA scan, and with SA's performance being what it is, the clock does run out
sometimes.
--
Devin \ aqua(at)devin.com, IRC:Requiem; http://www.devin.com
Carraway \ 1024D/E9ABFCD2: 13E7 199E DD1E 65F0 8905 2E43 5395 CA0D E9AB FCD2
