[Dovecot] Problems with Outlook clients after a migration
Hi,
I'm doing the final tests before I migrate my 10000 users from RHEL 4 + dovecot 1.1.20 to RHEL5 + dovecot 1.2.11, and I'm having some serious problems with outlook 2007 clients disconnecting very often.
In dovecot's log I see lot of connects and disconnects from these clients (as oposed to my kmail, that just connects once when I come in and disconnects when I shut it off). After unchecking the "chek every X minutes" thing in outlook I get fewer of those -while functionality remains-, but the main problem still persists: every now and then (more or less 30 mins), the client disconnects, and sometimes the client goes offline. This didn't happen with my previous setup.
I use the outlook-idle workaround, but it doesn't seem to make any difference.
Any ideas?
My dovecot -n
1.2.11: /usr/local/etc/dovecot.conf
OS: Linux 2.6.18-164.11.1.el5 x86_64 Red Hat Enterprise Linux Server release
5.4 (Tikanga) syslog_facility: local1 protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /usr/share/ssl/certs/imapd.pem ssl_key_file: /usr/share/ssl/certs/imapd.pem disable_plaintext_auth: no login_dir: /usr/local/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_process_per_connection: no login_max_processes_count: 256 max_mail_processes: 2048 first_valid_uid: 100 mail_location: maildir:~/Maildir:INDEX=/var/dovecot/%u:CONTROL=/var/dovecot- nas/%u/control mail_nfs_storage: yes lock_method: dotlock 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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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 imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %v.%u auth default: cache_size: 1000 cache_ttl: 6000 master_user_separator: * debug: yes passdb: driver: passwd-file args: /usr/local/etc/bloqueados deny: yes passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf passdb: driver: pam passdb: driver: passwd-file args: /usr/local/etc/dovecot-master.conf master: yes userdb: driver: prefetch userdb: driver: passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: fs
-- Joseba Torre. Vicegerencia de TICs, área de Explotación
Also: I've moved from 32 to 64 bits. Maybe some problem related to this?
Joseba Torre. Vicegerencia de TICs, área de Explotación
On Wed, 2010-05-26 at 11:43 +0200, Joseba Torre wrote:
What does Dovecot log as the disconnect reason when this happens? It does seem like it's related to the 30 min timeout.
I use the outlook-idle workaround, but it doesn't seem to make any difference.
Since v1.1 outlook-idle workaround hasn't done anything. Dovecot now never disconnects IDLEing client.
On Miércoles 26 Mayo 2010 12:39:05 Timo Sirainen escribió:
I get some
May 26 12:18:05 s000085 dovecot: IMAP(lgsavbaf): Disconnected: Logged out bytes=142/1525
(is this outlook quitting?)
but also some May 26 12:19:22 s000085 dovecot: IMAP(lgsavbaf): Disconnected in IDLE bytes=161/2018
-- Joseba Torre. Vicegerencia de TICs, área de Explotación
On Wed, 2010-05-26 at 13:13 +0200, Joseba Torre wrote:
Yes, Outlook sent LOGOUT command.
Something disconnected the client. Maybe you've a firewall/load-balancer/etc in the middle that doesn't like long idling connections? Although that wouldn't explain why it worked with v1.1.
You could also try it yourself:
telnet imap.server.com 143 a login user pass b idle
and see if it gets disconnected. It should also send "* OK Still here" every 2 minutes, so I'd guess nothing should disconnect it..
Some new data:
If I remember correctly, I've changed:
- commented out the outlook-idle workaround.
- the server's iptables now doesn't use state in 993 port
and the situation is much better. I've got some "Disconnected in IDLE" messages, but must of them where related to changes in the client (twice thunderbird dying, and once a system being suspended). There're still some from one of the most problematic clients (windows 7 + outlook 2007) with no apparent reason, but the user didn't sensed anything.
I'll keep my test for some days before the final migration, but now it seems ok.
Joseba Torre. Vicegerencia de TICs, área de Explotación
participants (2)
-
Joseba Torre
-
Timo Sirainen