Initial Mail Search - Intermittant Quirk

[MightyGorilla]

We're running v6.0.10 OS (x64) and some users (including myself) have seen their initial mail search set to after:"some date" when we login, instead of in:"inbox" like the COS has defined.

Before we enabled the display search setting, it was really confusing just what was being displayed - and it was frustrating for users. Now at least we know what it's showing us, but I don't understand why.

Out of curiosity I calculated the number of days between today and the date it was displaying all mail after (Jul 17, 2010) and it was 200 days for what that's worth.

Anyone seen this issue, or is this just some boneheaded mistake in the COS or elsewhere? I don't understand why it wouldn't always happen if it was the configuration?

Thanks-

[MightyGorilla]

In case this helps - I have noticed that when the web client is loading initially, for a fraction of a second I see in:"inbox" in the search box, and then the after: search pops in and the mail refreshes with everything after that date.

I've tried reindexing the user's mailbox and that did not help the issue.

[phoenix]

I don't have a specific answer for you but why don't you check in the COS & and the users accounts what the setting is for the initial search? Use the following:

zmprov gc default | grep zimbraPrefMailInitialSearch
zmprov ga user@yourdomain.com | grep zimbraPrefMailInitialSearch

See if either of them returns strange results.

[MightyGorilla]

Thanks phoenix, but those queries all returned in:"inbox" as expected.

I don't have a clue why this would not consistently occur - whatever may be causing it, but my next place to look will be Zimlets. We have quite a few installed and only use a couple of them. I'm going to ditch some of the less used ones and see if one of them may have been the culprit.

[phoenix]

Thanks phoenix, but those queries all returned in:"inbox" as expected.

Unfortunately that's what I expected. Is there any consistency in the browser used or the operating system for the users?

[MightyGorilla]

I didn't narrow it down to exactly which one, but we had a few that were fairly dated. I suppose if your client loads up ok, and then a moment later something unwanted happens, you might want to check your Zimlets. We probably would have had a better chance or identifying it as Zimlet-related immediately after the last upgrade, had it not been intermittant.

Thanks for the help-