proton-bridge
gluon
proton-bridge | gluon | |
---|---|---|
4 | 5 | |
2 | 430 | |
- | 1.9% | |
0.0 | 7.2 | |
over 1 year ago | 3 days ago | |
Go | Go | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
proton-bridge
-
Protonmail can delete the wrong email and nobody cares
I've suffered from exactly the same issues with Protonmail Bridge, and just this last weekend I decided (reluctantly) to move to a more standard mail provider (I chose Mailbox.org).
Aside from the UID issue discussed I also had problems with Bridge not supporting my particular use-cases. I created my own fork (see https://github.com/polaris64/proton-bridge) to work around some limitations and to add features, but maintaining this was too much work, especially as paying for a mail provider was supposed to reduce maintenance burden. I have had a pull request open since the 23rd of June to merge these to the upstream version, but so far I haven't received any comments from the Proton team.
I like ProtonMail, I just wish Bridge was more standards-compliant.
-
New beta on ProtonMail Bridge: redesigned app, more stability, and better performance
Is there any chance we could get the functionality mentioned in this issue added to the new version? I've forked PM Bridge from version 1.8.3 and added it myself but it would be great to have it in the official version too!
-
If ProtonMail's apps are open source, can't the community fix the apps?
There are some forks, such as my own of ProtonMail Bridge :)
-
Experimental mail tag support for `mu4e` and ProtonMail Bridge
ProtonMail Bridge does not currently support that functionality, so I have created a fork which does.
gluon
-
Inside Gluon, our new IMAP library
Check our blog to learn more: https://proton.me/blog/gluon-imap-library. You can peek into it yourself on our GitHub: https://github.com/ProtonMail/gluon.
-
Bridge and Thunderbird Trash
They are going to replace go-imap with gluon. That's an effort which has been going on for quite a while.
-
Proton Bridge: Message UIDs are not stable / possible data loss (deletion of wrong messages)
Hi all, we want to share more info about the reported issue with Proton Mail Bridge, our desktop IMAP/SMTP gateway to Proton Mail encrypted email. The fact that Bridge and its client can become desynchronized sporadically for some users is a high priority issue we have been working on. Bridge is open source, and as a result relies upon open-source components, and the root cause is an architectural issue in a library that Bridge uses to implement IMAP. When there are network issues, this library returns errors to email clients. Unfortunately, there are hundreds of email clients, and some email clients don’t handle errors properly, and this leads to desynchronization. Our error tracking shows this does not happen often (1-2% of Bridge users) and the symptom is usually incorrect display of messages or read/unread status which is fixed with an inbox resynchronization. There are cases where a combination of a desynchronized mailbox and a specific series of user actions can lead to accidental email deletion, but this is far rarer than desynchronization. Our implementation tries as hard as possible to avoid this. If you find you are missing an email, our implementation works around the issue by placing it in your All Mail folder, so please check there. If you believe you have an email that is accidentally deleted, please contact our support team and we will do our best to help you undelete it. As Bridge is open source, updates on this issue have always been publicly posted on GitHub. IMAP-compatible encryption is a very difficult task and Bridge must interface with many different email clients, most of which are not open-source making it almost impossible to address all cases where certain clients don’t do error handling properly. Addressing this issue at the source requires replacing the core IMAP library. Unfortunately, there is not exactly a large selection of open-source IMAP libraries to pick from. None in fact are sufficiently well maintained to ensure we don’t run into this issue again. And a commercial library does not work because of Proton’s open-source nature. Therefore, the solution is to build our own IMAP library called Gluon, which we have been focusing on since this issue was reported to us. You can follow the progress or participate in this open-source effort here: https://github.com/ProtonMail/gluon
-
Protonmail can delete the wrong email and nobody cares
This is Bart, Proton CTO here. For clarity, the issue mentioned here only impacts Proton Mail Bridge, our desktop IMAP/SMTP gateway to Proton Mail encrypted email.
The fact that Bridge and its client can become desynchronized sporadically for some users is a high priority issue we have been working on. Bridge is open source, and as a result relies upon open-source components, and the root cause is an architectural issue in a library that Bridge uses to implement IMAP. When there are network issues, this library returns errors to email clients.
Unfortunately, there are hundreds of email clients, and some email clients don’t handle errors properly, and this leads to desynchronization.
Our error tracking shows this does not happen often (1-2% of Bridge users) and the symptom is usually incorrect display of messages or read/unread status which is fixed with an inbox resynchronization. There are cases where a combination of a desynchronized mailbox and a specific series of user actions can lead to accidental email deletion, but this is far rarer than desynchronization. Our implementation tries as hard as possible to avoid this. If you find you are missing an email, our implementation works around the issue by placing it in a users’ All Mail folder.
As Bridge is open source, updates on this issue have always been publicly posted on GitHub. Addressing this issue at the source requires replacing the core IMAP library. Unfortunately, there are no FOSS IMAP libraries that are sufficiently well maintained. Therefore, the solution is to build our own IMAP library called Gluon, which we have been focusing on since this issue was reported to us. You can follow the progress of this open-source project here: https://github.com/ProtonMail/gluon
We are not refusing to fix the problem. The only possible solution is writing a new open-source IMAP library which we can maintain ourselves to ensure this class of errors cannot occur again. We have doubled the size of the team working on this this year so it is a priority for us.
We’re confident that this addresses the main sources of desynchronization and will be available in the beta version of Bridge by the end of the year.
What are some alternatives?
hydroxide - A third-party, open-source ProtonMail CardDAV, IMAP and SMTP bridge
proton-bridge - Proton Mail Bridge application
go-imap - 📥 An IMAP library for clients and servers
jmap - JSON Meta Application Protocol Specification (JMAP)
gpgmda - GPG encrypting MDA