Hi i would like to make clear that this depends of the used mail.jar (javax developed by sun, i think). The version used in james 2.3.2 is a little bit old and does not support all of the properties you mentioned. So not james is ignoring it, the mail.jar simply does not know this properties.
We have the same problem in our project. There is a newer version of mail.jar, but we never tried if the newer version would solve the problems. We are not sure if changing the mail.jar does have other side effects. Currently we solved this in own code. I am currently offline, so I have to use my own 'memory'. I think the version used is 1.4.1, and actual is 1.4.3, but that may be wrong. You need to check which property has come after 1.4.1 (since ...). Or look at the source of the classes in mail.jar. You could try to simply replace the mail.jar with a newer version. I do not know if james3 has fixed that, but it is newer, so it will be better. Greetings from holidays, Bernd -------- Ursprüngliche Nachricht -------- Von: Moshe Akirav <[email protected]> Datum: An: James Users List <[email protected]> Betreff: RE: James 2 Emails with Attachments and Missing Start Boundary Error Hi, Did anyone find a solution for that ? Thanks in advanced, Moshe. -----Original Message----- From: Barry Lai [mailto:[email protected]] 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 [cid:imp_0.4304146392369115_Image_01]
smime.p7s
Description: S/MIME Cryptographic Signature
