Error sending message to gmail

algito

Verified User
Joined
Dec 9, 2022
Messages
9
Hi, I am new to this and I recently installed directadmin on a CENTOS server and it shows this error when I try to send a message to gmail.

Code:
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  [email protected]
    host gmail-smtp-in.l.google.com [2607:f8b0:4023:c0d::1a]
    SMTP error from remote mail server after end of data:
    550-5.7.25 [2602:fd92:110:a::c] The IP address sending this message does not
    550-5.7.25 have a PTR record setup, or the corresponding forward DNS entry does
    550-5.7.25 not point to the sending IP. As a policy, Gmail does not accept
    550-5.7.25 messages from IPs with missing PTR records. Please visit
    550-5.7.25  https://support.google.com/mail/answer/81126#ip-practices for more
    550 5.7.25 information. j4-20020a170902da8400b00189abdd3fcbsi2406024plx.263 - gsmtp

I am looking for the solution, thank you very much for your answers.
 
Hello,

The error is "The IP address sending this message does not have a PTR record setup". You should add a correct PTR record for your IPv6 2602:fd92:110:a::c. It can be done through the control panel where you purchased your virtual server. You might check documentation of your server provider on how to do it.

A server should have a valid hostname, which is to resolve to IPv4 and/or IPv6 from your network device. The mentioned IPv4/IPv6 should resolve to the hostname used on the server.
 
If I use a valid Host in IPv4, but it seems to me that my service does not allow me to do the same in IPv6 or if there is any way I would appreciate it.


Screenshot_3.jpg

Screenshot_4.jpg
 
does not allow me to do the same in IPv6 or if there is any way I would appreciate it.
Did you create a PTR record at your ipv6 provider (datacenter mostly) for your hostname too?
Because you need to have a PTR record for both ipv4 and ipv6 if you want to use both.

And it seems you don't have a PTR record for your ipv6 ip yet.
 
If I use a valid Host in IPv4, but it seems to me that my service does not allow me to do the same in IPv6 or if there is any way I would appreciate it.

So if it is a Google Cloud you might take a look at this page: https://cloud.google.com/compute/docs/instances/create-ptr-record

If they do not allow to change PTR records for IPv6, then you might disable Exim from using it per this guide: https://docs.directadmin.com/other-...iled-address-family-not-supported-by-protocol
 
@zEitEr and @Erulezz aren't you both mistaken?

When I look at the error notice, I see this:
[email protected]
host gmail-smtp-in.l.google.com [2607:f8b0:4023:c0d::1a]
So this ipv6 is indeed from Google, as this is the receiving server.

The information of the sending server is below these lines:
SMTP error from remote mail server after end of data:
550-5.7.25 [2602:fd92:110:a::c] The IP address sending this message does not
550-5.7.25 have a PTR record setup, or the corresponding forward DNS entry does
So to this says that 2602:fd92:110:a::c is the originating ipv6 from his server. And as far as I can see that is not from Google or Google Cloud.
It's from Madcityservers LLC in Chicago, or are they also from Google?

IMHO he only needs to create a PTR record for his 2602:fd92:110:a::c ip address.
Or am I missing something?
 
I agree with Richard. He needs the PTR record for 2602:fd92:110:a::c and the corresponding AAAA record for the forward. I have been through this myself with Google and ipv6.
 
So if it is a Google Cloud you might take a look at this page: https://cloud.google.com/compute/docs/instances/create-ptr-record

If they do not allow to change PTR records for IPv6, then you might disable Exim from using it per this guide: https://docs.directadmin.com/other-...iled-address-family-not-supported-by-protocol
Well I stopped using IPV6 and now the mail messaging works correctly.

I have a question, if I stop using IPv6 I may have a problem...

Thank you very much for your answers.
 
Last edited:
I have a question, if I stop using IPv6 I may have a problem...
Normally not. We don't use ipv6 yet either. But we disabled ipv6 totally.

However, as you can read it's a simple solution, enable ipv6 and then set the PTR record, just not in Google cloud but at your datacenter, same as you did with the ipv4 ip.

But again, you can also just use ipv4 until ipv6 is really required. It's not yet so it normally won't give issues.
And if it does, just report back here on the forums. :)
 
Back
Top