Open
Bug 780768
Opened 14 years ago
Updated 2 years ago
Advanced Searching by Body not available/offered after renaming IMAP folder
Categories
(Thunderbird :: Search, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: aberglund, Unassigned)
References
(Depends on 1 open bug)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.25 (KHTML, like Gecko) Version/6.0 Safari/536.25
Steps to reproduce:
Rename a folder on the IMAP server.
Actual results:
The search param dropdown no longer offers Body as a choice.
Expected results:
All choices should be available.
| Reporter | ||
Comment 1•14 years ago
|
||
We can duplicate this on version 13 & 14, both Mac and PC. It appears to be related to local indexes getting messed up.
If you search (locally, not on server) a folder where everything is normal, Body is an option in the drop-down. Re-name the folder, and try again - Body does not appear. Closing and re-opening Thunderbird does not bring back the ability to do a Body search on this re-named folder, nor does a folder repair. Re-naming back to the original name will bring back the Body option. Or you can unsubscribe-resubscribe to the re-named folder, then Body is again available.
| Reporter | ||
Updated•14 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Comment 2•10 years ago
|
||
Is this about Ctrl+Shift+F? If so, this may be related with ticket 543416.
Comment 3•10 years ago
|
||
(In reply to Filipus Klutiero from comment #2)
> Is this about Ctrl+Shift+F? If so, this may be related with ticket 543416.
perhaps in a way, yes per bug 543416 comment 5 "I have indexing turned off and I am not using local synchronization."
I can reproduce this precisely with the steps of comment 0. (on a gmail account)
After the folder rename, the folder sync property is disabled.
Restarting THunderbird doesn't help.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Searching by Body not available on IMAP account → Advanced Searching by Body not available/offered after renaming IMAP folder
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•