Earlier quoted context omitted.
What if google just immediately fetches images for all received messages, regardless of deliverability? They can dedupe wherever possible, but the sender still ends up with no information about whether the message was delivered, much less read.
AND it could create a dis-incentive to load up an email with unique images since as soon as you send the email out all of those gmail addresses are coming right back at your server to request the images.
Gmail blows up e-mail marketing by caching all images on Google servers
171–180 of 322 posts
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#172Some other technical aspects of this: GMail serves all images from a datacenter in Mountain View, CA, so if your email's images were served from multiple datacenters or a CDN, there is a good chance they will load more slowly, depending on your caching headers. They optimize images on the fly, which may introduce more latency. Their optimizer doesn't take into account whether the optimized image is smaller than the o…
Citation needed.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#173holy smokes google is going to further grow their monopoly and try to take over the advertising market with this. They'll cache and own even more of your data and keep it out of the hands of spammers - in turn spammers will have to buy into google to get data about you. This isn't for us, this was done to make money off of us.
As a Gmail user, that's what I want.
> keep it out of the hands of spammers - in turn spammers will have to buy into google to get data about you.
Again, that's what I want. Spammers depend upon an incredibly low cost of sending emails with almost no accountability through botnets and foreign servers. If they need to open Google advertising accounts, provide a credit number, have to get their ads approved, and get charged market rates for their impressions ... I'm all for it.
But none of them will actually do it. Google won't make a dime from them.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#174Earlier quoted context omitted.
I think any email marketers who want to get around this easily can. Just change robots.txt to not give permission to Google fetching the images. Copyright will laws will prevent them from wilfully ignoring that, presumably.
robots.txt is for crawlers, it would not stop an email client from rendering the email on behalf of its user upon receipt.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#175Re: Gmail blows up e-mail marketing by caching all images on Google servers
#176Earlier quoted context omitted.
Google could retrieve and cache a random sample of the images and hash them. Then they could note which image links go to the same images. And they could identify image links by noting that a bunch of emails have the same structure except for one image link that's different for every recipient. So I think they actually could take a pretty good stab a deduping images with unique tracking URLs. It might not be perfect,…
What if the images are slightly modified for each user? A mixture of image processing and hashing can be used for deduping though.
It'd be a gold mine.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#177Earlier quoted context omitted.
I wasn't describing a new tactic for spamming, I was describing possible new tactics for targeted attacks. They're different things.
An attack that relies on the possibility of being able to send millions of emails without being detected as spam; so it is unlikely to succeed.
And spammers aren't even that smart, they're just numerous and financially motivated.
If somebody wanted to annoy someone else with this, they could.
And, again, even if this doesn't work against Google directly, it certainly would work against other service providers who decide to follow Google's lead.
Heck, just look at the recent popularity of the WhatsApp spam that spread malware to tons of people (including Cryptolocker in some cases), or the "Secure Document" phish that made the rounds in Gmail in September.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#178Earlier quoted context omitted.
Consider this @codeflo: 1. Google may cache all images in all emails sent to gmail.com instantly and regardless of the existence of the address. This would remove the possibility for marketers to check user timestamp, remove user data from request and hide user email existence. 2. Google does _not_ need to save each image from each unique URL separately, all they need to do is fetch each image and check against an al…
I thought that 99% of the images included in emails for tracking purposes are single pixel transparent GIFs - so no biggie in working out which ones those are...
Using a separate tracking pixel is pointless unless you for some reason want to let some third party track the opens (which some people might, e.g. to prove certain open rates)
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#179> E-mail marketers will no longer be able to get any information from images—they will see a single request from Google, which will then be used to send the image out to all Gmail users. Unless you click on a link, marketers will have no idea the e-mail has been seen. Absurdly wrong, marketers already use a unique image URL for each email recipient, and Google has no way to know that all of those point to the same im…
I reply to this question here. Sadly, a request is done each time and only when a user loads the image.
https://news.ycombinator.com/item?id=6898087
Which makes the Ars article even more wrong.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#180> E-mail marketers will no longer be able to get any information from images—they will see a single request from Google, which will then be used to send the image out to all Gmail users. Unless you click on a link, marketers will have no idea the e-mail has been seen. Absurdly wrong, marketers already use a unique image URL for each email recipient, and Google has no way to know that all of those point to the same im…
As someone who co-invented email image bugs with a million other programmers over 15 years ago, you are absolutely correct. (for the curious, my reason for coming up with it was to tell when a customer who requested a car insurance quote from the company I worked at read their email which instantly initiated an outbound call to them). The entire article is just plain wrong. For instance: This move will allow Google t…
If the same, just show a cached version. No more tracking.
(of course, email marketers would thwart this by making each image slightly different. google would respond by checking if the images are almost exactly the same. repeat. whack-a-mole ad infinitum).