Summary
The advanced.pool.enabled property in the Custom SMTP Server integration configuration is being deprecated. This property currently controls SMTP connection pooling, but it duplicates the functionality of the existing permanentCxn property, which provides the same behavior with clearer naming.
Going forward, customers should use permanentCxn to enable SMTP connection pooling.
Effective Date
Sunday, April 19, 2026
Details
Currently, SMTP connection pooling can be enabled in two different ways:
• permanentCxn: true
• advanced.pool.enabled: true
Having two properties for the same capability creates confusion for customers and increases maintenance complexity. The permanentCxn property aligns better with naming conventions used in other integrations and is the preferred configuration going forward.
Customer Impact
• Backward compatibility is fully maintained during the deprecation period.
• Both properties will continue to work together using OR logic (connection pooling is enabled if either property is set to true).
• No immediate action is required, and there is no risk of service disruption at this time.
• Customers currently using advanced.pool.enabled should plan to migrate to permanentCxn.
• Deprecation warnings will appear in logs when the deprecated property is used.
• After the deprecated property is removed, customers who have not migrated may lose connection pooling functionality, which could impact email sending performance.
Impacted Resources
No APIs are impacted.(Custom SMTP Server Integration Configuration - advanced.pool.enabled property in the advanced configuration section)
Issue References
POSTINO-2532
Contacts
@Shangeeth Rajasekar Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.