[Dovecot] Deleted / read mails show up as new on remote imap clients
Hi,
I've one problem:
Mails, which I already read or deleted via my IMAP client (Thunderbird) on the same machine running the server (it runs behind DynDNS on my local machine, thanks to http://mein.homelinux.com/wiki/mailserver/) show up again if I connect via IMAP from other client computers, i.e. my notebook (Thunderbird again).
As you can see from the config below I have /home/user/Maildir, not /var/mail - is that the problem? Or is that anything else, resulting in status from emails not being stored (or not being available remote) in the responding dovecot files (dovecot.index?).
Some month ago I migrated from Cyrus, and if I remember correct I had some problems with migrating subscriptions, stati and so on (one had to use a special script, sorry, it's been some time now) ;-) So maybe s.th. went wrong which could be the source of this problem? Just guessing ...
Ok, here's my config:
root@linux:/lost+found# dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.5.0-25-generic x86_64 Ubuntu 12.10 auth_verbose = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes list = yes location = prefix = separator = . type = private } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = postmaster@localhost protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } root@linux:/lost+found# root@linux:/lost+found# dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.5.0-25-generic x86_64 Ubuntu 12.10 auth_verbose = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes list = yes location = prefix = separator = . type = private } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = postmaster@localhost protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } root@linux:/lost+found#
If you need other info pls let me know.
Any help is greatly appreciated! Regards Andre
-- rheinSinn - A. Bischof Gottesweg 46, 50969 Köln Tel. 0221 / 46 75 59 87 - Mob. 0179 / 510 45 92 andre.bischof@rheinsinn.de www.rheinsinn.de - www.coaching-evaluationen.de
Hi Andre,
Andre Bischof wrote:
Mails, which I already read or deleted via my IMAP client (Thunderbird) on the same machine running the server (it runs behind DynDNS on my local machine, thanks to http://mein.homelinux.com/wiki/mailserver/) show up again if I connect via IMAP from other client computers, i.e. my notebook (Thunderbird again).
I had a similar problem where deleted folders showed up again in Thunderbird. The following imap_client_workaround setting worked for me:
protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep }
Kind regards Daniel
On 2013-02-24 1:23 PM, Daniel Parthey <daniel.parthey@informatik.tu-chemnitz.de> wrote:
protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep }
Did you try these one at a time? Meaning, were both required to solve the problem?
Also, what version of Thunderbird do either/both of you have?
--
Best regards,
*/Charles/*
Charles Marcus wrote:
On 2013-02-24 1:23 PM, Daniel Parthey <daniel.parthey@informatik.tu-chemnitz.de> wrote:
protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep }
Did you try these one at a time? Meaning, were both required to solve the problem?
No. I just added tb-extra-mailbox-sep and this did the trick. The workaround for delay-newmail had already been set before.
Also, what version of Thunderbird do either/both of you have?
10.0.12
Regards Daniel
On 2013-02-25 5:02 PM, Daniel Parthey <daniel.parthey@informatik.tu-chemnitz.de> wrote:
Charles Marcus wrote:
On 2013-02-24 1:23 PM, Daniel Parthey <daniel.parthey@informatik.tu-chemnitz.de> wrote:
protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep } Did you try these one at a time? Meaning, were both required to solve the problem? No. I just added tb-extra-mailbox-sep and this did the trick. The workaround for delay-newmail had already been set before.
Ok, thanks...
Also, what version of Thunderbird do either/both of you have? 10.0.12
Ummm... even the ESR is already at 17.0.3... why stuck in the stone age?
--
Best regards,
*/Charles/*
Charles Marcus wrote:
On 2013-02-25 5:02 PM, Daniel Parthey <daniel.parthey@informatik.tu-chemnitz.de> wrote:
Charles Marcus wrote:
On 2013-02-24 1:23 PM, Daniel Parthey <daniel.parthey@informatik.tu-chemnitz.de> wrote:
protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep } Did you try these one at a time? Meaning, were both required to solve the problem? No. I just added tb-extra-mailbox-sep and this did the trick. The workaround for delay-newmail had already been set before.
Ok, thanks...
Also, what version of Thunderbird do either/both of you have? 10.0.12
Ummm... even the ESR is already at 17.0.3... why stuck in the stone age?
Debian "testing/unstable" currently ships Icedove 10.0.12-1: http://packages.debian.org/search?keywords=icedove
There is 17.0.2-1 in the experimental repositories, but I'd rather not break my systems.
This is getting off-topic and does not help to solve the problem. Sorry, we should stop here or continue in private email.
Regards Daniel
Hi,
Am 24.02.2013 19:23, schrieb Daniel Parthey:
Hi Andre,
Andre Bischof wrote:
Mails, which I already read or deleted via my IMAP client (Thunderbird) on the same machine running the server (it runs behind DynDNS on my local machine, thanks to http://mein.homelinux.com/wiki/mailserver/) show up again if I connect via IMAP from other client computers, i.e. my notebook (Thunderbird again). I had a similar problem where deleted folders showed up again in Thunderbird. The following imap_client_workaround setting worked for me:
protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep } unfortunatly this has no effect to me. I put this in 20-imap.conf and restarted dovecot - no changes.
I run TB 17.0.2 under Ubuntu 12.10 (both machines), but had this problem before with former versions and Ubuntu 12.04.
I don't know whether this was before as well, but subfolders don't show up as well - I have to search for mails i.e. in the sent-folder, afterwards it shows up. IMHO subfolders should be autosubcribed?
This is only true for my notebook. On the machine running the server, all subfolders are visible in TB. I have TB configured to move deleted mails to the trash folder - I guess that's default. There is a setting to expunge the inbox when leaving TB - this is unchecked. Could that be connected to the problem? But still, why are my read mails marked unseen when looking them up from my notebook?
Strange. Any further clues?
Cheers Andre
-- rheinSinn - A. Bischof Gottesweg 46, 50969 Köln Tel. 0221 / 46 75 59 87 - Mob. 0179 / 510 45 92 andre.bischof@rheinsinn.de www.rheinsinn.de - www.coaching-evaluationen.de
At 3PM +0100 on 25/02/13 you (Andre Bischof) wrote:
Am 24.02.2013 19:23, schrieb Daniel Parthey:
Hi Andre,
Andre Bischof wrote:
Mails, which I already read or deleted via my IMAP client (Thunderbird) on the same machine running the server (it runs behind DynDNS on my local machine, thanks to http://mein.homelinux.com/wiki/mailserver/) show up again if I connect via IMAP from other client computers, i.e. my notebook (Thunderbird again). I had a similar problem where deleted folders showed up again in Thunderbird. The following imap_client_workaround setting worked for me:
protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep } [...]
This is only true for my notebook. On the machine running the server, all subfolders are visible in TB. I have TB configured to move deleted mails to the trash folder - I guess that's default. There is a setting to expunge the inbox when leaving TB - this is unchecked. Could that be connected to the problem? But still, why are my read mails marked unseen when looking them up from my notebook?
Strange. Any further clues?
Can you use tcpdump or wireshark to see what TB is actually telling the server to do? If you use TLS you will need to put
ssl_cipher_list = RSAin your dovecot.conf and point wireshark at the key file for the server's certificate; make sure you remove that setting afterwards, since it's a little less secure. (Specifically, TLS will normally use an ephemeral Diffie-Hellman key in addition to the certificate's private key, in order to make as little use of the cert key as possible. This makes it impossible for a third party (like wireshark) to decrypt the conversation, even with access to the private key. ssl_cipher_list=RSA disables this.)
Ben
Hi Ben,
Am 25.02.2013 15:39, schrieb Ben Morrow:
...
Can you use tcpdump or wireshark to see what TB is actually telling the server to do? If you use TLS you will need to put ssl_cipher_list = RSA in your dovecot.conf and point wireshark at the key file for the server's certificate; make sure you remove that setting afterwards, since it's a little less secure. (Specifically, TLS will normally use an ephemeral Diffie-Hellman key in addition to the certificate's private key, in order to make as little use of the cert key as possible. This makes it impossible for a third party (like wireshark) to decrypt the conversation, even with access to the private key. ssl_cipher_list=RSA disables this.) Ben
To be honest, I can't. I remember using wireshark (it was named s.th. else at this time) years ago and that it was very complicated.
If you could be more specific and walk me through I surely try.
Kind regards Andre
-- rheinSinn - A. Bischof Gottesweg 46, 50969 Köln Tel. 0221 / 46 75 59 87 - Mob. 0179 / 510 45 92 andre.bischof@rheinsinn.de www.rheinsinn.de - www.coaching-evaluationen.de
At 6PM +0100 on 25/02/13 you (Andre Bischof) wrote:
Am 25.02.2013 15:39, schrieb Ben Morrow:
...
Can you use tcpdump or wireshark to see what TB is actually telling the server to do? If you use TLS you will need to put ssl_cipher_list = RSA in your dovecot.conf and point wireshark at the key file for the server's certificate; make sure you remove that setting afterwards, since it's a little less secure. (Specifically, TLS will normally use an ephemeral Diffie-Hellman key in addition to the certificate's private key, in order to make as little use of the cert key as possible. This makes it impossible for a third party (like wireshark) to decrypt the conversation, even with access to the private key. ssl_cipher_list=RSA disables this.) Ben
To be honest, I can't. I remember using wireshark (it was named s.th. else at this time) years ago and that it was very complicated.
OK.
If you could be more specific and walk me through I surely try.
Hmm, I don't think I can, really; at least, not if you're using SSL. Even if you aren't you would want to at least edit the capture to remove passwords before showing it to anyone, which would require understanding what had been captured.
Are you able to get a capture with http://wiki2.dovecot.org/Debugging/Rawlog instead?
Ben
participants (4)
-
Andre Bischof
-
Ben Morrow
-
Charles Marcus
-
Daniel Parthey