On Tue, 2014-04-15 at 14:17 -0400, Jeff Blaine wrote: > Has anyone seen this before? Are there known oddities? The RT instance > is using MySQL.
If you're using 3.8, you're using the database's LIKE operator on the Content column. RT sometimes stores data, even plain-text data, with a content-encoding, however, meaning that the explicit string "34.100.108.26" doesn't appear in the Content column, but in the _decoded_ content. My guess is that if you look at the contents of the Attachments table for the other two transactions that should match, you'll find they have a ContentEncoding. RT 4.0's full-text search doesn't have this problem, since it decodes the content before indexing. - Alex -- RT Training - Dallas May 20-21 http://bestpractical.com/training
