Support for self signed certificates and using a different domain for email accounts vs internal domain #21
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.
I'm not very good with python, so I'm not sure if my code is very good. I've tested it on my setup and it's working nicely however.
The domain replacement is quite simple, it just replaces the domain if another is defined.
The self signed certs aren't done by just ignoring validation, the container will run update-ca-certificates and you would have to add your certificates to the host and then uncomment the volume.
None of these features are enabled by default, users will have to uncomment them in docker override yml.