feat: follow certificate check parameter in autoconfig#8284
Merged
Conversation
link2xt
reviewed
May 28, 2026
link2xt
force-pushed
the
feat/allow-insecure-autoconfig
branch
from
00e9400 to
6303882
Compare
Collaborator
|
I pushed lint fixes (rustfmt, removed one unused import). This will also run the tests. |
link2xt
force-pushed
the
feat/allow-insecure-autoconfig
branch
from
6303882 to
ca22603
Compare
link2xt
approved these changes
May 28, 2026
Contributor
Author
|
Thanks for the fast review and for your changes! |
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
2 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.
The HTTPS requests made during IMAP+SMTP autoconfig now respect the "Accept invalid certificates" setting in advanced server options.
This is useful for cases where the mail server is in an internal network where a signed HTTPS certificate cannot be obtained; in such cases the app currently requires entering all of the server details by hand. This will allow using self-signed certificates for the web server providing the autoconfig infos.
This PR constitutes somewhat of a replacement for #7472.