Problem with special chars in template

Gateway
1

Hello

we try to use special chars (german Umlaute) in the notification
templates for encryption. Our template looks like this :

···

From: <${from!""}>
<#if to??>
To: <#list to as recipient><${recipient}><#if recipient_has_next>,
</#if></#list>
</#if>
<#if replyTo??>
Reply-To: <${replyTo}>
</#if>
Subject: Ihre e-Mail wurde korrekt verschluesselt!
In-Reply-To: ${(mail.message.messageID)!""}
Auto-Submitted: auto-generated
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Die e-Mail mit dem Betreff "${qp(subject!"")}" wurde wie angefordert
verschlüsselt und digital signiert an den/die Empfänger "<#list
mail.recipients as recipient> ${qp(recipient)} </#list>" verschickt.
Damit ist sichergestellt das der Inhalt der e-Mail von Dritten weder
gelesen noch verändert werden kann.

<#if body??>

${body}

</#if>

But the result is something like this :

Subject: Ihre e-Mail wurde korrekt verschluesselt!
In-Reply-To: <4B73E2B7.3030300(a)kwsoft.de>
Auto-Submitted: auto-generated
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Message-ID: <1304234679.395.1265885877916.JavaMail.djigzo(a)mailer.hq.kwsoft.de>
Date: Thu, 11 Feb 2010 11:57:57 +0100 (CET)

Die e-Mail mit dem Betreff "asasffafasf=C3=B6=C3=B6=C3=B6" wurde wie angefo=
rdert verschl?sselt und digital signiert an den/die Empf?nger " xxxxxx
" verschickt. Damit ist sichergestellt das der Inh=
alt der e-Mail von Dritten weder gelesen noch ver?ndert werden kann.

Note that the subject is encoded, but the special chars in the text
are not. Any comment how to get it working?

Many Thanks

Andreas

2

The templates by default now uses a quoted-printable
Content-Transfer-Encoding. That means that all non-ascii characters
should be quoted-printable.

There are two solutions.

1) make sure that all non-ascii chars are quoted printable

the following command encodes the text as quoted-printable
${qp("verschlüsselt")}

Instead of doing the conversion every time you can write ü (and other
non-ascii characters) directly in quoted-printable form (send the
message and look at the source how ü is written in QP form)

2) make the template completely 8bit. You should remove all the ${qp()}
lines.

I think 1 is better because not all email servers do support 8bit
correctly (one Djigzo user has problems with an Exchange server and
8bit).

Martijn

···

On Thu, 2010-02-11 at 12:04 +0100, lst_hoe02(a)kwsoft.de wrote:

_______________________________________________
Users mailing list
Users(a)lists.djigzo.com
http://lists.djigzo.com/lists/listinfo/users
email message attachment (attached message.eml)
> -------- Forwarded Message --------
>

3

Zitat von Martijn Brinkers <martijn(a)djigzo.com>:

The templates by default now uses a quoted-printable
Content-Transfer-Encoding. That means that all non-ascii characters
should be quoted-printable.

There are two solutions.

1) make sure that all non-ascii chars are quoted printable

the following command encodes the text as quoted-printable
${qp("verschlüsselt")}

Ah, i wondered how the encoding could be set. Works fine, thanks!

Andreas