SDM 17.1.0.11 Mail Eater Error "javax.mail.internet.AddressException: Local address contains control or whitespace"

[STUART MATTHEWS]

Hi there,

We have one specific sender that SDM 17.1.0.11 mail eater will not log. Other senders hitting this mailbox log without any issues, the error in NX_ROOT\log\maileater_nxd.log is:

2021-12-31 15:13:53:031 ERROR [ForkJoinPool-1-worker-2] c.c.S.m.ConnectSession - [mailbox:ServiceDesk:400002] Error processing email from: server.com:143
javax.mail.internet.AddressException: Local address contains control or whitespace
at javax.mail.internet.InternetAddress.checkAddress(InternetAddress.java:1365)
at javax.mail.internet.InternetAddress.parse(InternetAddress.java:1089)
at javax.mail.internet.InternetAddress.parseHeader(InternetAddress.java:777)
at javax.mail.internet.MimeMessage.getAddressHeader(MimeMessage.java:756)
at javax.mail.internet.MimeMessage.getReplyTo(MimeMessage.java:730)
at com.ca.ServicePlus.maileater.JavaMailParser.parseMessage(JavaMailParser.java:505)
at com.ca.ServicePlus.maileater.ConnectSession.getAndProcessMessage(ConnectSession.java:212)
at com.ca.ServicePlus.maileater.ConnectSession.check_mail(ConnectSession.java:188)
at com.ca.ServicePlus.maileater.IMAP4EmailClient.check_mail(IMAP4EmailClient.java:138)
at com.ca.ServicePlus.maileater.Mailbox.lambda$new$1(Mailbox.java:822)
at java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(Unknown Source)
at java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(Unknown Source)
at java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)
at java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)

I see this Broadcom article eMail notification fails with Failed to convert to JAVA MAIL (broadcom.com) but the error is slightly different, and I don't see any **** characters in the senders address. We are already running SDM 17.1.0.11 and the fix is referencing 17.1.0.03 and I'm not keen on the other suggested fix unless I know what is happening.

Anyone out there encountered this?

Thanks
Stuart

[Charles Nack]

Stuart, 
Thank you for your question. First as you know 17.1 went end of support and 17.2 is coming up on end of support at the end of March. We highly suggest upgrading your system to 17.3 + Latest RU to ensure all fixes and security patches are applied to your environment. 
https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/ca-service-management/17-3/upgrading.html

As this is a specific sender, is it a specific email address or specific domain that is being affected?
You can try enabling trace\debug logging to get more information around the mail coming in to understand what may be the issue.
https://knowledge.broadcom.com/external/article/98428/

Hope this puts you in the right direction!