Currently when I'll receive a security advisor notification, the sender address is info@e.atlassian.com. That's the same address that is also used for e.g.:
I'll think something like security advisories should be using a separate sender address so it won't handled / process as junk because usually it's marketing related content.
Also funny :D
That notifications often miss a site, etc. is another story but please, think about sending security related notifications with a better address.
Kind Regards,
Tim
I tend to agree too.
I'm not so sure that we should have a plethora of "from" addresses for every possible subject, but I do think there should be a (small) handful of grouped subjects.
Security stuff is definitely something that should be separated out. "As an admin, I don't really care about insider offers, adverts, training, invites, and the other stuff end-users might be using, but I really do need to be able to quickly identify security and update things immediately"
Having a few "sent by <well named id>@atlassian.com" would make it a lot easier to identify that!
Just a little oberservation, the recent notification for https://confluence.atlassian.com/security/cve-2023-22518-improper-authorization-vulnerability-in-confluence-data-center-and-server-1311473907.html was send with security@e.atlassian.com
This time, finally lands in the inbox folder an gets immediate attention by myself 👍