Tickets :: [#3199] messages with bad headers - fallback to iso-8859-1 charset

Summary	messages with bad headers - fallback to iso-8859-1 charset
Queue	IMP
Queue Version	HEAD
Type	Enhancement
State	Rejected
Priority	2. Medium
Owners
Requester	kimmo.liikonen (at) phnet (dot) fi
Created	12/27/2005 (7300 days ago)
Due
Updated	12/27/2005 (7300 days ago)
Assigned
Resolved	12/27/2005 (7300 days ago)
Milestone
Patch	No

12/27/2005 01:29:59 PM	Jan Schneider	Comment #2 State ⇒ Rejected	Reply to this comment
Closing this, because it is a duplicate of ~~request 2702~~. But I added a bounty for that feature that should show up on the website within an hour. Please use the bounty pages to sponsor this bounty.

12/27/2005 01:16:07 PM	kimmo (dot) liikonen (at) phnet (dot) fi	Comment #1 State ⇒ New Priority ⇒ 2. Medium Type ⇒ Enhancement Summary ⇒ messages with bad headers - fallback to iso-8859-1 charset Queue ⇒ IMP	Reply to this comment
In earlier versions of IMP (3.x) if message had bad headers (missing mime-version or content-type or content-transfer-encoding) IMP did fallback to iso-8859-1 charset (at least when language was selected as finnish). Nowdays in IMP version 4.0 and newer if message has bad headers, IMP fallbacks to utf-8 (displays message with utf-8 charset). At least in our situation 99,9% of broken messages are in iso-8859-1 charset. Is there any way to add configuration option to IMP, for example that it would display broken message in iso-8859-1 charset? (instead of utf-8 charset). Maybe it could detect which charset to fallback from language selection? My company is willing to pay 500$ bounty, if this new feature will be added.