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.




On 21-05-14 14:23, Daniel Schütze wrote:
Short Version

Is there any reason why the conf variable login_timeout should be cutting
off an active connection (say an imap session with outlook or mail accessed
via webmail)?  It appears increasing the timeout on my server may have
solved an issue of downloading larger files.

More detailed version

We are using dbmail 3.1.13 on FreeBSD and relatively recently (I’m afraid I
don’t know exactly how long) we have been having issues where users are
unable to download large attachments.  Typically the users report messages
of more than 2 meg cannot be downloaded.  I must admit I’ve been putting
this down to poor internet connections lately.  However it occurred to me
that people reporting issues were able to download very large files from our
webserver.

So today I was trying to test it and I tried downloading a 16meg file
remotely using a webmail client and it was repeatedly cut off mid transfer.

To cut a long story short (where long story means trying cutting our various
possible sources, using multiple internet connections and trying another
dbmail installation) I realised that the download was being interrupted
after almost exactly 30 seconds (and repeated this several times).  Looking
at the dbmail.conf file I could only see one 30 second timeout and this was

# Idle time allowed before a connection is shut off if you have not logged
in yet.
#dms default 60
login_timeout         = 30

I changed this to 60 and low and behold the download repeatedly went on for
60 seconds.

I then changed it to 3000 and the download actually completed for the first
time as did another random 15meg download I tried.

Now this may be an amazing co-incidence but if I have determined this is the
cause of the “cutting off” of our connections is this feature working as
intended?

I have not altered this variable for quite some time and my gut feeling
wonders if this is something which has happened in recent dbmail versions.

Daniel Schütze

------------------------
CWA International
Balmoral House
9 John Street
London
WC1N 2ES

(t) + 44 (0)20 7242 8444
(e) [email protected]
(w) http://www.cwa.uk.com/



_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


--
________________________________________________________________
Paul J Stevens       pjstevns @ gmail, twitter, github, linkedin
           www.nfg.nl/[email protected]/+31.85.877.99.97
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Reply via email to