🚀 go-pugleaf

Hi,

I thought a code sample might help...

[code]
                IdMessage1->Body->Text = Memo2->Lines->Text;
                int error;
                AnsiString ErrMsg;
                try
                        {
    	                IdSMTP1->Send(IdMessage1);
                        }
                catch(EIdProtocolReplyError &E)
                        {
                        error = E.ReplyErrorCode;
                        ErrMsg = E.Message;
                        Memo3->Lines->Append(ErrMsg);
                        Memo3->Lines->Append("");
                        }
                catch(EIdConnClosedGracefully &E)
                        {
                        Memo3->Lines->Append(E.Message);
                        Memo3->Lines->Append("");
                        }
                catch(EFOpenError &E)
                        {
                        Memo3->Lines->Append(E.Message);
                        Memo3->Lines->Append("");
                        }
                catch(...)
                        {
                        Memo3->Lines->Append("Unidentified error!");
                        Memo3->Lines->Append("");
                        }
[/code]

Hope this helps...
Bud

"Bud Manz" <amanz@northweststate.edu> wrote:
>
>Ok, Thanks!
>
>I did finally get past that, but now when I finally get to the IdSMTP1->Send(IdMessage1); instruction, the program blows up with an error message that says "...raised exception class EIdProtocolReplyError with message '250 2.1.5 <amanz@northweststate.edu>... Recipient ok'. Process stopped. Use Step or Run to continue.".
>
>Can you (or anyone) help me with this?
>
>Thanks in advance,
>Bud
>
>"Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote:
>>
>>"Bud Manz" <amanz@northweststate.edu> wrote in message
>>news:42e6bf3e$1@newsgroups.borland.com...
>>
>>> If my understanding is correct, the try block will "try" a
>>> block of instruction(s) and return an error code to the catch
>>> block upon completion.
>>
>>No, that is not how exceptions work.  Your understanding is not correct.
>>When an exception is thrown, the code in the try block is not run to
>>completion.  Code execution immediately jumps from the place the exception
>>is thrown to the nearest catch block that knows how to handle the exception.
>>If there is no catch block that can handle the exception, or if a catch
>>block re-throws the exception, then the exception travels up the call stack
>>until the next suitable catch block is found, and so on, until either the
>>exception is finally handled and discarded, or until the exception reaches
>>the system's main exception handler, which usually terminates the process
>>immediately.
>>
>>
>>Gambit
>>
>>
>