[Dovecot] Squirrelmail - messages not marked as read
As of test-60 and test-61, running Squirrelmail 1.5.1[cvs] on FreeBSD 5.3-STABLE, messages are not marked as read after they are read.
If I switch back to test-59, it works normally.
When switching back to test-59, with log_path = /var/log/dovelog dovelog shows:
dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/dovecot.index.cache: indexid changed dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Drafts/dovecot.index.cache: indexid changed dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Sent/dovecot.index.cache: indexid changed dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Trash/dovecot.index.cache: indexid changed
If I change to test-61, when starting Squirrelmail for the first time the same will logged:
log dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/dovecot.index.cache: indexid changed dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Drafts/dovecot.index.cache: indexid changed dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Sent/dovecot.index.cache: indexid changed dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Trash/dovecot.index.cache: indexid changed
After this initial version switch, it will not log any errors.
Each time switching back to test-59 will cause the 'read' state to again work correctly (and a one-time logging as above.)
Please let me know if there is anything I can do to help debug this.
regards -kim
-- w8hdkim@yahoo.com
Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com
This behavior has been broken with squirrelmail in .99.11 and .99.12, and bugged the hound out of people as it was resetting their pop3 read flags on all the mail on the server. Ie, after logging into squirrelmail, all your pop3 mail downloads again.
We switched to openwebmail on our way to starting to use eGroupware or OpenGroupWare.
Openwebmail does not exhibit any of this behavior.
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Kim Culhan Sent: Friday, January 14, 2005 11:09 AM To: dovecot@dovecot.org Subject: [Dovecot] Squirrelmail - messages not marked as read
As of test-60 and test-61, running Squirrelmail 1.5.1[cvs] on FreeBSD 5.3-STABLE, messages are not marked as read after they are read.
If I switch back to test-59, it works normally.
When switching back to test-59, with log_path = /var/log/dovelog dovelog shows:
dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/dovecot.index.cache: indexid changed dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Drafts/dovecot.index.cache: indexid changed dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Sent/dovecot.index.cache: indexid changed dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Trash/dovecot.index.cache: indexid changed
If I change to test-61, when starting Squirrelmail for the first time the same will logged:
log dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/dovecot.index.cache: indexid changed dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Drafts/dovecot.index.cache: indexid changed dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Sent/dovecot.index.cache: indexid changed dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Trash/dovecot.index.cache: indexid changed
After this initial version switch, it will not log any errors.
Each time switching back to test-59 will cause the 'read' state to again work correctly (and a one-time logging as above.)
Please let me know if there is anything I can do to help debug this.
regards -kim
-- w8hdkim@yahoo.com
Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com
--- Michael Joy mdjoy@phy.olemiss.edu wrote:
This behavior has been broken with squirrelmail in .99.11 and .99.12, and bugged the hound out of people as it was resetting their pop3 read flags on all the mail on the server. Ie, after logging into squirrelmail, all your pop3 mail downloads again.
I think it will be possible to find the cause and fix this.
The reliability of the Squirrelmail/dovecot combination has been very good to this point and the dovecot author believes in making it compatible with various clients. Doing this even though it might be argued that this or that client is 'at fault'.
Working around the various bugs in Microsoft mail clients is a good example of this philosophy.
-kim
Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250
Le 01/14/2005 06:08 PM, Kim Culhan a écrit :
As of test-60 and test-61, running Squirrelmail 1.5.1[cvs] on FreeBSD 5.3-STABLE, messages are not marked as read after they are read.
I have the same behaviour with thunderbird, running -test61. Some messages are not marked as read and there are no errors in the logfile.
-- Nico La perfection est atteinte non quand il ne reste rien à ajouter, mais quand il ne reste rien à enlever. -+- Antoine de Saint-Exupéry (1900-1944) -+-
On 14.1.2005, at 19:08, Kim Culhan wrote:
As of test-60 and test-61, running Squirrelmail 1.5.1[cvs] on FreeBSD 5.3-STABLE, messages are not marked as read after they are read.
Fixed: http://dovecot.org/list/dovecot-cvs/2005-January/004032.html
participants (4)
-
Kim Culhan
-
Michael Joy
-
Nicolas STRANSKY
-
Timo Sirainen