-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use port 110 instead of port 25? #105
Comments
This is the exact reason that I don't use GCP. And it seems that they don't let you remap ports which is silly. The easiest solution is to see if you can use a reverse proxy like Traefik (this is what I do to get email on 110). If you want to do it natively in the container then you will have to clone the repo and build your own with port 110 exposed instead of 25, you will also have to make the necessary postfix changes. |
I believe this can be easily achieved by remapping the port by the docker run -e SMF_CONFIG -p 25:110 zixia/simple-mail-forwarder |
Hi Huan, Can you confirm if this indeed works? |
@ibnYusrat I have not confirmed by myself, but I guess it should work, except that the port should be switched: docker run -e SMF_CONFIG -p 0.0.0.0:110:25 zixia/simple-mail-forwarder See: https://docs.docker.com/config/containers/container-networking/ |
Hi,
Thank you for this amazing docker image. I am trying to deploy this in a compute engine on GCP. However, by default GCP has blocked port 25 permanently. Is it possible to use port 110 instead? Please help!
The text was updated successfully, but these errors were encountered: