I suspect this error is being caused by SpamCop reporting, not razor. As a test, try reporting a message that's two weeks old and see if the error message changes/goes away.
For me, the "Insecure dependency" message goes away and is "replaced" by a message to the effect that older mails won't be reported to SpamCop.
You are right.
[EMAIL PROTECTED] matias]# spamassassin -D -r old [...] debug: Razor2: spam report, response is "1". debug: leaving helper-app run mode debug: SpamAssassin: spam reported to Razor. SpamCop -> message older than 2 days, not reporting debug: SpamAssassin: could not report spam to SpamCop. 1 message(s) examined. [EMAIL PROTECTED] matias]#
There is a way to solve this?
Also the file scanned have tree messages, but the SpamCop output says 1 message(s) examined.
BR, Matías.
On Thu, 3 Mar 2005, Matias Lopez Bergero wrote:
Hello,
I have a little problem reporting spam with sa, I got this error message wen reporting:
% spamassassin -D -r spam
[...]
Insecure dependency in connect while running with -T switch at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/IO/Socket.pm line 114.
I have read trough the wiki and found something similar but related to razor and SA 2.6 with a patch, but I have no problems reporting spam with razor2 and I'm using SA 3.
Setup: Linux 2.4, SA 3.0.2, sendmail 8.13, milter-spamc 0.25, Razor Agents 2.67, Pyzor 0.4.0 and DCC 1.2.69.
Any ideas/comments are most welcome.
BR, Matías.
