Email or username:

Password:

Forgot your password?
Top-level
dgr

@abcdw

This is why I send the public key as a attachment in every mail. This way you just import it.

On account.proton.me/u/0/mail/enc you can also import keys for advanced users like you.

Proton mail doesn't want to be able to read your mails so your browser needs to unlock your mailbox. IMAP would require them to be able to read your mailbox so they provide you with the bridge so you can install IMAP on a host YOU trust.

@fidel

4 comments
Andrew Tropin

@dgr @fidel I understand why the proton bridge is needed for imap access to proton, but I don't think it's right architectural decision. migadu's approach looks more apropriate to me:
migadu.com/procon/#not-encrypt

dgr

@abcdw @fidel Not quite understand there approach from the link.
But I disagree on some of the points. Encryption on rest means it's a legal hurdle as much as a technological one and there hinting at the Hollywood scenario is stupid as IMHO the worries are nosy admins and greedy police states. I don't think I care about spam and viruses for encrypted mails. Also I could use the bridge to solve the search issue.

Andrew Tropin

@dgr @fidel The approach is to stick to vanilla emails without forced encryption and custom gui apps to access your emails via standard protocols.

If you want encryption, encrypt it with your usual pgp tool.

Personally, I don't see how proton and similiar services improve something, but I clearly see how they make it harder to use standard tools.

dgr

@abcdw for me it's gmail with a added price that ensures, that I'm the customer and not the product. Also it makes it easy for me to handle encrypted email without access to my setup (at work).
@fidel

Go Up