On Sun, 12 Mar 2006 12:33:42 -0600, Sam <sam@email-scan.com>
wrote:

>Gerard Bok writes:
>
>> On Sun, 12 Mar 2006 18:48:30 +0200, Yizhar Hurwitz
>> <yizhar@mail.dot.com> wrote:
>>
>>>Gerard Bok wrote:
>>>>
>>>> I also got word from the ISP involved: they did not raise the
>>>> number of simultaneous connections on that mail account.
>>>> But that shouldn't matter as XP Home is not able to make more
>>>> than 5 connections anyway, I think.
>>>> And problems also occur when there's only one single user active.
>>
>>>You are wrong.
>>
>> Could be :-)
>>
>>>The connection limit in Windows XP (both Home and Pro versions) with SP2,
>>>refers to embryonic or half-open connections when the XP clients sends the first packet of the TCP handshake,
>>>and is waiting for the first response from the server (or whatever device in the other side).
>>>
>>>If the TCPIP stack on the XP computer reaches that limit, you will find a yellow Event ID 4226 that tells you.
>>>So, if you don't see Event 4226, then this is not the issue.
>>>
>>>You can read more info about this limit and workaround here:
>>>SpeedGuide.net :: Windows XP SP2:
>>>http://www.speedguide.net/read_articles.php?id=1497
>>
>> I think this story is rather different from Q314882 which talks
>> about "Any file, print, named pipe, or mail slot session...."
>>
>> Aren't we talking about mail slot sessions here ?
>
>Correct.
>
>As I explained before, the IMAP server's default settings impose a limit of
>5 connections from the same IP address. You have confirmed with your host
>that the server's default settings have not been adjusted. So that's your
>answer.
>
>Poorly-written Microsoft bugware sometimes opens a separate connection for
>each folder in the mailbox.

True. But in this case we cannot blame MS.

These 10 mailboxes are indeed 10 separate user accounts, each
with it's own set of access codes.

(I just answered the ISP's counter question "what do you mean by
subaddressing?" :-)
Any length to solve / avoid the problem :-)

--
Kind regards,
Gerard Bok