311122 - Bugmail does not specify content-type for utf8

Status: RESOLVED FIXED

(Bugzilla :: Email Notifications, defect)

Description

[Joel Peshkin]

Ideally, the content-type should follow trhe UTF-8 setting in defparams.  That
may be tricky considering the newchangedmail parameter.  Most likely, we should
change the default and put a reminder where the UTF-8 selection is controlled.




	joel	Mail clients (includign thunderbird) seem to be very spotty about
displaying the Asian characters properly
	mkanat	joel: Is the Content-Type header correct? And does the viewer have the
right fonts installed?
	joel	The bugmail doesn't have content-type.
	mkanat	joel: Ahh, that'll break it, then.
	joel	What should it be... UTF-8??
	mkanat	joel: It'll need a Content-Type: text/plain;charset=utf-8
	mkanat	joel: Yeah.
	joel	sounds like a bug... that should happen automatically when UTF-8 is selected.
	mkanat	joel: RFC specifies that mails without a content-type are in ISO-8859-1.

Comment 1

[Olav Vitters]

<bkor> is that with 2.21? I have content-type utf-8 there

encode_message in Bugzilla/BugMail.pm does add that header +
Content-Transfer-Encoding, but only if it contains 8bit chars (which is assumed
to be utf8). However, these headers are not enough. On bugzilla.gnome.org we use
the following:

Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

The UTF-8 (caps) didn't work for someone. utf-8 did. Of course
Content-transfer-encoding is correctly handled by encode_message.

Comment 2

[Joel Peshkin]

This works for the content.

It is hard to say how this should be handled.  Should newchangedmail be replaced
with a template?

Comment 3

[Marc Schumann [:Wurblzap]]

MessageToMTA calls encode_message under certain conditions, which does some Content-Type setting (including charset specification) for message parts. Maybe we can teach MessageToMTA to add a correct Content-Type header for all other messages, too, and remove the stuff from templates where they're doing it themselves?

Comment 4

[Max Kanat-Alexander]

bug 353711 will fix this.

Comment 5

[Max Kanat-Alexander]

And it was indeed fixed there, long ago. :-)