On Thu, February 4, 2010 00:23, Tomas Kuliavas wrote: > 2010.02.03 23:47 James B. Byrne raÅ¡Ä?: >>> >>> I've asked to run status command on all boxes. STATUS "INBOX" >>> (MESSAGES UNSEEN RECENT) shows message counts only for INBOX. >>> If you have "Check all boxes, not just INBOX: yes", plugin >>> checks all subscribed folders. Please run IMAP STATUS command >>> on every subscribed folder and find the one which >>> has higher recent message count. >> >> I have on the order of 100+ subscribed mailboxes. I cannot >> contemplate running this command on them one by one and I am >> unable to find a way for STATUS to check all of them in one >> invocation. > > Unsubscribe folders one by one until your newmail recent status is > correct. Find folder which causes higher recent count. I did that, before I came to the list with my problem. I also went through each and every folder, displayed all messages therein, toggled all, and selected read. In some folders this resulted in the newmail report changing. It became closer to the actual number of unread messages displayed on the mailbox tree and in the delivery folder. However, the reported number never exactly matched the expected value. Also, when opened a new instance of squrrelmail the delta between actual unread and that reported by newmail was reset to the previously displayed value. So, all of that work was for naught. This was when I began to suspect that there was something else going on. Which is why I brought it to the attention of the list. The IMAP setup we have is Cyrus_Imap as distributed with CentOS-5.4 and there is nothing unusual about its configuration that I am aware of. We do not have scripts that mangle delivered mail before it gets into the user mailboxes. I am not aware of any shared folders. I certainly have not set any up and I doubt that the installation routine would do so. > > I suspect that some of your folders return invalid counters for > recent messages. You can't have messages with recent flag and > seen flag. If you change message flags from unseen to seen in > SquirrelMail, you will remove recent flag. I did exactly that for every message and while the delta between actual and reported changed it did not entirely disappear. Further, when I next started a Squirrelmail session, the delta returned to its former value. > Or maybe you are not telling something about your setup. Anything that I have not revealed is unknown to me as well. > Maybe you have some custom server side filters that mark new > messages as read No. > or you have some read-only mailboxes that belong to other user. > Also, no. > Please explain how you get combination of message flag values, which > is not possible in normal setups. If I could answer that question then I would not be here seeking an answer. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@xxxxxxxxxxxxx Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
