Link to home
Start Free TrialLog in
Avatar of RJMiller78229
RJMiller78229Flag for United States of America

asked on

Bounce when sending to gmail accounts

Very recently I have had users starting to get this error.  We are in transition from postini to google apps.  We don't use postini for outgoing and incoming email seems to be unaffected as does email to other domains but gmail.com.

This is the error that my users are getting when sending to gmail addresses.

mx.google.com rejected your message to the following e-mail addresses:
rjmiller78229@gmail.com
mx.google.com gave this error:
[2002:18f2:a483::18f2:a483 16] Our system has detected that this message does not meet IPv6 sending guidelines regarding PTR records and authentication. Please review https://support.google.com/mail/answer/81126 for more information. u6si2399853obi.28 - gsmtp
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 e-mail from certain senders, or another restriction may be preventing delivery.
Avatar of Jamie McKillop
Jamie McKillop
Flag of Canada image

Hello,

You need to have a PTR record created in your reverse zone for the IP of your Exchange server.

JJ
ASKER CERTIFIED SOLUTION
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of RJMiller78229

ASKER

The problem seems that Google has begun doing reverse dns checks on IPv6 addresses if provided by server sending to their domain (gmail.com).

I do not explicitly have IPv6 turned on or IPv6 dhcp, etc.  However Microsoft has provided a 6to4 network device which provides some type of IPv6 address.  I am not aware if it is local or public or even if that distinction is relevant to IPv6.  Anyway, in order to fix this your email server MUST NOT have an IPv6 address as it will send it in the email packet.

I solved this by deleting the 6to4 adapter and IPv6 tunnel adapter... worked for a while, until they "grew back".

Final solution was to disable both.  Has not "grown back" or enabled "itself".

Sembee2 was on the track of the solution but did not actually provide a solution.  His information did send me down the right track which I probably would never have found by myself.

Thanks, Sembee2.

RJMiller
See my posting... didn't know I should put my comments here.

Thanks, Simon.