Last week, I upgraded dovecot. The problem did not occur with the earlier
version:
# dovecot -n
# 1.2.13: /etc/dovecot.conf
# OS: Linux 2.6.18-8.1.15.el5 x86_64 CentOS release 5 (Final)
syslog_facility: local5
protocols: imap imaps
listen: *:143
ssl_listen: *:993
disable_plaintext_auth: yes
login_dir: /var/run/dovecot/login
login_executable: /usr/libexec/dovecot/imap-login
login_log_format_elements: user=<%u> method=%m pid=%p rip=%r lip=%l %c
login_processes_count: 32
login_max_processes_count: 512
mail_max_userip_connections: 5
first_valid_uid: 8
first_valid_gid: 12
mail_location: mbox:%h/mail:INBOX=%h/mbox:INDEX=/var/log/imapd.indexes/%u
mbox_read_locks: dotlock
mbox_write_locks: dotlock fcntl
mail_log_prefix: %Us(%u): pid=%p, rip=%r, lip=%l,
auth default:
passdb:
driver: passwd-file
args: /etc/dovecot.deny
deny: yes
passdb:
driver: pam
userdb:
driver: passwd
Manoel
On 12/09/2010 02:22 PM, Paul Tansom wrote:
** Manoel Prazeres<praze...@impa.br> [2010-12-09 15:47]:
Hi
Sometimes mutt freezes saying "Closing connection to imap.impa.br...".
Any clue?
** end quote [Manoel Prazeres]
I get that sometimes and in my case it is always due to a network problem, one
of:
1. I've just rebooted the server without disconnecting my client [1]
2. My netbook has just come out of hibernation and the wifi hasn't connected
yet
It takes a good while to recover after this, which I assume is a Mutt issue,
but since it is always self inflicted I've not investigated further.
Could be worth checking your network connectivity at the time of the problem
starting (it could have recovered quite quickly and no longer be an issue
though). I've not checked, but there may be something in the Mutt configuration
to improve its handling of a lost connection perhaps.
