shenxn / protonmail-bridge-docker

ProtonMail IMAP/SMTP Bridge Docker container
GNU General Public License v3.0
356 stars 73 forks source link

SMTP access from local network #2

Open bjladner opened 4 years ago

bjladner commented 4 years ago

Are you able to use the SMTP server from a different machine on the local network? Protonmail-bridge only listens on 127.0.0.1? I assume this is possible since each docker container has a different ip address, but I can't figure out how to do it? Can you help me?

shenxn commented 4 years ago

The socat here will do this for you https://github.com/shenxn/protonmail-bridge-docker/blob/155b4767a4b20b5945494f8b2432ed97cb930655/entrypoint.sh#L37-L41 This is actually a workaround by Hendrik Meyer in his implementation.

bjladner commented 4 years ago

Thanks. It must be a different reason I am not getting emails. Is there a log I can refer to for errors?

shenxn commented 4 years ago

@bjladner Have you tried installing the bridge directly on your machine? The logs are located at /root/.local/state/protonmail/bridge inside the docker image.

bjladner commented 4 years ago

I've tried everything from scratch and it still failed. The log has a bunch (>50) lines that say:

{"level":"warning","msg":"Retrying /settings/mail after 10s induced by http code 429","pkg":"pmapi","time":"2020-05-16T21:19:55Z","userID":"ojLEJrizXRfVS3_mk4HbltaSEKqlynwov3gUn7nv0O1VbkfIt_zB-a_Us3OfPerHrR9y9ANIOmJrkyxqz83SpA=="}

I can ping the server and telnet the port (1025) from the local network, however, when I try to use it as a smtp server, nothing connects to it. I'm using the provided port, username, password and STARTTLS options from the initial setup.

bjladner commented 4 years ago

I am also seeing this too :

{"level":"warning","msg":"Matched fingerprint (\"pin-sha256=\\\"***ireplacedthiswithabunchofletters***=\\\"\") was not primary pinned key (was key #3)","pkg":"pmapi/tls-pinning","time":"2020-05-16T23:30:04Z"}
shenxn commented 4 years ago

@bjladner The log does not mean much to me. There is obviously something going on here since I don't see these logs on my local docker and everything works well. Just wanna check, have you tried the official installer directly on your machine? Is that working well? Also, what operating system and email client are you using?

bjladner commented 4 years ago

I have not tried it on it directly on my machine. I have only tried the docker install. I am using a headless ubuntu 20.04 virtual machine and was hoping to use this proton mail bridge as an SMTP server for other dockers on other VMs to use when they need to email error reports. If I try it directly on the VM, I'm not sure what I can use to test it out since clients can only be on 127.0.0.1 and this "machine" is headless. I have a windows machine I can try it on directly to help debug. Thanks for your help. I'll let you know if I get any more information.

shenxn commented 4 years ago

@bjladner Try install bridge on your windows machine and test. Currently the bridge has problem with many email clients. See https://protonmail.com/bridge/clients for the list of clients that are promised to work.

TrevorSLong commented 3 years ago

I know this thread is old but I'm going to list what worked for me on Unraid after a while of troubleshooting to hopefully help someone in the future: -Put the network type to host mode -I matched the host port to container port (25 and 143) -In Bitwarden and Nextcloud I put the host as my Unraids IP number (192.168.X.X) -Use port 25 for in SMTP settings -Username and password as what is listed if you type info -In Bitwarden I had to change secure SMTP to off and force TLS to on -In Nextcloud I had to turn encryption off

Currently everything is working for me, hope this helps!