On 10/13/16 10:42 AM, Urban Loesch wrote:

Am 13.10.2016 um 16:53 schrieb Bryan Holloway:
On 10/13/16 9:07 AM, Aki Tuomi wrote:

On October 13, 2016 at 4:55 PM Jerry <je...@seibercom.net> wrote:

On Thu, 13 Oct 2016 08:36:23 -0500, Bryan Holloway stated:

I also extended the "Server Timeout" setting in OT2010 to 10 minutes,
which doesn't seem to help either. (!)

Outlook 2010 is a very old version. Why not update to the 2016 version.
I am running it without any problems. If you do update, remember to
remove the old version completely first.


I do wonder if the real culprit is some firewall that timeouts the
idle connection.


I considered that, but again everything worked fine until we moved
them from 2.1 to 2.2. Their same firewall is in use.

Is there a way to see the IMAP commands coming from the client? I've
tried looking at PCAPs, but of course they're encrypted so I can't see
the actual
dialog going on between the server and client. I didn't see an obvious
way to do this in the docs.

There is a "rawlog" feature, which writes down the hole decrypted imap
session in files.

service imap {
    executable = imap postlogin


service postlogin {
  executable = script-login -d rawlog
  unix_listener postlogin {

This should write *.in an *.out files to
"$mail_location/dovecot.rawlog/" directory for each imap session.
The directory should be writeable by the dovecot user. I tested this
some years ago, so I'm not shure if the configuration
is still valid.


Great! I will try this.

Reply via email to