This is a bad thing. Gmail needs to be e-mail and nothing more or this is EEE.
Sorry, what's EEE?
Email Markup in Gmail
21–30 of 113 posts
Re: Email Markup in Gmail
#22Re: Email Markup in Gmail
#23Earlier quoted context omitted.
ProtonMail may not be the best choice if you're a stickler for standards. Their service unapologetically works only within ProtonMail. Send an e-mail to someone with a different provider and they get a link to a https view of the email.
Thanks, though I set it up yesterday mostly for receiving, I don't plan to send anything from it Is there another email provider that isn't hotmail, gmail or yahoo mail with good prospects at the moment?
Re: Email Markup in Gmail
#24Note that this only is available to high volume senders ( https://developers.google.com/gmail/markup/registering-with-... ): > Consistent history of sending a high volume of mail from your domain (order of hundred emails a day minimum to Gmail) for a few weeks at least.
I have a very small SaaS and I was approved. I don't send hundred of e-mail to other e-mail addresses daily, but I do send a lot of e-mails to myself (server alerts and notifications). Approval process is very easy and takes 2 minutes, it is worth applying.
Re: Email Markup in Gmail
#25Earlier quoted context omitted.
Why can email not evolve? Structured data in markup works well on the web. It's open and could be implemented by any client.
It's only ever going to work for gmail users. For people who read their email in text-only clients this will never do anything. You know, people who use serious email, not to send pictures of balloons and 96-pt Happy Birthday in pink on purple text.
That of course assumes that "serious" e-mail happens only in text-only clients.
Meanwhile, my work e-mail account is fairly busy, pretty much all HTML, and I haven't seen balloons, 96-pt text, or purple background. (I do occasionally send pink text, though. I'm that person)
And all of these markup items are highly welcome. I'd rather live in the 21st century. (Although I would kill for procmail, but we can't win them all)
Re: Email Markup in Gmail
#26I would love to be able to do this for internal email within a Google Apps for Work domain, etc.
Why can't you? I mean, their examples in the link even show how to implement this with a simple Google Apps Script project.
Re: Email Markup in Gmail
#27Took a peak, saw tag, left.
The tag only contains a JSON object. It's not a function that runs or something client-side.
Re: Email Markup in Gmail
#28Re: Email Markup in Gmail
#29Re: Email Markup in Gmail
#30I would love to be able to do this for internal email within a Google Apps for Work domain, etc.
Why can't you? I mean, their examples in the link even show how to implement this with a simple Google Apps Script project.
Huh, this has been available for a while so I actually didn't realize this was a new announcement. I was hoping the registration would be less strict if you're only sending within your own domain, but this is good enough really.