Dear, I used spamassassin quite a while without any troubles. Yesterday I suddenly noticed that my mails are not filtered anymore. (Missing X-Spam headers and of course SPAM in my inbox)
Inside the procmail.log I found for each mail: ----- procmail: Timeout, terminating "/usr/bin/spamassassin" procmail: Rescue of unfiltered data succeeded ----- Really weird is, that I did not changed any thing in my configuration. The first unfiltered mail has a arrival time very near of my last dselect update. If I remember correct, some of the perl packets were updated. Maybe there is a problem with perl? I tried to test around a bit and sent myself some mails (one by one). I looked at several logfiles and measured the running time of the called /usr/bin/spamassassin process. (procmail calls it.) For empty mails (empty body or only a signature) it took 4.6 minutes to pass spamassassin and/or razor. I do not know what would be normal but I guess for my machine that's much too slow. (see system details at the end of this mail) When I passed "normal" (with a message in the body) mails through spamassassin the timeout was reachead and procmail dumped two lines as shown above. I have really no idea why its so slow now. My only guess is that I have a perl problem made by the last update. System and Software: P4, 2GHz, 900 MB RAM debian woody 2.4.17 spamassassin 2.20 razor 1.20 (both selfconfiguring deb packets) postfix 1.1.11 procmail 3.22 cyrus-imapd 1.5.19 Way of email: fetchmail -> postfix -> procmail -> cyrus inside procmail: procmail -> spamassassin -> razor -> procmail For any help I would be very glad! kind regards Timm -- Timm Riesen <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
