We sporadically have this issue as well. It seems an e-mail get's stuck in the mailbox and LDSD refuses to read anything after that. We just assumed up to now that as we are connecting to Lotus Notes it was another one of the many 'features' of Lotus Notes/Domino that was causing the problem. We end up having to go through one by one in the mailbox to find the dodgy email and then remove it. Once done the rest get processed right through. I haven't tried rebooting the LDSD server to see if it fixes though.
Not sure if any of that helps?
I think what we are seeing is slightly different. It doesn't matter what email it is (or even if there are any emails waiting to be picked up).
It just fails to connect.
After a reboot it usually connects fine and then will read all emails that are waiting.
(we also get the odd email it can't read - usually if in chinese/korean - but it just skips these).
Thanks - Adam.
Ahh ok - Maybe ours is just Lotus Notes then!
I remember when we all used either Notes or Groupwise....
Now our Director is talking about outsourcing our email to the "Cloud" (everyone's favourite word these days).
TBH I don't think our problem is with LanDesk SD itself - just wondered if anyone else had encountered it or had any ideas.
Cheers - Adam.
I'd set up an application pool for the TPS inbound is using and do a pool recycle at (say) 2am every day. It will not fix the problem, but might reduce the frequency. At the time it happens, I'd also do a telnet connection on the server to the right port on the mail server and see what comes back. If an announcement for some sort of IMAP service doesn't appear from the mail server, then indeed the issue is nothing to do with LANDesk. (and the opposite is also true). If you can connect on the IMAP port and have recycled the pool and inbound still fails to conenct, then I'd be asking your local LANDesk support team to be on standby to set up a remote session for them to take a look.
This hits us about once every six weeks or so and we can usually correct it by switching from SSL to plaintext, waiting for one full connection, then switching back to SSL. Just restarting the service doesn't do it.