Angus Robertson - Magenta Systems Ltd wrote:
> The headers may have different charset to the content, indeed they are
> usually ASCII. Never use the body charset to decode the headers.
OK, I see. I guess I have all necessary parts together now. Thanks!
Regards,
Tobias
--
To unsubscribe or chang
Tobias Rapp wrote:
> Thanks Arno for the help.
>
> Would it also work if I would set Allow8BitChars to TRUE, Charset to
> "UTF-8" and manually encode all string properties like "HdrTo",
> "HdrSubject" and "MailMessage.Text" using Utf8Encode()?
Just Utf8Encode() isn't enough. In headers only 7-bit
> Would it also work if I would set Allow8BitChars to TRUE, Charset to
> "UTF-8" and manually encode all string properties like "HdrTo",
> "HdrSubject" and "MailMessage.Text" using Utf8Encode()?
No, the headers contain their charset inline as part of the string, and
are encoded using function HdrE
Thanks Arno for the help.
Would it also work if I would set Allow8BitChars to TRUE, Charset to
"UTF-8" and manually encode all string properties like "HdrTo",
"HdrSubject" and "MailMessage.Text" using Utf8Encode()?
My assumption was that the header lines should not contain non-ASCII
characters, b
Tobias Rapp wrote:
> Hi!
>
> I am currently using the TSmtpCli component to send email
> notifications to users. I want to change the HdrTo property value to
> additionaly contain the user name instead of just the plain email
> address.
>
> As my user name is retrieved from a database as WideStr