Actually, many local nntp servers (Hong Kong) contain non-ascii messages as well and didn't well quote RFC 2047 in header and even have no Content-Type defined (because some bad nntp clients like Outlook express and Outlook express provide a default charset option for reading message -_-!).
e.g. http://put.hk/source/news.3home.net/test/13769.html With mime4j, these kind of messages cannot be well parsed as Message entity provide no way to pass a default charset if the message didn't mention the charset. MIME4j's Message, by default will use US-ASCII to parse message and will have distorted result. Someone has hacked into MIME4j before to workaround this problem: http://sourceforge.net/projects/android-usenet/files/source-release/usenet.git.tar.bz2/download Thanks to your attention. Regards, Ken -- View this message in context: http://old.nabble.com/quoteprintable-message-distorted-tp29317840p29327569.html Sent from the James - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
