- Plesk for Linux
- Plesk for Windows
Unable to send an email with one of the following message:
CONFIG_TEXT: 554-example.com (hostname) ESMTP Service not available
554-No SMTP service
554 invalid DNS PTR resource record, IP=203.0.113.2
CONFIG_TEXT: Service not available 554-No SMTP service 554-Bad DNS PTR resource record.
CONFIG_TEXT: 21 Temporarily rejected. Reverse DNS for this IP failed. IB108 The IP address attempting to send mail does not have reverse DNS setup, or the DNS lookup failed. Verify the sending IP address has reverse DNS setup before resending the email.
CONFIG_TEXT: 550-5.7.1 [203.0.113.2] The IP address sending this message does not have a PTR
On Linux servers, the one of the following error appears in the
CONFIG_TEXT: postfix/smtp: ... ESMTP Service not available 554-No SMTP service 554 invalid DNS PTR resource record, IP=203.0.113.2
CONFIG_TEXT: hostname postfix/smtp: 52D2D44039: to=<firstname.lastname@example.org>, relay=example.com[203.0.113.111]:25, delay=323220, delays=323220/0.02/0.02/0, dsn=4.0.0, status=deferred (host recipient.com[203.0.113.111] refused to talk to me: Service not available - no PTR record for 203.0.113.2)
CONFIG_TEXT: 550 No rDNS entry for
CONFIG_TEXT: status=bounced (host gmail-smtp-in.l.google.com[2a00:1450:400c:c0b::1b] said: 550-5.7.1 [2001:db8:f61:a1ff:0:0:0:80] Our system has detected that this message does 550-5.7.1 not meet IPv6 sending guidelines regarding PTR records and 550-5.7.1 authentication. Please review 550-5.7.1 https://support.google.com/mail/?p=IPv6AuthError for more information 550 5.7.1 . 138-v6si16372612wmn.177 - gsmtp (in reply to end of DATA command)
CONFIG_TEXT: X-Host-Lookup-Failed: Reverse DNS lookup failed for 203.0.113.2
There is no DNS PTR record for the sender's hostname:
# dig example.com A +short
# dig -x 203.0.113.2 +short
(empty output or not example.com)
PTR (reverse DNS) record is missing for sender's hostname. The mail message is rejected due to security policy on the recipient side.
- Contact Internet Service Provider (ISP) in order to add appropriate PTR records.
- In case of Plesk is installed on Cloud Server check the article How to add PTR record to Cloud Server with installed Plesk?
Note: DNS propagation usually takes 24-48 hours.