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

Cannot write property 'security' on boolean false #909

Closed
3 tasks done
CherryDT opened this issue Nov 7, 2023 · 2 comments · Fixed by #917
Closed
3 tasks done

Cannot write property 'security' on boolean false #909

CherryDT opened this issue Nov 7, 2023 · 2 comments · Fixed by #917
Labels
App Issue affects the standalone application bug

Comments

@CherryDT
Copy link

CherryDT commented Nov 7, 2023

Prerequisites

  • Tried the most recent nightly build
  • Checked if your issue is already reported.
  • Answered all the questions in this template (Or provide a working crystal ball).

What happened?

Download latest nightly build. Import from Thunderbird. Observe "hang". Check devtools to find error "Cannot write property 'security' on boolean false":

image

This seems to happen because of this call:

sieve.connect(new SieveUrl(`sieve://${this.hostname}:${port}`), false);

Here, false is passed, however sieve.connect seems to expect an options object as second argument.

What did you expect to happen?

Successful import.

Which Version

Include information about your system, server and most important if it is about the app or webextension.

  • Latest standalone app (20231017.1)
  • Operating system: Win10
  • Sieve/Mail Server - hosted at dogado

Seems like this regression was introduced by #680

However, I'm not even sure why false is passed here in the first place as opposed to true, because this argument apparently used to be secure and my Thunderbird profile has "SSL/TLS" set for this account!

@thsmi thsmi added bug App Issue affects the standalone application labels Dec 28, 2023
@thsmi
Copy link
Owner

thsmi commented Dec 28, 2023

Concerning you question:

Sieve uses implicit startTLS means you always start insecure and then update to secure. You normally upgrade before authenticating.

In case you just want to read read the server's capabilities then you don't need to authenticate, and thus you don't upgrade your connection to secure. You just connect ask the server what are your capabilities and then disconnect.

If you got a useful response you know everything is fine and in every other case you know you are not talking to a sieve server and thus the basic configuration is wrong.

@thsmi thsmi linked a pull request Dec 29, 2023 that will close this issue
@thsmi
Copy link
Owner

thsmi commented Dec 29, 2023

@thsmi thsmi closed this as completed in #917 Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
App Issue affects the standalone application bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants