[Dovecot] Dovecot 1.2 & Thunderbird 3.0
Hello.
After updating to TB-3.0 I notice what sometimes messages in IMAP folder lost "seen flag". Entire folder star to be unseen fully. It happen often then I chose(click on it) some folder .
Has some one have this bug too?
root@mail [~]dovecot -n # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.1-RELEASE-p7 i386 ufs base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot-debug.log protocols: imap imaps pop3 pop3s managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 ssl_ca_file: /usr/local/etc/certs/GlobalSignCA.crt ssl_cert_file: /usr/local/etc/certs/fxclub_org.crt ssl_key_file: /usr/local/etc/certs/fxclub_org.key ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_process_size: 128 login_processes_count: 20 login_max_processes_count: 512 mail_max_userip_connections(default): 256 mail_max_userip_connections(imap): 256 mail_max_userip_connections(pop3): 20 mail_max_userip_connections(managesieve): 10 verbose_proctitle: yes first_valid_gid: 0 mail_privileged_group: mail mail_uid: dmail mail_gid: dmail mail_location: maildir:/var/spool/dovecot/domains/%d/%n mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_process_size: 512 mail_plugins(default): quota imap_quota autocreate mail_log mail_plugins(imap): quota imap_quota autocreate mail_log mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): lda: postmaster_address: postmaster@fxclub.org hostname: mail.fxclub.org mail_plugins: sieve quota mail_plugin_dir: /usr/local/lib/dovecot/lda quota_full_tempfail: yes deliver_log_format: msgid=%m: %$ %f %s log_path: /var/log/dovecot/deliver.log info_log_path: /var/log/dovecot/deliver.log sendmail_path: /usr/sbin/sendmail rejection_reason: Your message to <%t> was automatically rejected:%n%r auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login user: dovecot-auth username_format: %Lu worker_max_count: 100 passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: exim master: path: /var/run/dovecot/auth-master mode: 384 user: dmail plugin: quota: maildir quota_rule: *:storage=1024M quota_rule2: Trash:storage=1256M quota_rule3: SPAM:ignore quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/quota-warning.sh 80 autocreate: Trash autocreate2: Sent autocreate3: Spam autosubscribe: Trash autosubscribe2: Sent autosubscribe3: Spam sieve_dir: ~/sieve sieve: ~/.dovecot.sieve sieve_global_path: /var/spool/dovecot/global.sieve mail_log_events: delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields: uid box msgid size mail_log_max_lines_per_sec: 0
-- Best regards. Proskurin Kirill
Seems everyone is starting to notice this now. :)
Yes, there are several flaws and bug reports open with Mozilla on broken behavior with TB 3.0 and TB 3.0.1. Currently the easiest fix is to turn off CONDSTOR either server side or in TB itself. There is also a TB 3.0.2pre nightly available that seems to be working for most people.
https://bugzilla.mozilla.org/show_bug.cgi?id=540554 https://bugzilla.mozilla.org/show_bug.cgi?id=524902 https://bugzilla.mozilla.org/show_bug.cgi?id=517461
On 1/23/2010 3:38 PM, Proskurin Kirill wrote:
Hello.
After updating to TB-3.0 I notice what sometimes messages in IMAP folder lost "seen flag". Entire folder star to be unseen fully. It happen often then I chose(click on it) some folder .
Has some one have this bug too?
root@mail [~]dovecot -n # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.1-RELEASE-p7 i386 ufs base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot-debug.log protocols: imap imaps pop3 pop3s managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 ssl_ca_file: /usr/local/etc/certs/GlobalSignCA.crt ssl_cert_file: /usr/local/etc/certs/fxclub_org.crt ssl_key_file: /usr/local/etc/certs/fxclub_org.key ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_process_size: 128 login_processes_count: 20 login_max_processes_count: 512 mail_max_userip_connections(default): 256 mail_max_userip_connections(imap): 256 mail_max_userip_connections(pop3): 20 mail_max_userip_connections(managesieve): 10 verbose_proctitle: yes first_valid_gid: 0 mail_privileged_group: mail mail_uid: dmail mail_gid: dmail mail_location: maildir:/var/spool/dovecot/domains/%d/%n mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_process_size: 512 mail_plugins(default): quota imap_quota autocreate mail_log mail_plugins(imap): quota imap_quota autocreate mail_log mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): lda: postmaster_address: postmaster@fxclub.org hostname: mail.fxclub.org mail_plugins: sieve quota mail_plugin_dir: /usr/local/lib/dovecot/lda quota_full_tempfail: yes deliver_log_format: msgid=%m: %$ %f %s log_path: /var/log/dovecot/deliver.log info_log_path: /var/log/dovecot/deliver.log sendmail_path: /usr/sbin/sendmail rejection_reason: Your message to <%t> was automatically rejected:%n%r auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login user: dovecot-auth username_format: %Lu worker_max_count: 100 passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: exim master: path: /var/run/dovecot/auth-master mode: 384 user: dmail plugin: quota: maildir quota_rule: *:storage=1024M quota_rule2: Trash:storage=1256M quota_rule3: SPAM:ignore quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/quota-warning.sh 80 autocreate: Trash autocreate2: Sent autocreate3: Spam autosubscribe: Trash autosubscribe2: Sent autosubscribe3: Spam sieve_dir: ~/sieve sieve: ~/.dovecot.sieve sieve_global_path: /var/spool/dovecot/global.sieve mail_log_events: delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields: uid box msgid size mail_log_max_lines_per_sec: 0
On 23.01.2010 23:51, David Halik wrote:
Seems everyone is starting to notice this now. :)
Yes, there are several flaws and bug reports open with Mozilla on broken behavior with TB 3.0 and TB 3.0.1. Currently the easiest fix is to turn off CONDSTOR either server side or in TB itself. There is also a TB 3.0.2pre nightly available that seems to be working for most people.
https://bugzilla.mozilla.org/show_bug.cgi?id=540554 https://bugzilla.mozilla.org/show_bug.cgi?id=524902 https://bugzilla.mozilla.org/show_bug.cgi?id=517461
Thank you for great explain! Will wait for 3.0.2
-- Best regards, Proskurin Kirill
On 23.01.2010 21:51, David Halik wrote:
Seems everyone is starting to notice this now. :)
Yes, there are several flaws and bug reports open with Mozilla on broken behavior with TB 3.0 and TB 3.0.1. Currently the easiest fix is to turn off CONDSTOR either server side or in TB itself. There is also a TB 3.0.2pre nightly available that seems to be working for most people.
https://bugzilla.mozilla.org/show_bug.cgi?id=540554 https://bugzilla.mozilla.org/show_bug.cgi?id=524902 https://bugzilla.mozilla.org/show_bug.cgi?id=517461
Thanks for this info, I was about to post this issue here myself. :)
Disabled in TB 3.0.1 and it works like a charm.
-A
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
David Halik said the following on 23/01/10 21:51:
Seems everyone is starting to notice this now. :)
Yes, there are several flaws and bug reports open with Mozilla on broken behavior with TB 3.0 and TB 3.0.1. Currently the easiest fix is to turn off CONDSTOR either server side or in TB itself. There is also a TB 3.0.2pre nightly available that seems to be working for most people.
I was thinking that this was a problem of *my* TB installation.
Thank you for poiting out the solution: it works.
Ciao, luigi
/ +--[Luigi Rosa]-- \
When you become obsessed with the enemy, you become the enemy. --Jeffrey Sinclair, "Infection", Babylon 5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAktb2R0ACgkQ3kWu7Tfl6ZTZXACgiVYxwi6SK688RnMbC4MiAe/C SlgAoLOWlukaQT6q+e1VzfkzDvnlb7qj =sfWB -----END PGP SIGNATURE-----
On 2010-01-23 3:51 PM, David Halik wrote:
Yes, there are several flaws and bug reports open with Mozilla on broken behavior with TB 3.0 and TB 3.0.1. Currently the easiest fix is to turn off CONDSTOR either server side or in TB itself. There is also a TB 3.0.2pre nightly available that seems to be working for most people.
Ok, I read some of the RFC on CONDSTORE (I assume this is what you meant instead of CONDSTOR?) - but as usual, got a headache before any light bulb went on.
So, what is the real world benefit of CONDSTORE? In other words, what do you lose by disabling it?
--
Best regards,
Charles
So, what is the real world benefit of CONDSTORE? In other words, what do you lose by disabling it?
My general understanding is that it reduces both client and server sync load by essentially allowing the two to be smarter about flag/time changes. When a client connects it does not need to make as many queries and trips back to the IMAP server to resync with the latest status... essentially it frees up transactional load.
So, my guess would be that turning it off only means that your server might see more load, and your client might not appear to be as "snappy" on initial connections. Syncing should still happen just fine.
Hope that helps.
On 2010-01-24 12:11 PM, David Halik wrote:
So, what is the real world benefit of CONDSTORE? In other words, what do you lose by disabling it?
My general understanding is that it reduces both client and server sync load by essentially allowing the two to be smarter about flag/time changes. When a client connects it does not need to make as many queries and trips back to the IMAP server to resync with the latest status... essentially it frees up transactional load.
So, my guess would be that turning it off only means that your server might see more load, and your client might not appear to be as "snappy" on initial connections. Syncing should still happen just fine.
Hope that helps.
Yup, thanks... so, now to go vote for the TB bug to be fixed... :)
participants (5)
-
Alexander Hoogerhuis
-
Charles Marcus
-
David Halik
-
Luigi Rosa
-
Proskurin Kirill