It was terrifying enough that it has made me rethink how I manage all of my online accounts. Incidentally, I never had that issue with Gmail in 10+ years.
Not a Protonmail fan.
161–170 of 254 posts
It was terrifying enough that it has made me rethink how I manage all of my online accounts. Incidentally, I never had that issue with Gmail in 10+ years.
Not a Protonmail fan.
Earlier quoted context omitted.
If you’ve been using your mailbox (and deleting mail) for a while, have over 50K mails in it now, and see (what you think is) a UID of 51950 on the most recent email, the chances that it’s “U” are extremely low, meaning there’s a gap in understanding or in implementation.
Every time I see that, I’m floored by it. The fact that message IDs in IMAP change when you delete messages has got to be one of the worst design choices in any in-use protocol. I’m flabbergasted by it. The sooner everyone moves to jmap the better.
The first mechanism is message sequence IDs. If you have a mailbox with N messages in it, these messages are numbered 1-N (inclusive); a new message gets N+1; and deleting message, say, 3 causes 4-N to be renumbered to 3-(N-1). Note that the server can be the one to delete the message (say another connected client deletes it), but server-to-client notifications of message deletion can only happen at specified times in the protocol. The client might still have stale sequence numbers when it sends you the next command however, because IMAP is pipelined. And if you think this sounds like a recipe for lots of weird bugs, you are indeed correct in those thoughts.
So what everyone uses instead are UIDs, which are stable IDs for a message (kind of). UIDs are monotonically increasing (a message with UID 100 is newer than one with UID 95, but there's no guarantee that UID 97 exists), and are not impacted by message creation or deletion. One way to think of them are offsets in the underlying mbox file of where the message lives. If UIDs need to be renumbered (... yay mbox), the server changes the UIDVALIDITY which means that previous UIDs are no longer necessarily valid.
The message sequence numbers kind of make sense, if you imagine that IMAP clients are very, very thin clients that don't maintain any local information, and if you imagine that servers are not expected to support two clients connecting to the same mailbox at the same time. But modern email clients need to maintain their own local database of email metadata, which means that the IMAP protocol has become, in effect, a database synchronization protocol, even though it's not originally designed as such (later IMAP extensions added features that made some elements of synchronization much faster).
Some years ago, I evaluated Protonmail as a replacement for my personal gmail account. When came the steps "can I easily move from this service?", I realized you have to _pay_ to export all your emails from the service. They make it super easy for you to open an account and receive emails, and then makes you pay if you want to get a copy of your own data. I contacted the support to tell them it is likely illegal unde…
Okay, rather than just complaining, I suppose we should gather alternatives, right? mailbox.org hey fastmail tutanota mailfence disroot posteo barracuda (for businesses) vivaldi mail mailpile countermail hushmail I haven't used any of these, so if anyone has others or has experience with any of these, please share your experience.
Earlier quoted context omitted.
Current title is "Protonmail can delete the wrong email and nobody cares". It makes it seem as if using just protonmail could result in deleting a wrong email. This is not the case, you have to be using proton bridge. People who care about protonmail but don't care about proton bridge have to click the link to learn that.
You don’t have to use the bridge for this to happen. Read the issues.
UIDs get desynced between IMAP client and bridge, as the bridge does not seem to use persistent UIDs for messages.
If you don't use the bridge you won't have issues with mismatched UIDs.
JMAP is a replacement for IMAP. Unlike IMAP it has immutable IDs[0] but not much support[1]. [0] https://jmap.io/#faq [1] https://jmap.io/software.html
It would be worthwhile for many reasons not just the immutable IDs. I'd certainly donate to someone showing initiative working on this.
Some years ago, I evaluated Protonmail as a replacement for my personal gmail account. When came the steps "can I easily move from this service?", I realized you have to _pay_ to export all your emails from the service. They make it super easy for you to open an account and receive emails, and then makes you pay if you want to get a copy of your own data. I contacted the support to tell them it is likely illegal unde…
Earlier quoted context omitted.
Nowadays they do provide an app (Import-Export) to export all your mail , even for free tier accounts, so it's quite easy to move away. See: https://proton.me/support/export-emails-import-export-app
Hmm. When I was using Protonmail in free tier, the Import-Export feature was only for the paid tier. Seems strange that they only opened it for free tier now. This should be a feature available to any tier in the first place.
Could the title be update to contain the word bridge as the issue is in the Protonmail bridge application and not on Protonmail itself. The entire title is clickbaity, but adding the birdge moves it away from being misleading.
How is it a click bait? Don't forget bridge is a paid feature of Protonmail.
Earlier quoted context omitted.
Which is close-source (or I didn't find it in their github repo).
The repository for Proton Mail Bridge (which is open source) claims to also host the source for the Import Export app. Here: https://github.com/ProtonMail/proton-bridge Briefly looking at the files and code it's hard to tell whether that is still the case, but it's fair to assume Import-Export would reuse most of the machinery behind Bridge.