Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
2.3.1
-
None
-
RHE Linux
j2sdk1.4.2_13
Description
We are getting quite a lot of these exceptions on our server:
java.io.IOException: Unknown encoding: 8-bit
at javax.mail.internet.MimePartDataSource.getInputStream(MimePartDataSource.java:106)
at com.sun.mail.handlers.text_plain.getContent(text_plain.java:82)
at javax.activation.DataSourceDataContentHandler.getContent(DataHandler.java:789)
at javax.activation.DataHandler.getContent(DataHandler.java:536)
at javax.mail.internet.MimeMessage.getContent(MimeMessage.java:1380)
at org.apache.james.core.MimeMessageCopyOnWriteProxy.getContent(MimeMessageCopyOnWriteProxy.java:34
3)
at org.apache.james.transport.matchers.AttachmentFileNameIs.matchFound(AttachmentFileNameIs.java:16
2)
at org.apache.james.transport.matchers.AttachmentFileNameIs.match(AttachmentFileNameIs.java:130)
at org.apache.james.transport.LinearProcessor.service(LinearProcessor.java:357)
at org.apache.james.transport.JamesSpoolManager.process(JamesSpoolManager.java:405)
at org.apache.james.transport.JamesSpoolManager.run(JamesSpoolManager.java:309)
at java.lang.Thread.run(Thread.java:534)
We have other matchers/mailets called before AttachmentFileNameIs in our configuration but this is the only place the exception is thrown.
Other mailets probably do not throw exception because they don't need to parse the message.
You just need to take care of the exception based on what you want to do when the mimemessage is invalid:
http://wiki.apache.org/james/HandlingExceptions