?
Solved

Removing x400 addresses from default e-mail policy

Posted on 2012-03-26
5
Medium Priority
?
3,033 Views
Last Modified: 2012-06-07
Hey Everyone,

In the past we have had issues with with bounce backs on accounts that were re-created for users. I believe the issue is due to the users' x400 addresses. We are looking to remove the x400 from our default email policy to avoid this issue in the future. If I am understanding it correctly, by removing the x400 address, an account that is created in the future will not receive a bounce back because it is only looking at the SMTP address and not looking for a x400 address?

By removing the x400 address from the default policy and applying it, will that remove the x400 address for all accounts that have one or will it keep them and not add an x400 address for future accounts that are created?

Also, we are running Exchange 2010. Recently upgraded from exchange 2003 about 6 months ago.

Any help is appreciated.

Thanks!
0
Comment
Question by:post_university
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
5 Comments
 
LVL 40

Expert Comment

by:als315
ID: 37766925
0
 

Expert Comment

by:ExchangeOnTheRocks
ID: 37767358
Yes, you can safely remove the X400 addresses given that you do not have any other emailing systems apart from Exchange in your setup.
Removing it from the default email policy and applying them will prevent new users from being stamped in Exchnage 2010. Old accounts will still have the X400 address for which you can run the above mentioned script.
0
 

Author Comment

by:post_university
ID: 37770981
After changing the default email policy and running the script to remove all the x400 addresses will we have a bunch of bounce backs since all of our users use autocomplete?

Will their autocomplete file look for that x400 address that is now missing and bounce back?
0
 
LVL 40

Assisted Solution

by:als315
als315 earned 750 total points
ID: 37771176
Autocomplete should not search for x400 addresses, but you can test it: delete one x400 address and try autocomplete
0
 

Accepted Solution

by:
ExchangeOnTheRocks earned 750 total points
ID: 37772394
Autocomplete feature is based on the .nk2 files and looks for legaqcyDN values. It should not look for X400 addresses and hence there should not be any bounce backs.
0

Featured Post

Get real performance insights from real users

Key features:
- Total Pages Views and Load times
- Top Pages Viewed and Load Times
- Real Time Site Page Build Performance
- Users’ Browser and Platform Performance
- Geographic User Breakdown
- And more

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
Outlook for dependable use in a very small business   This article is about using the Outlook application (part of Microsoft Office) in a very small business, or for homeowners where dependability and reliability are critical requirements. This …
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
Suggested Courses

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question