"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:474b5952@newsgroups.borland.com...
> That is not what I meant. I wanted to see the raw email data that
> TIdMessage generates, not the code that sets it up.
That IS necesary to see that I'm not messing out with my code. Imagine that
I am doing Mess.Subject:= '=?ISO-1225?Q?'+somestring+'?='; or some other
incorrect code. That's why it's important to speak clearly. The important
raw message code comes later... like NOW:
>> The subject OTOH looks rawly like:
>>
>> ?utf-8?B?w5HCi8OQwrLDkMK6w5HCi8OQwrA=?=
>
> That is perfectly normal and valid.
It seems so. But it doesn't
> You did not show what your original string was to begin with. If it
Can't do that so easily. Is a test string with russian, greek and swedish
text for testing purposes. If it is so important to the case, the
UTF8encoded AND Base64 encode (for Usenet safe transmition is)
0YvQstC60YvQsCBzZGZzZGZzZGYgICDOus6+zrPOv86zzr7Ou866zrPOuw==
> You never said which version of Indy you are actually using. Older
> versions did not support UTF-8 at all. Recent snapshots of Indy 10 do,
> and will automatically encode Ansi and MBCS strings.
>
OK, that's why I questiones in the other message. As always using the last
snapshot. So the string IS encoded anyway. That's explain a lot. The subject
is getting DOUBLE encoded. And that's exlpain that the only was to do what I
want is, unfortunatly, setting NoEncode to true and doing the whole work by
myself, including the attachment encodings, as far as I know....
Unfortunatly, setting NoEncode to true means that all the work and
especially multipart messages must be done manually by the user....
AFAIK....
