RSA Identity Governance and Lifecycle reports fail to send emails with error SMTPSendFailedException:552 5.3.4 Message size exceeds fixed maximum message size
Originally Published: 2017-09-13
Article Number
Applies To
RSA Version/Condition: 6.x, 7.x
Issue
<span style="color: rgb(255, 0, 0);"><span style="font-size: 12px;"><span style="font-family: arial,helvetica,sans-serif;">
09/05/2017
04:32:53.828 ERROR (EmailSenderServiceProvider) [com.aveksa.server.email.sender.EmailSenderServiceProvider]
FAILED method=SendEmail subTask=processMessage EmailLogMessage{messageData='From: <sender-email>
</span></span>To: <receipient-email><span style="font-size: 12px;"><span style="font-family: arial,helvetica,sans-serif;">
Message-ID: <AV-6355-REF.1054519700.14851504600121791.JavaMail.oracle@servername.com>
Subject: New "All Application Entitlements&Groups Report" report results
available 9/5/17 4:20 AM
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_185_1918193552.1504600121791"
X-Priority: 3
X-Aveksa-Message-Reference: AV-6355-REF
------=_Part_185_1918193552.1504600121791
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<html><body>Results for report: All Application Entitlements&Groups Report
Saved on: 9/5/17 4:28 AM
Comment: Scheduled Report
Dear Admin,
You are receiving this email as the attached report needs action taken. Please review this report for critical missing information on the
application feed. Please update the feed within 5 business days.
Thank You,
------=_Part_185_1918193552.1504600121791
Content-Type: application/octet-stream;
name="All Application Entitlements&Groups Report.CSV"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="All Application Entitlements&Groups Report.CSV"
QXBwbGljYXRpb24gTmFtZSxFbnRpdGxlbWVudCBOYW1lLERlc2NyaXB0aW9uLE93bmVyCiIxMDEw
RGF0YXNldCIsIkFTSUMgUHVibGljIFJlcG9ydGluZyAtIEFTSUMgT1RDIFBvc2l0aW9uIDogZHRj
Y19kcy5hc2ljLm90Y19wb3NpdGlvbiIsIkFTSUMgUHVibGljIFJlcG9ydGluZyBBU0lDIE9UQyBQ
IiwiQ049RkFfVEZfRmlsZXhmZXJfUHJvZF9Eb3dubG9hZC1QUkMsT1U9RUZUIEFwcGxpY2F0aW9u
.............
QFhBQ1Q6USIsIlhJUiBOb24tUmVzdHJpY3RlZCBSZXBvcnRzIiwiMTIyNDciCiwiWElSQFhBQ1Q6
VCIsIlhJUiBOb24tUmVzdHJpY3RlZCBSZXBvcnRzIiwiMTIyNDciCiwiWElSQFhBQ1Q6VSIsIlhJ
UiBOb24tUmVzdHJpY3RlZCBSZXBvcnRzIiwiMTIyNDciCiwiWkJSQURNOkEiCiwiWkJSQURNOlAi
CiwiWkJSQURNOlEiCiwiWkJSQURNOlQiCiwiWkJSQURNOlUiCg==
------=_Part_185_1918193552.1504600121791--
', id=6355, senderAccountName='general', msgType='WFE_RP', msgIDWithinMsgType='39202',
messageID='<AV-6355-REF.1054519700.14851504600121791.JavaMail.oracle@servername.com>', isOutbound='Y',
subject='New "All Application Entitlements&Groups Report" report results available9/5/17 4:20 AM', fromStr='<sender-email>',
toCnt=1, toStr='receiver-email', ccCnt=0, ccStr='', bccCnt=0, bccStr='', insertTime=2017-09-05 04:28:44.260622,
completedTime=Tue Sep 05 04:32:39 EDT 2017, processAction='null'}
com.sun.mail.smtp.SMTPSendFailedException: 552 5.3.4 Message size exceeds fixed maximum message size
at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
at com.sun.mail.smtp.SMTPTransport.finishData(SMTPTransport.java:1215)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:586)
at com.aveksa.server.email.EmailClient.sendEmail(EmailClient.java:306)
at com.aveksa.server.email.sender.EmailSenderServiceProvider.processMessage(EmailSenderServiceProvider.java:334)
at com.aveksa.server.email.sender.EmailSenderServiceProvider.processMessageBatch(EmailSenderServiceProvider.java:256)
at com.aveksa.server.email.sender.EmailSenderServiceProvider.processMail(EmailSenderServiceProvider.java:204)
at com.aveksa.server.email.sender.EmailSenderThread.run(EmailSenderThread.java:42)
09/05/2017 04:38:04.147 DEBUG (EmailSenderServiceProvider) [com.aveksa.server.email.sender.EmailSenderThread] Running Loop
to check for mail to send.</span></span></span>Cause
Error 552 ‘5.3.4 Message size exceeds fixed maximum message size’ is an email error commonly seen, when the message is too large for the SMTP server to handle, the mail stays in the mailbox and errors like the above will be printed in logs.
Every mail server has custom settings for the size of emails users can send and receive through it. These limits can either be global, individual-account specific or both. To limit bandwidth usage, this email size limit is often restricted to a few MBs in most servers. If the email size exceeds that limit, it will be rejected by the mail server.
Resolution
For example, on Microsoft Exchange mail servers, content conversion happens for email. The Exchange server converts an internet/MIME message to MAPI/Exchange format, and vice versa for transmission. After this content conversion process, the message size generally increases by about 30%. As a result, a message of 9 MB may fail to deliver to a server with a size limit of 10 MB.
Related Articles
RSA Announces the Availability of RSA Identity Management and Governance 6.9.1 Patch 131 7Number of Views Account and Group Resolutions fail when running a Data Entitlement Aggregate (DEA) Data Access Collector in RSA Identity G… 20Number of Views Account and Group Resolutions fail when running a Data Entitlement Aggregate (DEA) Data Access Collector in RSA Identity G… 38Number of Views Z: TCE Collection Initiative - Summary of End points from which RSA Identity Governance and Lifecycle can collect data 42Number of Views Synchronize Users from Internal Database to Cloud Authentication Service 51Number of Views
Trending Articles
How to recover the Application and AFX after an unexpected database failure in RSA Identity Governance & Lifecycle Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager Upgrade Process
Don't see what you're looking for?