On Jan 17, 2008, at 07:34, [EMAIL PROTECTED] wrote:
it didnt fix the issue, got a pop3 not ready exception today.
Can you post some code so that we know how you tried to fix it?
dZ.
--
DZ-Jay [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
--
To
DZ-Jay wrote:
Can you post some code so that we know how you tried to fix it?
The bug I found is the Special processing for Quit below.
procedure TCustomPop3Cli.TriggerRequestDone(Error: Word);
begin
== (*
{ Special processing for Quit (Roger Morton 24-12-99) }
if FRequestType =
AG It helps alot to post a short message when you either think
AG the problem is resolved or not. Thanks.
it didnt fix the issue, got a pop3 not ready exception today.
AG --
AG Arno Garrels [TeamICS]
AG http://www.overbyte.be/eng/overbyte/teamics.html
i also hope that the bug gets
[EMAIL PROTECTED] wrote:
AG It helps alot to post a short message when you either think
AG the problem is resolved or not. Thanks.
it didnt fix the issue, got a pop3 not ready exception today.
You did not provide any further information, not ready exceptions
may happen, i.e. due to incorrect
hi, i use a custom pop3 component in my program, and frome time to
time i get this errormessage from the server:
-ERR System temporarily unavailable, please try again later.
on the next connect try i get the pop3 component not ready exception,
even if i check for connected:
function
[EMAIL PROTECTED] wrote:
procedure TMailAlert.Pop3ClientRequestDone;
begin
if (FPop.connected) and (CheckError) then begin
FPop.quit;
exit;
end;
...
what could be the cause that the component is not ready after the
error ?
After sending command Quit you should receive a
