Gerard: It's hard for me to believe that you are the only user having
similar problems. Does the mail provider have any support forums or
technical assistance for you to go to? It truly sounds like a firewall
problem but you say you have the appropriate port (143) opened but I wonder
if something else is interfering such as an antivirus or antispam program?

Beyond that, I'm stumped unless you have some "malware" installed that is
interfering.
--
Jim Pickering, MVP, Outlook Express
https://mvp.support.microsoft.com/pr...8-1171988A62D6



"Gerard Bok" wrote in message
...
On Fri, 10 Mar 2006 10:22:46 -0800, "Jim Pickering"
wrote:

Is there by any chance a router involved in the total equation? Is it a
LinkSys router? Have you searched for any updated firmware for it from
the
manufacturer?

The router involved is a PC, running Smoothwall (with patches 1
to 8).

It sounds like it could be a configuration problem in your OE accounts.

Quite unlikely, as the problems occur at all locations.
Accounts are created on different PC's, different locations,
different ISP's , etc.
The only thing they have in common is the administrator.
(And he is beyond any suspicion. Anyone know the smiley for an
aureole ?)

Let
OE make a connection, then click Tools|Accounts|Mail. In the connection
column, they should all show "Any Available".

Check :-)

See if that helps at all.

No! Sorry :-) But I am very grateful for all suggestions though.

Also very weird is the fact, that there is a link with the
server's load. But although I can set the timeout value at 3
minutes, the whole circus crashes in a session that lasts 20
seconds in total.

At 5 PM, I can hardly get any mail at all. At 8 PM I can.
Without firewall, all accounts at once. With the firewall
enabled, just one by one.

"Gerard Bok" wrote in message
...
On Wed, 8 Mar 2006 11:59:10 -0800, "Jim Pickering"
wrote:

813514 - OL: Error 0x800ccc0d or 0x800ccc0f When Receiving and Sending
E-Mail:
http://support.microsoft.com/?kbid=813514

Situation: 10 mailboxes on a Courier IMAP server.
Multiple users on multiple locations, all sharing all mailboxes.

Synchronize accounts produces loads of 0x800CCC0F errors.
Once I try to sync all accounts at once, loads of errors are
reported, on random mailboxes and even when I just finished an
individual sync.

--
Kind regards,
Gerard Bok

Gerard Bok writes:

Looking for some guidance. Or aspirin :-)

Situation: 10 mailboxes on a Courier IMAP server.
Multiple users on multiple locations, all sharing all mailboxes.

The aim is to use Outlook 2003.
Couldn't get that operational at all, so for the time being, we
settled for Outlook Express instead.

Synchronize accounts produces loads of 0x800CCC0F errors.
More specific: at quiet times, I am able to sync each mailbox
individually without any error.
Once I try to sync all accounts at once, loads of errors are
reported, on random mailboxes and even when I just finished an
individual sync.

By mailboxes I presume you are referring to IMAP folders. I doubt that you
are logging in to ten different IMAP accounts.

The default Courier-IMAP server configuration permits a maximum of five
simultaneous connections from the same IP address.

It appears that your mail client opens a separate connection for each IMAP
folder. The server refuses to accept any more connections, after the first
five, and then your mail client vomits all over itself.

Either increase the maximum number of allowed simultaneous connections, in
the server's configuration file, or switch to a different mail client that
implements IMAP properly.



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)

iD8DBQBED28Vx9p3GYHlUOIRAnyfAJ0bF9VVLu3CUdrkapHoDB GFI8W9uQCeOlmA
Irltd1jj5Tt6P4+6g/6zgbM=
=b5zI
-----END PGP SIGNATURE-----

Sam's reply was as follows (but since he used encryption w/o providing the
key, you may have missed it):

By mailboxes I presume you are referring to IMAP folders. I doubt that you
are logging in to ten different IMAP accounts.

The default Courier-IMAP server configuration permits a maximum of five
simultaneous connections from the same IP address.

It appears that your mail client opens a separate connection for each IMAP
folder. The server refuses to accept any more connections, after the first
five, and then your mail client vomits all over itself.

Either increase the maximum number of allowed simultaneous connections, in
the server's configuration file, or switch to a different mail client that
implements IMAP properly.


"Sam" wrote in message
il-scan.com...

Jim Pickering writes:

Sam's reply was as follows (but since he used encryption w/o providing the
key, you may have missed it):

That's not the reason he might've "missed" it.

The only reason he might've missed it would be if he was using broken
Microsoft E-mail virus propagation ****ware, that fails to properly
implement a ten-year old standard for digital signatures.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)

iD8DBQBEEBjMx9p3GYHlUOIRAgeLAJ9IjninP6dSpu+5N3q/Qwm/vP4xQACfTxCL
9UQTM2WG+e8eJuNLEMQqcLk=
=vBzy
-----END PGP SIGNATURE-----

Hi Sam:

Hope you feel better, now that you've vented about MS. Have a great day.
--
Jim Pickering, MVP, Outlook Express
https://mvp.support.microsoft.com/pr...8-1171988A62D6



"Sam" wrote in message
ail-scan.com...

(posting to msnews; no access to USENET newsgroups)
"Jim Pickering" wrote in message

....
Sam's reply was as follows (but since he used encryption w/o providing the
key, you may have missed it):
....


Jim,

The others aren't using OE as their newsreaders
so there may not be a problem for them. ; )

