Add mailcow subdomain sample config #756
Open
Conversation
This file contains 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.
Description
I made a sample reverse proxy config for mailcow. It is made according to the documentation and modified with some head-bashing :)
Benefits of this PR and context
Users, which host their mailcow mail server behind a SWAG reverse proxy will be able to easily set it up.
How Has This Been Tested?
The config was tested for a mailcow server I am hosting for myself. It took some time to unbreak the SOGo mail client Exchange ActiveSync functionality after I mistakenly appended the URI for it to the end of the
proxy_passdirective in the corresponding location block.Source / References