On Wed, Nov 4, 2009 at 7:24 PM, dcheckoway <dchecko...@gmail.com> wrote: > > Is there any way to "intercept" the raw mail message content before it gets > passed to the java mail API? I would be happy to manually munge the > Content-Type header if I detect one of the known-to-be-funky charsets in > there. >
You can use a custom MailBinding class, e.g. extending the on in camel-maill. But from the stack trace it appears as if when using getContent() on he Mail API you get that exception. I wonder if you can munge it to remove the charset header etc. A remedy we can build in is to detect in the stacktrace hierachy that is the unsupported charset and then have a kind of invalid message. You can probably not read its content but Camel should be able to move on. That could be a plan b. > > > Claus Ibsen-2 wrote: >> >> On Wed, Nov 4, 2009 at 4:57 PM, dcheckoway <dchecko...@gmail.com> wrote: >> Unfortunately I guess the camel-mail component will pre extract the >> data before its being routed, and thus before the error handling kicks >> in. >> >> And the stacktrace indicates the root problem is deep inside the SUN >> mail jar which makes it hard to fix the unsupported charset. >> >> > > -- > View this message in context: > http://old.nabble.com/Camel-Mail-issue-with-unsupported-charset-tp24755585p26201924.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
