Email Deliverability Issue

[kartick35]

can anyone suggest what to do ,,

REVERSE DNS (PTR) PROBLEMS EXIST
The system uses an alternate HELO of “47-113-201-241.cprapid.com” when sending mail from the “sumenedu.com” domain.
The system sends “abcd.com”’s outgoing email from the “x.x.x.x” IP address. The only PTR value for this IP address must be “x-x-x-x.cprapid.com”. This is the name that this server sends with SMTP’s “HELO” command to send “abcd.com”’s outgoing email.
1 unexpected PTR value exists for this IP address:

• abcd.com

To fix this problem, contact your system administrator and request that they replace all PTR records for “x.x.x.x.in-addr.arpa” with the following record at “rdns1.alidns.com” and “rdns2.alidns.com”:
Suggested “PTR” (PTR) Record PTR

 

[cPRex]

Hey there! It sounds like the first thing you may want to resolve is to setup a permanent hostname on the machine so you aren't using the cprapid.com domain name. We have a guide on changing the hostname here:

Change Hostname | cPanel & WHM Documentation

This interface allows you to change your server's hostname.

docs.cpanel.net

Once that is done, can you make sure the reverse DNS is setup properly at the hosting provider? After that, I would expect the message on that page to change.

 

[kartick35]

Hey there! It sounds like the first thing you may want to resolve is to setup a permanent hostname on the machine so you aren't using the cprapid.com domain name. We have a guide on changing the hostname here:

Change Hostname | cPanel & WHM Documentation

This interface allows you to change your server's hostname.

docs.cpanel.net

Once that is done, can you make sure the reverse DNS is setup properly at the hosting provider? After that, I would expect the message on that page to change.

Thanks fyr

so 1st need to change host name of server current name is 47-113-201-241.cprapid.com ?
i am facing same to another server

 

[cPRex]

That's exactly correct - I would start by making sure the hostname is valid and pointing to a domain you control.

 

[t0mth3cat]

i have change my hostname but still work only with 13-215-151-251.cprapid.com
any idea?

 

[cPRex]

@t0mth3cat - we need more details on the problem you're having. Can you let us know what exactly isn't working properly, and if you get any errors?

 

[t0mth3cat]

<redacted by moderator>

 

[cPRex]

Thanks for those details. It's best not to include public domains for security reasons so I removed that post.

In general, you only want to use the hostname of the server for the actual hostname. You're likely experiencing DNS propagation with the new changes, as they aren't working instantly. I do see there is an A record in place for the admin subdomain, so once that exists for a bit I would also expect that to work for the MX record if you wanted to use it there.

If that isn't happening, please submit a support ticket to our team so we can take a look at the server settings for you.

 

[t0mth3cat]

Thank you! it work this time, it could be my ssl configuration. However, my outlook 2021 configuration does not seem to work now with the new hostname. any idea? imap and smtp

 

[cPanelWilliam]

Hi,

Can you let us know what type of error you were receiving in Outlook? If it is an SSL-related error, you may want to ensure the hostname is covered by an SSL certificate. You can use the /usr/local/cpanel/bin/checkallsslcerts script to renew the hostname certificate if it is not valid.

 

[t0mth3cat]

Hi, it just could not connect with the new hostname, imap and smtp in outlook but work fine in webmail horde

The system will check for the certificate for the “cpanel” service.
The system will attempt to verify that the certificate for the “cpanel” service is still valid using OCSP (Online Certificate Status Protocol).
The “cpanel” service’s SSL certificate is invalid. (Certificate #2 (ST=California,L=San Francisco,OU=CloudFlare Origin SSL Certificate Authority,O=CloudFlare\, Inc.,C=US) has 2 validation errors:SELF_SIGNED_CERT_IN_CHAIN, CERT_HAS_EXPIRED.) The system will attempt to replace it with a new certificate from the cPanel Store.
The system will attempt to install a certificate for the “cpanel” service from the system ssl storage.
The system will use the signed certificate for the hostname, on the “cpanel” service, that it found in the system’s SSL datastore.
Attempting to verify your certificate.....
warn [checkallsslcerts] CloudFlare Origin Certificate domain name must have a valid TLD label
warn [checkallsslcerts] The primary domain “CloudFlare Origin Certificate” on certificate that iscurrently installed for “cpanel” is not valid.
Querying Apache TLS for installations of the previous certificate …
The new certificate is the same certificate as the previous one.
The system will check for the certificate for the “dovecot” service.
The system will attempt to verify that the certificate for the “dovecot” service is still valid using OCSP (Online Certificate Status Protocol).
The “dovecot” service’s SSL certificate is invalid. (Certificate #2 (ST=California,L=San Francisco,OU=CloudFlare Origin SSL Certificate Authority,O=CloudFlare\, Inc.,C=US) has 2 validation errors: SELF_SIGNED_CERT_IN_CHAIN, CERT_HAS_EXPIRED.) The system will attempt to replace it with a new certificate from the cPanel Store.
The system will attempt to install a certificate for the “dovecot” service from the system ssl storage.
The system will use the signed certificate for the hostname, on the “dovecot” service, that it found in the system’s SSL datastore.
Attempting to verify your certificate.....
warn [checkallsslcerts] CloudFlare Origin Certificate domain name must have a valid TLD label
warn [checkallsslcerts] The primary domain “CloudFlare Origin Certificate” on certificate that iscurrently installed for “dovecot” is not valid.
The system will check for the certificate for the “exim” service.
The system will attempt to verify that the certificate for the “exim” service is still valid using OCSP (Online Certificate Status Protocol).
The “exim” service’s SSL certificate is invalid. (Certificate #2 (ST=California,L=San Francisco,OU=CloudFlare Origin SSL Certificate Authority,O=CloudFlare\, Inc.,C=US) has 2 validation errors: SELF_SIGNED_CERT_IN_CHAIN, CERT_HAS_EXPIRED.) The system will attempt to replace it with a new certificate from the cPanel Store.
The system will attempt to install a certificate for the “exim” service from the system ssl storage.
The system will use the signed certificate for the hostname, on the “exim” service, that it foundin the system’s SSL datastore.
Attempting to verify your certificate.....
warn [checkallsslcerts] CloudFlare Origin Certificate domain name must have a valid TLD label
warn [checkallsslcerts] The primary domain “CloudFlare Origin Certificate” on certificate that iscurrently installed for “exim” is not valid.
warn [checkallsslcerts] CloudFlare Origin Certificate domain name must have a valid TLD label
warn [checkallsslcerts] The primary domain “CloudFlare Origin Certificate” on certificate that iscurrently installed for “exim” is not valid.
Failed to analyze certificate for service: exim at /usr/local/cpanel/Cpanel/SSLCerts.pm line 1092.
warn [checkallsslcerts] CloudFlare Origin Certificate domain name must have a valid TLD label
warn [checkallsslcerts] The primary domain “CloudFlare Origin Certificate” on certificate that iscurrently installed for “cpanel” is not valid.
Failed to analyze certificate for service: cpanel at /usr/local/cpanel/Cpanel/SSLCerts.pm line 1092.
warn [checkallsslcerts] CloudFlare Origin Certificate domain name must have a valid TLD label
warn [checkallsslcerts] The primary domain “CloudFlare Origin Certificate” on certificate that iscurrently installed for “dovecot” is not valid.
Failed to analyze certificate for service: dovecot at /usr/local/cpanel/Cpanel/SSLCerts.pm line 1092.

 

[cPRex]

It looks like the CloudFlare certificate could be the problem, as that's not something that is issued by cPanel.