Date: Fri, 7 Dec 2001 15:41:37 -0500 (EST) From: Matt Allen <[EMAIL PROTECTED]>
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? This was a bug that was introduced in 1.5.something. It has been fixed in 2.1.0. You should be running at least 2.0.16. Larry
