If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
IPv6 with Local Exchange sending Bounce Backs
We have a client who is on Comcast with a static IPv4 address and local Exchange. Comcast has started rolling out IPv6 on everything and they are now receiving bounce backs when sending out (message below). I've contacted Comcast and they say that they cannot assign a static IPv6 address, therefore we cannot set reverse DNS for IPv6. I have added their IPv6 address to their SPF record which solved the issue temporarily, but since the IPv6 is dynamic it has changed, then they get bounce backs again.
We have a number of clients behind a hardware firewall, which we disable IPv6 on, and they are not having any problems as they are only communicating with the world on IPv4.
Any idea on a permanent fix to resolve this IPv6 dynamic address issue that inevitably causes bounce backs?
We have a number of clients behind a hardware firewall, which we disable IPv6 on, and they are not having any problems as they are only communicating with the world on IPv4.
Any idea on a permanent fix to resolve this IPv6 dynamic address issue that inevitably causes bounce backs?
Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.
The following organization rejected your message: mx.google.com.
____________________________________ ____
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: SERVER.[xxxx].local
[xxxx]@gmail.com
mx.google.com #550-5.7.1 [2601:[xxxx]:c05c] Our system has detected that 550-5.7.1 this message does not meet IPv6 sending guidelines regarding PTR 550-5.7.1 records and authentication. Please review 550-5.7.1 https://support.google.com/mail/?p=ipv6_authentication_error for more 550 5.7.1 information. x75si3472751ioi.11 - gsmtp ##
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
We're not having an issue with Exchange itself, the problem is the bounce back we receive when sending. I don't see how the version of Exchange would be causing this type of bounce back, but again, I don't know which is why I'm here. If this is the case, is there any more information you could provide?
Thank you, good article. One client we're having the issue with is on Exchange 2010, the other is on Exchange 2013.
In both cases, everything seems to be working as far as IPv6 is concerned, the issue is with external spam filters, namely Google in this case, bouncing back messages with the message in my original post.
We are not able to get reverse DNS setup on the IPv6 address because it is not static, and since it's not static and keeps changing, SPF records need to be updated frequently.
So, in either case of whether or not the version of Exchange supports IPv6, the issue is not appear to be with Exchange itself. (Exchange was the best tag I could use on this post)
In both cases, everything seems to be working as far as IPv6 is concerned, the issue is with external spam filters, namely Google in this case, bouncing back messages with the message in my original post.
We are not able to get reverse DNS setup on the IPv6 address because it is not static, and since it's not static and keeps changing, SPF records need to be updated frequently.
So, in either case of whether or not the version of Exchange supports IPv6, the issue is not appear to be with Exchange itself. (Exchange was the best tag I could use on this post)
Why IPv6 is not static in your case? If you are using Public IPs then they will be static else your natting will not work.
Comcast does not offer static IPv6. The client does have static IPv4, but Comcast says they cannot assign static IPv6.
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trialIt's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange
From novice to tech pro — start learning today.
-
Microsoft ApplicationsCertification: MOS Microsoft Office Specialist - Word 2013 Part … 198 lessons
-
Microsoft ApplicationsCertification: MOS Microsoft Office Specialist - Outlook 2007 Ad… 147 lessons
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with premium.
Start your 7-day free trial.
Newer version like Exchange 2013 and 2016 are supporting IPv6.