373554 - 'Search Messages...' in IMAP 'Body' should process (readable) inline attachments too

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Serge Gautherie (:sgautherie)]

[Mozilla Thunderbird, version 2.0pre (20070311)] (nightly) (W2Ksp4)
[Mozilla Thunderbird, version 3 alpha 1 (20070310)] (nightly) (W2Ksp4)

(No bug.)


[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a3pre) Gecko/20070310 SeaMonkey/1.5a] (nightly) (W2Ksp4)

I tried to search for "penelope" in a message which had the following attachement (header):
{{
Content-Type: text/html; charset=UTF-8;
 name="https://bugzilla.mozilla.org/enter_bug.cgi?full=1"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="https://bugzilla.mozilla.org/enter_bug.cgi?full=1"
Content-Base: "https://bugzilla.mozilla.org/enter_bug.cgi?full=1"
Content-Location: "https://bugzilla.mozilla.org/enter_bug.cgi?full=1"
}}

I got a "no matches found";
while displaying the message and using FindAsYouType does find the string/message.

(I noticed this on a real life case ... but I'm using a known URI here.)

Comment 1

[Mike Cowperthwaite]

> Content-Transfer-Encoding: base64

Bug 132340 addresses this.  


> [Mozilla Thunderbird, version 2.0pre (20070311)] (nightly) (W2Ksp4)
> [Mozilla Thunderbird, version 3 alpha 1 (20070310)] (nightly) (W2Ksp4)
> (No bug.)

??  Decoding base64 for searching isn't implemented anywhere, as far as I know.

Comment 2

[Serge Gautherie (:sgautherie)]

Agreed:
I have now checked (and confirmed with Trunk SM/TB) that this bug, on a Local folder, is Core bug 132340.

***

Yet, detailing/morphing this very report to apply to IMAP (Inbox) folder:
SM does not find anything, while somehow TB does.

Bug 132340 comment 0 reads
{{
IMAP search does not have this problem.
}}
Then could this be a SM regression !?

Comment 3

[Mike Cowperthwaite]

WFM, Seamonkey 1.1.1 & 1.5a-0307, Win2K.

Comment 4

[Serge Gautherie (:sgautherie)]

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.12pre) Gecko/20070322 SeaMonkey/1.0.8] (nightly) (W2Ksp4)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.4pre) Gecko/20070322 SeaMonkey/1.1.1] (nightly) (W2Ksp4)
and
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a3pre) Gecko/20070307 SeaMonkey/1.5a] (nightly) (W2Ksp4)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a3pre) Gecko/20070310 SeaMonkey/1.5a] (nightly) (W2Ksp4)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a3pre) Gecko/20070321 SeaMonkey/1.5a] (nightly) (W2Ksp4)

Show this comment 2 bug.

***

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a3pre) Gecko/20070321 SeaMonkey/1.5a] (nightly) (W2Ksp4)

But, I tried a new profile ... and the search succeeds.

Then it's profile-related ... but I don't see yet what the trigger could be.
I'll try to find out...

Comment 5

[Wayne Mery (:wsmwk)]

Serge, So it's not a dupe of bug 132340?  Any luck finding cause?