• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 204
  • Last Modified:

Exchange 2007 custom recipient policy

I'm running an Exchange 2007 site where the default email address policy is <first name>@<domain> - nothing more.  It's a fairly small site, but we've suddenly got 3 people called Graham...

Using the recipient policies in Exchange, I get "Graham@domain", but then "Graham2@domain" etc.  Is there a way of specifying an alternative template in case of conflicts?

My template at the moment is (obviously) %g@domain, but I'd like it to revert to %g%1s@domain in case of conflicts.

Thanks!
0
Filthy_Defiler
Asked:
Filthy_Defiler
1 Solution
 
apache09Commented:

Best Practice is to use firstname.lastname@domain.com

As this isnt always practiced its never too late to change

You can go in to the Users AD account
Under Emaill Addresses

Add additional SMTP address if Graham.LastName@domain.com

Set this a primary address


0
 
e_aravindCommented:
IMO, we dont have any template to detect the conflict and use the other rule
best and simple option is to identify the conflict users and manually edit the email-address?


Else, we may need to find some other common attribute and for the users with the "common attribute" we need to kick-in some other receipient rules.
0
 
Hendrik WieseCommented:
No you cannot change the behavior of exchange when it comes to duplicate names.

As suggested by apache09 industry standard is firstname.lastname@domain, but it seems like that is not the option that you would like to go for (Although this is strongly recommended as a standard).

So since you were planning to use the %g%1s@domain as an alternative. Why not just add that to the policy and have that set to everyone's primary.

I mean they will still be receiving mails sent to any of the aliases the only difference is that their reply address will change.

Or you could of course insert the new alias manually as suggested by "e aravind ", but then you would have to un-tick the "Automatically update e-mail addresses based on email address policy" tick box on the "Email Addresses" tab in the user's properties, and manually update all those users should something change with regards to your email policy.

Cheers!!
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
Filthy_DefilerAuthor Commented:
I've already suggested changing the format to %g%1s@domain for everyone, but I've met resistance from directors.  I've offered what Hendrik mentioned (keeping the old email addresses as an alias), but they just don't like it.  That's why I'm looking for a way to have a fallback template.

I'll leave this open over the weekend to see if anyone has a solution that gives me just that.  Any more ideas, folks?

0
 
Hendrik WieseCommented:
As suggested that will not be possible. So your only option would be to un-tick the "Automatically update e-mail addresses based on email address policy" tick box on the "Email Addresses" tab in the user's properties, and manually update all those users should something change with regards to your email policy.

But lets see if you get any better solutions.

Cheers!!!
0
 
Filthy_DefilerAuthor Commented:
Well, I guess that means nobody else had any good ideas.  I was hoping there might be some Powershell cleverness or something, but I guess I'm out of luck.

I'll push for a more sensible email address format for future use.
0

Featured Post

Has Powershell sent you back into the Stone Age?

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.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now