Tickets :: [#3804] Default charset not being used

6.0.0-beta1

11/9/25

Summary	Default charset not being used
Queue	IMP
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	2. Medium
Owners	slusarz (at) horde (dot) org
Requester	jan (at) horde (dot) org
Created	04/20/2006 (7143 days ago)
Due
Updated	05/04/2006 (7129 days ago)
Assigned	04/20/2006 (7143 days ago)
Resolved	05/04/2006 (7129 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

05/04/2006 06:05:47 PM	Michael Slusarz	Deleted Original Message

05/04/2006 06:04:46 PM	Michael Slusarz	Comment #4 State ⇒ Resolved Priority ⇒ 2. Medium	Reply to this comment
Looks like an issue where c-client was automatically adding a 'charset = us-ascii' parameter for all non-MIME messages, even though that parameter didn't exist in the original headers. This has been fixed in HEAD and Horde 3.1.2.

04/20/2006 10:51:40 PM	Jan Schneider	Comment #3 New Attachment: Newsletter-Service.eml	Reply to this comment
I thought this bug had been fixed in Whups...

04/20/2006 10:07:18 PM	Michael Slusarz	Comment #2	Reply to this comment
For some reason, the attached message is still not properly rendered if I set the default charset to iso-8859-1. .... probably because there is no message :)

04/20/2006 09:16:34 PM	Jan Schneider	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Default charset not being used Queue ⇒ IMP Assigned to Michael Slusarz State ⇒ Assigned	Reply to this comment
For some reason, the attached message is still not properly rendered if I set the default charset to iso-8859-1.