docs: Document fix for PROXY protocol with postscreen#4066
Merged
georglauterbach merged 1 commit intomasterfrom Jun 15, 2024
Merged
docs: Document fix for PROXY protocol with postscreen#4066georglauterbach merged 1 commit intomasterfrom
postscreen#4066georglauterbach merged 1 commit intomasterfrom
Conversation
Contributor
|
Documentation preview for this PR is ready! 🎉 Built with commit: ab99156 |
georglauterbach
approved these changes
Jun 15, 2024
casperklein
approved these changes
Jun 15, 2024
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
3 participants
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.
Description
Port 25 is managed by the Postfix service
postscreen. By default it expects and exclusive lock. When more than one SMTP inbound service is running (an additional PROXY protocol port), this is a problem that can be resolved by configuringpostscreento useproxy:table for cache access instead.Credit and thanks to @pdehne for troubleshooting a configuration I missed, and sharing the solution: #4058 (comment)
Fixes #4058
Type of change