I have been asked to replace the MUA Message-ID of SASL senders with a Postfix-generated ID. The Message-ID of incoming mail which arrives via the same Postfix instance, but does not originate from a SASL authenticated sender, should not be touched. The submission service runs on port 587. Are there any unintended consequences with (or more efficient alternatives to) the following implementation?
In master.cf: - create cleanup clone called "special" with its own header_checks setting. - add "-o cleanup_service_name=special" under the submission service In header_checks.submit, which is referenced by the cleanup clone: /^Message-/ IGNORE This works as I'd expect, but will it break anything else? -- Sahil Tandon <sa...@tandon.net>
