SpamProbe + ClamAV
Nikolaus Hiebaum <[email protected]> Sun, 28 Jan 2007 10:33:34 +0100 (CET)
| Newsgroups | gmane.mail.spam.spamprobe.general |
|---|---|
| Message-ID | <[email protected]> |
Hello, A while ago, I asked a question here regarding an obscure ClamAV error that happens in combination with SpamProbe. Well, nobody replied; hence, I'll try again ... I am running SpamProbe 1.4d and ClamAV 0.88.7 on my system (a shared FreeBSD server). Both SpamProbe and ClamAV are invoked through a .procmailrc rule. In general, my .procmailrc-setup looks like this: 1) Run everything through ClamAV (via Clamassassin) 2) Check if mails are for mailing lists and shuffle them in the respective folder 3) Run SpamProbe 4) Do more mail shuffling Every now and then it happens that e-mails get "destroyed" and there is an obscure error in the mail header: Clamscan error 137. Googling didn't reveal anything and there was no info from the ClamAV maili= ng list. I observed that the mailing list mails never suffer this fate; it can only happen to mails that ran through SpamProbe (so mails of step 4). So, my question is if anyone of you has an idea what could be the cause of = the problem. Also, what would you suggest in terms of order and processing efficiency of ClamAV & SpamProbe. -- = Beste Gr=FC=DFe / Best regards , Nikolaus Hiebaum ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE= VDEV