Emails With Encoding UTF-7 Can't Be Processed By JMailClient and error "JMailClient object failed to retrieve message stream object from email server" is displayed
(Doc ID 2969811.1)
Last updated on NOVEMBER 09, 2023
Applies to:
Siebel CRM - Version 23.2 and laterInformation in this document applies to any platform.
Symptoms
Emails with encoding UTF-7 cannot be processed by JMailClient
After migrating mailboxes from on-premise Exchange to Exchange Online (except one mailbox) when an email with encoding UTF-7 arrives the JMailClient cannot retrieve the email. The UTF-7 encoded email is already marked as read in the mailbox and JMailClient stops processing another mails in this mailbox. In the on-premise Exchange mailbox the emails with UTF-7 encoding can be processed successfully without any errors.
The issue didn’t happen in the IP16 version.
The following errors occurs in the IMAPSMTP and in CIR logs:
IMAPSMTP_***.log
DBG: Return: ERROR
ERROR:Error retrieving mail stream object, could not copy stream object
ERROR:JMailClient object failed to retrieve message stream object from email server
ERROR:Could not retrieve email message
ERROR:JMailClient object failed to retrieve message stream object from email server
ERROR:Could not retrieve email message
CommInboundRcvr_***.log
JMailClient object failed to retrieve message stream object from email server
Could not retrieve email message
The issue can be reproduced at will with the following steps:
1. Migrate mailboxes from on-premise Exchange to Exchange Online
2. A new mail with UTF-7 encoding is received
3. JMailClient stops processing other mails for this mailbox as it’s stuck in this UTF-7 one and is already marked as read in the mailbox
Changes
Migrate mailboxes from on-premises Exchange to the Exchange Online.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |