Thank you, increasing the process count solved the problem!
Amda
On 01.03.2016 15:22, Wietse Venema wrote:
Wietse Venema:
gsotsas:
Feb 29 10:36:45 sh3 postfix/smtp[10878]: A49A26C693:
to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, conn_use=16,
delay=1129, delays=0.05/1115/0/13, dsn=2.0.0, status=sent (250 2.0.0
from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 5B5236C65C)
Your mail is stuck before your content filter. Make the filter
faster (look in the mail filter logging for hints), or run more
filters in parallel.
According to your logs, it takes 13-15 seconds to filter a message,
and you have only two filters running in parallel. This limits
email throughput to only 8 messages per minute.
With that kind of performance you need only ~100 messages to build
up a delay of ~1000 seconds.
What I find very suspicious is that all deliveries to the filter
are time-synchronized:
Feb 29 10:36:45 sh3 postfix/smtp[10878]: A49A26C693:
Feb 29 10:36:45 sh3 postfix/smtp[10770]: B0DCD6C694:
Feb 29 10:36:58 sh3 postfix/smtp[10770]: C20696C696:
Feb 29 10:36:59 sh3 postfix/smtp[10878]: B9C026C695:
Feb 29 10:37:12 sh3 postfix/smtp[10770]: D43E96C697:
Feb 29 10:37:12 sh3 postfix/smtp[10878]: E3CC76C698:
Feb 29 10:37:26 sh3 postfix/smtp[10770]: F238B6C699:
Feb 29 10:37:26 sh3 postfix/smtp[10878]: 084C56C69A:
Perhaps the content filter is stuck in some global timeout.
Wietse
