This does not appear to be expected behaviour since I do not see this listed in the release notes.
I do see an internal defect was filed for this yesterday after this was brought to our attention and is currently being reviewed by the development team.
At the moment the only available workaround would be to send a copy of the email to review its details.
Regards,
Libin Varghese