You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I read under closed issues, that "the first user with the permission to send" is used as sender. It was not explained what makes a user the "first" user. In our test the user as which Pulse is sending the mail is the primary admin on system level, meaning that is happening without us changeing any settings in that regard. Which is actually how we want it to be. But: while the sender email is correct, the name of the sender as seen by the recipients is "Admin User". That "name" is set up nowhere by us, though. The primary admin is named "Xyz Academy" (Xyz being the company name). You can see how this can be a problem, getting important mails with a generic name like that, esp. since other emails like from course recompletion do use the correct "Xyz Academy" name, resulting in mixed names for mails from the same context.
The text was updated successfully, but these errors were encountered:
We have a similar problem. When creating an instance and using the "custom sender" you only can add a valid email address and same as VOOM108 case the recipient of the email will see the first part of the email, in lowercase, just a suspicious "noreply" and not the "Whatever Academy" that would look serious and be consistent with all other communications of our Campus.
I think it's important to fix this issue.
Thank you.
I read under closed issues, that "the first user with the permission to send" is used as sender. It was not explained what makes a user the "first" user. In our test the user as which Pulse is sending the mail is the primary admin on system level, meaning that is happening without us changeing any settings in that regard. Which is actually how we want it to be. But: while the sender email is correct, the name of the sender as seen by the recipients is "Admin User". That "name" is set up nowhere by us, though. The primary admin is named "Xyz Academy" (Xyz being the company name). You can see how this can be a problem, getting important mails with a generic name like that, esp. since other emails like from course recompletion do use the correct "Xyz Academy" name, resulting in mixed names for mails from the same context.
The text was updated successfully, but these errors were encountered: