XCON: Wrong Mapping of Msg Priority Between MSMAIL and Exchange

 Last reviewed: April 9, 1997
Article ID: Q161936
The Information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SYMPTOMS

Messages sent with normal priority from Microsoft Mail Windows clients go through the low priority queue in the Microsoft Exchange message transfer agent (MTA).

This problem does not affect the priority displayed in the recipient mailbox but only affects the order in which the MTA handles the three queues, high, normal, and low.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0 This problem was corrected in the latest Microsoft Exchange 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

MORE INFORMATION

Note that high priority messages sent by Microsoft Mail users go through the normal priority queue in the Microsoft Exchange MTA if the Microsoft Mail users haven't been granted the right "Urgent" by Microsoft Mail administrators.

With the right "Urgent," these messages go through the high priority queue in Exchange MTA.

Keywords : kbbug4.00 kbfix4.00.sp4 kbusage XCON
Version : 4.0
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix

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 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.