system
119
Techie,
For info. and re our previous message(s).
As said, things appear to work fine with your suggestion of working one a/c .
Being that it had been some time since the last error, I thought I’d see what happened if I reverted to checking ALL a/c’s. Gues what… first attempt and nada!.. Avast didn’t kick in, so my isp returned invalid user/pass.
We have been moving down the path of interaction/communication between the mail client and Avast, so… I closed Pegasus, shut down the dial-up… see where I’m going with this
. OK, let’s assume the only thing left in memory (relavent to this issue) is Avast y/n?. So I established another dial-up, opened Pegasus and tried again… same thing… Avast didn’t kick in.
My thinking is (rightly or wrongly ??? what do you think)… Avast is was the only ‘contributing’ app that was left running and had not been restarted and the problem persisted.
I re-booted the machine and all a/c’s where checked normally. Avast obviously gets re-booted at this stage too, so the assumption can be that Avast was the culprit because function returned after Avast was rebooted.
I’ve sent the 3rd report to Vojtech as he requested. For info., this is what the error bit looks like;…
01/03/04 20:31:10: POP accept connection from: 127.0.0.1
01/03/04 20:31:10: --XXX sleep
01/03/04 20:31:11: ->FAK (USER USERNAME.isp)#pop3.terra.es
01/03/04 20:31:11: Cannot connect to POP server pop3.terra.es:110. Invalid host.
01/03/04 20:31:11: <-POP -ERR Server ‘pop3.terra.es’ unavailable
01/03/04 20:31:11: --XXX sleep
01/03/04 20:31:11: --XXX sleep
01/03/04 20:31:11: --XXX sleep
Same old thing still :-\
Walker.