> Hello, > I've been working with Mr. Libenzi on getting XMail + SpamAssassin to > behave itself on a Solaris SPARC SMP box (E3500 8 CPU + 4GB > RAM, patched > to latest rev. last Sunday). We've observed some very stange > behavior. > With 1.15 through 1.17, XMail would spawn a bunch of processes and the > root process would lock up, mail would no longer go into or > out of XMail, > and the root process would require a kill -9 to stop it. In > all cases, I'd > get emails from the syslog daemon like the following: > > ....[ID 702911 daemon.error] Filter error (-5):... > > We're currently working on a version 1.18 that appears to > behave itself on > all other platforms, but on Solaris SPARC SMP. It now seems > to bounce the > email back and forth between XMail and the filter and considers each > message a new email. There's no longer the problem with the locked up > root process, or the spawning of dead XMail procs, but the > result was that > I had 50K+ emails in various inboxes and the spool this morning. I'm > using the latest sa_filter.pl. Are there any XMail + > SpamAssassin experts > out there that can diagnose this? Perhaps there's something > grossly wrong > with the sa_filter.pl script? > > Kelly McTiernan >
Kelly, I wrote the SpamAssassin filter you're using, I'd be happy to help. Could you send to me (off-line) your logs for today? As well, I would like a copy of the emails that were generated (at least the headers). I also need a copy of filters.in.tab and filters.out.tab. What version of SpamAssassin are you running? What version of perl are you running (output of: perl -V)? Davide, what is that Filter error (-5) coming from? Thanks. -Don - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
