Topic: SPAM with new clam av? oops no key

[mike_mattos]

seems that since updating to the newer .96 clam, my spam filter isn't working any more. 

I'm getting multiple copies of the same spam via the SME hosted email accounts, essentially none via the ISP accounts.

log says
2010-04-26 08:07:09.311006500 [16340] info: spamd: connection from localhost [127.0.0.1] at port 41098
2010-04-26 08:07:09.312985500 [16340] info: spamd: checking message <000e01cae538$f849dd00$514f4261@rome.com> for qpsmtpd:1005
2010-04-26 08:07:09.318351500 [16340] warn: plugin: eval failed: oops, no key at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/AsyncLoop.pm line 173, <GEN351> line 59.
2010-04-26 08:07:09.320174500 [16340] warn: rules: failed to run DNS_FROM_AHBL_RHSBL RBL test, skipping:
2010-04-26 08:07:09.320196500 [16340] warn:  (oops, no id at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/AsyncLoop.pm line 172, <GEN351> line 59.

[Stefano]

mike, please, don't report problems here and search bugzilla first, there's a bug already open for this issue

[mike_mattos]

I don't think a 2 year old report on an upgrade to 7.3 is quite the same thing as a 7.4 failing right after a virus upgrade and email lockups during the transition.

Also, the failure is at a different line in AsyncLoop.pm

Seems to me that before raising an SME bug, it is useful to see if the problem really is an SME bug or if it is a user error, or configuration problem, or a SpamAssassin bug.

Once I know where to raise the bug, I'll be sure to raise it.

[CharlieBrady]

Once I know where to raise the bug, I'll be sure to raise it.

Try the BUGS link on this page. Or the 'bug tracker' link in the advice which appears every time you post here.

Don't report problems here - Please report bugs and potential bugs in the bug tracker.

http://bugs.contribs.org/

[CharlieBrady]

Seems to me that before raising an SME bug, it is useful to see if the problem really is an SME bug or if it is a user error, or configuration problem, or a SpamAssassin bug.

All of those should be reported in the SME bug tracker. SME software should make user error and configuration problems (close to) impossible. SpamAssassin bug would mean that SME server needs a different version of SpamAssassin. SME bug is self-explanatory.