Identity as a Service:System bounces emails from legacy IDaaS instances

Problem description

When you use a legacy IDaaS EIAM 1.X instance, you may receive a bounced email notification. The email subject is: "Sorry, the email you sent was bounced by the system".

Possible causes

This issue occurs for the following reasons:

1. IDaaS EIAM 1.X automatically creates a default account. This account is used for internal system operations and management.

2. The default account is configured with a sample email address, such as "example@example.com". This email address cannot receive emails.

3. When the system tries to send notifications, such as account expiration reminders, the email is bounced because the sample email address of the default account is invalid.

This is the expected system behavior and does not affect system features or performance.

Notes

• Scope: This document applies to legacy IDaaS EIAM 1.X instances. If you have upgraded to version 2.0, this document does not apply.

• No service impact: This issue is caused by default configurations and does not affect your existing services or business.

• Long-term recommendation: We recommend that you evaluate and migrate to IDaaS 2.0 as soon as possible to benefit from improved features and better security support.

Solution

To prevent this type of problem from recurring, perform the following steps:

1. Change the email address of the default account.

   1. Log on to the IDaaS console and open the mailbox configuration page for the default account from the Accounts And Organizations module.

   2. In the console, locate the default account. This is usually the administrator account that the system automatically creates.

   3. Click the Edit button and locate the email configuration item.

   4. Replace the sample email address, such as example@example.com, with a valid corporate email address.

   5. Save the changes. Ensure that the new email address is a valid address within your organization that can receive emails.

2. Check and update other related configurations.

   1. If other accounts in the instance have similar default configurations, update them to valid addresses.

   2. Ensure that all related notification features, such as account expiration reminders and password reset notifications, use valid email addresses.

3. Verify the changes.

   1. After you save the changes, you can manually trigger a test email to verify that the new email address can receive emails.

   2. If the test is successful, the issue is resolved.

References

• Change plan for 1.x legacy instances