Have you put the client email program into logging mode and then reviewed the 
logs to see if it sheds any light?

John T
eServices For You

-----Original Message-----
From: "SM Admin" <[email protected]>
Sent: Tuesday, September 16, 2014 9:43am
To: [email protected]
Subject: [MBF] Re: server time-outs

Scott Jibben E-Mail SignatureNo thoughts anyone?

From: SM Admin 
Sent: Friday, September 12, 2014 12:07 PM
To: [email protected] 
Subject: [MBF] server time-outs

Soooo... I have one of those questions which really isn’t about Declude or spam 
but the people here are more likely to have good ideas than anywhere else I can 
think.
We’re running SM 12.x (whatever is the latest version) and the most common 
client app is Microsoft Live Mail (formerly Outlook Express) using IMAP.  The 
problem is that if a client computer has been sitting idle for more than a few 
minutes, when you return to your mail box, you get a ‘server disconnected due 
to time-out’ type error.  Here’s a typical scenario from my own computer:
I’ve got Live Mail open and I leave my desk for 20 minutes.  I come back and 
there are various new messages showing (so I know it’s been connected), and I 
start deleting, replying, moving messages to other folders, etc.  After about 
two minutes, I suddenly get the error message about disconnected from the 
server.  And everything I just did (all the deletions, moving, etc.) are 
un-done.  Any messages I wrote (new or replies) still go out, but everything 
else that I did is gone.  
This is mostly a nuisance but I’d sure like to figure out why it happens. I 
can’t decide if it’s the client software, the server software, some sort of DNS 
mis-configuration, or a server hardware misconfiguration.  I did run one test 
with interesting results: I tested for the same problem on an internal IP on 
the LAN and the disconnected became very rare.
The server is mail.bcwebhost.net, which has a public IP of 173.164.65.200.  For 
the test I just mentioned, I linked the server to the LAN using an internal IP 
(10.1.10.9) and configured SM to listen to both IPs. Then I set up the clients 
on the LAN to connect to that internal IP instead of the usual host name.  As I 
said, that seemed to work much better. So that would imply it’s not a problem 
with SM, but maybe with our external configuration (either hardware or DNS).
So, any suggestions, thoughts, proposed further tests?
Thanks,
Ben




#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[email protected]>.
To unsubscribe, E-mail to: <[email protected]>
To switch to the DIGEST mode, E-mail to <[email protected]>
To switch to the INDEX mode, E-mail to <[email protected]>
Send administrative queries to  <[email protected]>

Reply via email to