sounds more like an approval process than testing. We blast emails to a set of test account email addresses and a QA Analyst meticulously goes through a pre-defined and client approved list of devices, platforms, OS etc. checking content and rendering and reporting issues. They also check links and validate code. There may be a few rounds of fixes before they approve the mailing for sending to the team/agency/client for approval. This process can indeed create bottlenecks and on fairly simple emails, take longer than the development time but it ensures we are sending out quality emails ;)
I had a similar thing with Taylor Swift! Seems certain key words are so "important/relevant" that the email client decides that the user is interested in going where it wants them to and not where the sender does!
I insert the zero-width non-joiner into troublesome words and this removes the auto-links.
This is the fix for me! The others whilst working in part, didn't fix the render issues I was having in Safari.
The "download" button still gets applied to images of a certain size (just like gmail) but at least you don't have to apply real hrefs to every structural image - I just created a template using side slithers to allow for flexible heights but needed 1px wide images and bgcolors to achieve the design - you can imagine the render issues this was causing.
Great job with the fixes guys :))
I'm hoping that unless Gmail's interpretation of media queries differs from the native apps, I won't need to change the way I code emails, just that mobile gmail app users will get a better experience :)