Wino-Mail
Wino-Mail copied to clipboard
bkaankose
Cannot connect to Proton Mail Bridge
It doesn't seems like Wino Mail is able to connect to proton bridge (protonmail uses an IMAP bridge with SSL) While adding the account, Wino says the server doesnt respond. Turning on the logs doesn;t give any info
Thanks
Having the same issue, nothing showing up in either of the logs as well.
Error:
Proton Bridge settings:
I think @Benjin had a fix for this issue. It was caused by some certification issue and he stepped in for help.
@rafirafirafi @kareigu could you please try this solution to see if it works for you?
Worth noting that it worked for me after I tried that on the beta preview; it’s possible that I also needed some of the fixes between the latest public and the preview.
I tried exporting the certs from Proton Bridge and adding them as personal keys in certmgr, but didn't change anything.
I'm not understanding how to go about setting the auth to "none". Can't seem to find any setting for this in Proton Bridge nor Wino.
@kareigu try with the beta in this release; that's where I was able to get ProtonMail to work.
You'll have to enable Developer Mode and install the app dev certificate on your system for it to install.
Aight, with the beta release I can get a bit further where it seemingly connects to Proton Bridge but then fails during "Preparing folders"
Nothing in the logs this time either.
Tried setting auth to none as well but no luck.
@kareigu Did you set both IMAP and SMTP to "none" auth? They're two different tabs in the configuration view.
I'm out of ideas now. If you're comfortable building it yourself, can you stick a breakpoint here and see what the full error message/stacktrace is?
Okay, from building and running I managed to get to the same error message about TLS you had in your Discord message.
However, setting the "Connection security" to None seems to make it able to connect normally. On 1.6 and beta 1.7 releases this doesn't seem to work, only on the current master version.
Still doesn't work for me on the current release. I get the same error with the IMAP client pool failure. Anything possible to do about that?
Still doesn't work for me on the current release. I get the same error with the IMAP client pool failure. Anything possible to do about that?
There was a problem with testing the IMAP connectivity in this release. I am preparing a hotfix release that will fix and help you guys to share IMAP protocol log easily for further potential problems with IMAP.
1.7.3 is expected to go live in few hours/tomorrow depending on the certification delay on Microsoft Store.
Just chiming in to confirm that this issue is still open. I tested it just now using the Store app and the 1.8.0 beta, and in both cases I was unable to connect to Proton Bridge. Setting auth to none for both IMAP and SMTP has no effect. I also enabled IMAP logging but this always produced a log file with a length of 0 bytes.
Just chiming in to confirm that this issue is still open. I tested it just now using the Store app and the 1.8.0 beta, and in both cases I was unable to connect to Proton Bridge. Setting auth to none for both IMAP and SMTP has no effect. I also enabled IMAP logging but this always produced a log file with a length of 0 bytes.
All synchronization and authentication is handled in the server companion in Beta version. So UWP has no restriction in this case. Using Proton Bridge with proper configuration must work without any blockers.
For Store version, I believe somebody shared in Discord that you must except Wino Mail from the localhost loopback. Described here
https://stackoverflow.com/questions/33259763/uwp-enable-local-network-loopback
Thanks for replying! I noticed that the beta is distributed as an msixpackage so I think it has the same restrictions as the store app (it gets installed in the UWP sandbox). So I followed the advice in the link to enable loopback, and it worked!
For anyone who had the same issues as me, an extra required step is to export the TLS certificate from Proton Bridge (you'll find the option in the advanced settings) and then install the cert.pem file in the Windows root certificate store. Instructions on how to do that are here: https://www.incredigeek.com/home/import-cert-pem-on-windows/
After I installed the TLS certificate and enabled loopback for the Wino UWP container, everything worked and I was able to access my Proton emails.
@bkaankose feel free to mark this issue as closed. With the new 1.8.0.0 version, enabling loopback and installing the TLS certificate, it should work for everyone who uses Proton now.
Loopback should not be required for Wino beta anymore. Server is WPF app, which doesn't have the same restrictions like UWP.
Thanks for replying! I noticed that the beta is distributed as an msixpackage so I think it has the same restrictions as the store app (it gets installed in the UWP sandbox). So I followed the advice in the link to enable loopback, and it worked!
For anyone who had the same issues as me, an extra required step is to export the TLS certificate from Proton Bridge (you'll find the option in the advanced settings) and then install the cert.pem file in the Windows root certificate store. Instructions on how to do that are here: https://www.incredigeek.com/home/import-cert-pem-on-windows/
After I installed the TLS certificate and enabled loopback for the Wino UWP container, everything worked and I was able to access my Proton emails.
I'm glad that you figured it out. Thank you for providing the steps for others.
Even though server companion is in the same bundle, it shouldn't be blocked for loopback. UWP sandboxing should only apply for the client, not the server. I will check if something is wrong with the capabilities.
Personally never used Proton Mail. I may run some tests to make this work all fine.
@mdfarragher
After I installed the TLS certificate and enabled loopback for the Wino UWP container, everything worked and I was able to access my Proton emails.
I don't recall having to enable loopback when I was testing this, so maybe that step isn't actually necessary as @Tiktack and @bkaankose have said.
@bkaankose Perhaps it'd be a good idea to embed some instructions about exporting the TLS cert that get displayed if Wino is getting configured to point to 127.0.0.1? Otherwise, it's not a particularly discoverable solution.