我正在尝试按照自我测试说明测试发件人和收件人是相同（我的）帐户的Gmail 架构
您可以通过向您的 Gmail 帐户发送带有架构的电子邮件来轻松测试您的标记是否在端到端正常工作。发件人和收件人为同一账号的所有邮件均忽略注册要求，可用于自测。
但没有预期的结果，“操作”按钮不显示。
我尝试使用 JSON-LD 和 Microdata 都没有结果。
这里是来自我的 Gmail 帐户的电子邮件的“显示原件”：
Return-Path: <fake-account-email-x@gmail.com>
Received: *****
Message-ID: <fake-email-id@gmail.com>
Date: Tue, 12 Nov 2013 09:41:53 +0100
From: Cristian <fake-account-email-x@gmail.com>
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
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div itemscope="" itemtype="http://schema.org/EmailMessage">
<meta itemprop="description" content="Approval request for John's
$10.13 expense for office supplies">
<div itemprop="action" itemscope=""
itemtype="http://schema.org/ConfirmAction">
<meta itemprop="name" content="Approve Registration">
<div itemprop="handler" itemscope=""
itemtype="http://schema.org/HttpActionHandler">
<link itemprop="url" href="http://www.example.com/">
</div>
</div>
</div>
<h1>Ciao ${FIRSTNAME}$</h1>
<ul>
<li>punto 1</li>
<li>punto 2</li>
<li>punto 3</li>
</ul>
</body>
</html>
--------------090703050903040805020509--
以及它在列表中的显示方式：
在消息中：
我还通过标记测试器验证了我的代码
我的测试中的错误在哪里？我想不通:(
更新 20131113
正如 Devnook 所建议的那样，通过Test Gmail Schemas发送电子邮件一切正常，但使用我的 Thunderbird 客户端（通过 SMTP 使用我的帐户）不行。
这里是来自“Test Gmail Schema”的测试来源
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: <3yyCDUg0JErIYeSad-SUlagfkYeSad.UgeUjaklaSf.hgjlS.UjpYeSad.Uge@2UIX4H7XYGSZ66WEERLQ.apphosting.bounces.google.com>
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: <fake-email-id@google.com>
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
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div itemscope="" itemtype="http://schema.org/EmailMessage">
<meta itemprop="description" content="Approval request for John's
$10.13 expense for office supplies">
<div itemprop="action" itemscope=""
itemtype="http://schema.org/ConfirmAction">
<meta itemprop="name" content="Approve Registration">
<div itemprop="handler" itemscope=""
itemtype="http://schema.org/HttpActionHandler">
<link itemprop="url" href="http://www.example.com/">
</div>
</div>
</div>
<h1>Ciao ${FIRSTNAME}$</h1>
<ul>
<li>punto 1</li>
<li>punto 2</li>
<li>punto 3</li>
</ul>
</body>
</html>
--001a11c2c63a28cf0504eb095b6e--
“大”区别在于这封电子邮件的标题包含 DKIM-Signature 和 SPF，但在理论上emails where the sender and the recipient are the same account ignore the registration requirements
在这里它如何显示“正确”的电子邮件
