OL2K connection error to POP3 server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

OL2K SP3 pop3log.txt has the following error messsages:

POP3: 13:09:06 [db] Connecting to 'mail301468.popserver.pop.net' on port 110.
POP3: 13:09:51 [db] err: WSAGETSELECTEVENT = 0x10, WSAGETSELECTERROR = 10060
POP3: 13:09:51 [db] ERROR: "The connection to the server has failed.", hr=2148322318
POP3: 13:09:51 [db] Connecting to 'mail301468.popserver.pop.net' on port 110.
POP3: 13:09:52 [db] srv_name = "mail301468.popserver.pop.net" srv_addr = 199.171.54.232
POP3: 13:10:37 [db] err: WSAGETSELECTEVENT = 0x10, WSAGETSELECTERROR = 10060
POP3: 13:10:37 [db] ERROR: "The connection to the server has failed.", hr=2148322318
POP3: 13:19:12 [db] Connecting to 'mail301468.popserver.pop.net' on port 110.
POP3: 13:19:12 [db] srv_name = "mail301468.popserver.pop.net" srv_addr = 199.171.54.232
POP3: 13:19:57 [db] err: WSAGETSELECTEVENT = 0x10, WSAGETSELECTERROR = 10060
POP3: 13:19:57 [db] ERROR: "The connection to the server has failed.", hr=2148322318

What is this indicating? This issue is affecting at least two users who lose their ability to retrieve mail. But, there will be no indication to the end-user that a communication error has occurred. One user has Windows 2000 Professional SP4 and the other is a Windows NT 4.0 SP6a workstation.

Is there a way to trap the error and notify the end-user? Or, can the error be trapped and perform some form of corrective action?
 
well, it has been a month since i submitted this question and have no reply. i presume no one will ever reply.

my work around was to utilize a shareware progrem called TickerMyMail (TMM) by logiware in germany. the program checks the pop3 server if any mail is present. if there is it will scroll a ticker at the top of the screen displaying the sender, subject , size and time. It can successfully check the pop3 server when OL2K is unable to communicate with the server. When our users see that TMM finds mail and OL2K can not pull it, then something has to be done with OL2K. If it is a Windows Pro 2000 user, simply cycling OL2K will fix it. If it is Windows NT SP6a, the workstation must be restarted along with OL2K.
 
Back
Top