Add schema.org ViewAction to email messages

[kamalmarhubi]

This would allow messages to include a "View thread" (or similar) link. This is how GitHub "View Issue" and "View Pull Request" links get included in the GMail and Google Inbox interfaces. (See note below on GMail requiring registration.)

More information:

• ViewAction on schema.org
• Google developer documentation on ViewAction

The changes are simply adding more to the message templates. The code from a recent GitHub issue comment email I received:

<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/nix-rust/nix/issues/363#issuecomment-215311264"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

---

NB For GMail, the domain must be whitelisted via a webform; see guidelines. Frustratingly, the guidelines state

We are currently only approving Go-To actions for very specific high-value usecase with high interaction rate (e.g. Flight Check-in, Shipment tracking links).

For the other sender guidelines, Community seems in good shape:

• Emails must be authenticated via DKIM or SPF
• The top-level domain (TLD) of the SPF check or DKIM signature must match the TLD of your From: email address.
• Emails must come from a static email address, e.g. foo@bar.com
• Emails must follow the Gmail Bulk Sender Guidelines
• 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.
• A very very low rate of spam complaints from users.

The main issues are the from address, which is also discussed in #321, and the volume, which I can't speak for.

The changes are simple enough that this could be added in hopes that they'd allow it. They would also benefit any other clients that use the metadata.

[zachallaun]

Hey Kamal! Thanks for all the info here. I haven't missed or forgotten
about this, but have been heads-down on some other dev priorities. I hope
to carve out some time for Community issues soon.

On Tue, May 17, 2016 at 11:14 AM Kamal Marhubi notifications@github.com
wrote:

This would allow messages to include a "View thread" (or similar) link.
This is how GitHub "View Issue" and "View Pull Request" links get included
in the GMail and Google Inbox interfaces. (See note below on GMail
requiring registration.)

More information:

• ViewAction on schema.org http://schema.org/ViewAction
• Google developer documentation on ViewAction
  https://developers.google.com/gmail/markup/reference/go-to-action#view_action

The changes are simply adding more to the message templates. The code from
a recent GitHub issue comment email I received:

---

NB For GMail, the domain must be whitelisted via a webform; see
guidelines
https://developers.google.com/gmail/markup/registering-with-google.
Frustratingly, the guidelines state

We are currently only approving Go-To actions for very specific high-value
usecase with high interaction rate (e.g. Flight Check-in, Shipment tracking
links).

For the other sender guidelines, Community seems in good shape:

• Emails must be authenticated via DKIM or SPF
• The top-level domain (TLD) of the SPF check or DKIM signature must
  match the TLD of your From: email address.
• Emails must come from a static email address, e.g. foo@bar.com
• Emails must follow the Gmail Bulk Sender Guidelines
• 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.
• A very very low rate of spam complaints from users.

The main issues are the from address, which is also discussed in #321
#321, and the volume,
which I can't speak for.

The changes are simple enough that this could be added in hopes that
they'd allow it. They would also benefit any other clients that use the
metadata.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#333

[kamalmarhubi]

@zachallaun it's unclear that Community would meet Google's criteria anyway, which is the main place this would be useful, I think.