On closer inspection it appears not to be server related, but
Thunderbird related (as you might expect).
Two machines, one having only used Dovecot, and the other only having
used Courier *do* indeed show different inbox ordering.
BUT, if I reset the folder and redownload the courier folder
Hi All,
can anyone confirm whether auth_username_format = %n works or not?
R
/Lars
Dovecot v1.1.alpha4 imap after some time stops responding.
It can not be restarted as
/etc/init.d/dovecot restart
killall imap
also does not help
killall -9 imap
and then restart does help
in log I see message (repeted periodically) that
Sep 12 09:50:02 localhost postfix/local[22533]:
Hi
I am trying to do a staged migration over to dovecot, but having
troubles at the first hurdle. I setup the proxy feature to redirect
most of our users back to the current Courier imap/pop server, and it's
partly working, but I'm getting some serious errors using Thunderbird
and IMAP.
Ed W wrote:
All I'm getting from Thunderbird is an Invalid Command response. Is
there an easy way to get a look inside the imap stream to try and see
what's failing?
From the client end of things:
http://wiki.dovecot.org/Debugging/Thunderbird
-te
--
Troy Engel | Systems Engineer
Fluid
Thanks Troy
Can anyone help translate this (also why it's only breaking through the
proxy mode?)
5188[50431f8]: 2998a00:mail.mailasail.com:A:CreateNewLineFromSocket: 4
OK LSUB completed
5188[50431f8]: 2998a00:mail.mailasail.com:A:SendData: 5 lsub #shared.*
5188[50431f8]: ReadNextLine
# dovecot -n
# 1.0.5: /etc/dovecot/dovecot.conf
base_dir: /var/run/dovecot/
protocols: imap imaps pop3 pop3s
listen: [87.106.95.71]
ssl_cert_file: /etc/ssl/dovecot/server.pem
ssl_key_file: /etc/ssl/dovecot/server.key
disable_plaintext_auth: no
login_dir: /var/run/dovecot//login
5188[50431f8]: 2998a00:mail.mailasail.com:S-INBOX.Drafts:SendData:
5188[50431f8]: ReadNextLine [stream=2e682c8 nb=49 needmore=0]
5188[50431f8]:
2998a00:mail.mailasail.com:S-INBOX.Drafts:CreateNewLineFromSocket: 10
NO Error in IMAP command received by server.
I just tried this connecting
The problem persists with mbox inbox folders in v1.1.alpha4.
I get a stalled process imap which can not be killed by
killall imap
only by
killall -9 imap
This process takes a lock of user mailbox thus prevents the user to
read/send mail.
Other users are OK
Vladislav Malyshkin wrote:
Dovecot
