Paul
I wasn't really getting expected behaviour when I tried it with nc (i.e. if
I connect it bails out after login_timeout and if I login it appears to stay
connected).
However as our production server is playing up I was experimenting with
routing more traffic through our second server and noticed the same cut off
was happening. This server has login_timeout = 60
So I use a web client, log in and start to download a file and the logs give
the following after 60 seconds
May 30 21:42:28 newgate dbmail/imap4d[88536]: Debug:[clientbase]
ci_write(+343): [0x8075d4000] S > [8192/10542643:uvr39/^M
89zxRp5l2uO84DBBC/pn/Of16Ve4WGR]
May 30 21:42:28 newgate dbmail/imap4d[88536]: Debug:[imap]
imap_cb_time(+344): [0x8085d2740]
May 30 21:42:28 newgate dbmail/imap4d[88536]: Debug:[imap]
dbmail_imap_session_set_state(+1660): [0x8085d2740] state [3]->[6]
May 30 21:42:28 newgate dbmail/imap4d[88536]: Debug:[imap]
imap_session_bailout(+170): [0x8085d2740] state [6] ci[0x8075d4000]
May 30 21:42:28 newgate dbmail/imap4d[88536]: Debug:[imap]
dbmail_imap_session_set_state(+1660): [0x8085d2740] state [6]->[7]
May 30 21:42:28 newgate dbmail/imap4d[88536]: Debug:[imap]
imap_cleanup_deferred(+155): [0x8075d4000] DEFERRED_MAX_LOOP reached;
cleanup session
May 30 21:42:28 newgate dbmail/imap4d[88536]: Debug:[imap]
dbmail_imap_session_delete(+197): [0x8085d2740]
May 30 21:42:28 newgate dbmail/imap4d[88536]: Debug:[clientbase]
ci_close(+518): closing clientbase [0x8075d4000] [18] [18]
May 30 21:42:28 newgate dbmail/imap4d[88536]: Debug:[clientbase]
ci_cork(+205): [0x8075d4000]
Actually checking 60 seconds before the download started at 21:41:29
May 30 21:41:28 newgate dbmail/imap4d[88536]: Debug:[MailboxState]
MailboxState_flush_recent(+971): flush [0] recent messages
May 30 21:41:29 newgate dbmail/imap4d[88536]: Debug:[clientbase]
ci_write(+343): [0x8075d4000] S > [33304/18639358:* 11 FETCH (UID 4539357
BODY[2] {186393]
May 30 21:41:29 newgate dbmail/imap4d[88536]: Debug:[clientbase]
ci_write(+343): [0x8075d4000] S >
[16000/18606057:vozfM2M+n+ev6pXjLtb+v6/U4/P+v67f9uj44Wm]
May 30 21:41:29 newgate dbmail/imap4d[88536]: Debug:[imap]
_ic_cb_leave(+680): handling imap session [0x8085d2740] client_state []
May 30 21:41:29 newgate dbmail/imap4d[88536]: Debug:[clientbase]
ci_uncork(+212): [0x8075d4000]
May 30 21:41:29 newgate dbmail/imap4d[88536]: Debug:[imap]
imap_handle_exit(+439): [0x8085d2740] state [3] command_status [1] [FETCH]
returned with status [0]
May 30 21:41:29 newgate dbmail/imap4d[88536]: Debug:[imap]
imap_session_reset(+264): [0x8085d2740]
May 30 21:41:29 newgate dbmail/imap4d[88536]: Debug:[clientbase]
ci_uncork(+212): [0x8075d4000]
May 30 21:41:29 newgate dbmail/imap4d[88536]: Debug:[clientbase]
ci_write(+343): [0x8075d4000] S >
[7276/18590087:xRfZz94Y/Kqt7tyUYZP409kMUkZ+Un60b7^M geq]
Is that of any assistance?
Regards
Daniel
===============================
Daniel,
The login_timeout is supposed to be just that! It is a pre-authentication
guard.
If it kicks in on active connections something else must be going on.
Try to generate some debug logs. Keep it simple.
simply connect:
nc imaphost imapport
wait login_timeout seconds. Connection should be terminated.
nc imaphost imapport
x login someuser somepassword
wait timeout seconds. Connection should not be terminated before.
share the logs, and the dbmail.conf file.
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
