** HTTP Response 404: http://....EML URL not found. ** - The Blame game.

"Its a Microsoft problem. See KB256385" I was told today by an EMC/Legato tech. Well, ok, yes I can see that.

However, that article says this:

"In Outlook Web Access, when you try to view any existing folders that were created in Outlook (MAPI client) that have names that contain these special characters, you may receive the following error messages:
The page cannot be found HTTP 404 - File not found "

Well, they must have fixed something because the only time I get the 404 messages is when shortcutting from EmailXtract. OWA seems to display these messages just fine. Its all a matter of using the correct URL - which EmailXtract does not do. I even tested it. I created a folder in Outlook for each of the character examples they used on that KB. Then copied a message into each one. Then I opened up OWA and browsed to each folder. All the messages displayed correctly, so obviously the problem has been resolved. Yet the support specialist seemed bound and determined to blamed Microsoft for it. I tried to explain to him that all EmailXtract has to do, so that it doesn't get errors, is to use the exact same URL OWA uses to display these messages. For example, if the folder ends in a period, add an additional '%20' to the name of the folder. If it has a backslash (\), replace it with '_xF8FE_'. These are simple fixes I think any developer could do to get EmailXtract to work with how OWA handles MAPI special characters. However, the tech seem reluctant to even send my suggestion up the chain to development. I'm currently waiting on management approval. So, I just had to vent on this forum. Hopefully someone will see this and verify my findings.