Am 01.11.2014 um 20:20 schrieb Wietse Venema:
li...@rhsoft.net:
The Postfix SMTP/LMTP client has time limits for DNS lookups, TCP
handshakes, SMTP handshakes, TLS handshakes, and for individial
SMTP/LMTP commands.
Without a crystal ball I can't say which of the time limits is in
effect.
there was nothing further in the logs, also after "postfix flush"
however, the real problem where that the lmtpd started to hang in case
of the oldest message with a NULL char (reported upstream)
The Postfix client will log a timeout event after a while. Until
then it makes no noise
>
You have delivery concurrency of 1? Why?
dbmail-lmtpd is single threaded and would anyways process only one
message at the same time - the setting is recommended upstream
Single threaded, and it locks up with nulls? Bleh.
sadly yes
however, the message should not have made it through spmass-milter
1.6 NULL_IN_BODY FULL: Message has NUL (ASCII 0) byte in message
UPDATED: /etc/mail/spamassassin/local.cf
238a239
> score NULL_IN_BODY 8.0
Postfix has a diaper for that, called message_strip_characters.
This was originally implemented for buggy Microsoft servers
thanks for the hint
i added the reject param for that since this was the first message where
the SA-rule got triggered and the milter would reject it too, well last
but not least it was c lear junk mail
message_reject_characters = \0
