Is anyone else all of a sudden not seeing graphics in CC sent emails? Last Thursday we had 3 (maybe more) employees all using different OS and outlooks just stop being able to see the graphics of our company emails from CC. We've googled and looked at security settings and enabled features, etc. Can't seem to figure out why suddenly some stopped being able to view graphics.
Anyone else experiencing this?
Has CC changed some settings?
Any advice on what to look for?
help! I have no idea if any of my 3000+ customers are also experiencing this from our emails.
Jun 25, 2021 7:38:49 AM
Here is an update on the current status of the issue. We were able to get a change made to our SSL certificate configuration that is a possible fix. Our Network and product teams are closely monitoring the issue to confirm before we say this is officially resolved.
Has anyone noticed any improvement with their images loading in Outlook?
Absolutely no word from CC about this issue at all. Be sure to speak with billing about getting your account credited! The whole situation is a complete joke to them. They have no interest in fixing the issue.
Thanks for reaching out to the Community with this question! GaryD675 has the correct answer and workaround, so I am here to provide a bit of background.
We recently did a security upgrade on our end to TLS 1.3, but not all versions of outlook have done the same. While we are waiting for Outlook to catch up, there may be some instances of images not displaying correctly. We are currently tracking this issue, and will do everything we can to get it resolved.
For each image that is not showing:
Hi Kara. Thank you very much for your reply and explanation. It is certainly nice to have the issue confirmed. Is there a work around for the CC stock images like the social media icons? Can I ask what you mean by "While we are waiting for Outlook to catch up"? We still have lots of subscribers on Windows 7 with older email clients like Outlook 2010 & 2013 which are no longer receiving updates. Also I'm not even sure Windows 7 supports TLS 1.3 does it? Thanks again!
Once a stock image is uploaded to your Constant Contact library a URL is created for it just like images uploaded from your computer, so the same workaround will apply.
I apologize, I should have not said "While we are waiting for Outlook to catch up" because I honestly don't know what their plans are for the older versions of outlook. I did find this article
Microsoft TLS 1.3 Support Reference from January 2020 which may give you some more information.
Hi Kara. Thank you for the quick reply. The social media icons are built in to CC and not in my media library. I can't change them nor can I see a URL for them.
From what I have gathered, this issue appears to only happen on Windows 7 machines. I really hope it can be resolved soon.
Hi Kara, yes, your recent upgrade caused the images problem just in the past week for me. You reference you are waiting for outlook to catch up. I use Mac Mail 7.3 on an older mac running 10.9.5 i no longer get images in CC emails from any of the constant contact accounts I use to send out emails. your "upgrade" should not prevent our emails thru CC from not being seen by thousands of people who use older softwares.
Any idea when or if there will be a fix for this? I only discovered this as some of machines are running Outlook 2003.
Ive done the workaround as explained above for my current campaign, but its a bit of a pain for each image.
For a month now (maybe more) the emails from Constant Contact have stopped displaying images that are part of the newsletter, when sent to Outlook desktop clients. It occurs both when testing by ourselves to our own outlook system, and when we circulate the actual final newsletter (it did display in mobile devices though).
We have verified that no new measures have been implemented on the organizational level, and have verified that our outlook version (we checked number of various versions) are set to the least protective level, as they were before. Nothing helped and the emails are incoming now with the images labeled:
"The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location"
previously it said: "Right-click here to download pictures. To help protect your privacy, Outlook prevented automatic download of this picture from the Internet."
Do you have any suggestion to the reason why it occurs, and better yet, how to fix it?
Hello @LimorD ,
We've recently updated our own security certificates, which we're still waiting on some versions of Outlook to catch up on. While our engineers are looking into the issue you're describing, it'll ultimately come down to Microsoft making sure all of its email systems are up-to-date. Making sure the domains we use are safelisted in your system may help let the images through, as we've seen that resolve similar prior issues with specific email clients blocking images.
We've also seen this issue pop up in Outlook before, which Microsoft has discussed and provided some potential workarounds of their own.
Your response is appreciated however conflicts with Kara's reply we received on March 2nd. There is nothing for Microsoft to "fix". This is an issue on your end as stated by 3 different Constant Contact staff members (recorded in chat transcripts). You folks really need to get your ducks in a row and come together to fix this problem. I know I am not the only one already looking into alternative providers specifically because of how Constant Contact has responded to this issue.
Let’s be clear....
1) Constant Contact is the ONLY email service provider that seems to be having this issue.
2) I have been using Constant Contact with various companies for years now without issue. This is something that just started happening recently – as per all of the other comments in this thread!
Just to appease, I did check the setting that the Microsoft article refers to. That option was already disabled.
I do hope that with all of this information, you will be able to provide a helpful update on the issue. Thank you again for all of your time and efforts.
Quite honestly, I'm not sure why the chat reps default to the "this appears to be an issue on our end" line whenever they see an active service request, including ones that are explicitly noted to not be an issue on our end. Regardless, this is down to Microsoft simply not updating some of their older versions of Outlook yet, as explained by Kara on March 2nd. Our engineers aren't going to be able to rollback a major security update that was necessary to begin with, and that pretty much every other email client is fully compliant with.
If we ourselves have an update on this issue that we're able to provide, it will be communicated. Until then, as of the time of this response, the issue remains isolated to specific versions of Outlook and will require MS to resolve. This is fully in line with what Kara explained on March 2nd.
This mass thread will continue to be updated, so that we can keep these posts consolidated for our engineers when they communicate with Outlook. If you're subscribed to this thread, then you'll likely continue to receive subscription updates, even when it's merely another thread being merged in (such as with Limor's).
Thank you for the quick reply.
1) I did not "default" to the issue being on your end. That is what I was told by 3 separate CC staff.
2) If this is simply an Outlook issue, how do you explain the other comments on this thread where people mention multiple OS's?
3) So if this was caused by a TLS 1.3 update on your end, why on earth would such an update take place that would ultimately affect so many people?
4) Let's suppose the update was indeed "necessary to begin with" as you say. How on earth is a major update like this done without warning people in advance?
So please correct this statement if it is wrong: The bottom line is that unless 3rd party vendors (ie: Microsoft & Apple), add backwards compatibility for TLS 1.3, Constant Contact is now only compatible with a limited amount of software.
1) The statement was in reference to the wording of the chat agents, nothing at all to what you've been saying in your various posts in this thread and others. I apologize if the wording of my response came off that way.
2) Outlook is an email program. Operating systems (OS's) would be in reference to iOS, PC, Android, etc. While there can be some significant differences in functionalities between versions of the program depending on the OS of the device, the security elements are generally pretty comprehensive between all variations. If there's a comment in the thread that's using the term "OS" in reference to an email client, we'll try to make sure that wording is cleared up during our regular check-ins with Voice-of-Customer and other dev teams.
3, 4, and the final bit) The issue is with specific older versions of Outlook that MS hasn't updated yet, and have been trying to resolve on their end as well. Security certificates and other security elements are regularly updated by companies all the time. There is (from what I've researched) never really been a need to "warn" our customers of better security, because it's something that the major email clients will normally have already updated to - i.e. we update our security system to match what the major clients utilize.
Thank you again for your quick reply William! Very much appreciated. I'm certainly not trying to be difficult or argumentative. In regards to #2) I should have been more clear, sorry. There are people on this thread saying that this is also happening in other email clients. Older versions of Mac Mail for example. That wouldn't be the case if this was strictly an Outlook issue?
But this last bit is true isn't it?
Unless 3rd party vendors (ie: Microsoft & Apple), add backwards compatibility for TLS 1.3, Constant Contact is now only compatible with a limited amount of software.
No need to apologize, I (and the rest of CTCT) understand the concerns and problems of this issue, especially since there are undoubtedly many other users still using the affected versions of Outlook.
I've modified my original response a bit to hopefully make my points a little more constructive and explanatory.
As far as the issue affecting older versions of Mac Mail, that is something the engineers are looking into as well, but so far appears to be hinging on the same expectations currently set for MS. Regardless, our engineers are doing what they can to gather info, and address the issue from our side in a way that doesn't result in retroactively causing additional deliverability issues from trying to attempt a security update rollback.
Good morning William. Lots of new posts in this thread every day. The latest from PeterP003 is a good one! Why is this only happening with CC emails (for me as well)?? Interesting info about his externally hosted image which works just fine with https. Are you still not convinced that this is a Constant Contact issue?
We have the same issue. Different people on different systems not seeing the images and only on CC mails. Even the mail from CC itself didn't show the images. The workaround of taking off the s from https seems to have worked, although this requires additional time so is not a long-term viable solution. Neither am I convinced that this is exactly the issue as we tested with an externally hosted image which was https and this worked fine. It is absolutely a CC issue that needs to be fixed to stop us and others going elsewhere.
The cipher list used by the Akamai endpoints publishing the image URLs for Constant Contact campaigns has changed recently resulting in older Windows and MacOS implementations being incompatible with TLS negoiation requirements to render images embedded in Constant Contact campaigns.
Can the previous cipher list be rolled back to restore compatibility with these older systems? There are still very common, and the additional security gained by removing the older ciphers really isn't warranted for this application.