The error information will be available in the <@ERRORS></@ERRORS> block. The mail action does not - to my knowledge - assign anything into @@request$resultset.
Recent builds of the 5.5 server are now aware of a number of email server error responses, as per this chart: eCanNotConnectToServer = -321 eNoFromAddress = -322 eHighASCIIinMessage = -323 eFailInCommunication = -324 eNoToAddress = -325 eBadFromAddress = -326 eUnexpectedError = -327 eNoAttachPath = -328 eCHeaderTooBig = -329 eBadToAddress = -330 I'm not too sure how much of this has been documented, and only the latest version(s) of the server report these properly. I currently capture the -330 error in an email queuing program that I have. I can then search for these errors and retrieve the email address that caused them and from that either correct it, or contact the user. Another good use of these errors is the -321. If you were to say restart your email server, Witango will throw this error and your email will not be sent. If you check for this error, you can code you application to try to send the email again at a later time, once the email server is responding again. Robert -----Original Message----- From: Peter Fogg [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 25, 2005 4:01 PM To: [email protected] Subject: Re: Witango-Talk: e-mail acton error It seems that as soon as I post a question I find the answer! This is the code that I put in the errorHTML of the e-mail acton: @@resultset <@ASSIGN NAME="error" VALUE="1" SCOPE="Request"> <@CLEARERRORS> @@Request$error The "1" appears but not the contents of the resultset. ???? > Peter, > > The @clearerrors trick is great to move on if there is an error (I do > that a lot with mailing out to a list of users), but if you want to > capture the errors try putting a @@resultset tag in the error-results- > html of the mail action (highlight the mail action and click on the > '?' icon next to the results/no results icons for that action) > > That should give you the error info you're looking for, I think. > > Jason > > ----- > > Jason Pamental > Director of Web Services > North Sails > > Office: 401.643.1415 > Fax: 401.643.1420 > Mobile: 401.743.4406 > Email: [EMAIL PROTECTED] > > > On Oct 25, 2005, at 1:31 PM, Peter Fogg wrote: > >> My apology in advance if this topic has been covered in witango-talk >> before, I have been unable to find it in the list. >> >> If I try to send an e-mail to a bogus e-mail address, I get the >> following >> server error message: >> >> . >> . >> . >> File: testEmailA.taf >> Position: send_email_to_bogus_email_addr >> Class: Internal >> Main Error Number: -330 >> . >> . >> . >> >> I have been unable to capture the e-mail action resultset in order to >> parse it for the error code. How do I do trap this error? >> >> Thanks for your help. >> >> Peter - >> >> ______________________________________________________________________ >> __ >> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> >> Visit us at http://www.northsails.com >> >> [This E-mail scanned for viruses by Declude Virus] >> >> >> > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
