Operating system: Ubuntu
OS version: 20.04
it is the second issue on my way to the happiness with Virtualmin :-).
For outgoing mail it looks like the messages are received by postfix - I can see them in the Mail Queue but the postfix cannot connect to the recipient’s server - I see the connection timeout messages
What about Dovecot - I have no idea where to look - the remote sender “successfully” send the mail without any errors but I cannot see it in my inbox.
Check first of all if your VPS provider has blocked port 25 and it is this which is preventing your system from sending out mail - and if so, see
If your VPS host (AWS, OVH, Vultr, Bluehost, Digital Ocean et al) is blocking port 25 and this is causing problems with your Virtualmin installation and testing, I will be happy to offer you free smarthost / mail relay service for testing or low volume email.
To get started, you will need to send me the IP address of your Virtualmin box (VPS) and the list of domain names which will be authorized to send email. I will then give you the IP address of my Virtualmin box and the SPF and DKIM records…
Use Virtualmin’s webmail on port 20000 to check if the incoming mail has landed in the mailbox.
For both questions you need to check in
You should have log entries similar to what I have pasted below.
Jan 14 14:22:16 alpha postfix/smtpd: EA5F661222: client=unknown[xxxxxxxxx], sasl_method=PLAIN,
Jan 14 14:22:17 alpha postfix/cleanup: EA5F661222: message-id= firstname.lastname@example.org
Jan 14 14:22:17 alpha postfix/qmgr: EA5F661222: from= email@example.com, size=740, nrcpt=1 (queue active)
Jan 14 14:22:17 alpha postfix/smtp: EA5F661222: to= firstname.lastname@example.org, relay=smtp.domain.no[xxxxxxxxx]:26, delay=1.1, delays=0.2/0.02/0.79/0.05, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as F12F7BFA3A)
Jan 14 14:22:17 alpha postfix/qmgr: EA5F661222: removed
Jan 14 15:05:29 alpha postfix/smtpd: CC62C61217: client=sf3.domain.no[xxxxx]
Jan 14 15:05:29 alpha postfix/cleanup: CC62C61217: message-id= 0.1.235.6F9.1D6EA7E487DA94A.email@example.com
Jan 14 15:05:30 alpha postfix/qmgr: CC62C61217: from= firstname.lastname@example.org, size=18449, nrcpt=1 (queue active)
Jan 14 15:05:30 alpha postfix/local: CC62C61217: to= xxx-domain.net@x, orig_to= email@example.com, relay=local, delay=0.85, delays=0.81/0.02/0/0.02, dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail-wrapper -o -a $DOMAIN -d $LOGNAME)
Jan 14 15:05:30 alpha postfix/qmgr: CC62C61217: removed
While writing this, I noticed
@calport also replied and mentioned checking port 25 like I also was going to say.
An easy way of checking that is trying to telnet port 25 of a known mailserver:
Connected to alt2.gmail-smtp-in.l.google.com.
Escape character is ‘^]’.
220 mx.google.com ESMTP bd8si6250279plb.207 - gsmtp
Yes. The port is blocked. It is AWS. But does it mean that there is no way to have my own smtp server on AWS instance?
You can take a look
Personally don’t use AWS but according to this it should be possible.
Some more details.
On AWS instances i can open port 25 but only the incoming connections are under my control. It resolved the problem with incoming messages.
The outgoing messages are still under the big question. I will contact AWS about it.
Sounds correct. The link I gave you tells you which form to fill to request opening of outbound also.
Thank you so much. They’ve opened 25 port for me. Bud it needed some magic with dns records also.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.