Mail server dont send emails

arky_

Verified User
Joined
Apr 25, 2020
Messages
67
I have directadmin installed on proxmox server.
Yesterday I migrated the domain from another provider to directadmin with all the contents of the mailboxes using imapsync.
I have another virtual machine on the same server (proxmox), from which I am trying to send an email via the domain to directadmin.
And here I encountered a problem because the e-mails do not come out.
Both virtuals have the same IP subclass.
I can receive and send e-mails from my personal computer from this domain.
It looks like a firewall is blocking access from the inside
Unfortunately, turning off the firewall does not change anything.

I would like to add that from the virtual machine from which the mail.domena.com server is trying to send e-mails, it responds to the ping.

What is wrong then?
 
On the directadmin server and the second one from which I am trying to send telnet e-mails, it returns to me:
Trying 108.177.127.26 ...
Connected to smtp.google.com.
Escape character is '^]'.
220 mx.google.com ESMTP p17si13570759edq.209 - gsmtp
451 4.4.2 Timeout - closing connection. p17si13570759edq.209 - gsmtp
Connection closed by foreign host.
 
I have an MX record.
I normally send and receive mail from my computer from this domain transferred to directadmin
 
I have an MX record.
No you don't. Or at least it's not propagated then or present on the wrong place.
I don't see your domain name now anymore, but when I check it, no MX record was present.

State your domain name again and I will check again.

What can I do in this case?
Fix your dns.
Next to that it should be mail,domain.com or server.domain.com not domain.example.com. ;)
 
My domain: psk-net.pl

My MX record
Zrzut ekranu (133).png
 
Oke I thought you had some other domain mentioned before. At least now this is good. However, you have some glue record issues.

It seems it finds 176.115.253.11 as nameserver, but only 176.115.253.10 is present as nameservers according to mxtoolbox.
It's not a good idea to run your own nameservers with only 1 ip. But oke, this does not explain the outgoing mail issue.

Then there is another issue. Your mailserver responded with another hostname. It responded with server1.web-hxxxxx4.pl but there is no rDNS record present for this hostname, which will get you into trouble with anti-spam systems, because they almost all check for a valid rDNS record.

Als for connections to mail.psk-net.pl I don't have any issues connecting to port 25, 587 or 993 from my server.
Maybe your home isp is blocking these ports outgoing or if you running this server at home, there can be the issue that your modem does not support nat-loopback, which is needed for this to work.

But as said, from external source, so from my systems, I can connect to these ports on that domain name without issues.

I'll send you pm with something to test for the outgoing mail.
 
Back
Top