🚀 go-pugleaf

"Hans Galema" <notused@notused.nl> wrote in message
news:4514ff01@newsgroups.borland.com...

> -text+(html+graphic) I cannot handle this like it should.

Indy 9 has never been able to support that particular format.  Indy 9's MIME
capabilities are very limited.  It simply canot handle the more complex MIME
hierarchies that are being used nowadays.  You will have to continue using
"text+html+attachment" instead, or format the nested MIME manually, or else
upgrade to Indy 10.

> As there are two Content-Type's I wonder how I should tell
> that to TIdMessage.

The only way to do that with Indy 9 is to put the entire "multipart/reated"
block into a text attachment.   You will not be able to create such a
message using individual message parts alone.  For example:

    IdMessage1->Subject = "indy text+(html+graphic)"
    IdMessage1->ContentType = "multipart/alternative";

    TIdText *pText = new TIdText(IdMessage1->MessageParts, NULL);
    pText->ContentType = "text/plain"; charset=us-ascii; format=flowed";
    pText->ContentTransfer = "7bit";
    pText->Body->Texzt = "Hello you. Here a picture:";

    pText = new TIdText(IdMessage1->MessageParts, NULL);
    pText->Content-Type = "multipart/related;
boundary=\"------------myboundary\"";
    pText->Body->Text = "the entire multipart/related content goes here";

> If I send it to mij gmail.com account the message is received.
> If I send it to the account at my provider the message is not
> received. No exceptions thrown and the .eml produced.

If Send() returns without throwing an exception, then the provider has
accepted the message and is then responsible for delivering it.  There is
nothing Indy can do to help the provider once Send() has been called.  If
the provider cannot deliver the message, then it will send an error email to
the return address of the message explaining why the message could not be
delivered.


Gambit

Remy Lebeau (TeamB) wrote:
>>-text+(html+graphic) I cannot handle this like it should.
> 
> Indy 9 has never been able to support that particular format. 

But as said: It (mostly) sends a message that is interpreted
by thunderbird and OE as intended.

> .. or else
> upgrade to Indy 10.

As you will know that is currently not supported for C++Builder.
But following your advise I tried the IDE to grab Indy10
instead of Indy9 and did the following:

Menu Tools | Options | Environment Options | C++ Options | Paths and Directories
SearchPath (choose one):
$(BDS)\Include\Indy9;$(BDS)\Lib\Indy9
$(BDS)\Include\Indy10;$(BDS)\Lib\Indy10

Browsing Path(choose one):
$(BDS)\source\Win32\Indy9
$(BDS)\source\Indy10

But having applied these changes then from IdWinSock2.hpp
there is the warning:
//-- user supplied -----------------------------------------------------------
#error Indy 10 does not currently support C++Builder

Q.E.D.

>>As there are two Content-Type's I wonder how I should tell
>>that to TIdMessage.
>  
> The only way to do that with Indy 9 is to put the entire "multipart/reated"
> block into a text attachment.   You will not be able to create such a
> message using individual message parts alone.  For example:

OK. Thanks for the example.

> If Send() returns without throwing an exception, then the provider has
> accepted the message and is then responsible for delivering it.  There is
> nothing Indy can do to help the provider once Send() has been called.

OK. That is fair.

>  If
> the provider cannot deliver the message, then it will send an error email to
> the return address of the message explaining why the message could not be
> delivered.

But it does not here in the case I described.

Hans.