Exchange 2007 Server cannot parse X-Priority headers from clients that submit X-Priority headers that contain additional comments

This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
Some mail clients or other third-party SMTP-based clients notate message priority by using the X-Priority header. When a mail client or a third-party SMTP-based client submits an X-Priority header that contains additional comments, Microsoft Exchange Server 2007 cannot parse the X-Priority header. Instead, Exchange Server 2007 handles the message as if the message has a normal priority.
RESOLUTION
To resolve this problem, install Update Rollup 7 for Exchange 2007 Service Pack 1. For more information about Update Rollup 7 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic: For more information about how to install the latest Exchange service pack or update rollup, see the following Exchange Help topic:
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For example, this problem occurs when a message includes one of the following texts in the X-Priority header:
  • X-Priority: 2 (High)
  • X-Priority: 1 (Highest)
Exchange Server 2007 cannot parse the "(High)" comment or the "(Highest)" comment. For Exchange Server to parse the X-Priority header, the header must resemble one of the following:
  • X-Priority: 2
  • X-Priority: 1
Properties

Article ID: 958638 - Last Review: 01/15/2015 10:22:15 - Revision: 1.1

  • Microsoft Exchange Server 2007 Service Pack 1
  • kbnosurvey kbarchive kbexpertiseinter kbhotfixrollup kbsurveynew kbqfe KB958638
Feedback