Identity as a Service:Old IDaaS mail returned by system

Problem

When customers use IDaaS EIAM 1.X version instances (old version), they receive a mail with the subject of "Sorry, your email has been returned by this system."

Possible causes

This email may be generated due to the following reasons:

1. IDaaS EIAM 1.X version automatically creates a default account for internal operations and management.

2. A sample email address (such as "example@example.com") is configured in the default account, and this email address cannot receive emails normally.

3. When the system attempts to send notifications such as account expiration reminders, the email is returned because the sample email address in the default account is invalid.

This situation is normal and does not affect the functionality or performance of the system.

Notes

• Applicable scope: This topic applies to IDaaS EIAM 1.X version instances (old version). If you have upgraded to version 2.0, please ignore this topic.

• No service impact: This issue is only an email return caused by the system default configuration and does not have any impact on existing services or business.

• Recommendation: We recommend that you evaluate and migrate to IDaaS 2.0 as soon as possible to enjoy more comprehensive features and higher security support.

Solution

To prevent this issue from occurring, follow these steps:

1. Modify the email address of the default account.

   1. Log on to the IDaaS console, enter the Accounts and Orgs module, and find the email configuration page of the default account.

   2. Locate the default account in the console (usually the administrator account automatically created by the system).

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

   4. Replace the sample email address (such as example@example.com) with an active enterprise email address.

   5. Save the changes (ensure that the newly configured email address is valid and can receive emails within the enterprise).

2. Check and update other related configurations.

   1. If there are other similar default configured email addresses in the instance, we recommend checking and updating them to valid addresses as well.

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

3. Verify the modification results.

   1. After completing the modification, manually trigger a test email to verify whether the newly configured email address can receive emails normally.

   2. If the test is successful, the problem has been resolved.

Reference

• 1.x old version instance change solution