mouss put forth on 9/10/2010 5:54 PM:
> for header_checks, the option is no_header_body_checks:
> http://www.postfix.org/postconf.5.html#receive_override_options
Got it, I think.
> for smtpd restrictions:
> -o smtpd_foo_restrictions=blahblah
>
> if you want per smtpd header checks,
No. I simply want header_checks on the "public" smtpd and none on the
new private submission smtpd.
Here's what I currently have:
10125 inet n - - - - smtpd -v
-o smtpd_client_restrictions=
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o receive_override_options=no_unknown_recipient_checks,/
no_address_mappings,no_header_body_checks
(The line wrap "/" there is mine as my MUA wraps at 78 IIRC)
It's working, and submission at my MUA seems to be much snappier.
However, this troubles me:
Sep 10 22:30:14 greer postfix/smtpd[12354]: before input_transp_cleanup:
cleanup flags = enable_header_body_filter enable_automatic_bcc
enable_address_mapping enable_milters
Sep 10 22:30:14 greer postfix/smtpd[12354]: after input_transp_cleanup:
cleanup flags = none
I'm unable to comprehend Wietse's note in the docs:
no_header_body_checks
Disable header/body_checks. This is typically specified AFTER an
external content filter.
I don't use an external content filter. I don't understand the "before"
and "after" descriptions in the log. "before" has everything enabled,
"after" apparently doesn't. How does
-o receive_override_options=
relate to the "before input_transp_cleanup" and "after
input_transp_cleanup"? Are header checks being performed for this smtpd
daemon or not? I'm unable to discern this from the log.
Just a tad confusing...
--
Stan
