> > What I can see is that it sends with charset=US-ASCII, even if the characters are
> > non-US.
> 
> That's the key point. I changed it such that elog uses now the charset defined in the
> configuration file, now it should work fine. Can you give it a try? The new version is
> under CVS.

Tried it now, using the same charset I get when sending email from Mutt: (this is right)
Subject: Testing =?iso-8859-1?B?+Obl?=
To: michael.husbyn@.........
Message-id: <20050415125415.GA30539@njord........>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: QUOTED-PRINTABLE
Content-disposition: inline
User-Agent: Mutt/1.4.1i

When sending from Elog with the same subject (from the same server):
Subject: IKT sak =?UNKNOWN?B?KDExMCk6?= Testing =?UNKNOWN?B?+Obl?=
To: Michael.Husbyn@............
Message-id: <200504151304.j3FD4aKP006491@njord..................>
MIME-version: 1.0
X-Mailer: Elog, Version 2.5.8-3
Content-type: TEXT/PLAIN; charset=iso-8859-1
Content-transfer-encoding: QUOTED-PRINTABLE
X-Elog-URL: http://njord................:8090/ikt/110
X-Elog-submit-type: web|elog


--

So the subject needs some change. In my example I left out what Elog inserts before
the subject I put in Elog.

Just for the fun, changed my old subject (in elog) to the one Mutt formatted it to:
Testing =?iso-8859-1?B?+Obl?=

And then I get what I want... ;)


Best regards
Michael Husbyn

So you tell me that the message body is ok with Norwegian characters, it's only the subject?
That would mean that outlook interpretes the charset only for the message body, but not for
the subject. So if you have characters with an ASCII value greater than 127, your mail
program requires to enclose it into

=?<charset>?B?+<text>?=

Do you know that the "B" is for? I would not like to "blindly" do whatever Mutt does, I
would like to understand it. If someone can point me to a document which describes this
properly, I could implement it.

Ok, I found it. It's in RFC2047 at

http://www.faqs.org/rfcs/rfc2047.html

I will try to implement it.

I implemented this, but found some problems. If I encode the subject like

Subject: =?ISO-8859-1?Q?ורז?=

it displays well unde MS Outlook, but not under Mozilla Thunderbird or pine,
which both display the full text (including the ISO...). So it looks like
there is no single solution which satisfies all mail programs. It should at
least work for Outlook and Thunderbird, so if anyone has an idea please let me
know.

> Subject: Testing ורז
> 
> Becomes
> Subject: IKT sak =?UNKNOWN?B?KDYwKTo=?= Testing =?UNKNOWN?B?5fjm?=
> 
> config:
> Use Email Subject = IKT sak ($message id): $Tittel

You could put the encoding there manually:

Use Email Subject = =?ISO-8859-1?Q?IKT sak ($message id): $Tittel?=

would this work?

> I implemented this, but found some problems. If I encode the subject like
> 
> Subject: =?ISO-8859-1?Q?ורז?=
> 
> it displays well unde MS Outlook, but not under Mozilla Thunderbird or pine,
> which both display the full text (including the ISO...). So it looks like
> there is no single solution which satisfies all mail programs. It should at
> least work for Outlook and Thunderbird, so if anyone has an idea please let me
> know.

If I read the RFC correctly when you use B encoding you are using BASE64 encoding.
Maybe that could be a solution?

Best regards
Michael

> If I read the RFC correctly when you use B encoding you are using BASE64 encoding.
> Maybe that could be a solution?

Indeed it is. Works for all email programs I know. So I added that to elog, new
version is committed to CVS. Let me know if it works for you.

> > If I read the RFC correctly when you use B encoding you are using BASE64 encoding.
> > Maybe that could be a solution?
> 
> Indeed it is. Works for all email programs I know. So I added that to elog, new
> version is committed to CVS. Let me know if it works for you.


Stefan! You are *THE MAN* :)

It works :)

You are indeed "speedy gonzales" ;)

Thank you very much!


Best regards
Michael 'very impressed' Husbyn