Closed
Bug 772689
Opened 12 years ago
Closed 2 years ago
TB 13.0.1 on OSX 10.7 with Spotlight finds .mozeml message but does not display the item
Categories
(Thunderbird :: OS Integration, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: francis.duyck, Unassigned)
Details
Attachments
(1 file)
513.23 KB,
application/pdf
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20100101 Firefox/13.0.1 Build ID: 20120614114901 Steps to reproduce: Although TB 13 is supposed to be integrated with Spotlight, I still get .mozeml messages when searching for email messages from Spotlight in OS 10.7. Of course I have it enabled from Preferences/Advanced/General : Allow Spotlight to search messages. Spotlight seems to find the TB messages with the search keywords, but the TB messages are not displayed, I only see an identifier message : ???????.mozeml In order to see the message, I have to select it and open it in TB. Actual results: I don't know what could be wrong. It might be related to the fact that I have my TB accounts not in the default folders. Since I have programs and data strictly separated, I have my local TB data on another volume. (Tools/Account Settings/myaccount.com/Server Settings/Local directory) My account has full access rights (777) on that folder. Expected results: What should happen ? Messages from TB should also be displayed from Spotlight as messages from within Mail.
Reporter | ||
Updated•12 years ago
|
Reporter | ||
Updated•12 years ago
|
Summary: TB 13.0.1 on OSX 10.7 with Spotlight gives .mozeml message and does not display the item → TB 13.0.1 on OSX 10.7 with Spotlight finds .mozeml message but does not display the item
Comment 1•12 years ago
|
||
Anything in Tools -> Error console when this happens ?
Severity: blocker → normal
Keywords: mail-integration
Updated•2 years ago
|
Severity: normal → S3
Comment 2•2 years ago
|
||
reporter is gone -> incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•