Re: [twsocket] pop3 and lastresponse

2010-09-20 Thread Arno Garrels
Arno Garrels wrote: Zvone wrote: IMO the component should clear LastResponse on before connect. Maybe it should, but what it does is different story :) I checked in a few changes today, it's rev #600: Log: Pop3Prot V6.08 Moved HMAC-MD5 code to OverbyteIcsMD5.pas. Ensure that var

Re: [twsocket] pop3 and lastresponse

2010-09-19 Thread Arno Garrels
Zvone wrote: IMO the component should clear LastResponse on before connect. Maybe it should, but what it does is different story :) Yes, it has to be fixed IMO. So what about a numeric property LastErrorNumber? There is no such property nowhere in pop3 (or in any ICS file). That was a

Re: [twsocket] pop3 and lastresponse

2010-09-18 Thread Angus Robertson - Magenta Systems Ltd
While Timeout works rather nice as far as Idle version goes, connect version is usually preceded by Windows built-in timeout An application can not cleanly stop a TCP connection attempt, you have to wait for Windows to timeout, usually 40 seconds unless there is an error of some sort earlier.

Re: [twsocket] pop3 and lastresponse

2010-09-18 Thread Arno Garrels
Hello, Zvone wrote: I found something that might also be issue with pop3 component. If you check one pop3 account and end the session usually LastResponse will be some ending message like +OK sayonara. But if you then reinitialize pop3 for another account and this account fails to connect,

Re: [twsocket] pop3 and lastresponse

2010-09-18 Thread Zvone
IMO the component should clear LastResponse on before connect. Maybe it should, but what it does is different story :) The following fails also with non-sync version but sync is easier to copy-paste. //-- SyncPop3Cli-Host = put-valid-server-here;