Bahman wrote:
>
> Hi all!
>
> As requested I have more info regarding the error message.
>
> ERROR
> ===================
> exception! javax.mail.MessagingException: Could not read message;
>   nested exception is:
>         java.io.UnsupportedEncodingException: %CHARSET
> exception! javax.mail.MessagingException: Could not read message;
>   nested exception is:
>         java.io.UnsupportedEncodingException: %CHARSET
> JVM exiting abnormally. Shutting down Phoenix.

Is that really all there was? Do you see anything more expansive in the logs
([root]/apps/james/logs)?

Seeing 'java.io.UnsupportedEncodingException: %CHARSET' reported suggests
the mail is incorrectly formed. I would expect to see something like
'java.io.UnsupportedEncodingException: unicode-1-1-utf-7' which is at least
a valid character set, though unsupported by JavaMail.

If you have access to the problem email, you can examine the source and
confirm that '%CHARSET' is present, and that this diagnosis is correct.

James should be more graceful in handling such exceptions rather than simply
exiting. If memory serves me well this is addressed for the forthcoming
release.

Can anyone closer to the action confirm this?

-- Steve


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to