Bridge runs in the background by seamlessly encrypting and decrypting messages as they enter and leave your computer. ProtonMail Bridge is an application available to all paid users that enables the integration of your ProtonMail account with popular email clients, such as Microsoft Outlook, Mozilla Thunderbird, or Apple Mail. Let me quote them because it basically explains it all: If you found this post you most likely already know what ProtonMail Bridge is. I am happy to pay ProtonMail and have my mind at ease. You can argue why not self host? Well for my personal situation I think setting up and maintaining a mailserver is just not worth my time. Online privacy is something I am very concerned with and that’s why it was a logical move for me to switch to ProtonMail. In this post I will show you how to properly configure ProtonMail Bridge SMTP config with Apple Mail on macOS Big Sur. Output of route in the Docker container: Kernel IP routing tableĭestination Gateway Genmask Flags Metric Ref Use Ifaceġ72.17.0.0 0.0.0.0 255.255.0.Reading Time: 4 minutes ProtonMail with ProtonMail bridge I'm not sure if this is the problem either. Nmap 172.17.0.1 in the docker container does not output any 1025 port. Nmap 127.0.0.1 on the host machine outputs: Nmap scan report for localhost (127.0.0.1) I’m wondering if the Protonmail Bridge service that’s listening on 127.0.0.1:1025 is not accepting connections from the Docker container because they are not coming from 127.0.0.1 exactly? If this is the problem, how to validate and fix? If this is not the problem, what am I doing wrong? Openssl s_client -connect 127.0.01:1025 -starttls smtp State Recv-Q Send-Q Local Address:Port Peer Address:Port Process I checked open ports on the host machine, all good: ss -plnt Issue: From the Docker container, I cannot connect to the SMTP server exposed by the Protonmail Bridge on the host machine. Docker container running Discourse with their default recommended setup.Host machine running Protonmail Bridge as a service.
0 kommentar(er)
