OK, we are having an issue with Outlook resolving an alias. Every user here
has a 3 character alias in Exchange 2003. Some people have a second e-mail
address associated with the mailbox for external mail purposes.
We have one user with the alias "swh" and their e-mail is "swh@domain.com".
We have a second user with the alias "sdw", but they have a second address
for external use that is "swhite@domain.com". So the problem is that in
Outlook if a user just types in "swh" Outlook resolves both "swh" and
"swhite" since they both start with "swh".
Normally this wouldn't be an issue since you can just choose one or the
other and that will be the end of it. The problem is that we have a program
that sends notifications automatically out to other users when changes are made. So if "swh" is logged in to this program and makes a change then the program tries to automatically send out a notification. But when it tries to authenticate with Exchange using the user's logon of "swh" Exchange will not send the notification because it doesn't know if the person sending the message is "swh" or "swhite".
Is there a way to force Exchange to automatically resolve the 3 character
alias/logon? The second address of "swhite" isn't even the logon ID for that user, so I'm not sure why this is an issue.
Hope that made some sort of sense.
Thanks!
has a 3 character alias in Exchange 2003. Some people have a second e-mail
address associated with the mailbox for external mail purposes.
We have one user with the alias "swh" and their e-mail is "swh@domain.com".
We have a second user with the alias "sdw", but they have a second address
for external use that is "swhite@domain.com". So the problem is that in
Outlook if a user just types in "swh" Outlook resolves both "swh" and
"swhite" since they both start with "swh".
Normally this wouldn't be an issue since you can just choose one or the
other and that will be the end of it. The problem is that we have a program
that sends notifications automatically out to other users when changes are made. So if "swh" is logged in to this program and makes a change then the program tries to automatically send out a notification. But when it tries to authenticate with Exchange using the user's logon of "swh" Exchange will not send the notification because it doesn't know if the person sending the message is "swh" or "swhite".
Is there a way to force Exchange to automatically resolve the 3 character
alias/logon? The second address of "swhite" isn't even the logon ID for that user, so I'm not sure why this is an issue.
Hope that made some sort of sense.
Thanks!
