E
Ephemeris Lappis
I'm using Outlook 2000 on Windows 2000, but, according to several forums and
groups, similar problems seem to occur with more recent versions.
Both Windows and Office are uptodate, according to ms update report.
I've configured several POP accounts with SSL on port 995, some of them
hosted by one server, others coming from a same host. All that usually works
fine. But, when an error occurs on a account, generally because the host is
too busy and rejects the connection, the account stays in error state and any
further polling produces similar errors. This seem to affect only the given
account, and the other accounts hosted on the same server go on working until
a new connection error occurs. If i close outlook and start it again, the
error disappears, and all is ok until the next server failure.
This seems to occur only with ssl connections : indeed, similar errors often
occur with non-secured pop servers on port 110, when the server is down for
example, but the error is generally recovered when it comes back.
I've been trying to dump what is occuring after such an error, using my
ethereal traces, and, i'm not sure, but since i've no log when i manually
launch the account refresh, it seems that after the first connection error
outlook doesn't open a socket for the failed account, and just report an
error.
Could somebody confirm similar behaviour with any version of outlook ?
Is this directly an outlook problem, or a more global tcp/ip or ssl windows
issue ?
Thanks for your help.
groups, similar problems seem to occur with more recent versions.
Both Windows and Office are uptodate, according to ms update report.
I've configured several POP accounts with SSL on port 995, some of them
hosted by one server, others coming from a same host. All that usually works
fine. But, when an error occurs on a account, generally because the host is
too busy and rejects the connection, the account stays in error state and any
further polling produces similar errors. This seem to affect only the given
account, and the other accounts hosted on the same server go on working until
a new connection error occurs. If i close outlook and start it again, the
error disappears, and all is ok until the next server failure.
This seems to occur only with ssl connections : indeed, similar errors often
occur with non-secured pop servers on port 110, when the server is down for
example, but the error is generally recovered when it comes back.
I've been trying to dump what is occuring after such an error, using my
ethereal traces, and, i'm not sure, but since i've no log when i manually
launch the account refresh, it seems that after the first connection error
outlook doesn't open a socket for the failed account, and just report an
error.
Could somebody confirm similar behaviour with any version of outlook ?
Is this directly an outlook problem, or a more global tcp/ip or ssl windows
issue ?
Thanks for your help.