Frodo Larik wrote:
>
> On Sep 22, 2007, at 1:41 PM, Frodo Larik wrote:
>
>>> If it *is* idle, you can disable that command
by editing the dbmail.conf
>>> and setting:
>>>
>>> [imap]
>>> capability = IMAP4 IMAP4rev1
AUTH=LOGIN ACL NAMESPACE
>>> CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT
UNSELECT
>
>
> It looks like it is the IDLE command:
>
> /var/log/syslog:
> Sep 22 13:49:16 pretpark dbmail/imap4d[20039]:
Info:[imap]
> imap4.c,IMAPClientHandler(+187): COMMAND: [70 IDLE]
> Sep 22 13:49:16 pretpark dbmail/imap4d[20039]:
Info:[imap]
> imap4.c,IMAPClientHandler(+298): Executing command
idle...
>
> /var/log/dbmail/dbmail.err
> Sep 22 13:49:16 pretpark dbmail-imapd[20039]:
Error:[imap]
> imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
>
> I disabled it.
>
>
>>> [imap]
>>> maxconnects = 1
>
> I now get stuff like this as an error (is it really an
error or just a
> NOTICE?):
>
> /var/log/dbmail/dbmail.err
> Sep 22 13:54:35 pretpark dbmail-imapd[21239]:
Error:[serverchild]
> serverchild.c, PerformChildTask(+385): maximum number
of connections
> reached, stopping now
>
That's a side-effect of 'maxconnects = 1'. Set it to
something like
1000, and disable the IDLE command instead.
--
____________________________________________________________
____
Paul Stevens paul at
nfg.nl
NET FACILITIES GROUP GPG/PGP:
1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail dbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail
|