🚀 go-pugleaf

Thanks for your reply, I am using the Indy component (V6 I think) that 
ships with BCB6.  I also realize that that is probably the problem.  I 
am going to install Indy 9 and see what happens.

Bud

Remy Lebeau (TeamB) wrote:
> "Bud Manz" <amanz@northweststate.edu> wrote in message
> news:43171e80$1@newsgroups.borland.com...
> 
> 
>>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.".
> 
> 
> You did not specify which version of Indy you are using.  Offhand, you
> should NOT be getting that exception at all.  The only way an
> EIdProtocolReplyError can be thrown is if the server sends back a reply code
> that is different than what TIdSMTP expects.  However, reply code 250 is a
> valid reply code when specifying the recipients for a message.
> 
> You need to provide more details.  Please attach one of the TIdLog...
> components to TIdSMTP, or use an external packet sniffer such as Ethereal
> (http://www.ethereal.com), to see what the actual SMTP commands and replies
> look like.
> 
> 
> Gambit
> 
>