View Issue Details

IDProjectCategoryView StatusLast Update
0010479mantisbtemailpublic2010-04-23 23:22
Reportermichauko Assigned Tovboctor  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
OSDebianOS VersionStable 5.0 Lenny 
Product Version1.1.6 
Summary0010479: charset missing in some "Content-Type" email headers
Description

Hi,

I'm running Mantis 1.1.6 (the one packaged in Debian "stable"), MySQL 5.0.51, apache 2.2.9, PHP 5.2.6
OS has UTF-8 locales configured
I tried the following with all "$g_phpMailer_method" possible values (0, 1, 2): same thing happens - just in case

  • Symptom:
    French e-mails (both custom strings and user content) are badly encoded, thus, the following are not correctly displayed: é à ç ç â and so on

  • some e-mails are built with:
    Content-Type: text/plain; charset="utf-8"
    example : When you send a reminder

  • some with :
    Content-Type: text/plain; charset=""
    example : when you assign an issue to someone

  • How I temporarily fixed it:
    I located in core/email_api.php, line 766:
    $mail->CharSet = $t_email_data->metadata['charset'];
    it must be empty sometimes

I forced it to:
$mail->CharSet = 'utf-8';

  • A better solution ?
  • Is it still happening in later releases ?
  • What's the right fix in 1.1.6? (because hardcoding it the way I did is dirty I guess)
Steps To Reproduce

Send an e-mail (assign an issue ; sending an alarm works) to a french account, there is an encoding issue. Thus, you have this:

Le bogue suivant a été assigné.
[...]
http://blah...
[...]
Catégorie: demande d'évolution

TagsNo tags attached.

Activities

michauko

michauko

2009-05-11 09:03

reporter   ~0021803

Everything is correcly stored at DB level (tables are latin1_swedish_ci ; the default, I didn't change anything)

michauko

michauko

2009-05-11 10:48

reporter   ~0021805

working fine on a fresh &.1.7 tar.gz installation
on the same server

bug in 1.1.6 ? something in the debian pkg ?

dhx

dhx

2009-08-18 20:55

reporter   ~0022754

This should already be fixed in 1.2.x but there aren't any plans to backport it (as it isn't a critical security fix).

michauko

michauko

2009-08-24 03:28

reporter   ~0022802

I understand.
I guess this issue can be closed, then.
Maybe Google will find this and help some Debian users with the old 1.1.6.

Regards