• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Reverse DNS does not match SMTP Banner

JohnBee

Basic Pleskian
It would appear that I have this problem on my Plesk server, and I can't figure out what's causing it.
I recently tried replying to an email and got a message saying my email was rejected - I assume this is the cause

With that said, could someone help me troubleshoot and fix this?
 
SMTP Banner is normally the hostname, and it should be a FQDN in an best case scenario.
Reverse DNS needs to be set normally over the Server Providers Panel or Support

You can check the SMTP Banner with:
Code:
# telnet localhost 25

Here as an example:
Code:
root@mail ~ # telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
220 mail.example.com ESMTP Postfix
quit
221 2.0.0 Bye
Connection closed by foreign host.
Here the Banner is mail.example.com

The hostname can be changed over Tools & Settings > Server Settings and over CLI
Code:
# hosnamectl set-hostname mail.example.com

the PTR/Reverse DNS can be checked with:
Code:
# host <IP>

Here as an example:
Code:
root@mail ~ # host 203.0.113.2
2.113.0.203.in-addr.arpa domain name pointer mail.example.com.
 
Hi and thanks so much for helping out with this.
I ran the tests and found the following;

# telnet localhost 25

Connected to localhost.localdomain.
Escape character is '^]'.
220 webshot-5eb7aafc891d2.local ESMTP Postfix

I then looked in Tools & Settings, and found that hostname was indeed properly set with my.hostname.net
I then ran the following command:

# hosnamectl set-hostname my.hostname.net

Then verified with the following:
# host <my IP>

And receive the following response
157.136.141.99.in-addr.arpa domain name pointer my.hostname.net.

With that said, it would appear that my Postfix banner is reporting the webhost hostname rather than the set hostname
Any idea what could cause this, or how I might fix it?
 
Last edited:
My SMTP banner is:
220 mydomain.ca ESMTP Postfix

Is the suggestion really to change the whole server hostname to mail.mydomain.ca ?

Wouldn't the hostname applies to more than just the mail server ?
 
SMTP Banner is normally the hostname, and it should be a FQDN in an best case scenario.
Reverse DNS needs to be set normally over the Server Providers Panel or Support

You can check the SMTP Banner with:
Code:
# telnet localhost 25

Here as an example:
Code:
root@mail ~ # telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
220 mail.example.com ESMTP Postfix
quit
221 2.0.0 Bye
Connection closed by foreign host.
Here the Banner is mail.example.com

The hostname can be changed over Tools & Settings > Server Settings and over CLI
Code:
# hosnamectl set-hostname mail.example.com

the PTR/Reverse DNS can be checked with:
Code:
# host <IP>

Here as an example:
Code:
root@mail ~ # host 203.0.113.2
2.113.0.203.in-addr.arpa domain name pointer mail.example.com.
In my case, I have two records of PTR. Is it okay.
 
The PTR record for a reverse name is expected to resolve to the canonical name of that ip address. That is said 1 name. Why would you want to have multiple PTR records?
 
Back
Top