WinBatch Tech Support Home

Database Search

If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.

TechHome

Postie

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

kStatusInfo Return Codes

Keywords: 	  kStatusInfo  return codes

Question:

The Help file indicates...

"The kStatusInfo function returns success and error message details about the last function executed before kStatusInfo is called"...."A string containing the descriptive error or success message."

What specifically is returned? I cannot find anything detailing the return codes/string etc. I need to check on "SPECIFIC" success or failure of kGetmail, kSendText, kSendFile, and kDeletePop3.

Answer:

The exact string returned depends on your mail server. kStatusInfo simply passes the text error message received from the mail server to your script.

Each mail server may have different wordings for various messages. However the three initial numbers more or less follow RFC guidelines

The error codes to which you are referring are called DSN's and are fully documented in the RFC associated with the SMTP protocol.

In summary a DSN number represents a three digit code returned by the SMTP server to which you are sending commands to.

A DSN beginning with 2 as in 220 indicates the last command sent to the SMTP server was 'successful'.

A DSN number beginning with a '4' as in 451 indicates that the last command sent to the SMTP server was a temporary failure.

A DSN number beginning with a '5' as in 553 indicates that the last command sent to the SMTP server was a permanent failure.

The difference between temporary and permanent failures is that when you receive a temporary failure you should retry sending the message(s) to the SMTP server. If you recieve a permanent failure, you should not retry sending the message(s) to the SMTP server.

For further information on the SMTP protocol and the DSN numbers associated please refer to RFC 2821 and RFC 2822.

http://www.faqs.org/rfcs/rfc2821.html

http://www.faqs.org/rfcs/rfc2822.html


Article ID:   W15067
File Created: 2017:07:28:13:58:36
Last Updated: 2006:03:29:08:36:44