| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Heads-up, do not merge this PR. It's waiting on @pwntester for advice (if any), relating to our CI docs preview no longer working for PRs coming from forks: #4247 (comment) EDIT: Resolved and verified by #4267 |
Sorry, something went wrong.
|
Documentation preview for this PR is ready! 🎉 Built with commit: cefc1d8 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
SASLAUTHD_MECHANISMS only has test coverage for ldap and rimap, which were discussed during the original implementation of the feature.
The other mechanisms were added for the sake of it, but likely don't make much sense with DMS.
Generally SASLAUTHD related support is not necessary for users. It was contributed as an alternative SASL auth method for Postfix to use when DMS has Dovecot disabled that would normally be delegated for SASL authentication.
Users interested in MySQL or similar DB access could configure for such directly with Postfix and Dovecot (or just Dovecot due to existing SASL auth config).
There may be potential breakage with SMTP_ONLY=1 users. I've not considered this as our support/docs for such are lacking. As this is for a breaking release, it should be fine and we can easily bring these back should users raise issues about it.
Docs wise, I don't see how the note about multiple values for mechanisms being supported was valid. Perhaps it was for direct usage of the command but not with how we start the supervisord services.
Fixes #4251
UPDATE: I forgot to remove these values from our reference ENV file, mailserver.env. This has been spotted and contributed: #4472
Type of change
Checklist