google-schemas

Can't get gmail one click confirm action button working

落花浮王杯 提交于 2019-12-09 01:23:48
问题 I am following the guidelines as described here https://developers.google.com/gmail/schemas/reference/one-click-action But It's just wont appear for me. As described here Self testing 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. I am using my same gmail address in both to and from

Efficient way of syncing Gmail Inbox messages using the new Gmail API?

隐身守侯 提交于 2019-12-08 13:54:20
问题 A web application sends an email on behalf of a UserA to UserB , using the new Gmail API ( Users.messages: send ). The synchronous response contains threadId , messageId which are stored in the database. We then query the history API for any changes in user's inbox ( Users.history: list ). Is there an efficient way to get all the updates since last sync (new replies, read/unread changes)? One implementation that we tried was to filter the history API results through a custom label.

Google Schema button not showing up when testing

只谈情不闲聊 提交于 2019-12-08 06:51:15
问题 I'm testing my schema button by sending to myself (I am overriding the "From" email header address with my gmail address to test from the server that sends the email). Both recipient and sender are my gmail email address. The schema shows up when I view the original email, but I don't see any buttons in my inbox. Here is the script tag I am sending as part of my HTML email template: <script type="application/ld+json"> { "@context": "schema.org", "@type": "EmailMessage", "description": "User

Gmail Actions in Inbox: End to end example with google apps account

被刻印的时光 ゝ 提交于 2019-12-05 18:31:43
Is there a restriction with google apps accounts to test actions in inbox with schema? I tried the example but no buttons showed in inbox. The app was created with a google apps account in appengine. The received mail is : Delivered-To: XXX@XXX.XXX Received: by 10.70.62.71 with SMTP id w7csp85423pdr; Fri, 24 May 2013 07:05:48 -0700 (PDT) X-Received: by 10.236.167.199 with SMTP id i47mr2955609yhl.91.1369404348508; Fri, 24 May 2013 07:05:48 -0700 (PDT) Return-Path: <3vHOfUQoJBbMfXebTVbhglZfTbe.VhfWTkbhZnsbd.Vhf.Tk@2uix4h7xygsz66weerlq.apphosting.bounces.google.com> Received: from mail-gh0-f200

Testing Gmail Schemas Fails

≯℡__Kan透↙ 提交于 2019-12-05 01:59:40
问题 I'm trying to test Gmail Schemas where the sender and the recipient are the same(mine) account following the Self Testing Notes 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. but without the expected result, the "Action" button is not displayed. I have tried using both the JSON-LD and

Does Google Schema support quoted-printable encoding?

主宰稳场 提交于 2019-12-04 11:49:38
I'm trying to self-test my email schemas. My mail is sent with: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable The original script tag <script type="application/ld+json"> is rendered as <script type=3D"application/ld+json"> , when I View Original the marked up email. This fails the markup tester , but when I manually remove the 3D , it passes the test. Q1 - Does Google support quoted-printable encoding? Q2 - Why does the test fail? Note: On a Rails application I use the Mandrill API to send the email. 1.) Yes, quoted-printable is supported. 2.) You're

access delegated mail folder with gmail api

三世轮回 提交于 2019-12-04 07:14:37
问题 let's say there are alice@gmail.com and bob@gmail.com. Alice has delegated her account to Bob. When I authenticate with Bob and try to list Alice inbox using the REST interface I get a 403 error: bob@gmail.com does not have privileges to alice@gmail.com mailbox. The URL used to query the inbox is: www.googleapis.com/gmail/v1/users/alice@gmail.com/messages When I use bob@gmail.com (or me) as userId there is no problem. How do I access Alice's account? Greetings 回答1: You would need to get alice

Testing Gmail Schemas Fails

≯℡__Kan透↙ 提交于 2019-12-03 17:11:05
I'm trying to test Gmail Schemas where the sender and the recipient are the same(mine) account following the Self Testing Notes 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. but without the expected result, the "Action" button is not displayed. I have tried using both the JSON-LD and Microdata without results. Here the "Show original" of the email from my Gmail Account: Return-Path:

Google Now Event card - How to display more information

一世执手 提交于 2019-12-03 05:04:35
I'm testing the Event card in Google Now through adding schema data to a confirmation email. At the moment I'm playing around with populating the event card with rail journey info, since the rail journey schema isn't supported. Unfortunately, I can only get a tiny amount of the info provided to show in the card in Google Now. Here's what I'm adding to the email: <html> <body> <script type="application/ld+json"> { "@context": "http://schema.org", "@type": "EventReservation", "reservationNumber": "123456789", "reservationStatus": "http://schema.org/Confirmed", "url": "http://www.eastcoast.co.uk"

RFC822 Message-Id in new Gmail API

好久不见. 提交于 2019-12-02 13:19:54
问题 We are trying to set manually the RFC822 Message-Id when sending emails using the gmail api. We have tested but seen that Gmail overrides our value. Do you know if there is a reason for this? Can we do something for this? 回答1: Yes the Message-Id is always set for mail sending to be the proper format for outgoing Gmail mail, the same format as the web interface. What exactly is reason for needing to specify your own value instead of using either the message.id value returned during send for