A certificate you have issued yourself may have details you can more easily verify. If you know or remember certificate details to the Bridge, you can easily verify if something is odd if your mail client warns you about the connection. 1 ShantanuBedajna, because using the ProtonMail SMTP Bridge you're actually connecting to your localhost:1025 first (which is managed by Bridge) and then, through the Bridge, to the actual ProtonMail service. This would also be a good checkpoint, as most IMAP/SMTP clients I've used complains if the cert changes. I believe you can replace them with some certs you have created yourself. In regards to certificates, they are generated on-the-fly if not present.

However, Disroot does support IMAP and POP3 so that you can access your. In this case your VPN server fends off all attacks towards your IMAP/SMTP ports from non-authenticated connections coming from the Internet. ProtonMail uses end-to-end encryption so that messages are only viewable by you. If you put your Bridge behind a properly configured and secured VPN, I would be less concerned. I also don't know how much efforts has been put into hardening the 'server' code, in the regards to fend off various attack possibilities (buffer under-/overflow, memory leaks, etc - anything resulting in breaking authentication or, worse, enabling remote execution of code). The security related to the random generated passwords may be too weak for bruteforce attacks as well. The Bridge is not designed to be accessible via a public IP Address.

Protonmail imap smtp