Actually, I tried that as well. I know, I should have mentioned that...
Attempted with:
--enable-unicode by itself
And
--enable-unicode with the
%define xflags set to --enable-unicode=utf-8,iso-2022-jp,iso-8859-1
Neither attempt resolved the issue.
From: Sam Varshavchik <mrs...@courier-mta.com>
Date: Fri, 26 Jan 2007 18:55:57 -0500
To: <cour...@lists.sourceforge.net>
Subject: Re: [courier-users] Issue with webmail utf-8/iso-2202-jp display
Jason Benguerel writes:
I just did a major server upgrade and moved my mail services to a new
machine. I'm using courier-0.54.2 built via the rpmbuild mechanism with
--disable-autorenamesent and with_fax 0 as the only modifications to the
spec file. The issue is that webmail doesn't seem to want to correctly
display my ISO-2022-JP mail anymore. It is serving it with the Content-Type:
If that's the only non-default option you used, then sqwebmail simply does
not know anything about iso-2022-jp. By default, only utf-8 and iso-8859-1
character maps get compiled in.
Recompile with the --enable-unicode option.
6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Issue with webmai...
