🚀 go-pugleaf

Hi Remy,

> That is not what I wanted to see.  Please show the COMPLETE message data,
> including all headers.

I don't think that this is neccessary.

> The ContentType alone has no effect whatsoever on Indy's encoders.  They
> don't care about the ContentType at all.  The value is written to the 
> header
> inside the message data and then ignored for everything else.

That is a good hint. That means, the encoding in Indy should correct, the 
additional bytes are added
from the receiving mailserver (because I was using the wrong ContentType, 
ok).

> For any file, binary or text, you have to use the proper ContentType.  For
> example, .txt files must use "text/plain", .htm files must use 
> "text/html",
> .pdf must use "application/pdf", .zip files must use
> "application/x-zip-compressed", etc.  So unless you know for sure off the
> top of your head what a given file should use, then you should always use
> Indy's GetMIMETypeFromFile() function instead, ie:

That's not bad, but actually, as Hans noted, it does not care about the file 
itself.
And, sometimes I want to send binary files with a .txt extension(why not? If 
it's just for me..).

But I did some tests and all that I really want is to send any attachment 
unchanged (in
a binary mode). So, with "image/jpg" or "application/x-zip-compressed" I 
could send all attachments I tried so far unchanged, and no additional 
bytes.
And, could it be bad to transfer even a plain text attachment in this mode?

By the way, when you put the text message in a text-attachment like that:
    ...
    TIdText *text1 = new TIdText(IdMessage1->MessageParts, NULL);
    text1->Body->Add("Some text...");
    text1->ContentType = "text/plain";
    ...
and not in the IdMessage1->Body, it's not possible to use UUEncoding (Indy 
gives an errormessage that only a simple textmessage plus attachment are 
allowed in UU-mode) .
And, in MIME mode, this text is ignored at the receiving mailserver (or the 
mailclient?), at least
at our company Exchangeserver 2003 and the one from web.de (which is 
according to the MIME
standard as far as I understand). But in the form: text message in the 
messagebody and
other files as attachements, it works also well.


Best regards Robert