Skip to main content
Question

Did 25R2 deployment overwrite MAIL_SENDER1 configuration parameters?

  • July 14, 2026
  • 2 replies
  • 29 views
maheshmuz
Hero (Partner)
Forum|alt.badge.img+11

We recently deployed the IFS Cloud 25R2 upgrade to our environment. Post-deployment, we noticed that our default mail sender settings in IFS Connect (MAIL_SENDER1) appear to have changed or reset.

I want to understand the standard behavior of the 25R2 installer regarding IFS Connect sender templates:

Does the 25R2 deployment automatically restore MAIL_SENDER1 back to its default core values?

What is the best practice to ensure our custom mail sender parameters are not affected during major release deployments?

Any insights from anyone who has experienced this during their 25R2 upgrade would be greatly appreciated.

2 replies

ashen_malaka_ranasinghe
Hero (Employee)
Forum|alt.badge.img+14

Hi ​@maheshmuz,

From my understanding, MAIL_SENDER1 is an IFS Connect configuration object rather than application metadata that is normally recreated during every release deployment. Therefore, under normal circumstances, I would not expect a 25R2 upgrade to intentionally reset a customer-configured MAIL_SENDER1 instance back to the original core values. However, the actual outcome can depend on how the environment was upgraded, whether configuration data was restored from backups, whether environment recreation was involved, and whether any post-upgrade activities were performed on the IFS Connect configuration. I have not found any release documentation stating that 25R2 explicitly resets MAIL_SENDER1 to its default configuration during deployment.

If the sender configuration changed after the upgrade, I would suggest investigating whether the MAIL_SENDER1 parameters were maintained as environment-specific configuration or if they were overwritten during a configuration import, environment refresh, delivery deployment, or other post-upgrade activities. In several IFS Connect implementations, customer-specific sender definitions and authentication settings are considered operational configuration and should ideally remain unchanged unless a deployment activity explicitly updates them. The fact that the change was observed immediately after the upgrade does not necessarily prove that the 25R2 installer itself performed the reset.

Find me on LinkedIn as Ashen Malaka: https://www.linkedin.com/in/ashen-malaka-ranasinghe/
maheshmuz
Hero (Partner)
Forum|alt.badge.img+11
  • maheshmuz
  • Author
  • Hero (Partner)
  • July 15, 2026

Hi ​@ashen_malaka_ranasinghe ,

Thank you for your response.

Sorry, I should have mentioned that this was not an upgrade but an update that we applied to the environment. Previously, the environment was running 25R1, and we applied the 25R2 update.

The issue occurred after applying the 25R2 update. We did not experience this problem with the previous updates that were installed in the environment. This appears to have started only after the 25R2 update installation.

Terms & ConditionsAccessibility statement