IJ22062: EMAIL LISTENER CANNOT PULL NEXT EMAIL WHEN ILLEGAL CHARACTER ERROR OCCURS

APAR status

• Closed as program error.

Error description

• PROBLEM:
  
  While email listener runs and below error occurs, email
  listener cron stuck there and do not move on to next email.
  
  
  [7/19/19 15:41:29:764 AEST] 000001d1 SystemOut O 19 Jul 2019
  15:41:29:764 [ERROR] [MAXIMO] [CID-CRON-3895] Could not extract
  e-mail contents from message object.
  javax.mail.internet.AddressException: Domain contains illegal
  character in string     'wilson@maildomain.com'''''
  at
  javax.mail.internet.InternetAddress.checkAddress(InternetAddress
  .java:1279)
  at
  javax.mail.internet.InternetAddress.parse(InternetAddress.java:9
  73)
  at
  javax.mail.internet.InternetAddress.parseHeader(InternetAddress.
  java:663)
  at
  javax.mail.internet.MimeMessage.getAddressHeader(MimeMessage.jav
  a:733)
  at
  javax.mail.internet.MimeMessage.getRecipients(MimeMessage.java:5
  65)
  at
  psdi.common.emailstner.EmailListnerTask.getMailData(EmailListner
  Task.java:1668)
  at
  psdi.common.emailstner.EmailListnerTask.readMessagesFromMailServ
  er(EmailListnerTask.java:749)
  at
  psdi.common.emailstner.EmailListnerTask.performTask(EmailListner
  Task.java:275)
  at
  psdi.common.emailstner.EmailListnerCron.cronAction(EmailListnerC
  ron.java:49)
  at
  psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:
  2479)
  at
  psdi.server.CronTaskManager.access$1100(CronTaskManager.java:104
  )
  at
  psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:
  3371)
  at
  java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja
  va:522)
  at java.util.concurrent.FutureTask.run(FutureTask.java:277)
  at
  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFuture
  Task.access$201(ScheduledThreadPoolExecutor.java:191)
  at
  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFuture
  Task.run(ScheduledThreadPoolExecutor.java:304)
  at
  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
  utor.java:1160)
  at
  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
  cutor.java:635)
  at java.lang.Thread.run(Thread.java:811)
  
  
  ACTION TAKEN:
  Tested with no-Queue and Queue base email listener but both can
  stuck at same error and do not move to next email.
  
  
  EXPECTED RESULT:
  Skip the error and to move on to next email so it can create SR
  from next email.
  
  
  This will only fix CC fields.  The TO field is an "action"
  field and must be sacrosanct.  If the address exception occurs
  in a CC field, we'll catch the exception.  When the exception
  occurs, the JavaMail API DOES NOT allow for recovery of valid
  email individual addresses when this occurs; one bad address
  spoils the whole batch.  If one is bad the whole field is
  unrecoverable and we'll set CC to 'null' so that the email can
  be processed.
  
  REPORTED IN VERSION:
  Tivoli's process automation engine 7.6.1.0 Build 20180718-1141
  DB Build V7610-83
  

Local fix

• na
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Email listener customers who received messages with          *
  * malformed (non-RFC compliant) addresses.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Email listener was not catching email address exceptions.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Applying the fix should help with this problem but customers *
  * should mitigate the root cause in their email clients /      *
  * systems.                                                     *
  ****************************************************************
  

Problem conclusion

• This is fixed in code.
  The fix for this APAR is contained in the following maintenance
  package:
  	 | release\fix pack | Interim Fix for Release 7.6.1.2 Product
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels