No further useful feedback.

Well, it doesn't happen to any other of the thousands, if not tens of 
thousands installations of IMP 3 around the world. Maybe they both use 
a customized version packaged from a third-party vendor/distributor. 
As noone experienced this in the 4-5 years that IMP 3 is on the 
market, your ISPs have to track it down themselves.

Well, I cannot state on this point, but I repeat that the problem occurs

with *two* distincts providers who us IMP as webmail.



O V H (www dot ovh dot fr) on which you have to pay a very cheap amount

to get a mail account, who use IMP 3.2.6.

I used this version to do most of my tests.



Free (www dot free dot fr) on which you can create a free account,

who uses Imp 3.2.5

===

Subject: accents

MIME-Version: 1.0

Content-Type: text/plain; charset=UTF-8

Content-Transfer-Encoding: 8bit

User-Agent: Internet Messaging Program (IMP) 3.2.5

===



I don't know the Horde project/community, but what is the probability

that they use the same "mess" that leads exactly to the same

reproductible problem ?



and why does it only appear with mozilla and not IE or firefox ?

I cannot tell where the problem is, but there undoubtly is a problem.

I can only explain it with someone having messed with the IMP code.

To be clear as well : only the header contains an utf8 reference.

The body is encoded in latin1, hence the problem.

so how do you explain this behaviour ?

Let's say this clear: IMP 3.2.6 does *not* send messages in UTF-8.

I'm sorry, but I'm not sure of what you mean.

Do you need more information about my test protocol ?

I've just cut and pasted header parts from my two messages.



My recipients cannot easily read my messages written using mozilla.

This doesn't make any sense, because IMP 3.x doesn't have support for 
UTF-8 at all.

When I create a message with accents in mozilla, here is the an 
excerpt of the header :



===

Subject: this message contains accents

MIME-Version: 1.0

Content-Type: text/plain; charset=UTF-8

Content-Transfer-Encoding: 8bit

User-Agent: Internet Messaging Program (IMP) 3.2.6

===



If I do exactly the same thing, but with internet explorer, I get this 
header :



===

Subject: this message contains accents

MIME-Version: 1.0

Content-Type: text/plain; charset=ISO-8859-1

Content-Transfer-Encoding: 8bit

User-Agent: Internet Messaging Program (IMP) 3.2.6

===



Notice that the charset chosen is latin1 for the second message while

it is utf-8 for the first one.



The correct behaviour is internet explorer one.

Mozilla version is latest release 1.7.12.

Internet explorer is 5.5.



I've tested with firefox, and there is no problem with firefox.



So Imp uses the wrong charset with mozilla only, and both two of my ISP

(personnal and work) use an IMP version that leads to this behaviour.