Redmine

Here are some common reasons why status change notifications might not be sending, even if your SMTP server is configured correctly:

Common Causes for Notification Failures
Notification Rules/Conditions: Many systems have specific rules that dictate when a notification should be sent.

Is the "send notification on status change" rule still active? It might have been inadvertently disabled or misconfigured.

Are there specific conditions (e.g., only for certain status changes, or only if specific fields are updated) that are no longer being met? For instance, if the old SMTP server was tied to a different profile that had the correct notification settings, and the new one doesn't.

User/Group Associations: Are the users or groups who should receive notifications still correctly associated with the notification rule?

Event Triggers: The system relies on an "event" to trigger the email.

Is the system correctly registering the status change as an event that should trigger a notification? There might be a disconnect between the status update and the notification system's awareness of it.

System Configuration Post-Migration: When you change an SMTP server, sometimes other related settings can be affected or require re-verification.

Default sender email: Is the "from" email address configured in the system still valid and allowed by the new SMTP server?

Permissions: Does the system user account sending the emails have the necessary permissions on the new SMTP server or within your application?

System Caching: Sometimes, systems cache old configurations.

Have you cleared the system's cache after making the SMTP server change? A simple restart of the application or service might also help.

Logs and Error Messages: The most crucial place to look is the system logs.

What do the application logs say when a status change occurs? Look for any errors related to sending emails, notification failures, or even warnings about missing configurations. This will often pinpoint the exact problem.

Specific Software/Platform: Without knowing what software or platform you're using (e.g., Jira, ServiceNow, a custom application, etc.), it's hard to give more specific advice. Different systems have different places where these rules are configured.

Next Steps to Troubleshoot
Check Notification Rules: Go into the administrative settings of your application and carefully review all notification rules related to status changes. Ensure they are enabled and correctly configured for the desired status transitions.

Verify User/Group Subscriptions: Confirm that the intended recipients are still subscribed or configured to receive these notifications.

Examine System Logs: This is the most important step. Find the application's logs and look for any entries around the time you make a status change that should trigger an email. Look for keywords like "email," "notification," "SMTP," "send," or "error."

Compare Configurations: If possible, compare the notification settings from when it was working with the old SMTP server to the current settings. There might be a subtle difference

Restart Application/Service: If you haven't already, try restarting the application or service that handles these notifications.