13242 Views Previous 1 2 3 Next 39 Replies Latest reply: Aug 12, 2008 4:42 AM by Rick Lecoat Go to original post
I'm not quite sure if this has the same cause, but when I read my email with a webclient (squirrel mail), I can see all the message that I deleted long ago (crossed out).
I must say, however, that I don't get any old messages in Mail (Mail 3.2).
And, I think, this has already occurred under Tiger, too.
I just found out IMAP idle does work, but only when you have the mailbox selected that receives the mail. You can however collapse your "Inbox" and select that. Works on my machine
Found info here: http://www.dovecot.org/list/dovecot/2007-November/026732.html
The same problem (or a very similar problem) seems to be cropping up on my server which runs Debian GNU/Linux with UW-IMAP. The odd part is the problem only occurs intermittently.
I host mail for several other people on the server including some family members, and my parents seem to be having this problem the most. It will work just fine for days or even weeks, but then one day Mail stops removing messages from the Inbox when you delete them. They appear to be gone but as soon as you quit and relaunch Mail, they come right back. They have an iBook and a MacBook which are both on 10.5.2, and I should note that sometimes they do open Mail on both computers at the same time.
When I reboot the server or restart the IMAP daemon it is solved... for a while.
I initially thought there was a problem with Mail being too aggressive about keeping a lock on open mailboxes. That is, I noticed when one copy of Mail in Leopard is open, my other clients (including SquirrelMail or Alpine) can't modify the Inbox. They give me errors about not being able to get a lock on the mailbox, so they open it read-only. If you quit Mail, it lets go and the other clients work fine again. However, when the problem pops up for my parents, quitting both copies of Mail doesn't have any affect. Only restarting the IMAP service fixes it.
Rick, it does seem to be limited to Leopard. On a 10.4.11 machine whose Mail.app was working well, an upgrade to 10.5.3 broke the ability to move messages on IMAP servers.
One web page reports that it depends on the imapd (the server). I'm investigating.
I submitted at bugreport.apple.com. Has anyone else?
Same here: mail.app just keeps opening new processes without every closing the old ones. Even with only one or two accounts being checked, they quickly pile up until the server shuts down the whole system.
In thunderbird you can configure how many processes it opens at a time, and how it keeps them open.
Apple, please give us some control over mail.app! And please fix these bugs, because we like mail.app, but only when it works and doesn't overflow the server with old processes!
So, it's what, 9+ months and 3 revisions since Leopard was released? and Mail's IMAP is still broken. I constantly see the same pattern: mail that has been marked as read, mail that has been moved to a new folder (either by a rule or manually), mail that has been deleted/moved to trash... all these pop right up in the Inbox again as soon as the next mail check occurs. If the original message was still in the InBox, it's simply re-marked as unread; if the message had been deleted or moved, then it's re-downloaded to the InBox and thus duplicated.
I probably spend about 10-20 minutes a day cleaning up after Mail's half-baked attempts to manage my email, and that adds up (approx 3-6 hours per month!)
This is completely unacceptable of course, and I'm amazed that it's not apparently a priority for Apple's engineers. Many of the apps that Apple supply (Final Cut etc) are niche products with smaller than average user bases, but everyone uses email, so why hasn't it been fixed?
Is it simply a case of "we can't be bothered, and what are you gonna do about it"?