Jim S <
jim@jimXscott.co.uk> wrote:
I have three accounts on Outlook2010.
Two of them work fine (Gmail and Virginmedia(IMAP) However my webhost
IMAP account, now and then, comes up with the 'server has closed the connection' or words to that effect (Error 0x800ccdd). I have tried
all the solutions suggested on various Googled sites, but none of
them work.
What puzzles me is that it is only on my web host address, which is
otherwise excellent. I have contacted them more than once and they
suggest that their security settings are more up to date than the
others and they will do the same in the fullness of time, but I'm not
sure I believe them. If I change hosts only to find the same, I will
be no further forward. They (my host) suggest I use Thunderbird and
it does work without any problems, but Outlook is so 'grown-up' in comparison, I would rather use it.
Has anyone here had the same problem with one account and not others;
is it Outlook2010's fault or is it the fault of my webhost.
PS I cannot afford to a later version of M$ Office and the rest works
fine.
Does their IMAP server support PUSH or IDLE?
https://en.wikipedia.org/wiki/Push-IMAP
https://en.wikipedia.org/wiki/IMAP_IDLE
However, as I recall, the client issues a command, like HELO or EHLO,
and looks at the response from the server to parse out keywords, like
PUSH or IDLE. From what I've read, Outlook 2010 supports IMAP IDLE. I
don't think IMAP PUSH has gotten much support yet. For example, if you
go into Send/Receive tab, Send/Receive Groups, Define Send/Receive
Groups, there is a polling option of "Schedule automatic send/receive
every X minutes". If that is disable, and if both client and server
support IMAP IDLE, then you still get notified when there is a new
message in your e-mail account.
https://tools.ietf.org/html/rfc2177
I'm not sure how IDLE all works. I doubt the client is given a
persistent connection, because that would consume resources at the
server that need to be freed up to grant connects from all their other
users. IDLE is something akin to a ping: "Any new messages?" versus
"Give me a list of all messages in all folders and I'll check which are
new."
https://www.imageway.com/2018/email-hosting-blog/imap-idle-the-best-approach-for-push-email
It looks like the client keeps reissuing an IDLE command to the server
to see if there are new messages available in the account. An IDLE has
the server just return status and is less demanding than issuing LIST or
UIDL commands to get a full list of messages in the account (LIST and
UIDL list all messages, and it's the client that tracks which are new or
old). The RFC says:
The server MAY consider a client inactive if it has an IDLE command
running, and if such a server has an inactivity timeout it MAY log
the client off implicitly at the end of its timeout period. Because
of that, clients using IDLE are advised to terminate the IDLE and
re-issue it at least every 29 minutes to avoid being logged off.
This still allows a client to receive immediate mailbox updates even
though it need only "poll" at half hour intervals.
So, check how often Outlook polls the server. You want it 5 minutes, or longer, but less than 29 minutes. I assume you are leaving Outlook
loaded and running all the time to check for new messages as they
arrive.
How often is the polling interval? Some servers don't like less than 5
minutes since this short of a polling interval is considered abusive.
If you don't have any new messages, the polls won't find any, but you
used resources at the server to find out there are no new messages. If
there are new messages, it'll probably take you longer than 5 minutes to
read through them. You'd have to check with your e-mail provider what anti-abuse and anti-spam quotas they enforce on their e-mail accounts to
make sure, for example, that you are not exceeding how many connects you
are allowed per day or per minute.
Do you have an anti-virus program installed with it configured to
intercept and interrogate your e-mail traffic? That is redundant,
because it detects nothing more than the on-access (real-time) scanner
of the AV program. The e-mail interrogation is using the same engine as
the on-access scanner. However, the local transparent proxy used by the
AV program to interrogate the e-mail traffic can cause timeouts (both to
the client when it is waiting for e-mails to download and to the server
when waiting for the client after it sends an e-mail). E-mail scanning
by AV is superfluous, so disable that feature or uninstall it (if it is
a separate module, like in Avast/AVG) and retest.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)