Note that there are some explanatory texts on larger screens.

plurals
  1. POTesting Gmail Schemas Fails
    text
    copied!<p>I'm trying to test <a href="https://developers.google.com/gmail/actions/" rel="nofollow noreferrer">Gmail Schemas</a> where the sender and the recipient are the same(mine) account following the <a href="https://developers.google.com/gmail/actions/testing-your-schema" rel="nofollow noreferrer">Self Testing Notes</a></p> <blockquote> <p>You can easily test if your markup is working correctly end-to-end by sending emails with schemas to your Gmail account. All emails where the sender and the recipient are the same account ignore the registration requirements and can be used for self-testing.</p> </blockquote> <p>but without the expected result, the "Action" button is not displayed.</p> <p>I have tried using both the JSON-LD and Microdata without results.</p> <p>Here the "Show original" of the email from my Gmail Account:</p> <pre><code>Return-Path: &lt;fake-account-email-x@gmail.com&gt; Received: ***** Message-ID: &lt;fake-email-id@gmail.com&gt; Date: Tue, 12 Nov 2013 09:41:53 +0100 From: Cristian &lt;fake-account-email-x@gmail.com&gt; User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 MIME-Version: 1.0 To: fake-account-email-x@gmail.com Subject: test Content-Type: multipart/alternative; boundary="------------090703050903040805020509" This is a multi-part message in MIME format. --------------090703050903040805020509 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Ciao ${FIRSTNAME}$ * punto 1 * punto 2 * punto 3 --------------090703050903040805020509 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit &lt;html&gt; &lt;head&gt; &lt;meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"&gt; &lt;/head&gt; &lt;body bgcolor="#FFFFFF" text="#000000"&gt; &lt;div itemscope="" itemtype="http://schema.org/EmailMessage"&gt; &lt;meta itemprop="description" content="Approval request for John's $10.13 expense for office supplies"&gt; &lt;div itemprop="action" itemscope="" itemtype="http://schema.org/ConfirmAction"&gt; &lt;meta itemprop="name" content="Approve Registration"&gt; &lt;div itemprop="handler" itemscope="" itemtype="http://schema.org/HttpActionHandler"&gt; &lt;link itemprop="url" href="http://www.example.com/"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;h1&gt;Ciao ${FIRSTNAME}$&lt;/h1&gt; &lt;ul&gt; &lt;li&gt;punto 1&lt;/li&gt; &lt;li&gt;punto 2&lt;/li&gt; &lt;li&gt;punto 3&lt;/li&gt; &lt;/ul&gt; &lt;/body&gt; &lt;/html&gt; --------------090703050903040805020509-- </code></pre> <p>And here how it appears from the list:</p> <p><img src="https://i.stack.imgur.com/Sh2Up.jpg" alt="enter image description here"></p> <p>And inside the message:</p> <p><img src="https://i.stack.imgur.com/w9Co7.jpg" alt="enter image description here"></p> <p>I have also validated my code via the <a href="https://www.google.com/webmasters/markup-tester/" rel="nofollow noreferrer">Markup Tester</a> </p> <p>Where is the error in my test? I can't figure out :(</p> <h1>UPDATE 20131113</h1> <p>Sending the email via <a href="http://gmail-actions.appspot.com/" rel="nofollow noreferrer">Test Gmail Schemas</a>, as suggested Devnook, all works fine, but using my Thunderbird client(using my account via SMTP) nope.</p> <p>Here the source from the test via "Test Gmail Schema"</p> <pre><code>Delivered-To: fake-account-email-x@gmail.com Received: by 10.224.58.135 with SMTP id g7csp190326qah; Tue, 12 Nov 2013 22:48:43 -0800 (PST) X-Google-DKIM-Signature: ********* X-Original-Authentication-Results: ******** Return-Path: &lt;3yyCDUg0JErIYeSad-SUlagfkYeSad.UgeUjaklaSf.hgjlS.UjpYeSad.Uge@2UIX4H7XYGSZ66WEERLQ.apphosting.bounces.google.com&gt; Received-SPF: pass ******** Authentication-Results: mr.google.com; spf=pass ******** X-Received: from mr.google.com ([10.224.24.65]) by 10.224.24.65 with SMTP id u1mr35599473qab.6.1384325323511 (num_hops = 1); Tue, 12 Nov 2013 22:48:43 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.224.24.65 with SMTP id u1mr25556165qab.6.1384325323474; Tue, 12 Nov 2013 22:48:43 -0800 (PST) X-Google-Appengine-App-Id: s~gmail-actions X-Google-Appengine-App-Id-Alias: gmail-actions Message-ID: &lt;fake-email-id@google.com&gt; Date: Wed, 13 Nov 2013 06:48:43 +0000 Subject: Testing Gmail Actions 2013-11-13 06:48 From: fake-account-email-x@gmail.com To: fake-account-email-x@gmail.com Content-Type: multipart/alternative; boundary=001a11c2c63a28cf0504eb095b6e --001a11c2c63a28cf0504eb095b6e Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Ciao ${FIRSTNAME}$ punto 1 punto 2 punto 3 --001a11c2c63a28cf0504eb095b6e Content-Type: text/html; charset=ISO-8859-1 &lt;html&gt; &lt;head&gt; &lt;meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"&gt; &lt;/head&gt; &lt;body bgcolor="#FFFFFF" text="#000000"&gt; &lt;div itemscope="" itemtype="http://schema.org/EmailMessage"&gt; &lt;meta itemprop="description" content="Approval request for John's $10.13 expense for office supplies"&gt; &lt;div itemprop="action" itemscope="" itemtype="http://schema.org/ConfirmAction"&gt; &lt;meta itemprop="name" content="Approve Registration"&gt; &lt;div itemprop="handler" itemscope="" itemtype="http://schema.org/HttpActionHandler"&gt; &lt;link itemprop="url" href="http://www.example.com/"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;h1&gt;Ciao ${FIRSTNAME}$&lt;/h1&gt; &lt;ul&gt; &lt;li&gt;punto 1&lt;/li&gt; &lt;li&gt;punto 2&lt;/li&gt; &lt;li&gt;punto 3&lt;/li&gt; &lt;/ul&gt; &lt;/body&gt; &lt;/html&gt; --001a11c2c63a28cf0504eb095b6e-- </code></pre> <p>The "big" difference are that the headers of this email contains the DKIM-Signature and SPF but in theory <code>emails where the sender and the recipient are the same account ignore the registration requirements</code></p> <p>Here how it appear the "correct" email </p> <p><img src="https://i.stack.imgur.com/HTSCH.jpg" alt="enter image description here"></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload