Thanks for the response.
This is probably worse than you've considered for any app that is implemented according to the Exchange 2007 Foreign Connector guidelines and is meant to allow for IMAP clients. The important thing to keep in mind is that this will break in ways that are very hard to trace and explain to customers, and generate lots of support calls.
Is there any way you would consider leaving this the way it is in RU8, where a FC that creates a tnef encoded message is able to squeeze in new x-headers? Or possibly Exchange could map x-headers to ids for messages that are sent through the Replay directory only?
Since there is no longer a MAPI gateway architecture, it makes sense to allow a little more flexibility here for those of us porting older gateways to the new 2007 FC architecture.
You mentioned in one post that x-headers/id mappings are changing from per mailbox store to per mailbox. Does this mean that in Ex 2010 we'll need to find a way to log onto each mailbox that may receive a message from a foreign connector and create the mapping wheras logging into one mailbox per store is good enough for 2007?