JavaMail Fails batch on bad email / RSA® IdentityGovernanceandLifecycle

This product (RSA® Identity Governance and Lifecycle ) appears to be using JavaMail.

We send emails out in the smallest batch size the software will allow us to set (25)

In the log file capture below, I have edited the email address so as to not leak information.

When it rejects one such recipient, the exception generated by JavaMail kills of the entire sending process. I consider the fact that the sending thread doesn’t catch the exception to be a bad design on RSA’s side.

Our mta. .org (mail transfer agent) actually requires that all email requests sent to it have valid email addresses.

, insertTime=2016-10-30 13:24:16.492905, completedTime=null, processAction='null'}

1. com.sun.mail.smtp.SMTPSendFailedException: 250 2.0.0 u9UKXxDe013634 Message accepted for delivery

;

nested exception is:

com.sun.mail.smtp.SMTPAddressFailedException: 550 5.0.0 <someone@ .org >... User unknown

at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:598)

at com.aveksa.server.email.EmailClient.sendEmail(EmailClient.java:238)

at com.aveksa.server.email.sender.EmailSenderServiceProvider.processMessage(EmailSenderServiceProvider.java:290)

at com.aveksa.server.email.sender.EmailSenderServiceProvider.processMessageBatch(EmailSenderServiceProvider.java:221)

at com.aveksa.server.email.sender.EmailSenderServiceProvider.processMail(EmailSenderServiceProvider.java:192)

at com.aveksa.server.email.sender.EmailSenderThread.run(EmailSenderThread.java:42)

Caused by: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.0.0 <someone@ .org >... User unknown

If you google com.sun.mail…..550, those are coming from the mail transfer agent (mta. .org) which – it makes sense – is probably required to only accept VALID email addresses.

The other example provided is someone who is recently married, last name changed.

It has been suggested we set up a mail relay agent to gracefully fail - but I don't have the skills required.