A surprise for me is that both Google Groups and
the web interface seem to have no trouble with Sam's replies.
E.g. normally both refuse to show "attachments".

http://groups.google.com/group/micro...f350be30910a22

http://www.microsoft.com/communities...6-315c8de265de


BTW how does WM do with this case? EG


FYI

Robert Aldwinckle
---

"Robert Aldwinckle" wrote in message
...
(posting to msnews; no access to USENET newsgroups)

BTW how does WM do with this case? EG


FYI

Robert Aldwinckle
---

No idea, Robert, since I've had problems with newsgroup subs in Vista.
Hopefully, the next build will be better but who knows?
--
Jim P.

Robert Aldwinckle wrote:
A surprise for me is that both Google Groups and
the web interface seem to have no trouble with Sam's replies.

Hints from headers?...

X-Mailer: http://www.courier-mta.org/cone/
snip
Content-Type: multipart/signed;
boundary="=_mimegpg-commodore.email-scan.com-11676-1141905612-0004";
--
~PA Bear

PA Bear writes:

Robert Aldwinckle wrote:
A surprise for me is that both Google Groups and
the web interface seem to have no trouble with Sam's replies.

Hints from headers?...

X-Mailer: http://www.courier-mta.org/cone/
snip
Content-Type: multipart/signed;
boundary="=_mimegpg-commodore.email-scan.com-11676-1141905612-0004";

Further clue: http://www.faqs.org/rfcs/rfc2015.html

Category: Standards Track, October 1996

A ten-year old Internet standard.

For the clue impaired: as a rule, Internet standards are fully backwards
compatible. A compliant mail client is not required to have any encryption
or digital signature-verification capabilities in order to show
digitally-signed messages. For example: Mozilla Thunderbird, out of the
box, displays digitally-signed messages perfectly fine, and no differently
than non-signed mail. This is because it's a MIME formatted message, and
any E-mail client that properly implements MIME will parse digitally-signed
messages as ordinary multipart MIME messages, perhaps with a tiny
attachment. Mozilla Thunderbird even has a tiny bit of additional logic of
suppressing the attachment that holds the digital signature. Even though
Thunderbird needs a PGP plugin to handle MIME-PGP mail, without the plugin,
and because Thunderbird properly implements MIME, unlike Outlook, it
displays the contents of signed messages without making a big fuss.

Where Microsoft screwed up, and has been incapable of fixing, for the last
ten years, is explained by section 7.2.6 of RFC 1521 (RFC 2046 eventually
superceded RFC 1521, but RFC 1521 was in effect at the time):

7.2.6. Other Multipart subtypes

Other multipart subtypes are expected in the future. MIME
implementations must in general treat unrecognized subtypes of
multipart as being equivalent to "multipart/mixed".

Of course, complying with Internet standards is not a top priority for
Microsoft. If Microsoft's virus distribution software was correctly
designed, in accordance with Internet standards, even if it chooses not
implement digitally-signed messages, which use multipart/signed, it should
treat them exactly as "multipart/mixed" messages, which are ordinary
messages, with ordinary attachments.

Interestingly enough, Microsoft's bugware has extensive support for
multipart/related MIME type (RFC 2387), which was introduced in 1998, two
years after multipart/signed.

So, for the last ten years, clueless MS cheerleaders have been constantly
whining because Outlook Express vomits all over itself when it sees a signed
message. They always blame everyone else when the real problem is the buggy
crapware they're using to occasionally read E-mail (when it's not otherwise
busy sending viruses and trojans to all E-mail addresses pulled from the
address book).


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)

iD8DBQBEEMNOx9p3GYHlUOIRAkLZAJoDfkDVBkbyiNv5QSdAmf IzhTPGywCeLIg2
LHvukJ95Qgka9Pt3ZffpWc0=
=bdmX
-----END PGP SIGNATURE-----

On Wed, 08 Mar 2006 17:56:06 -0600, Sam
wrote:

Gerard Bok writes:

Situation: 10 mailboxes on a Courier IMAP server.
Multiple users on multiple locations, all sharing all mailboxes.

Synchronize accounts produces loads of 0x800CCC0F errors.
More specific: at quiet times, I am able to sync each mailbox
individually without any error.
Once I try to sync all accounts at once, loads of errors are
reported, on random mailboxes and even when I just finished an
individual sync.

By mailboxes I presume you are referring to IMAP folders. I doubt that you
are logging in to ten different IMAP accounts.

Well, good question. But I guess we are :-)
There are 10 different email addresses on the server, each with
it's own mailbox and set of log in codes (and it's own aliases).

The default Courier-IMAP server configuration permits a maximum of five
simultaneous connections from the same IP address.

Before we could get this schema going the server's administrator
had to adjust something from 5 upwards. Now it is set to 100
instead. (Due to NAT up to 3 different PCs could be calling the
server from the same IP, so that would make 30 connections.)

It appears that your mail client opens a separate connection for each IMAP
folder. The server refuses to accept any more connections, after the first
five, and then your mail client vomits all over itself.

There definately is going something wrong. Peeking at the
communications shows [TCP Window Full] [TCP Out-of-order]
messages. I never see an indication of a connection being denied
though.

Either increase the maximum number of allowed simultaneous connections, in
the server's configuration file, or switch to a different mail client that
implements IMAP properly.

The first has been done already, I think. And the second is, I am
afraid, not (yet) an option.
Thanks!

--
Kind regards,
Gerard Bok