I am still having issues with new message count. When I move a message to another folder, it counts that message as new until you go into that folder. Is there a way I can solve this? Could it have something to do with NFS? I have tried all the NF workarounds with no luck... I have also tried NFSv3 and NFSv4, no difference. I store the indexes on the local drive...
Brian Taber wrote:> I am still having issues with new message count. When I move a message to > another folder, it counts that message as new until you go into that > folder. Is there a way I can solve this? Could it have something to do > with NFS? I have tried all the NF workarounds with no luck... I have > also tried NFSv3 and NFSv4, no difference. I store the indexes on the > local drive...Hi Brian, You really haven't provided enough details for anyone to be very helpful... dovecot/platform versions, dovecot -n output, etc... -- Best regards, Charles
On Fri, 2007-02-23 at 01:09 -0500, Brian Taber wrote:> I am still having issues with new message count. When I move a > message to > another folder, it counts that message as new until you go into that > folder. Is there a way I can solve this? Could it have something to > do > with NFS? I have tried all the NF workarounds with no luck... I have > also tried NFSv3 and NFSv4, no difference. I store the indexes on the > local drive...By "new" do you mean "unseen" or "recent" counter? What client do you use? I guess most clients use only the unseen counter. You could enable rawlog (http://dovecot.org/bugreport.html) and see what exactly is the command/reply that gives the wrong message count. Are your NFS server's and clients' clocks synchronized? Do you run Dovecot in more than one server? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20070301/7a8c9868/attachment.bin>