tracing bottlenecks ?

[lists at sbt.net.au]

On Sun, October 31, 2021 4:02 am, Matus UHLAR - fantomas wrote:
>> On Fri, October 29, 2021 9:18 pm, Matus UHLAR - fantomas wrote:
>>
>>> hard to say, maybe you could feed the file into spamassassin -D which
>>>  could show you more.
>
> On 30.10.21 12:31, lists at sbt.net.au wrote:
>
>> do you mean feed such an email file that took long time ? is it like:
>> spamassassin -D < mail.file
>
> precisely. You should do that as amavis user, redirecting error output so
>  something like
>
> su amavis -c 'spamassassin -D' < /tmp/input >/tmp/output 2>&1


Matus,

thanks. I'll go step by step, in case I'm doing it wrong:

I've searched recent maillog for example of 'delayed' email, found one:

Oct 25 12:56:13 amavis[18958]: (18958-14) Passed CLEAN {RelayedInbound},
[54.240.7.42]:37159 [54.240.7.42]
<0102017cb524e543-695815fb-86de-4f18-b7f0-64487ae071f3-000000 at eu-west-1.amazonses.com>
-> <aaa at bbb.au>, Queue-ID: 5BA8241E1CB0, Message-ID:
<0102017cb524e543-695815fb-86de-4f18-b7f0-64487ae071f3-000000 at eu-west-1.amazonses.com>,
mail_id: rKaBituAo6su, Hits: -1.898, size: 28444, queued_as: E949341DFFD9,
300397 ms

found same 'queued' string in an email file, email file copied to new file
'delayedemail'

# grep E949341DFFD9 delayedmail
        by sbt.net.au (Postfix) with ESMTP id E949341DFFD9

old]# su amavis -c 'spamassassin -D' < delayedmail > output 2>&1

takes maybe 5 secs to run. so far haven't noticed anything in 'output' file

- haven't as yet altered amavis log level

$log_level = 0;

I'll also alter $max_servers = 5; (I can see original file had 2, was
upped to 10 at some point )


Voytek