I wanted to ensure I was passing the addresses to the content filter unchanged, and having the final cleanup service handle any
I understand from Patrick's document that using 2 cleanup services gives more control than the receive_override_options settings.
What I'm not sure about is if I need that setting at all now.
His readme (section 4.2.3) added
To the submission port.
And I had this set globally in main.cf
That combination broke sending mail to a virtual user via the submission port. Virtual user not found...
I fixed that by moving
from main.cf to the pre-cleanup service in master.cf
And unlike Patrick's readme, setting the submission port to use the regular cleanup service.
I want to be sure what I have now is right. Bypassing the content filter for authenticated submission traffic,
but for everything else, wait on address rewriting until after the content filter:
2 ## QUESTION's marked below:
pre-cleanup unix n - n - 0 cleanup
# is this next option redundant or necessary here now
# with all the other re-writing things turned off above it?
# (I am only using virtual alias maps today)
cleanup unix n - n - 0 cleanup
submission inet n - n - - smtpd
# unlike Patricks document I am using the regular (post-filter) cleanup for 587 traffic
# anything wrong by not using the pre-cleanup here?
# -o cleanup_service_name=pre-cleanup
pickup fifo n - n 60 1 pickup
smtpd pass - - n - - smtpd