XFOR: ResolveP2 Registry Setting Expanded in Exchange 5.5

Last reviewed: January 23, 1998
Article ID: Q174755
The information in this article applies to:
  • Microsoft Exchange Server version 5.5

SUMMARY

Administrators of Microsoft Exchange Server 5.0 who are familiar with the P2 resolution features outlined in Microsoft Knowledge Base article Q166163 will find those options enhanced in version 5.5.

MORE INFORMATION

The ResolveP2 registry setting can now contain the previous settings (0=Don't resolve any P2, 1=Resolve all P2) or a set of flags from a revised IMS module included with Exchange Server 5.5. The flags currently defined are:

   ADDRESS_CONVERT_SENDER value 1
   ADDRESS_CONVERT_SENT_REPRESENTING value 2
   ADDRESS_CONVERT_RECEIVED_BY value 4
   ADDRESS_CONVERT_RECEIVED_REPRESENTING value 8
   ADDRESS_CONVERT_RECIPIENTS value 16
   ADDRESS_CONVERT_REPLY_TO value 32

To determine the value you want, add all of the elements you want resolved, then multiply by two. For example, to resolve all but the sender, enter (2+4+8+16+32) *2 = 124. To resolve only the recipients, enter 16*2 = 32.

Note: ADDRESS_CONVERT_SENDER does not resolve the P2 "from" field. ADDRESS_CONVERT_SENT_REPRESENTING does.

Keywords          : XFOR kbusage
Component         : IMail
Version           : WinNT:5.5
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: January 23, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.