You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Barry Lai <bl...@getabine.com> on 2014/03/05 16:14:23 UTC
James 2 Emails with Attachments and Missing Start Boundary Error
I'm receiving some emails with attachments that seem to be malformed and
throw:
javax.mail.MessagingException: Missing start boundary
at javax.mail.internet.MimeMultipart.parsebm(MimeMultipart.java:713)
In an attempt to be more lenient with missing start boundary, we have tried
the following system properties via PHOENIX_JVM_OPTS as well as using
System.setProperty() to IGNORE these errors but JAMES seems to ignore them:
export PHOENIX_JVM_OPTS="-Dmail.mime.parameters.strict=false
-Dmail.mime.allowencodedmessage=true
-Dmail.mime.decodetext.strict=false
-Dmail.mime.multipart.ignoremissingendboundary=true
-Dmail.mime.multipart.ignoremissingboundaryparameter=true
-Dmail.mime.ignoreunknownencoding=true
-Dmail.mime.multipart.ignoreexistingboundaryparameter=true
-Dmail.mime.multipart.ignorewhitespacelines=true
-Dmail.mime.decodeparameters.strict=false
-Dmail.mime.encodeparameters.strict=false"
Anyone encounter this issue? Does James 3 behave better here?
-
Barry Lai
Software Engineer, Abine
RE: James 2 Emails with Attachments and Missing Start Boundary
Error
Posted by Moshe Akirav <mo...@impactia.com>.
Hi,
Did anyone find a solution for that ?
Thanks in advanced,
Moshe.
-----Original Message-----
From: Barry Lai [mailto:blai@getabine.com]
Sent: Wednesday, March 05, 2014 17:14 PM
To: James Users List
Subject: James 2 Emails with Attachments and Missing Start Boundary Error
I'm receiving some emails with attachments that seem to be malformed and
throw:
javax.mail.MessagingException: Missing start boundary
at javax.mail.internet.MimeMultipart.parsebm(MimeMultipart.java:713)
In an attempt to be more lenient with missing start boundary, we have tried the following system properties via PHOENIX_JVM_OPTS as well as using
System.setProperty() to IGNORE these errors but JAMES seems to ignore them:
export PHOENIX_JVM_OPTS="-Dmail.mime.parameters.strict=false
-Dmail.mime.allowencodedmessage=true
-Dmail.mime.decodetext.strict=false
-Dmail.mime.multipart.ignoremissingendboundary=true
-Dmail.mime.multipart.ignoremissingboundaryparameter=true
-Dmail.mime.ignoreunknownencoding=true
-Dmail.mime.multipart.ignoreexistingboundaryparameter=true
-Dmail.mime.multipart.ignorewhitespacelines=true
-Dmail.mime.decodeparameters.strict=false
-Dmail.mime.encodeparameters.strict=false"
Anyone encounter this issue? Does James 3 behave better here?
-
Barry Lai
Software Engineer, Abine