Repository navigation
fix: remove dead check_policy_service unix:private/policy reference - #4
Merged
Merged
Conversation
smtpd_recipient_restrictions referenced a Postfix policy service named "policy" that Dockerfile never actually defines (only "policyd-spf" is defined via postconf -M). Every RCPT command triggered a "connect to private/policy: Connection refused" warning and a 451 "Server configuration problem" rejection -- breaking mail acceptance entirely, for both the Discourse and CE targets equally (this restriction isn't per-target). Verified locally: built the image, ran it standalone, confirmed a test message is now accepted cleanly (previously rejected with 451). Also drops the equivalent dead reference from the non-DMARC branch, which now falls back to Postfix's own sane default recipient restrictions instead of a config that was always broken.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Context
Found while regression-testing the multi-domain rebuild on do-3 — Discourse's mail path (which had been working via the stock upstream image) broke once rebuilt from our fork's freshly-built image. Root cause is unrelated to the CE work itself; this dead reference appears to predate this fork.
Test plan