Re: message_size_limit causes postfix to stop delivering messages

[Nick Bright]

On 2/6/2012 2:19 AM, Ralf Hildebrandt wrote:

Also, the content filter doesn't announce a SIZE:

You forgot to issue the EHLO command - only after this command the
filter might announce the SIZE extension.

Or rather LHLO (since mppscan seems to speak lmtp):

Oops!

$ telnet localhost 10025
Trying ::1...
Connected to localhost.
Escape character is '^]'.
220 mppd
LHLO TEST
250-mppd
250-PIPELINING
250-8BITMIME
250 XFORWARD NAME ADDR PROTO HELO SOURCE
quit
221 Service closing transmission channel

content_filter = mppscan:[127.0.0.1]:10025

It's a very odd setup, since only locally submitted mail (sendmail
command) gets filtered. Mail coming in via smtp is explicitly not sent
to the filter:

smtp    inet    n       -       n       -       200     smtpd
         -o content_filter=

submission inet n       -       n       -       200     smtpd
         -o content_filter=

smtps     inet  n       -       n       -       200     smtpd
    -o smtpd_tls_wrappermode=yes
    -o smtpd_sasl_auth_enable=yes
    -o milter_macro_daemon_name=ORIGINATING
    -o content_filter=

in all three cases we see "content_filter=" - disabled.

I haven't found any example of mail that doesn't flow through the content filter. This is how the vendors' setup scripts configure postfix to interact with the daemon (it's a commercial product). When I asked my vendor if the "-o content_filter=" should be removed, the vendor replied: "No, this is because we actually have the policy server which is first, then it is passing the message to the content_filter defined in main.cf; so if you remove that line from master.cf all mail will be scanned twice."

Some of these are down:

<RBL list snipped>

Unrelated to the issue at hand.

message_size_limit = 209715200

That's 200MB.

Yes, I know; however the actual value isn't relevant - even when I explicitly set the value of message_size_limit to the default value the same non-delivery queuing behavior occurs.

 - Nick Bright

I sincerely doubt that the content_filter configuration is related to the actual problem.

smime.p7s
Description: S/MIME Cryptographic Signature