3 ms·

I would beg to differ about email reliability, also see https://datatracker.ietf.org/doc/html/rfc5321#section-6.1 https://datatracker.ietf.org/doc/html/rfc5321#

I would beg to differ about email reliability, also see https://datatracker.ietf.org/doc/html/rfc5321#section-6.1 https://datatracker.ietf.org/doc/html/rfc5321#section-6.1 but do agree that everything could get lost for some reason. But that is not the main point. Even if the email was lost somewhere in Office 365, people were already pointing out to Atlassian that they should really send a follow up on Aug 27: https://jira.atlassian.com/browse/CONFSERVER-67940?focusedCommentId=2862709&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2862709 https://jira.atlassian.com/browse/CONFSERVER-67940?focusedCo...

qwertox 5y ago
The follow-up-request was to notify users that the advisory has been updated, not to ensure that customers received the Aug 25 email which linked to that advisory. Either is was Atlassian's mailing list software which did not attempt to re-send the email to you after it noticed that the connection got dropped (should that have happened), or is was Microsoft which dropped the email after receiving it, but before storing it into the database and assigning it to your account. You cannot know who is responsible for this delivery error unless you ask them directly.