Skip to content
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

Advanced Settings Ignored #1025

Closed
Jamie96ITS opened this issue Sep 30, 2019 · 13 comments · Fixed by #1082
Closed

Advanced Settings Ignored #1025

Jamie96ITS opened this issue Sep 30, 2019 · 13 comments · Fixed by #1082
Labels
bug Something isn't working

Comments

@Jamie96ITS
Copy link

  • Platform (linux/mac/windows): windows
  • Delta Chat Desktop Version: DeltaChat-0.201.0-win64
  • Expected behavior: Login to personal mail server sans SSL
  • Actual behavior: SSL Failure
  • Steps to reproduce the problem:
  • Screenshots:
  • Logs: https://pastebin.com/XFNVtCRA

Good day.

I am trying to use my local mail server with Delta-Chat, my family uses it for internal communications and a few IoT uses...

It does not have a proper SSL chain, nor does it need one as it's most often accessed only on LAN. I figured like most other apps I could tell this program to use no security, and I saw that option here but when using it I fail to login with this error:

Could not connect to IMAP-server 192.168.2.21:143. (A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. (os error -2146762487))

Other applications connect just fine without SSL, so I'm wondering if this is an issue with Deltachat trying for SSL even though I set security off?

@Jamie96ITS Jamie96ITS changed the title Advanced Security Setting Ignored Advanced Settings Ignored Sep 30, 2019
@hpk42
Copy link
Contributor

hpk42 commented Oct 1, 2019 via email

@link2xt
Copy link
Collaborator

link2xt commented Oct 1, 2019

@Jamie96ITS Thanks for reporting! It appears that plain IMAP was not properly tested before.

Try PR #1028 if you have a development environment installed or try to patch your installation in-place for a quick fix. In any case, I am pretty sure setting IMAP security to "plain" configured SMTP instead.

@Jikstra
Copy link
Contributor

Jikstra commented Oct 1, 2019

@Jamie96ITS you can try the fixed version of @link2xt by using on of the install files of this pr (so no need to set up a development environment):
https://github.com/deltachat/deltachat-desktop/pull/1028/checks?check_run_id=242872813

As you use windows, this should work for you: https://github.com/deltachat/deltachat-desktop/suites/245977487/artifacts/71703

Can you please try and tell us if this fixed it?

@Jamie96ITS
Copy link
Author

Jamie96ITS commented Oct 2, 2019

No dice.
https://pastebin.com/B6kQqFZE
Looks like it's still trying to upgrade to SSL, making calls to port 993 etc.

@Jikstra
Copy link
Contributor

Jikstra commented Oct 2, 2019

@r10s is it possible that this is the same problem as with the e2ee setting?

EDIT: Yup they are broken.

@link2xt
Copy link
Collaborator

link2xt commented Oct 2, 2019

Client::secure is not accepting invalid certs still, going to fix it.

Bug in the core indeed.

That does not explain why plain is not working though.

At the very least deltachat/deltachat-core-rust#647 should fix "invalid certificate" problem. Hopefully it will setup StartTLS connection in this case.

@Jikstra
Copy link
Contributor

Jikstra commented Oct 7, 2019

@r10s @link2xt any news? We probably need to update the rust core in the node bindings?

@link2xt
Copy link
Collaborator

link2xt commented Oct 7, 2019

I have not tested if it works since deltachat/deltachat-core-rust#647 got merged.

Updating core is good in any case.

@link2xt
Copy link
Collaborator

link2xt commented Oct 26, 2019

While attempting to make #1076 work, I found that settings still don't work. Even more, they are not saved into the database properly.

Command

sqlite3 ~/.config/DeltaChat/*/db.sqlite 'select * from config where not keyname like "%_pw"'

shows

13|server_flags|undefined

Preparing a PR now. Basically the problem seems to be that serverFlags is passed to node bindings instead of server_flags.

@nicodh
Copy link
Member

nicodh commented Oct 26, 2019

Advanced settings are persisted now but only on initial setup, not when updating in settings dialog

@nicodh nicodh reopened this Oct 26, 2019
@nicodh
Copy link
Member

nicodh commented Oct 26, 2019

It's also not possible to change the IMAP login name for example

@link2xt link2xt added bug Something isn't working and removed rust-core labels Oct 26, 2019
@nicodh
Copy link
Member

nicodh commented Nov 4, 2019

Can you please try again with current master?
It should be possible to create an account configured with PLAIN (at least it worked in my tests)
We still have a bug though: updating the server security in an existing account does not work yet...

@Jamie96ITS
Copy link
Author

Works now, thanks!

I was able to login using my local, plain mail server and play around with it, finding another bug/design flaw with it but that's another matter.

@hpk42 hpk42 closed this as completed Nov 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants