![]() Outlook 2013 and Outlook 2016 no longer do this and maintain the link to the location of the picture instead. Upon sending, Outlook used to take these pictures and places them within the message itself and change the references to an internal resource: the images were embedded within the email. Html-signatures don't actually contain the picture files themselves, they include html code with references to the location of the pictures. In Outlook 2013 and Outlook 2016, linked pictures will remain linked. In previous versions of Outlook, linked pictures would get embedded upon sending. Outlook 2013 and Outlook 2016 indeed include a change of defaults regarding the handling of linked pictures when compared to previous versions of Outlook. Why is this happening and how can I make my signature work with Outlook 2016? ![]() I've successfully used this signature for years with Outlook 2010 and the issue only occurs when I send a message with this signature from Outlook 2016. However, when I send the message, the recipient does not see this picture. This signature contains a picture and looks correct when composing a new message or reply. I've created my HTML signature in an external application and then placed the files (including txt and rtf versions) in the Signatures folder.
0 Comments
Leave a Reply. |