Microsoft KB Archive/292484

= XADM: Mail to a Public Folder Is Set as IPM.Post Instead of IPM.Note =

PSS ID Number: 292484

Article Last Modified on 2/5/2004

-

The information in this article applies to:


 * Microsoft Exchange 2000 Server

-



This article was previously published under Q292484



SYMPTOMS
When you send Simple Mail Transfer Protocol (SMTP) mail (mail that is not from a Messaging Application Programming Interface [MAPI] source) to an Exchange 2000 public folder, the message class is IPM.Post. In Microsoft Exchange Server 5.5, a message that is sent to a public folder is of the IPM.Note class.

With the Post form, you cannot directly reply to or forward to the sender; you also cannot see carbon copy (Cc) recipients. Because of this behavior change in Exchange 2000, you cannot use the public store as a central distribution point for listserver archives.



CAUSE
This issue can occur because support for native Multipurpose Internet Mail Extensions (MIME) is introduced in Exchange 2000. In Exchange Server 5.5, the message is converted to MAPI as it comes into the store. Because the message was IPM.Note at conversion, it remains IPM.Note in the public folder. In Exchange 2000, there is no message class at the time that the message is delivered to the folder; therefore, the message inherits the default message class for that (public) folder, which is IPM.Post.



RESOLUTION
A resolution for this issue has been identified. For additional information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:

817809 XADM: Update to Permit the Caching of Incoming SMTP Messages as IPM.Note



WORKAROUND
To work around this issue, use one of the following methods.

Method 1
To work around this issue:
 * 1) Use Active Directory Users and Computers to create a new Exchange 2000 mailbox.
 * 2) In Exchange System Manager, open the properties for the public folder, click the Exchange General tab, and then click Delivery Options. Under Forwarding Address, select the new mailbox that you created in step 1 in the Forward to list. Make sure that the Deliver Messages to both Forwarding address and Folder option is not selected.
 * 3) Use Microsoft Outlook to log on to the new mailbox, and then use the Rules Wizard to create a rule that moves all of the messages to the public folder. When you create the rule, make sure that you choose to move the messages to the public folder; do not choose to forward the messages to the public folder.

After you perform these steps, SMTP messages come in to the public folder as IPM.Note, which allows you to review and to reply all.

The advantages of this method are:
 * The message header remains intact, including both To and From addresses.
 * The e-mail address to send to the public folder is administered on the folder itself.
 * The e-mail address that is displayed on the To line of the message is the correct address to send to that folder.

The disadvantage of this method is:
 * The Outlook client must be open to run the move rule because a move is client-based. In other words, you are using a client-side rule.

NOTE: In testing, when the Outlook Inbox Assistant was used instead of the Rules Wizard, issues that involved message headers being removed occurred in some cases.

Method 2
To work around this issue:
 * 1) Use Active Directory Users and Computers to create a new Exchange 2000 mailbox.
 * 2) Create an SMTP e-mail address on the mailbox, and have users send mail for the public folder to this address instead of the actual public folder address.
 * 3) Use Outlook to log on to the new mailbox, and then use the Rules Wizard to create a rule that redirects all of the messages to the public folder.

After you perform these steps, SMTP messages come in to the public folder as IPM.Note, which allows you to review and to reply all.

The advantages of this method are:
 * The From address remains intact.
 * The rule still runs when Outlook is not running because the rule is a server-based rule.

The disadvantages of this method are:
 * The e-mail address that is used to send mail to the public folder is on the mailbox, so this e-mail address is actually administered on the mailbox, which is not advantageous because the public folder should not be mailed directly.
 * When the message appears in the public folder, the To line is changed to the real e-mail address of the folder, which you do not want to expose because you do not want users to mail the public folder address directly.

NOTE: In testing, when the Outlook Inbox Assistant was used instead of the Rules Wizard, issues that involved message headers being removed occurred in some cases.

Method 3
To work around this issue:
 * 1) Use Active Directory Users and Computers to create a new Exchange 2000 mailbox.
 * 2) Create an SMTP e-mail address on the mailbox, and have users send mail for the public folder to this address instead of the actual public folder address.
 * 3) Use Outlook to log on to the new mailbox, and then use the Rules Wizard to create a rule that forwards all of the messages to the public folder.

After you perform these steps, SMTP messages come in to the public folder as IPM.Note, which allows you to review and to reply all.

The advantage of this method is:
 * The rule still runs when Outlook is not running because the rule is a server-based rule.

The disadvantages of this method are:
 * The From address is changed to the e-mail address of the forwarding mailbox.
 * The To address is changed to the e-mail address of the public folder.
 * The e-mail address of the public folder is administered on the mailbox.
 * The real address of the public folder is exposed in the folder.

IMPORTANT: Because the From address is changed to the e-mail address of the forwarding mailbox, this method (Method 3) is not considered a viable workaround.

NOTE: In testing, when the Outlook Inbox Assistant was used instead of the Rules Wizard, issues that involved message headers being removed occurred in some cases.

Method 4
To work around this issue, create an Exchange 2000 synchronous store event sink.

For additional information about store event sinks, consult the Microsoft Developer Network (MSDN) Library and the Exchange 2000 Software Development Kit (SDK) that are available online and also for download at the following Microsoft Web site:

MSDN Library



MORE INFORMATION
Any SMTP mail that is sent (including any mail sent from Microsoft Outlook Express, Microsoft Outlook Web Access, and Internet Message Access Protocol, Version 4rev1 [IMAP4] clients), and any mail sent through the Internet (including mail that is sent from any MAPI client such as Outlook that is sent through the Internet) comes in to the public folder as IMP.Post because that is the default message class of the public folder. If a message comes from a MAPI client that is not sent through the Internet but through a local area network (LAN) or wide area network (WAN) that connects an Exchange organization, the default message class of the MAPI client (IPM.Note) is used, and the message comes in to the public folder as IPM.Note. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

817809 XADM: Update to Permit the Caching of Incoming SMTP Messages as IPM.Note

Additional query words: ESM

Keywords: kbprb KB292484

Technology: kbExchange2000Search kbExchange2000Serv kbExchange2000ServSearch kbExchangeSearch

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.