[Dovecot] wish now I'd not upgraded...
Upgraded from Debian Dovecot 1.0.15 to Debian Dovecot 1.2.10-1~bpo50+1.
I use Postfix local delivery to and Dovecot mbox. As per upgrade directions, I stopped dovecot processes and deleted all dovecot.index.cache files in /home/%user/mail/.imap. Performed upgrade to 1.2.10-1~bpo50+1. Modified new dovecot.conf for my environment. Started dovecot.
Problem: Instantly noticed in TB 3.0.1 Win32 that all emails in all folders were marked as unread. Stopped TB, stopped dovecot, deleted *all* files in /home/%user/mail/imap/ so indexes and caches could be rebuilt from scratch. Started dovecot, started TB. Same problem.
Then I got ugly, stopped TB and dovecot, deleted all ~.imap/ files *and* deleted *all* TB cache and index files with a time stamp of today. Restarted dovecot, restarted TB. Same damn problem. I sit hit right clicking folder after folder and selecting "mark as read", only to see all the emails in the folder go "read" and then within seconds go back to marked as unread (bold). Opening messages one at a time and moving to the next doesn't even keep them marked as read.
WTF is going on? Why won't they stay marked as read? I've got over 25,000 emails in these folders and I get a few hundred list mails a day. I really need to get this read/unread business straightened out.
What the heck am I missing? Is this a bug in the Debian backport? Good thing I have no hair or I'd have pulled half of it out by now...
-- Stan
On 15.2.2010, at 16.14, Stan Hoeppner wrote:
Upgraded from Debian Dovecot 1.0.15 to Debian Dovecot 1.2.10-1~bpo50+1.
Problem: Instantly noticed in TB 3.0.1 Win32 that all emails in all folders were marked as unread.
This is a Thunderbird bug and there have been several threads about this here. Basically the fix is to disable CONDSTORE support in Thunderbird until 3.0.2 is released.
Timo Sirainen put forth on 2/15/2010 8:18 AM:
On 15.2.2010, at 16.14, Stan Hoeppner wrote:
Upgraded from Debian Dovecot 1.0.15 to Debian Dovecot 1.2.10-1~bpo50+1.
Problem: Instantly noticed in TB 3.0.1 Win32 that all emails in all folders were marked as unread.
This is a Thunderbird bug and there have been several threads about this here. Basically the fix is to disable CONDSTORE support in Thunderbird until 3.0.2 is released.
I guess I should have paid closer attention to that thread. Since I wasn't seeing that problem with my 3.0.1 I assumed it didn't apply to me. Apparently it just didn't apply to dovecot 1.0.15, but does apply to 1.2.10. Yes? Dovecot 1.0.15 was working pretty much perfectly for me. But, it was so long in the tooth I figured I should upgrade now that a new Debian package was available.
Sorry the row. I should have remembered that thread. It was just a week or two ago.
-- Stan
On 15.2.2010, at 16.51, Stan Hoeppner wrote:
This is a Thunderbird bug and there have been several threads about this here. Basically the fix is to disable CONDSTORE support in Thunderbird until 3.0.2 is released.
I guess I should have paid closer attention to that thread. Since I wasn't seeing that problem with my 3.0.1 I assumed it didn't apply to me. Apparently it just didn't apply to dovecot 1.0.15, but does apply to 1.2.10. Yes?
Rght. v1.2 is the first version to support CONDSTORE extension.
Timo Sirainen put forth on 2/15/2010 8:58 AM:
On 15.2.2010, at 16.51, Stan Hoeppner wrote:
This is a Thunderbird bug and there have been several threads about this here. Basically the fix is to disable CONDSTORE support in Thunderbird until 3.0.2 is released.
I guess I should have paid closer attention to that thread. Since I wasn't seeing that problem with my 3.0.1 I assumed it didn't apply to me. Apparently it just didn't apply to dovecot 1.0.15, but does apply to 1.2.10. Yes?
Rght. v1.2 is the first version to support CONDSTORE extension.
Disabled condstore in about:config and all was instantly correct again after I restarted TB (3.0.1).
Thanks for the gentle nudge, instead of a trout slap Timo. :)
One last question on this TB condstore bug: Does this affect both mbox and maildir, i.e. it's a pure IMAP protocol handling bug, or is it specific to mbox?
-- Stan
On 15.2.2010, at 17.15, Stan Hoeppner wrote:
One last question on this TB condstore bug: Does this affect both mbox and maildir, i.e. it's a pure IMAP protocol handling bug, or is it specific to mbox?
I looked at the patch, and it looked like the code that handled condstore was simply just buggy. It was supposed to have cleared some variables in initialization code, but didn't. (And that's why with Dovecot APIs you can't allocate uninitialized memory, it's always zeroed out. Less work for programmer (me), less potential bugs/security holes.)
On 15.2.2010, at 17.23, Timo Sirainen wrote:
On 15.2.2010, at 17.15, Stan Hoeppner wrote:
One last question on this TB condstore bug: Does this affect both mbox and maildir, i.e. it's a pure IMAP protocol handling bug, or is it specific to mbox?
Oh, and: In general, IMAP clients aren't supposed to know what mailbox format the backend is using. The one difference it usually sees between mbox and maildir is that with mbox you can't have a mailbox with messages and child mailboxes (but with some configuration you can get around that too).
Timo Sirainen put forth on 2/15/2010 9:26 AM:
On 15.2.2010, at 17.23, Timo Sirainen wrote:
On 15.2.2010, at 17.15, Stan Hoeppner wrote:
One last question on this TB condstore bug: Does this affect both mbox and maildir, i.e. it's a pure IMAP protocol handling bug, or is it specific to mbox?
Oh, and: In general, IMAP clients aren't supposed to know what mailbox format the backend is using. The one difference it usually sees between mbox and maildir is that with mbox you can't have a mailbox with messages and child mailboxes (but with some configuration you can get around that too).
Speaking of which, I've tried creating empty imap folders and then creating subfolders in them. TB won't allow me to do this with Dovecot mbox accounts. Shouldn't I be able to do this? I've tried it with and without tb-extra-mailbox-sep enabled. I've read multiple places that tiered mbox imap folders should be possible, as long as the main folder contains no messages, only pointers to other mbox files, or "imap sub folders".
Is this a TB limitation, a dovecot limitation, or my knowledge limitation?
Thanks Timo.
-- Stan
On 15.2.2010, at 17.52, Stan Hoeppner wrote:
Speaking of which, I've tried creating empty imap folders and then creating subfolders in them. TB won't allow me to do this with Dovecot mbox accounts. Shouldn't I be able to do this? I've tried it with and without tb-extra-mailbox-sep enabled. I've read multiple places that tiered mbox imap folders should be possible, as long as the main folder contains no messages, only pointers to other mbox files, or "imap sub folders".
Is this a TB limitation, a dovecot limitation, or my knowledge limitation?
No idea. If you talk IMAP protocol directly, it should go like:
a create foo/
creates a foo directory that can hold child mailboxes
b create bar
creates bar mailbox that can't hold children
c create a/d
creates a that has a d child mailbox
If in doubt, it's usually the client that does something wrong.
Well, I had the same problem and a colleague pointed me to this cockeyed black-is-white TB config setting: Under Account Settings, Server Settings, Server Settings, Advanced, *UN*click "Server supports folders that contain sub-folders and messages". Then you can create sub-folders. Doesn't make any sense at all....but then it's Monday and the Red Queen is everywhere spreading the joys of enhanced entropy.......
Stan Hoeppner wrote:
Speaking of which, I've tried creating empty imap folders and then creating subfolders in them. TB won't allow me to do this with Dovecot mbox accounts. Shouldn't I be able to do this? I've tried it with and without tb-extra-mailbox-sep enabled. I've read multiple places that tiered mbox imap folders should be possible, as long as the main folder contains no messages, only pointers to other mbox files, or "imap sub folders".
Is this a TB limitation, a dovecot limitation, or my knowledge limitation?
Thanks Timo.
-- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean@bard.edu voice: 845-758-7475, fax: 845-758-7035
Well, the issue is, with mbox, you can decide if the name you create:
a) can hold child mailboxes, or messages
or
b) messages, and no mailboxes
it makes more sense when you think about them as directories and files. WIth mbox a mailbox is a file. So:
~/mailbox/inbox ~/mailbox/foo/ ~mailbox/foo/bar
in such setup inbox is a file and of course you can't create ~/mailbox/inbox/children files or directories. but ~/mailbox/foo/ is a directory, so you can create files or directories under it. But the foo itself is a directory, not an mbox file.
So with mbox the important thing is to either add nor not add the '/' trailing character to created mailbox names.
(And to think that with BikINI they thought this was a good feature of IMAP, not a bad one..)
On 15.2.2010, at 18.21, Stewart Dean wrote:
Well, I had the same problem and a colleague pointed me to this cockeyed black-is-white TB config setting: Under Account Settings, Server Settings, Server Settings, Advanced, *UN*click "Server supports folders that contain sub-folders and messages". Then you can create sub-folders. Doesn't make any sense at all....but then it's Monday and the Red Queen is everywhere spreading the joys of enhanced entropy.......
Stan Hoeppner wrote:
Speaking of which, I've tried creating empty imap folders and then creating subfolders in them. TB won't allow me to do this with Dovecot mbox accounts. Shouldn't I be able to do this? I've tried it with and without tb-extra-mailbox-sep enabled. I've read multiple places that tiered mbox imap folders should be possible, as long as the main folder contains no messages, only pointers to other mbox files, or "imap sub folders".
Is this a TB limitation, a dovecot limitation, or my knowledge limitation?
Thanks Timo.
-- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean@bard.edu voice: 845-758-7475, fax: 845-758-7035
Timo Sirainen put forth on 2/15/2010 11:19 AM:
Well, the issue is, with mbox, you can decide if the name you create:
a) can hold child mailboxes, or messages
or
b) messages, and no mailboxes
it makes more sense when you think about them as directories and files. WIth mbox a mailbox is a file. So:
The problem was not that I lack understanding of mbox "imap sub folder" implementation (read a lot about it trying to fix this), but that I incorrectly long ago read "or" instead of "and" in the TB check box description, and hadn't thoroughly re-read the description recently. :(
The important thing is that discussing it here and getting feedback from you wonderful folks helped me find the problem and fix it. :)
-- Stan
Am 15.02.10 15:18, schrieb Timo Sirainen:
On 15.2.2010, at 16.14, Stan Hoeppner wrote:
Upgraded from Debian Dovecot 1.0.15 to Debian Dovecot 1.2.10-1~bpo50+1.
Problem: Instantly noticed in TB 3.0.1 Win32 that all emails in all folders were marked as unread.
This is a Thunderbird bug and there have been several threads about this here. Basically the fix is to disable CONDSTORE support in Thunderbird until 3.0.2 is released.
But this should not happen with POP3? I'm asking because I want to migrate from courier to dovecot. In the Lab we've converted the mailbox to dovecot-format BUT when using POP3, TB wants to download all Mails again.
So is this also related to the TB-Bug?
Thanks, Werner
On 19.2.2010, at 17.28, Werner wrote:
Am 15.02.10 15:18, schrieb Timo Sirainen:
On 15.2.2010, at 16.14, Stan Hoeppner wrote:
Upgraded from Debian Dovecot 1.0.15 to Debian Dovecot 1.2.10-1~bpo50+1.
Problem: Instantly noticed in TB 3.0.1 Win32 that all emails in all folders were marked as unread.
This is a Thunderbird bug and there have been several threads about this here. Basically the fix is to disable CONDSTORE support in Thunderbird until 3.0.2 is released.
But this should not happen with POP3?
No.
I'm asking because I want to migrate from courier to dovecot. In the Lab we've converted the mailbox to dovecot-format BUT when using POP3, TB wants to download all Mails again.
Have you read http://wiki.dovecot.org/Migration and http://wiki.dovecot.org/Migration/Courier? If you have, especially note this part: Some clients re-download all mails if you change the hostname in the client configuration. Be aware of this when testing.
On 15.02.2010 17:14, Stan Hoeppner wrote:
Upgraded from Debian Dovecot 1.0.15 to Debian Dovecot 1.2.10-1~bpo50+1.
I use Postfix local delivery to and Dovecot mbox. As per upgrade directions, I stopped dovecot processes and deleted all dovecot.index.cache files in /home/%user/mail/.imap. Performed upgrade to 1.2.10-1~bpo50+1. Modified new dovecot.conf for my environment. Started dovecot.
Problem: Instantly noticed in TB 3.0.1 Win32 that all emails in all folders were marked as unread. Stopped TB, stopped dovecot, deleted *all* files in /home/%user/mail/imap/ so indexes and caches could be rebuilt from scratch. Started dovecot, started TB. Same problem.
Then I got ugly, stopped TB and dovecot, deleted all ~.imap/ files *and* deleted *all* TB cache and index files with a time stamp of today. Restarted dovecot, restarted TB. Same damn problem. I sit hit right clicking folder after folder and selecting "mark as read", only to see all the emails in the folder go "read" and then within seconds go back to marked as unread (bold). Opening messages one at a time and moving to the next doesn't even keep them marked as read.
WTF is going on? Why won't they stay marked as read? I've got over 25,000 emails in these folders and I get a few hundred list mails a day. I really need to get this read/unread business straightened out.
What the heck am I missing? Is this a bug in the Debian backport? Good thing I have no hair or I'd have pulled half of it out by now...
It's bug in TB 3.0 with CONDSTORE capability, it's fixed for next version 3.0.2. You can disable it in prefs mail.server.default.use_condstore = false untill 3.0.2 released
Em 15/02/2010 12:14, Stan Hoeppner escreveu:
WTF is going on? Why won't they stay marked as read? I've got over 25,000 emails in these folders and I get a few hundred list mails a day. I really need to get this read/unread business straightened out.
What the heck am I missing? Is this a bug in the Debian backport? Good thing I have no hair or I'd have pulled half of it out by now...
before blaming dovecot, you could have checked the mailing list archives and found that's a KNOWN bug on Thunderbird 3 (until 3.0.1) which was already fixed and will be published on TB 3.0.2.
if you had searched the archives, you could also have find a workaround for that on thunderbird side.
there's also a workaround on the dovecot side .... but i'll let you learn how to search the archives and find that :)
--
Atenciosamente / Sincerily,
Leonardo Rodrigues
Solutti Tecnologia
http://www.solutti.com.br
Minha armadilha de SPAM, NÃO mandem email
gertrudes@solutti.com.br
My SPAMTRAP, do not email itStan,
Quoting Stan Hoeppner stan@hardwarefreak.com:
Upgraded from Debian Dovecot 1.0.15 to Debian Dovecot 1.2.10-1~bpo50+1.
I use Postfix local delivery to and Dovecot mbox. As per upgrade
directions, I stopped dovecot processes and deleted all dovecot.index.cache files in /home/%user/mail/.imap. Performed upgrade to 1.2.10-1~bpo50+1. Modified new dovecot.conf for my environment. Started dovecot.Problem: Instantly noticed in TB 3.0.1 Win32 that all emails in all folders were marked as unread. Stopped TB, stopped dovecot, deleted *all* files in /home/%user/mail/imap/ so indexes and caches could be rebuilt from scratch. Started dovecot, started TB. Same problem. <snip>
Have a look at
http://old.nabble.com/Re%3A-Messages-marked-as-unread---Dovecot-1.2.10---Thu... - a quick Google search would point me towards the conclusion that it might be worth you having a look at your version of TB and (apparent) problems re read/unread
status
--Ronald
Ronald MacDonald : ronald@rmacd.com 4 1F1 Gillespie Crescent, Edinburgh. EH10 4HT. http://www.rmacd.com/ : (+44) 777 235 1655
participants (7)
-
Leonardo Rodrigues
-
Nikolay Shopik
-
ronald＠rmacd.com
-
Stan Hoeppner
-
Stewart Dean
-
Timo Sirainen
-
Werner