From miked at softtalker.com Mon Aug 1 14:54:23 2005 From: miked at softtalker.com (Mike Dillinger) Date: Mon, 1 Aug 2005 14:54:23 -0700 Subject: [SA-exim] SAmaxbody and sa-exim Panics Message-ID: <10010477937.20050801145423@softtalker.com> Hello, I have two weird things going on with sa-exim and I hope I can get some help. First of all, I noticed that sa-exim wasn't allowing Spamassassin to run testing on incoming mail. After looking at the log files, I noticed that sa-exim thought that the message size exceeded SAmaxbody setting. My SAmaxbody setting is 262144 (256KB). I sent a sample message from another email account of mine and watched the logs. The message I sent was between 2K and 3K, yet sa-exim wouldn't scan it, claiming it was more than 256KB. It seems that sa-exim is possibly multiplying the actual mail size by one hundred (or at least in my testing that was the case). How does sa-exim determine the size? And how do I fix this? Secondly, I increased my SAmaxbody to 524288 (512KB) to see if scanning worked. It doesn't seem to work. I get a panic. Here are the significant lines from my exim mainlog: 2005-08-01 14:24:08 1DzhlY-0003Nb-28 SA: Debug: SAEximRunCond expand returned: '1' 2005-08-01 14:24:08 1DzhlY-0003Nb-28 SA: Debug: check succeeded, running spamc 2005-08-01 14:24:08 1DzhlY-0003Nb-28 SA: PANIC: Unexpected error on read body (but message was accepted), file sa-exim.c, line 984: Bad file descriptor 2005-08-01 14:24:08 1DzhlY-0003Nb-28 SA: Debug: Writing message to /var/spool/sa-exim/SAerrorsave/new/1122931448_1DzhlY-0003Nb-28 2005-08-01 14:24:08 1DzhlY-0003Nb-28 SA: PANIC: Error in error handler while trying to save mail to /var/spool/sa-exim/SAerrorsave/1122931448_1DzhlY-0003Nb-28, file sa-exim.c, line 1470: Bad file descriptor I'm thinking the unexpected read body error has something to do with sa-exim thinking that the message is a lot larger than it really is. A couple of other things I noticed: 1. spamc takes a while to scan (and I don't know why), and sa-exim thinks it has finished before spamc actually has. 2. spamc runs fine when I scan the messages manually, i.e.: spamc /var/spool/sa-exim/SAerrorsave/new/1122931448_1DzhlY-0003Nb-28 Thanks for any help! -MikeD From merlins.org at paulm.com Thu Aug 25 13:54:51 2005 From: merlins.org at paulm.com (Paul Makepeace) Date: Thu, 25 Aug 2005 21:54:51 +0100 Subject: [SA-exim] Tweak for greylist cleaning Message-ID: <20050825205451.GA21886@mythix.realprogrammers.com> In greylistclean.cron, for cleaning empty dirs: -depth -mindepth 1 might be useful. -depth outputs directories depth first so they're more likely to get deleted in the right order. -mindepth 1 prevents the tuplets/ directory from being deleted. Cheers, Paul -- Paul Makepeace .............................. http://paulm.com/inchoate/ "If men are seduced by lovely things, then you're at a technical meeting without your laptop." -- http://paulm.com/toys/surrealism/ From merlins.org at paulm.com Thu Aug 25 16:24:27 2005 From: merlins.org at paulm.com (Paul Makepeace) Date: Fri, 26 Aug 2005 00:24:27 +0100 Subject: [SA-exim] Getting greylisting to work Message-ID: <20050825232427.GA2167@mythix.realprogrammers.com> On a fresh install of sa-exim, spamassassin, and spamc on Debian testing I needed to do the following to get greylisting to work: * /usr/share/perl5/Mail/SpamAssassin/Plugin/Greylisting.pm I believe this should start, package Mail::SpamAssassin::Plugin::Greylisting; * /etc/spamassassin/init.pre Add, # Greylisting - enable SA-exim's greylisting # loadplugin Mail::SpamAssassin::Plugin::Greylisting * /usr/share/doc/sa-exim/README.greylisting.gz The rule quoted in GREYLIST_ISWHITE: change reseval to eval If I haven't made any mistakes here I guess these are bugs? Cheers, Paul -- Paul Makepeace .............................. http://paulm.com/inchoate/ "What is my name? You must embrace the chaos." -- http://paulm.com/toys/surrealism/ From merlins.org at paulm.com Thu Aug 25 17:06:26 2005 From: merlins.org at paulm.com (Paul Makepeace) Date: Fri, 26 Aug 2005 01:06:26 +0100 Subject: [SA-exim] Getting greylisting to work In-Reply-To: <20050825232427.GA2167@mythix.realprogrammers.com> References: <20050825232427.GA2167@mythix.realprogrammers.com> Message-ID: <20050826000626.GC32260@mythix.realprogrammers.com> Je 2005-08-26 00:24:27 +0100, Paul Makepeace skribis: > On a fresh install of sa-exim, spamassassin, and spamc on Debian testing > I needed to do the following to get greylisting to work: > > * /usr/share/perl5/Mail/SpamAssassin/Plugin/Greylisting.pm > I believe this should start, > package Mail::SpamAssassin::Plugin::Greylisting; > > * /etc/spamassassin/init.pre > Add, > # Greylisting - enable SA-exim's greylisting > # > loadplugin Mail::SpamAssassin::Plugin::Greylisting > > * /usr/share/doc/sa-exim/README.greylisting.gz > The rule quoted in GREYLIST_ISWHITE: change reseval to eval Ah, I've just seen there's additional commentary on SA 3.x later in the file. Would be really useful to put a note to that effect "but if you're running SA 3.x see below". I see the loadplugin is mentioned - I think my suggestion above will enable it to be called with the same convention as the other plugins SA ships with. Paul -- Paul Makepeace .............................. http://paulm.com/inchoate/ "What is the color of newborn kittens? My place of wonder breasts." -- http://paulm.com/toys/surrealism/