-
-
Notifications
You must be signed in to change notification settings - Fork 99
Separate IMAP and SMTP configuration #1835
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Ping @link2xt maybe you can have a look at it, whether this was the way you intended it. You can also push at this pr, I will be careful with force pushing. |
The ci is failing, looks like this bug: rust-lang/rust#64496 |
} | ||
param.send_port = match param.send_security { | ||
Socket::Automatic => 0, | ||
Socket::STARTTLS | Socket::Plain => 587, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have changed heuristic to use port 587 instead of port 25 for plain.
Port 25 is for MTA-MTA transmission, it shoud not be used by Delta Chat at all.
654c038
to
ebb4269
Compare
ci in #1831 is failing because of the same bug - in fact, i came to this issue when searching for the error string in duckduckgo :) |
25db574
to
15eca6e
Compare
pub type SmtpServers = Vec<ServerParams>; | ||
|
||
#[derive(Debug)] | ||
pub struct LoginParamNew { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This name is unclear. Could it be named AutoconfigParam
or something like this?
As I understand it, loginparam_old_to_new
converts user-provided settings into the input for automatic configuration algorithm, and loginparam_new_to_old
is a very simple autoconfiguration algorithm that converts results obtained from autoconfig XML or provider database into LoginParam
with the first IMAP and SMTP server.
"Old" LoginParam
is not going anywhere until automatic reconfiguration is implemented, and it is not a short-term goal. It is what is saved in the database under configured_
settings.
Also this LoginParamNew
, besides renaming, could be moved into configure
module.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I had not really thought about naming before and such things before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As for loginparam_old_to_new and the other way round, the thought was that I could implement point 5 only partly first and then already test it using these conversion methods. And that they might come handy later under a different name.
So, feel free to rename and change these things, I never planned to merge these functions as they currently are.
6032a5c
to
88a4a0a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
read through most lines of the pr and also tested it with some accounts, already lgtm :)
i just have some comments to deltachat.h, however, i already created a pr to target that, #1839 can be merged to this pr.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good except for the db conversion that confused me a little.
I can't approve because this technically is my own pr.
b0842c9
to
8e70534
Compare
maybe we should do a bugfix-release core45 before merging that finally in, also as this requires some additional work in the uis. |
a60b2f8
to
5dcbb88
Compare
Co-Authored-By: link2xt <[email protected]> Co-Authored-By: bjoern <[email protected]>
From #1832 (for 2 it was necessary to also do 5, and I am not done with 2 yet, either)
(by @link2xt)
Fixes #646
Also fixes point (4), previously
AcceptInvalidCertificates
instead ofAutomatic
settings were applied for autoconfigured (with either XML or provider DB) servers, sostrict_tls
was not used.