🚀 go-pugleaf

Thanks for replying.

I commented the lines that were causing the problems in those two hpp files 
and it compiled.  then,  I wrote a quick app to send an email and it worked. 
I just need to send emails using an SMTP server and I was having problems to 
authenticate using Indy9.  I read that IdSMTP for Indy 10 incorporates more 
authentication mechanisms and I want to give it a try.

Do you think I could include those structures in the header for BCB5?

Are there good chances Indy10 works fine in BCB5?

JLo
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4679755d$1@newsgroups.borland.com...
>
> "JLoz" <jfsierra@excite.com> wrote in message
> news:46797172$2@newsgroups.borland.com...
>
>> 9) The linker gives me 4 errors as follows:
>
> Those are compiler errors, not linker errors.
>
>>      *   [C++ Error] IdWinSock2.hpp(154): E2257 , expected
>>           The line is 154:    typedef SOCKADDR_STORAGE
> TSockAddrStorage;
>>      *   [C++ Error] IdWinSock2.hpp(154): E2257 , expected
>>           The line is 248:    typedef WSAMSG  TWSAMSG;
>>      *   [C++ Error] IdWinSock2.hpp(154): E2257 , expected
>>           The line is 250:    typedef WSACMSGHDR  TWSACMsgHdr;
>>      *  [C++ Error] IdWship6.hpp(22): E2257 , expected
>>          The line is 22:  typedef IPV6_MREQ  TIPv6_MReq;
>
> Those structures are not defined in BCB 5.  They were not included in
> the API header files until BCB 6.
>
>> I also saw a comment of yours in another thread where you
>> say that Indy10 had not been tested for BCB5 (as of  2/26/07)
>
> It still isn't, and I don't expect it to be anything soon.  I just
> don't have any time for it anymore.
>
>> unfortunately using BCB6 is not an option for me and I need to
>> used the new features for idSMTP.
>
> What features do you need exactly?
>
>
> Gambit
>
>