FiveTech Software tech support forums

... ) } oOutMail:bConnected := { || oWndMdi:SetMsg( "Connected" ) } oOutMail:bDone := { || oWndMdi:SetMsg( "Message sent successfully" ) } oOutMail:bFailure := { || oOutMail:nStatus := 7 } oOutMail:SendMail( cFROM,; // From { cTO },; //, cPMOEMAIL, cSPOEMAIL },; // To cMESSAGE,; // Msg Text cSUBJECT,; ...

... ) } oOutMail:bConnected := { || oWndMdi:SetMsg( "Connected" ) } oOutMail:bDone := { || oWndMdi:SetMsg( "Message sent successfully" ) } oOutMail:bFailure := { || oOutMail:nStatus := 7 } oOutMail:SendMail( cFROM,; // From { cTO },; //, cPMOEMAIL, cSPOEMAIL },; // To cMESSAGE,; // Msg Text cSUBJECT,; ...

... * Mejora: En el método Failure() de la clase TSmtp. Los parámetros oSocket, nWSAError y cReply son proporcionados ahora cuando se evalua ::bFailure desde la función Failure(). * Nuevo: Un nuevo e interesante ejemplo samples\Signatur.prg que muestra como capturar una firma desde tus aplicaciones. ...

Yury,

thanks for your input, but it still doesnt work here
When no authentification is required, there are no problems and the blocks bConnected and bDone are evaluated. But with authentification, they both aren't evaluated, but also bFailure doesn't "show up"...

... the filter expression. Now it is ok. * Enhancement: Class TSmtp Method Failure(). Parameters oSocket, nWSAError, cReply are supplied now when ::bFailure is evaluated from Failure(). * New: A very interesting new example in samples\Signatur.prg that shows how to capture a signature from your ...

Rick, Please change bFailure this way: oOutMail:bFailure := { | oSocket, nError, cReply | LogFile( "log.txt", { nError, "--", cReply, ProcName( 2 ) } ), oOutMail:nStatus ...

Rick, James, Class TSmtp Method Failure() should be modified as it receives three parameters: oSocket, nWSAError, cReply but when the bFailure codeblock is evaluated from inside it, these parameters are not supplied to the codeblock. This is the proposed change: If ::bFailure != nil ...

Rick, took your suggestion and I must have some syntactical error where 7 is ST_QUIT Your suggestion : oOutMail:bFailure := { || LogFile( "mail.log", {oOutMail:aTo:[1] + " Failed"}), oOutMail:nStatus := ST_QUIT } Trying to get it to work .. unfortunitly the LogFile fires everytime ...

... to do what you suggest ... James .. I took your suggestion and I must have some syntactical error where 7 is ST_QUIT Your suggestion : oOutMail:bFailure := { || LogFile( "mail.log", {oOutMail:aTo:[1] + " Failed"}), oOutMail:nStatus := ST_QUIT } Trying to get it to work .. unfortunitly the LogFile ...

Rick,

Try something like this:

oOutMail:bFailure := { || LogFile( "mail.log", {oOutMail:aTo:[1] + " Failed"}), oOutMail:nStatus := ST_QUIT }

Regards,
James

Antonio oOutMail:bFailure := { || oOutMail:nStatus := 7 } is what I inserted .. st_quit was defined in tsmpt as 7 and I got a run time of this ( unfortunitly ) :( Rick Application =========== Path and name: C:\FOX\PMOSQL\PmoW32.Exe ...

Antonio

Please forgive my ignorance .. where do you want me to place this ??

Rick,

Please try this:

oOutMail:bFailure := { || oOutMail:nStatus := ST_QUIT }
_________________
regards, saludos

Antonio Linares
www.fivetechsoft.com

Rick,

Please try this:

oOutMail:bFailure := { || oOutMail:nStatus := ST_QUIT }

... .. Antonio is on the right track in that I can not check the internals of SMTP, however, when you look at the tsntp class .. you will see DATA bFailure AS CODEBLOCK INIT NIL and ::bFailure is evaluared in method METHOD Failure( oSocket, nWSAError, cReply ) CLASS TSmtp and it looks like my error ...