On Thu, May 17, 2012 at 11:22:04PM -0500, Stan Hoeppner wrote: > From: http://www.postfix.org/FILTER_README.html > > /etc/postfix/master.cf: > # ============================================================= > # service type private unpriv chroot wakeup maxproc command > # (yes) (yes) (yes) (never) (100) > # ============================================================= > smtp inet ...other stuff here, do not change... smtpd > -o content_filter=filter:dummy > > The "-o content_filter" line causes Postfix to add one content > filter request record to each incoming mail message, with content > "filter:dummy". This record overrides the normal mail routing and > causes mail to be given to the content filter instead. > > > > Until reading the above many times, based on previous discussions > here, I was under the impression that even with content_filter > enabled here as an after queue filter, messages rejected by > smtpd_foo_restrictions or header_checks would indeed be rejected > instead of being piped to the content_filter.
Right. > The above documentation seems to suggest that every message > entering via the smtpd service will be routed to the content_filter > no matter what, making all smtpd_foo_restrictions useless. Please > tell me I'm misreading the above, that smtpd_foo_restrictions take > precedence over content_filter implemented as above in master.cf. Mail routing is only applicable after the mail is accepted. smtpd_foo_restrictions can and often do decide not to accept mail. Note that you must disable restrictions on the reinjection from content_filter. You do NOT want to reject at that point, because it is risking backscatter. -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
