XCLN: Using the Equal Sign (=) to Resolve Alias Names

Last reviewed: April 3, 1997
Article ID: Q150989
The information in this article applies to:
  • Microsoft Exchange Windows 95 client, versions 4.0 and 5.0
  • Microsoft Exchange Windows 3.x client, versions 4.0 and 5.0
  • Microsoft Exchange Windows NT client, versions 4.0 and 5.0
  • Microsoft Exchange MS-DOS client, versions 4.0 and 5.0

SUMMARY

This article describes how to resolve Email alias names in Microsoft Exchange clients using the equal sign(=).

MORE INFORMATION

In most companies there are Email users that have the same first and last names. Their Email aliases will vary but when you try and resolve the name, you will get a list and must select the person to whom you intend to send Email. This also applies to Email aliases that are similar. For example:

   Danial Aaby's Email alias is:    Daniala
   Danial Aalberg's Email alias is: Danialaa

You want to send mail to Danial Aaby.

When you enter in 'Daniala' as the Email alias you wish to resolve, the Microsoft Exchange client will display both users names in a Check Name dialog list box where you must then select the appropriate name.

If you use the Equal sign in front of the users Email alias, then the alias name will be resolved to the exact match after the Equal sign. In other words, by typing:

   =daniala

in the To: (or Cc: field) and resolving, the user Danial Aaby will be resolved and a Check Name dialog list box will not be displayed.


Additional query words:
Keywords : kbusage XCLN
Version : 4.0 5.0
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 3, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.