Repository navigation
docs(services): ssl_mode required, and ManageSieve on the general PROXY keys - #276
Merged
Merged
Conversation
Collaborator
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.
Documents yarilomail/yarilo#2524 (chart 2.4.7-dev.2).
data/settings.yaml:services.*.ssl_modegainsrequired: where it applies, the start-up refusals, what is secured under it, the capability lists and replies per protocol, the log line, the chart key.services.*.haproxy_protocol: yarilo-managesieve-login uses the general keys; its oldmanagesieve_login_servicekeys are accepted with a warning, the general nets win when both are set. The ManageSieve exception leaves theauth_allow_cleartexttext.docs/reference/rfcs.md: RFC 3207 §4530 5.7.0before TLS under required; RFC 9051LOGINDISABLEDalways under required.Merge after #2524.