When accessing (through Thunderbird 1.5) an OWA 2003
server with MrPostman the connection will fail ("Error
when using RETR") since the Outlook script (versión
0.8) tries to access Msgids but does not properly
encode the URL string. I've seen this with:
- all messages including a ':' (URL encoded to %3A)
- messages including '(' or ')'
For example, MrPostman gets a 404 when retrieving this
(after downloading all the msgids)
https://owaserver/exchange/owauser/Inbox%2FRe%3A%20ZERT%20patch%20%5Bwas%3A%200day%20for%20IE%20%28Disabling%20Javascript%20no%20longer%20a%20fix%29%5D.EML%3FCmd%3Dopen?='
when (if you use a web browser) the URL used for that
message is this:
https://owaserver/exchange/owauser/Inbox/Re:%20ZERT%20patch%20%5Bwas:%200day%20for%20IE%20\(Disabling%20Javascript%20no%20longer%20a%20fix)%5D.EML?Cmd=open
I've fixed this for myself with the attached patch which:
- URL-decodes ':', '(' and ')' back to their original
values
- Replaces '%3FCmd%3Dopen' with '?Cmd=open'
I don't know if this is particular to the OWA version
I'm using on the server side (Spanish encoding) or
because there really is a bug in the latest version of
the script
(comparing it with version 0.7 it looks like this
urlencoding was introduced in the latest version).
Patch to the OWA2003 script (0.8.2)
Logged In: YES
user_id=404932
FWIW this was reported in the Forums at
http://sourceforge.net/forum/forum.php?thread_id=1538969&forum_id=231748
Logged In: YES
user_id=404932
Scratch the issues with ':', '(' and ')'. These are
non-existant, the real issue is that '?Cmd=open' gets URL
encoded when it shouldn't. If I remove the URL decodes of
the other characters back to their original values it still
works.
Logged In: YES
user_id=404932
Also reported at
http://sourceforge.net/forum/message.php?msg_id=3735633
(with a different patch)