Email notification is not being sent for conversation alerts
Article ID: 130840
Updated On:
Products
Clarity PPM SaaS
Clarity PPM On Premise
Issue/Introduction
We are currently going through a user application testing for in our development environment. We noticed that when a user are mentioned in the conversation, they don't get an email notification. However, it does appear under the notification icon with a message "... has mentioned you in a conversation ... If users hover over the notification bell icon within that particular project within the new user experience view.
We verify that the following configuration is enabled:
Under Administration - Notification - Conversation, the "Alert", "Email", "SMS" checkbox are selected for "Conversations".
Is there another setting that we need to enabled in order for users to get email notifications for Conversations alert?
We verify that the following configuration is enabled:
Under Administration - Notification - Conversation, the "Alert", "Email", "SMS" checkbox are selected for "Conversations".
Is there another setting that we need to enabled in order for users to get email notifications for Conversations alert?
Environment
Release:
Component: GROUPS
Component: GROUPS
Cause
SUMMARY OF DEFECT
The From Address in our email notifications places the sending user's email address (instead of "First_Name Last_Name" or "Last_name, First_Name") in the display name for the From attribute even when the Default Sender address is defined in the CSA. This causes many On Demand customer email systems to reject the emails due to possible spoofing.
EXAMPLE FROM THE EMAIL HEADER:
FROM: "[email protected]"
where [email protected] is the default sender address defined in the CSA.
AFFECTED VERSIONS: All
STEPS TO REPRODUCE
1. Set up a PPM system with email server information and a default sender address so that it can send emails
2. Perform any activity that will generate an out-of-the-box-notification. I tested adding and removing a participant on a project, sending a report completed notification, submitting a timesheet, and a process manual notification. All performed the same way
Expected Results: The FROM field will be structured so that "LAST_NAME, FIRST_NAME" or "First_Name Last_Name" in the display portion of the FROM field like most emails.
The From Address in our email notifications places the sending user's email address (instead of "First_Name Last_Name" or "Last_name, First_Name") in the display name for the From attribute even when the Default Sender address is defined in the CSA. This causes many On Demand customer email systems to reject the emails due to possible spoofing.
EXAMPLE FROM THE EMAIL HEADER:
FROM: "[email protected]"
where [email protected] is the default sender address defined in the CSA.
AFFECTED VERSIONS: All
STEPS TO REPRODUCE
1. Set up a PPM system with email server information and a default sender address so that it can send emails
2. Perform any activity that will generate an out-of-the-box-notification. I tested adding and removing a participant on a project, sending a report completed notification, submitting a timesheet, and a process manual notification. All performed the same way
Expected Results: The FROM field will be structured so that "LAST_NAME, FIRST_NAME" or "First_Name Last_Name" in the display portion of the FROM field like most emails.
Resolution
DE45179, Fixed in 15.6, also in patch 15.5.1.2
Feedback
Yes
No
Powered by
