A little something about everything

internet marketing and website development made simple..

Gmail rejecting exchange 2010 2013 emails with: The sender does not meet basic ipv6 sending guidelines of authentication and rdns resolution of sending ip.


gmail.com is rejecting emails from Microsoft Exchange 2010 and Microsoft Exchange 2013 email servers for no PTR records even if you do not have any IPv6 IPs assigned to the server.



The sender does not meet basic ipv6 sending guidelines of authentication and rdns resolution of sending ip. Please review https://support.google.com/mail/answer/81126for more information.

Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.

Diagnostic information for administrators:

Generating server: EXCHANGE.a51.biz

{email address}
mx.google.com #550-5.7.1 [ipv6info] The sender does not meet basic 550-5.7.1 ipv6 sending guidelines of authentication and rdns resolution of 550-5.7.1 sending ip. Please review 550 5.7.1 https://support.google.com/mail/answer/81126 for more information.



Disable certain IPv6 components yourself, follow these steps:

  1. Use the registry editor to edit the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
    • Edit or create DWORD (32-bit) value "DisabledComponents".
    • Default value is "0", you will need to change this to "0xffffffff"(Hexadecimal "ffffffff" or Decimal "4294967295") in order to disable all IPV6 other than local loopback.
  2. Verify that IPV6 is disabled with the following command: "reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /v DisabledComponents"
    • You may receive the following error message: "ERROR: The system was unable to find the specified registry key or value."
    • If you receive this error message, the DisabledComponents registry value is not set. If the DisabledComponents value is set, it overrides the settings in the connection properties.

Solution 2:

If you have IPv6 IP's enabled on the server verify that your PTR records are correctly setup.

Comments (8) -

  • M.S. Lucas - TAOS-IT

    8/22/2013 3:27:05 AM |


    Additional guidelines for IPv6
    •The sending IP must have a PTR record (i.e., a reverse DNS of the sending IP) and it should match the IP obtained via the forward DNS resolution of the hostname specified in the PTR record. Otherwise, mail will be marked as spam or possibly rejected.
    •The sending domain should pass either SPF check or DKIM check. Otherwise, mail might be marked as spam.

  • Dmitry

    9/12/2013 6:54:55 AM |

    thnx for your article,
    but you have little mistake - please edit DisabledComponets to DisabledComponents in first step

  • Shawn Hyde

    9/12/2013 3:04:02 PM |

    updated typo. Thanks!

  • Gil

    9/14/2013 12:29:34 PM |

    You forgot to mention you must restart the server for this to take effect.

  • Alf Sedeniussen

    9/24/2013 11:13:47 AM |

    I have 2 Exchange servers in our organization. I have disabled ipv6 on both, and added the key as described in this article, but we still get ipv6 error messages from gmail. Some emails get through, others is rejected by gmail.

  • Shawn Hyde

    9/24/2013 11:26:55 AM |

    Alf, verify that you have restarted the server. Also do you have any server in front of these for filtering etc?

  • Nikola

    10/8/2013 6:19:46 AM |

    Worked for me, thanks.
    Alf maybe you forgot the edge server?
    One other strange thing i noticed. I c&p 0xffffffff from this site to registry editor..im connected via rdp to my exchange server.
    when i paste this value to my dword it looks like this 0xffffff (6 fs) and regedit adds 41 so the key looks like this 0x41ffffff
    its not a clipboard issue since when i paste it as a key name on the same server at the same time it pastes fine.

  • Ravencio

    10/25/2013 10:44:48 PM |

    Can't I just go to properties of my network card and disable the IPv6 TCP/IP Protocol?? (since I do not plan on ever using that)

Add comment