javax.mail question - endless loop of email failures

gerber1

Every 5 minutes, I get exactly 10 of the following blocks in the Aware IM Server Output window, which vary only by the email address, and this occurs even during an autodeploy operation that takes about 5 minutes. The first block of these appears before the "Successfully auto-deployed" message:

javax.mail.MessagingException: Missing start boundary

at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
at javax.mail.internet.MimeMultipart.getCount(MimeMultipart.java:158-)
at com.bas.basserver.iopipes.EmailSource.A(Unknown Source)
at com.bas.basserver.iopipes.EmailSource.A(Unknown Source)
at com.bas.basserver.iopipes.EmailSource.A(Unknown Source)
at com.bas.basserver.iopipes.EmailSource.A(Unknown Source)
at com.bas.basserver.iopipes.EmailSource.A(Unknown Source)
at com.bas.basserver.iopipes.EmailSource.A(Unknown Source)
at com.bas.basserver.iopipes.EmailSource$_B.run(Unknown Source)
at java.lang.Thread.run(Thread.java:662)

2011-10-17 18:15:04,258 ERROR -Exception forming notification for e-mail failure notice from MAILER-DAEMON@oproxy5-pub.bluehost.com Missing start boundary E-mail will not be processed

I could use some help identifying where these are coming from and how to get rid of them. They waste cycles and make the transcript unreadable... I assume they are artifacts of the development process from when something went sideways, but the outgoingemail table is empty, and this still occurs, making it look like it is queued up in relation to the java email components.

Thanks in advance.

gerber1

I would add that I use the basic design of the email system from the library application, which has worked fine for several email tasks, but I did not see any of these javax.mail issues until that was implemented.

aware_support

Your application is setup to RECEIVE e-mails from some e-mail account and these messages are coming from this module - for some reason it cannot process the e-mails that are coming to this account. Maybe the protocol you specified is incorrect.