[SA-exim] Local_scan timeout -- config issue?

[Marc MERLIN]

On Tue, Dec 19, 2006 at 03:08:43PM +0000, Jon Armitage wrote:
> I have SAmaxbody left at the default and SATruncBodyCond: 0.
 
So, do you have 
SAmaxbody: 256000?
 
> Have I messed up the config somewhere? I was under the impression that I should
> get a message along the lines of:
> 
> 2006-12-19 02:13:47 1GwUSy-0004kn-UH SA: Action: check skipped due to message si
> ze (8885632 bytes) and SATruncBodyCond expanded to false (Message-Id: 1GwUSy-000
> 4kn-UH).

I'm not sure why this is happening then, the code has:
    if (SAEximDebug > 3)
    {
        log_write(0, LOG_MAIN, "SA: Debug4: Message body is about %.0f bytes and
 the initial offset is %.0f", (double)(fdsize-18), (double)fdstart);
    }

Set debugging to 4, and see what the message body size is reported as.
Then crosscheck with what spamd says when it's having issues.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/