Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Dynamic system settings for email integrations

Updated on April 6, 2022

Pega Platform provides dynamic system settings that you can use to modify the behavior of email processing on your system. For example, you can limit the size of an email message that your application accepts, or allow text attachments to be sent in the email body.

For more information on updating dynamic system settings, see Editing a dynamic system setting.

Note: To ensure optimal configurations, set dynamic system settings to the recommended values. If you do not use the recommended values, Pega Predictive Diagnostic Cloud™ displays a list of dynamic system settings that do not match the recommended values.
Services/EmailMaxSizeLimits the maximum size in KB for an email message. Enter -1 to allow messages of any size.

This value is overridden by the Maximum email size (KB) field on the Process tab of the Email Listener data instance.

Services/EmailSuppressUnknownContentErrorIf set to true, suppress any unknown content type errors.
Services/EmailSuppressMailAPILoggingIf set to true, suppress any API debugging messages.
email/timeoutConnection timeout for SMTP. The recommended values are between 50000 and180000 milliseconds. The default value is 60000.
email/fetchsizeControls size of fetch in bytes if IMAP partial-fetch feature is enabled. The recommended value is 1 MB. This value typically does not need to be reset. This setting is also known as mail.imap.fetchsize.
email/partialfetchControls whether to use the IMAP partial-fetch capability. The default value is true. Resetting this value is not recommended. This setting is also known as mail.imap.partialfetch.
email/blockResponseIf true, all responses are blocked. No response will be sent. The default value is false.
email/enableTextAttachmentInEmailBodyIf true, text attachments can be embedded in the Email body. The default value is false.
prconfig/initServices/initEmail/defaultControls whether the Email service is initialized by default at system startup. The default for the setting is true. In a multinode system, this setting allows you to control whether the Email service is available on individual nodes.
FailOnAddressExceptionIf set to true, this setting ensures that message processing failures are caught. If set to false, this setting ignores processing failures related to message headers. The default setting is false.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us