I recently upgraded from 1.5.2 to 2.0.12. One of my users has complained that message body searches for text strings with spaces no longer work. This only occurs when the message being searched is in the US-ASCII charset. The client is not an issue, as I've been testing it using the protocol directly. Is this intentional? Has anyone else seen this behavior?
I think I've found a workaround I can put in place in charset.c to fix it, but I'm curious if this is in fact a bug, and if anyone else has been affected by it. Thanks. -- Matt Allen Messaging Team UITS
