| 1 |
Am Sat, 12 Dec 2015 17:53:04 +0000 |
| 2 |
schrieb Stroller <stroller@××××××××××××××××××.uk>: |
| 3 |
|
| 4 |
> |
| 5 |
> > On Sat, 12 December 2015, at 3:08 a.m., jens wefer |
| 6 |
> > <jens.wefer@××××××.net> wrote: |
| 7 |
> > |
| 8 |
> > I set up a mail server, postfix/dovecot, ssl required. |
| 9 |
> > test with mail-client, all ok |
| 10 |
> > when I try to copy mails with imapsync (gentoo) comes timeout, |
| 11 |
> > and imapsync will login again. |
| 12 |
> > with each new login, a new process imap-login is generated. |
| 13 |
> |
| 14 |
> Sorry if this is a dumb question, but how do you know it's timing out? |
| 15 |
> |
| 16 |
> Could it just be slow, as it has to compile loads of messages in its |
| 17 |
> first run? |
| 18 |
> |
| 19 |
> Looks like dovecot has a 30 minute timeout. [1] |
| 20 |
> |
| 21 |
> An old message on the Dovecot mailing list [2] suggests to set |
| 22 |
> "verbose_proctitle = yes" in config to see why each process is open. |
| 23 |
> |
| 24 |
> It also suggests using high-performance mode, rather that the |
| 25 |
> default. |
| 26 |
> |
| 27 |
> Stroller. |
| 28 |
|
| 29 |
timeout comes from imapsync (default timeout 120 sec). |
| 30 |
after 10 minutes then running 5 Dovecot processes which want 100% CPU |
| 31 |
time. mail logfile: |
| 32 |
imap-login: Login: user = .... blablub, TLS ession, .. |
Archives