Docker Mailserver
How can I submit mail to port 25 for DMS to send? #3995
Replies: 2 comments 3 replies
-
|
Please note that this response was created using generative AI, leveraging previously available information from the repository. This information may be helpful. However, it is our strong recommendation that you carefully consider the information before blindly applying it. To assist you effectively, could you please provide the specific error message you are encountering when using port 25? This will help in diagnosing the issue more accurately. This comment was generated by Glime. |
Beta Was this translation helpful? Give feedback.
-
|
Port 25 is not authorized for mail submission, only delivery. You have ports 465 or 587 to authenticate against when you want to provide mail for DMS to send.
If you search our issues or discussions, you will find advice on how to enable port 25 for sending mail without authentication, but it would be better for you to troubleshoot the above guidance so that you can send mail properly. |
Beta Was this translation helpful? Give feedback.
-
|
Hello polarathene, Email is already setup and working I have it in Thunderbird working. All the apps are in container inside the same docker, when trying to send I constantly get this error. DockerMail -> port 465 TLS Passbolt -> port 465 TLS DockerMail -> port 587 TLS Passbolt -> port 587 TLS I forgot to put the compose file to check if I'm doing something wrong. One thing to keep in mind is the way I have the network designed. services:
mailserver:
image: ghcr.io/docker-mailserver/docker-mailserver:latest
container_name: mailserver
# Provide the FQDN of your mail server here (Your DNS MX record should point to this value)
hostname: mail.example.com
# Automatic cleanup (removes older image pulls from wasting disk space):
environment:
- SSL_TYPE=manual
- ENABLE_RSPAMD=1
- ENABLE_CLAMAV=1
- ENABLE_FAIL2BAN=1
- ONE_DIR=1
- POSTFIX_MESSAGE_SIZE_LIMIT=26214400
- ENABLE_OPENDKIM=0
- ENABLE_OPENDMARC=0
- ENABLE_POLICYD_SPF=0
- ENABLE_AMAVIS=0
- ENABLE_SPAMASSASSIN=0
- SSL_CERT_PATH=/tmp/dms/custom-certs/example.com.crt
- SSL_KEY_PATH=/tmp/dms/custom-certs/example.com.key
env_file: mailserver.env
# More information about the mail-server ports:
# https://docker-mailserver.github.io/docker-mailserver/latest/config/security/understanding-the-ports/
# To avoid conflicts with yaml base-60 float, DO NOT remove the quotation marks.
ports:
#- "25:25" # SMTP (explicit TLS => STARTTLS, Authentication is DISABLED => use port 465/587 instead)
#- "143:143" # IMAP4 (explicit TLS => STARTTLS)
- "465:465" # ESMTP (implicit TLS)
- "587:587" # ESMTP (explicit TLS => STARTTLS)
- "993:993" # IMAP4 (implicit TLS)
volumes:
- /docker/certificates/:/tmp/dms/custom-certs/:ro
- ./docker-data/dms/mail-data/:/var/mail/
- ./docker-data/dms/mail-state/:/var/mail-state/
- ./docker-data/dms/mail-logs/:/var/log/mail/
- ./docker-data/dms/config/:/tmp/docker-mailserver/
- /etc/localtime:/etc/localtime:ro
restart: unless-stopped
stop_grace_period: 1m
cap_add:
- NET_ADMIN
healthcheck:
test: "ss --listening --tcp | grep -P 'LISTEN.+:smtp' || exit 1"
timeout: 3s
retries: 0Thanks in advance for the assist. |
Beta Was this translation helpful? Give feedback.
-
This is likely because the connection is going through the docker network gateway (
These two similar errors are about the same issue. They cannot verify your custom cert as the CA is not known. The client (containers?) would need to have the CA used to sign your certificate in their trust stores to trust the certificate you've configured for DMS. Normally this is a non-issue as your certificate is signed by a CA already in the trust store like LetsEncrypt. If you are new to this, you'll want to gain a better understanding of how to work with your own internal certificates. This isn't likely to be a DMS specific issue. Ensure that you're not using self-signed certificates (no root CA used to establish trust), once you've provisioned the certs correctly and any client has the signing CA in their trust stores they should be able to verify without an issue. Some guidance for troubleshooting along the wayIn the DMS test suite, we use timeout 1 openssl s_client -connect mail.example.com:587 -starttls smtp -CAfile '/path/to/ca-cert.pem'You can run that locally or in the container (with That should then have some output that includes After that, you'll want to learn how to add your CA cert to your trust stores. This varies by OS distro, so might differ per container you have and you may need to run some commands to update the trust store beyond adding your CA cert there. When you've done that successfully, that |
Beta Was this translation helpful? Give feedback.
-
|
Hello @polarathene, Thank you for the information, there are a couple of things that are not clear to me. I'm using several containers inside the same docker, if I insert the
Is there a way in DockerMail to ignore TLS if connections are coming from private IPs or at least a whitelist to add the IP. Another thing that I want to check, is if all the apps and DockerMail are in the same docker network does that bypass the TLS requirements? I understand how certificates work, but this is my first time working with LetsEncrypt certificates not being run by the OS and yes by the proxy. Running by the OS it will insert the CA in the From my understanding the apps, mail servers, API, etc, should have the full chain certificate, usually a .pem, but in the variables for the several docker apps it seems that every app is only making "gets" to the .crt and .key, but in theory the .crt is also the CA which was copied to the trusted store. https://ubuntu.com/server/docs/install-a-root-ca-certificate-in-the-trust-store And yes the CA in theory was uploaded correctly to the trust store. For this reason I need a bit of help understanding how to make this viable without the certificates if private networking is in use or if all containers are in the same docker network. Only outgoing emails, communications, webservices or API are mandatory to have certificate signing, that the proxy handles it. In hopes this helps to have a cleared picture if what I'm facing and what I wish to accomplish. |
Beta Was this translation helpful? Give feedback.
-
when using port 25 I'm receiving the following error.
I'm using port 25 to send messages from apps since I'm struggling to get them to work with port 465 and I need a temporary solution.
Beta Was this translation helpful? Give feedback.
All reactions