Attendee is accepting a meeting created previously by organizer and received via email as ics file.
Here's a reply attendee is sending:
BEGIN:VCALENDAR
VERSION:2.0
METHOD:REPLY
PRODID:-//XXX//YYY//EN
BEGIN:VEVENT
UID:6i4roaen7444fh8n1imnq75ujt#google.com
STATUS:CONFIRMED
DTSTAMP:20190406T082440Z
DTSTART:20190406T180000Z
DTEND:20190406T190000Z
ORGANIZER;CN=organizer#gmail.com:MAILTO:organizer#gmail.com
SEQUENCE:0
SUMMARY:qwerty
DESCRIPTION:-::~:[CUT]:~:~::-
LOCATION:
ATTENDEE;CN=organizer#gmail.com;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RS
VP=TRUE:MAILTO:organizer#gmail.com
ATTENDEE;CN=attendee#gmail.com;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED
;RSVP=TRUE:MAILTO:attendee#gmail.com
END:VEVENT
END:VCALENDAR
...and an email attendee is sending back to the organizer:
Content-Type: text/calendar; charset="utf-8"; name="qwerty.ics"; method="REPLY"
Content-Transfer-Encoding: 7bit
Content-class: urn:content-classes:calendarmessage
MIME-Version: 1.0
Date: Sat, 06 Apr 2019 10:34:40 +0200
Message-ID: <6dc076ea-6770-4e6a-bc62-a6c630d38f14#example.com>
From: <attendee#gmail.com>
To: <organizer#gmail.com>
BEGIN:VCALENDAR
[CUT]
END:VCALENDAR
Organizer simply gets the email in his inbox (ics is shown as attachment) but calendar event is not updated with the attendee status.
I know what the problem is - duplicated ATTENDEE row.
Related
When trying to see AMP mail that received from AWS SES using a python script - I'm able to see only the HTML part and not the AMP part. I'm using Gmail on a web/desktop (not mobile).
I've been able to get emails from the Gmail amp playground (https://amp.gmail.dev/playground/) but no from my domain (using the developer options for my domain).
I've been qualified for the pre-requirements, such as DKIM, DMARC, and SPF for my domain - I've attached a screenshot for this qualification.
I've made sure that my mail contains only the minimal AMP content, and the MIME tree is organized in good order (the AMP appears before the HTML).
This is the mail that I'm getting on Gmail:
Delivered-To: XXXXXX
Received: by 2002:adf:a2ce:0:0:0:0:0 with SMTP id t14csp9667034wra;
Wed, 24 Jul 2019 00:50:42 -0700 (PDT)
X-Google-Smtp-Source: APXvYqwL5fGpFWN69lea/kepakqVoHfUbXMCm3R8pyGZW6SRJECQp/PJWL0TCVXLGPJH12TGQjPR
X-Received: by 2002:a50:e618:: with SMTP id y24mr69652549edm.142.1563954642448;
Wed, 24 Jul 2019 00:50:42 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1563954642; cv=none;
d=google.com; s=arc-20160816;
b=UIjwFXJ2f8uivW5CMliod/HeaqPgDEoPrLbJrGP1poPzSts/Ifv4asIs2Z5S1/oh5k
vKkAijZY38K6osr/Vh6cYhQSl2mAX8PAj5yqsrcEqJJxpQK0WZ43LBvhw5yVCe/20xnm
40XtgTp0pc2tQBnAxmMwdQs4/OebZx418KBGfoN3ZKStMU6S1vC69uadG3sQKyS9DfZ7
ioQh8rooPSPYBqVGO80jfwx2p5XldxFyfPsmks7H+jIAFMov7i6Z4qA14GtBMwiHt13E
5IgAtTDQneCR02krKwUCygYqYA1BU7U5F1wmNLUBQgfHgTSQwHRDv3HUIJVr4OwflMAx
SMkg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=feedback-id:date:message-id:to:from:subject:mime-version
:dkim-signature:dkim-signature;
bh=u8zKbqJArDsMg9NesmbsCH3q/TsRUKtAsLWu0QFVgOk=;
b=zIaivJ+RHM+PI6cjXZ/qTgh4Jl1caUIrdM8ljwaH8x9DrQzZFiLBlKzdKVjoPNnaa8
EIdn/+wIuPfvv7p02Gk4J71s41/Y3we6QIhsi9ZT7OGqopLb8fkcsqKLD4eD39MGfWOa
cpfWPLW+B8UqO9v2gKRLn622Y4XYtH8flYZSfOftMqd1fboTz9vMY5L+clYttZLyUIdn
0F59JyIB3oVtqqAqgfNje6ikbQvmGNxGob6UhUHt0EKQ7cS83S0NnV/P7KLtzQL17ld3
iFN3QgyPDJlNz44G4YR2S220pD8EyXj+Btz/gi9omqml+moLnWKwGTZx97lFlnfDYp2O
CXHA==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass header.i=#amiramen.com header.s=kz7cgy5efrrjqoowmf3kdany4nxqx5im header.b=yPnbkTNf;
dkim=pass header.i=#amazonses.com header.s=ihchhvubuqgjsxyuhssfvqohv7z3u4hn header.b="Iv9/seaV";
spf=pass (google.com: domain of 0102016c22f5fbce-fbba54af-35b0-4791-8877-32699f0c9e58-000000#eu-west-1.amazonses.com designates 54.240.7.37 as permitted sender) smtp.mailfrom=0102016c22f5fbce-fbba54af-35b0-4791-8877-32699f0c9e58-000000#eu-west-1.amazonses.com;
dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=amiramen.com
Return-Path: <0102016c22f5fbce-fbba54af-35b0-4791-8877-32699f0c9e58-000000#eu-west-1.amazonses.com>
Received: from a7-37.smtp-out.eu-west-1.amazonses.com (a7-37.smtp-out.eu-west-1.amazonses.com. [54.240.7.37])
by mx.google.com with ESMTPS id h3si44113583wrx.267.2019.07.24.00.50.42
for <mXXXXXX#gmail.com>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
Wed, 24 Jul 2019 00:50:42 -0700 (PDT)
Received-SPF: pass (google.com: domain of 0102016c22f5fbce-fbba54af-35b0-4791-8877-32699f0c9e58-000000#eu-west-1.amazonses.com designates 54.240.7.37 as permitted sender) client-ip=54.240.7.37;
Authentication-Results: mx.google.com;
dkim=pass header.i=#amiramen.com header.s=kz7cgy5efrrjqoowmf3kdany4nxqx5im header.b=yPnbkTNf;
dkim=pass header.i=#amazonses.com header.s=ihchhvubuqgjsxyuhssfvqohv7z3u4hn header.b="Iv9/seaV";
spf=pass (google.com: domain of 0102016c22f5fbce-fbba54af-35b0-4791-8877-32699f0c9e58-000000#eu-west-1.amazonses.com designates 54.240.7.37 as permitted sender) smtp.mailfrom=0102016c22f5fbce-fbba54af-35b0-4791-8877-32699f0c9e58-000000#eu-west-1.amazonses.com;
dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=amiramen.com
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=kz7cgy5efrrjqoowmf3kdany4nxqx5im; d=amiramen.com; t=1563954642;
h=Content-Type:MIME-Version:Subject:From:To:Message-ID:Date;
bh=u8zKbqJArDsMg9NesmbsCH3q/TsRUKtAsLWu0QFVgOk=;
b=yPnbkTNfpn2pwgrkQMLEnU4/CGK+n+l9o1JAY0HRREmfweP9MVjXgKUTAJUbDSOC
htjTUMZkICok+YIbJQBE/1+E+Za5vBaA9EYxiM4lFFfMoQeLvQWQ3l5r8FJ5Dquzb+h
f/9E3oinynOL6JkGFDuASLVj8SBCWlaEEirGe6Uk=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=ihchhvubuqgjsxyuhssfvqohv7z3u4hn; d=amazonses.com; t=1563954642;
h=Content-Type:MIME-Version:Subject:From:To:Message-ID:Date:Feedback-ID;
bh=u8zKbqJArDsMg9NesmbsCH3q/TsRUKtAsLWu0QFVgOk=;
b=Iv9/seaVrzV/GlvUAzt4ux3U4GEmK8mvSIzyMDZDCF+/Q9KGiN56gFGPlIyYskk3
5ENiJstFwKaOiSTEnyXgaCJAt6VxQlxsCwhvh2vKZIsT//p4d5ZDLv1PnuxkF78+e3i
MkLha3uWP+RD2ayol6NnqGa0psfPYqkNn3EyMp/k=
Content-Type: multipart/alternative; boundary="===============2017642074=="
MIME-Version: 1.0
Subject: Hey, Wizard! Check out this dynamic email. #2
From: team#amiramen.com
To: XXXXX#gmail.com
Message-ID: <0102016c22f5fbce-fbba54af-35b0-4791-8877-32699f0c9e58-000000#eu-west-1.amazonses.com>
Date: Wed, 24 Jul 2019 07:50:41 +0000
X-SES-Outgoing: 2019.07.24-54.240.7.37
Feedback-ID: 1.eu-west-1.sAWpWQT4Rmzt8hbl9MsPloIFHFP494ZwRbh0mXyiwjI=:AmazonSES
--===============2017642074==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
THVtb3MhIEluIHBsYWluIHRleHQu
--===============2017642074==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
PGh0bWw+Cjxib2R5PgogIDxwPkV4cGVsbGlhcm11cyEgSW4gSFRNTC48L3A+CjwvYm9keT4KPC9o
dG1sPgo=
--===============2017642074==
Content-Type: text/x-amp-html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
PCFkb2N0eXBlIGh0bWw+CjxodG1sID1FMj05QT1BMTRlbWFpbD4KPGhlYWQ+CiAgPG1ldGEgY2hh
cnNldD0zRCJ1dGYtOCI+CiAgPHNjcmlwdCBhc3luYyBzcmM9M0QiaHR0cHM6Ly9jZG4uYW1wcHJv
amVjdC5vcmcvdjAuanMiPjwvc2NyaXB0PgogIDxzdHlsZSBhbXA0ZW1haWwtYm9pbGVycGxhdGU+
Ym9keXt2aXNpYmlsaXR5OmhpZGRlbn08L3N0eWxlPgo8L2hlYWQ+Cjxib2R5PgogIEhlbGxvLCBB
TVA0RU1BSUwgd29ybGQuCjwvYm9keT4KPC9odG1sPgo=
--===============2017642074==--
I expecting to see the AMP part in my Gmail web-desktop client. What did I do wrong?
We are using Gmail API to send email. As per Gmail documentation we can send upto 500 emails per day but when we send more than 60 email we are getting this error on our Gmail account.
You have reached a limit for sending mail. Your message was not sent.
As per our code logic we are sending text email and one email in every two min to avoid Google API 100 second Quota. We have also checked the API console and in the last few days we have not reached our Quotas limit and not Received any errors but we are getting the above mention Error in our Gmail account. One last thing we want to mention is that we are only using Gmail send service. Thanks in advance.
Edit 1 :
We are only using one email address per email and this is our message original.
> Delivered-To: xyz#gmail.com
Received: by 10.36.69.2 with SMTP id y2csp7268660ita;
Mon, 23 Oct 2017 05:57:25 -0700 (PDT)
X-Received: by 10.157.40.142 with SMTP id s14mr7651348ota.123.1508763444992;
Mon, 23 Oct 2017 05:57:24 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1508763444; cv=none;
d=google.com; s=arc-20160816;
b=00GKWt5YJyup/zRaygHJ3YjdXhfUTp24XlsHFbRPJtoN4umiasNg/fhQ59VSR8cu4Q
Z2CLHOVxD9FoNb0UW3+4SJAHyrAaf2ZUnvbh9kUMNenVSNk1zYX2DaumMnaiUI+75eCj
oNzFEV4i5Ja/WQbr8kYziynh6d3oFgX81JqAC9ptphoZ2L3TJt0rxli/77+eNF2c7HSs
YTXDdsd2i8Hmm+aWaYQ/h5u8YABWmkiOFX/6xqAbxcBH65Ye1uLFR1+uWPPfcmzd13GC
KOyRbcbq5WAMBXI14Xuit+llwE9IgSb6dtiFxJ8oYNHZa4GBsv2HzaTiRrZeoc41rNEK
qWHA==ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed d=google.com; s=arc-20160816;
h=to:subject:message-id:date:mime-version:from:dkim-signature
:arc-authentication-results;
bh=TRygSnH7m96UEJAVfmK31uQcIqHJNyzan4DHUUOb9L0=;
b=HANggRPcRICCeKYpqmsbnYKcsMi8esLWFTf5tPLV8dXcXeLudPJtxPr2nOT5KK8ezt
Orgm6voF+si5jYJInKwLDmCpFrY9jogQQP39yknN9H0SqPH+awtn0HT4dvoeq9Wnr3Sq
dGPfQbqtYyT7T8ISDuT5rsjB2zI61Md8eWOCRO/dbfv+lovyYbfUbwoVG73LhSv4hGeX
2Nk0Lki/4DesnLk98wdUbwchY6Y78Trns1+tfi7awSClXlaobje2K4hz7i1y96R+9kpn
0yYGfTLtlCc65QfsKXJnSF42kZ32HlttuBQRjb5W6ua8gEBCCffxydD/v4cQ3e8iVSaT
UPWw==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass header.i=#gmail.com header.s=20161025 header.b=GLxhRGM2;
spf=pass (google.com: domain of xyz#gmail.com designates 209.85.220.65 as permitted sender) smtp.mailfrom=xyz#gmail.com;
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com
Return-Path: <xyz#gmail.com>
Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65])
by mx.google.com with SMTPS id j196sor1073671oib.38.2017.10.23.05.57.24
for <xyz#gmail.com>
(Google Transport Security);
Mon, 23 Oct 2017 05:57:24 -0700 (PDT)
Received-SPF: pass (google.com: domain of xyz#gmail.com designates 209.85.220.65 as permitted sender) client-ip=209.85.220.65;
Authentication-Results: mx.google.com;
dkim=pass header.i=#gmail.com header.s=20161025 header.b=GLxhRGM2;
spf=pass (google.com: domain of xyz#gmail.com designates 209.85.220.65 as permitted sender) smtp.mailfrom=xyz#gmail.com;
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20161025;
h=from:mime-version:date:message-id:subject:to;
bh=TRygSnH7m96UEJAVfmK31uQcIqHJNyzan4DHUUOb9L0=;
b=GLxhRGM2PoE2cV4Kv157dJ1SiFzqBCvjV9ksWGdO+3fm+NluMUY5qZ2XeDWsfxEqCV
AarV0FEoPqFEUkeDUpiwwz6FYRlPcqYGX91CQLyitB4QE4FHSzseiPFI8S21xXdqUn8X
wLnNW9k1fPs1y07d8OMP6CKmu5Cf3t2vbCieNj2/Btg4Ga3rDTpKo+LPdbyM0Oddr7ZZ
28W/iX/w3Q23fXZHhnpV5KKUab84df3fjSq5Vh/7WccUeAHIfudJQyn71xwjbpXGRxP+
iIILNOY6OR3lymHWXUki7FADK5/CREGfuKQJO0axZ/EUHYH942TAW/q74G3lGHNb5Dmq
4eqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:from:mime-version:date:message-id:subject:to;
bh=TRygSnH7m96UEJAVfmK31uQcIqHJNyzan4DHUUOb9L0=;
b=ThGC7Ye92WeBnpv88tssmK3jxoTh75t0TE0YSwIe7neSPQ9nkd02LfUy2E2I5DYYJl
Yu03UIUCnEyCECDx2N1chki4ifgXBMIXT2MNaN/V3dveaLEc3C8jyF3loTvTSFC63Sv/
fxsQgBQNmtH/RqkxG+c1rFGjclTdvmTaERHB2IiAuVzuEyAXaeFS6pippckq8W4CkfMb
VLawraTAdqKvgfCUEe7O6AdPhsaCSkWNgrBhigIXaVOSEnVAnywNeGxOzxZ6iK/vdUAT
bTJQTap/OL80gGk8or8MMuKDg1wNhv2PWyCUG/OASdY0FELNmj9gkcyeGJMmNBtLVfUy
3fPA==
X-Gm-Message-State: AMCzsaUOyy2JRzefxuZ+o3ROgrkTqFWfyu7Ox69vaaKaM19XX0T+88Th qGn9LmtYLTmLeVaaakvk3IeYDENzVWdRJwFw0BM=
X-Google-Smtp-Source: ABhQp+TqkpdDhP6uWvv5qUap3QIYchZYDradVOJSJlPXHTlHNnZBUXUQ7vdOdo5XThqLprbv/VlFJANYzjGyQg+QpAo=
X-Received: by 10.202.90.3 with SMTP id o3mr6602265oib.27.1508763444353; Mon, 23 Oct 2017 05:57:24 -0700 (PDT)
Received: from 385619130527 named unknown by gmailapi.google.com with HTTPREST; Mon, 23 Oct 2017 05:57:23 -0700
From: XYZ <XYZ#gmail.com>
MIME-Version: 1.0
Date: Mon, 23 Oct 2017 05:57:23 -0700
Message-ID: <CALB+=oPhh7AmZJSyimZXZb38SwNAD7eMFioUFv6GmZzdcWrU9A#mail.gmail.com>
Subject: Important Game
To: xyz#gmail.com
Content-Type: multipart/alternative; boundary="001a113d5edc26a056055c365d7e"
--001a113d5edc26a056055c365d7e
Content-Type: text/plain; charset="UTF-8"
I am using PHPMailer.
I added DKIM attributes when sending file.
The code is like:
// $mail is PHPMailer class
$mail->SMTPAuth = true;
$mail->SMTPSecure = "ssl";
$mail->Host = "*******";
$mail->Port = ***;
$mail->Mailer= "SMTP";
//...
$mail->DKIM_domain = 'mydomain.com';
$mail->DKIM_identity = '#mydomain.com';
$mail->DKIM_private = __DIR__ . '/privacy_key_mydomain.txt';
$mail->DKIM_selector = 'default';
$mail->DKIM_passphrase = ''; // only ssl.
//...
(Same as example on: Send mail in phpmailer using DKIM Keys)
When sending to email, such as mine (gmail), I have no problem, and I see that my email is signed by mydomain.com.
I see also, in the email source that DKIM-Signature is sent.
Nevertheless, some of my clients I am sending emails reject my email, with following message (especially for yahoo emails - more that 90% of rejects uses yahoo for their emails).
554 Message not allowed - Headers are not RFC compliant[291]
As I did some workaround, I found this message to be detected as a spam.
I am using CPANEL for my site, which has round-cube - so I test it at round-cube (sending the customer a message with round-cube) - seems OK. No spam detect.
So, I suspect the privacy key file may be incorrect (I have an SSL site - so I use the same privacy key as my own site).
What may be wrong? What shall I check out in order to avoid my emails will be detected as spams?
Here is the email source result:
Delivered-To: myaccount#gmail.com
Received: by 10.114.75.12 with SMTP id y12csp118366ldv;
Tue, 15 Jul 2014 11:44:11 -0700 (PDT)
X-Received: by 10.140.104.49 with SMTP id z46mr36090427qge.74.1405449850437;
Tue, 15 Jul 2014 11:44:10 -0700 (PDT)
Return-Path: <support#mydomain.com>
Received: from lin9.maindomain10.net (lin9.maindomain10.net. [1.2.3.4])
by mx.google.com with ESMTPS id t14si21957304qac.66.2014.07.15.11.44.09
for <myaccount#gmail.com>
(version=TLSv1 cipher=RC4-SHA bits=128/128);
Tue, 15 Jul 2014 11:44:10 -0700 (PDT)
Received-SPF: pass (google.com: domain of support#mydomain.com designates 1.2.3.4 as permitted sender) client-ip=1.2.3.4;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of support#mydomain.com designates 1.2.3.4 as permitted sender) smtp.mail=support#mydomain.com;
dkim=pass header.i=#mydomain.com
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mydomain.com; s=default;
h=Content-Type:Content-Transfer-Encoding:MIME-Version:Message-ID:Subject:Reply-To:From:To:Date:Subject:To; bh=HBLjhR1eb0w5FQ9aVj60Gu0x3jP9XWQ7LQkpzTRHjfQ=;
b=ECWMCs3iPsjuvlT473K9u3skwyNRVunmnv3p440Nk2ZJVrbuWoO0vgzaWM8gjCC503ADKivdfrrOek8TgTSEI7G4B3WMCHI50PWq68W5rcscYJqErWxuqAVcSl4r5tomk88AYPhHiotCugmRTjwQ2K/JBtHsAvMhTlVQMMXsMl0=;
Received: from mainuser by lin9.maindomain10.net with local (Exim 4.82)
(envelope-from <support#mydomain.com>)
id 1X77hp-0001f9-SH; Tue, 15 Jul 2014 14:44:01 -0400
To: myName Mizrahi <myaccount#gmail.com>
Subject: Statistics from Sample Name site
Date: Tue, 15 Jul 2014 14:44:01 -0400
To: myName Mizrahi <myaccount#gmail.com>
From: "donotreply#mydomain.com" <root#localhost>
Reply-To: Sample Name site <donotreply#mydomain.com>
Subject: Statistics from Sample Name site
Message-ID: <d984a2c6308ef2a97cf6ccfe6292263a#mydomain.com>
X-Priority: 3
X-Mailer: PHPMailer 5.2.4 (http://code.google.com/a/apache-extras.org/p/phpmailer/)
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=UTF-8
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - lin9.maindomain10.net
X-AntiAbuse: Original Domain - gmail.com
X-AntiAbuse: Originator/Caller UID/GID - [927 895] / [47 12]
X-AntiAbuse: Sender Address Domain - mydomain.com
X-Get-Message-Sender-Via: lin9.maindomain10.net: authenticated_id: mainuser/sender_address_domain
When sending message from round-cube, the email source look like this:
Delivered-To: myaccount#gmail.com
Received: by 10.114.75.12 with SMTP id y12csp118605ldv;
Tue, 15 Jul 2014 11:48:53 -0700 (PDT)
X-Received: by 10.224.161.129 with SMTP id r1mr34110372qax.86.1405450132678;
Tue, 15 Jul 2014 11:48:52 -0700 (PDT)
Return-Path: <support#mydomain.com>
Received: from lin9.maindomain10.net (lin9.maindomain10.net. [1.2.3.4])
by mx.google.com with ESMTPS id x8si13226659qas.81.2014.07.15.11.48.52
for <myaccount#gmail.com>
(version=TLSv1 cipher=RC4-SHA bits=128/128);
Tue, 15 Jul 2014 11:48:52 -0700 (PDT)
Received-SPF: pass (google.com: domain of support#mydomain.com designates 1.2.3.4 as permitted sender) client-ip=1.2.3.4;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of support#mydomain.com designates 1.2.3.4 as permitted sender) smtp.mail=support#mydomain.com;
dkim=pass header.i=#mydomain.com
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mydomain.com; s=default;
h=Message-ID:Subject:To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version; bh=Bynm51C7RZD/vZ81iEMKjxxLoAJtSmKFcwU/eyFzPs8=;
b=fUX+UKS9Ua0HK35AOBRBJbmqTEuKscCYAsPyxs3If3dhhvb/AvAjl1gR9Rz9AN0EX0mu275wtaN5Y1JWP+8w8VcGebJ9FEWsltCl9nwqL6bos/eEqJxTWjDG6ch9MHo3G0mSE326Pyc13JWa59InSgJyWi8MSstT1POfuEhfe28=;
Received: from localhost.localdomain ([127.0.0.1]:54911 helo=mydomain.com)
by lin9.maindomain10.net with esmtpa (Exim 4.82)
(envelope-from <support#mydomain.com>)
id 1X77mO-0001l7-1O
for myaccount#gmail.com; Tue, 15 Jul 2014 14:48:44 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
format=flowed
Content-Transfer-Encoding: 7bit
Date: Tue, 15 Jul 2014 14:48:43 -0400
From: support#mydomain.com
To: myaccount#gmail.com
Subject: test
Message-ID: <ed6307c2c9504e8ba9ec21f073d5f863#mydomain.com>
X-Sender: support#mydomain.com
User-Agent: Roundcube Webmail/0.9.5
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - lin9.maindomain10.net
X-AntiAbuse: Original Domain - gmail.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - mydomain.com
X-Get-Message-Sender-Via: lin9.maindomain10.net: authenticated_id: support#mydomain.com
Round-Cube works with no spam.
What is the main difference that's make the issue?
Thanks :)
5.2.4 is pretty old and buggy - You need to update to the latest PHPMailer from GitHub.
I'm trying to add View Action to my emails. For tests I'm send email from grif#ecwid.com to grif#ecwid.com
Example
Return-Path: <grif#ecwid.com>
Received: from 172.17.10.84 ([87.251.133.106])
by mx.google.com with ESMTPSA id bj7sm8223219lbc.22.2014.06.06.01.11.43
for <grif#ecwid.com>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Fri, 06 Jun 2014 01:11:44 -0700 (PDT)
Date: Fri, 06 Jun 2014 01:11:44 -0700 (PDT)
From: grif#ecwid.com
To: grif#ecwid.com
Message-ID: <1817181170.17.1402042304376.JavaMail.rinatgainullin#Rinats-MacBook-Pro-2.local>
Subject: =?UTF-8?B?0JTQvtCx0YDQviDQv9C+0LbQsNC70L7QstCw0YLRjCDQsiBFY3dpZCE=?=
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_15_1197020028.1402042304374"
------=_Part_15_1197020028.1402042304374
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
....
------=_Part_15_1197020028.1402042304374
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.=
w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns=3D"http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DU=
TF-8">
<title>=D0=94=D0=BE=D0=B1=D1=80=D0=BE =D0=BF=D0=BE=D0=B6=D0=B0=D0=
=BB=D0=BE=D0=B2=D0=B0=D1=82=D1=8C =D0=B2 Ecwid!</title>
=09=09
<style type=3D"text/css">
.....
</style></head>
<body leftmargin=3D"0" marginwidth=3D"0" topmargin=3D"0" marginheight=
=3D"0" offset=3D"0" style=3D"margin: 0;padding: 0;background-color: #ffffff=
;">
....
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
=09<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/ViewAct=
ion">
=09=09<link itemprop=3D"url" href=3D"https://my.grif.ecwid.com:8443/cp/vali=
date?h=3D123&ownerid=3D0"/>
=09=09<meta itemprop=3D"name" content=3D"=D0=9F=D0=BE=D0=B4=D1=82=D0=B2=D0=
=B5=D1=80=D0=B4=D0=B8=D1=82=D1=8C e-mail"/>
=09</div>
</div>
....
</body>
</html>
------=_Part_15_1197020028.1402042304374--
But my inbox letter looks like this http://i.stack.imgur.com/GAcs7.png
What I should to do to test my schema? Is this feature testing has any restriction?
Update
When I send mail for myself there are no dkim headers, but when my friend send me mail from his acc dkim header is present
No dkim
Return-Path: <grif#ecwid.com>
Received: from test-gmail-actions-0.gen.ec.ecwid.com (ec2-174-129-131-52.compute-1.amazonaws.com. [174.129.131.52])
by mx.google.com with ESMTPSA id s2sm10439008qaj.36.2014.06.26.02.45.56
for <grif#ecwid.com>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 26 Jun 2014 02:45:56 -0700 (PDT)
Date: Thu, 26 Jun 2014 02:45:56 -0700 (PDT)
From: Ecwid <grif#ecwid.com>
To: grif#ecwid.com
Message-ID: <22158846.2.1403775956083.JavaMail.root#test-gmail-actions-0>
Subject: =?UTF-8?B?0JTQvtCx0YDQviDQv9C+0LbQsNC70L7QstCw0YLRjCDQsiBFY3dpZCE=?=
MIME-Version: 1.0
Content-Type: multipart/alternative;
Dkim is present
Delivered-To: grif#ecwid.com
Received: by 10.229.14.202 with SMTP id h10csp5187qca; Thu, 26 Jun 2014 03:00:03 -0700 (PDT)
X-Received: by 10.140.96.38 with SMTP id j35mr18742954qge.5.1403776803018;Thu, 26 Jun 2014 03:00:03 -0700 (PDT)
Return-Path: <bender#ecwid.com>
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [2607:f8b0:400d:c00::22a])
by mx.google.com with ESMTPS id e8si8539327qgf.40.2014.06.26.03.00.02
for <grif#ecwid.com>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 26 Jun 2014 03:00:03 -0700 (PDT)
Received-SPF: pass (google.com: domain of bender#ecwid.com designates 2607:f8b0:400d:c00::22a as permitted sender) client-ip=2607:f8b0:400d:c00::22a;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of bender#ecwid.com designates 2607:f8b0:400d:c00::22a as permitted sender) smtp.mail=bender#ecwid.com;
dkim=pass header.i=#ecwid.com
Received: by mail-qa0-f42.google.com with SMTP id dc16so2614502qab.
for <grif#ecwid.com>; Thu, 26 Jun 2014 03:00:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;d=ecwid.com; s=google;
....
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
....
The email must be signed with DKIM/SPF, I don't see any of the relevant headers in your example.
I have implemented ntlmv2 for lync-server login in an custom made lync client.The message that I send to server is .....
(3rd register message)
REGISTER sip:example.com SIP/2.0
Via: SIP/2.0/TLS 19x.1xx.0.1xx:3246
From: <sip:lynctest8#example.com>;tag=2257063211;epid=22570632
To: <sip:lynctest8#example.com>
Call-ID: A2B000F95CB8XZRikcdYitb4QBvEr4P2
CSeq: 3 REGISTER
Contact: <sip:19x.1xx.0.1xx:3246;transport=tls;ms-opaque=28c9d310c1>;methods="INVITE, MESSAGE, INFO, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER, BENOTIFY";proxy=replace;+sip.instance="<urn:uuid:6b6590c5-2a3f-5dee-ad87-5ab6694cf66d>"
Max-Forwards: 70
User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
Supported: gruu-10, adhoclist, msrtc-event-categories
Supported: ms-forking
Supported: ms-cluster-failover
Supported: ms-userservices-state-notification
Ms-keep-alive: UAC;hop-hop=yes
Event: registration
Ms-subnet: 19x.1xx.0.0
Proxy-Authorization: NTLM qop="auth", realm="SIP Communications Service", opaque="8CEED616", targetname="lyncfe.example.com", version=4, gssapi-data="TlRMTVNTUAADAAAAGAAYAKgAAADGAMYAwAAAABAAEABYAAAALAAsAGgAAAAUABQAlAAAABAAEACGAQAAVYKQYgYBsR0AAAAPAAAAAAAAAAAAAAAAAAAAAG4AZQB5AGUAYgBhAGwAbABsAHkAbgBjAHQAZQBzAHQAOABAAG4AZQB5AGUAYgBhAGwAbAAuAGMAbwBtAEUAWQBFAEIAQQBMAEwALQBQAEMA9jYBMVaneo2SEFBrg1/YnLPWl4gGzCyjeTg+SJIb99jnRvh/xOM1KQEBAAAAAAAAAD9j2kfbzAGz1peIBswsowAAAAACABAATgBFAFkARQBCAEEATABMAAEADABMAFkATgBDAEYARQAEABgAbgBlAHkAZQBiAGEAbABsAC4AYwBvAG0AAwAmAGwAeQBuAGMAZgBlAC4AbgBlAHkAZQBiAGEAbABsAC4AYwBvAG0ABQAYAG4AZQB5AGUAYgBhAGwAbAAuAGMAbwBtAAcACABjQk/rRdvMAQAAAAAAAAAAGL4kYo+YoVBEmij7AkIylQ==" , crand="becdaa89", cnum ="1", response="0100000024A95BA08AA3947964000000"
Content-Length: 0
The response that I get from server is in log is......
TL_INFO(TF_COMPONENT) [0]05FC.02D0::01/25/2012-08:06:57.900.00000042 (SIPStack,CSIPMessage::CacheConnectionFlags:SIPMessage.cpp(1664))[0]( 00000000039B4DC0 ) From server [lyncfe.example.com] connection, flags [PeerInternal TrafficInternal 0xa0100c], CID [0x12300]
TL_INFO(TF_PROTOCOL) [0]05FC.02D0::01/25/2012-08:06:57.900.00000043 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 4074196035
Instance-Id: 000018F0
Direction: incoming;source="internal edge";destination="external edge"
Peer: lyncfe.example.com:5061
Message-Type: response
Start-Line: SIP/2.0 401 Unauthorized
From: <sip:lynctest8#example.com>;tag=1672455111;epid=16724551
To: <sip:lynctest8#example.com>;tag=6E92C85AEBAC66461CD3D9E7FF35D674
CSeq: 3 REGISTER
Call-ID: CDEA0494B083GDXKgQYZ3IuhqvqePNLL
Date: Wed, 25 Jan 2012 08:06:57 GMT
WWW-Authenticate: NTLM realm="SIP Communications Service", targetname="lyncfe.example.com", version=4
WWW-Authenticate: TLS-DSK realm="SIP Communications Service", targetname="lyncfe.example.com", version=4, sts-uri="https://lyncfe.example.com:443/CertProv/CertProvisioningService.svc"
Via: SIP/2.0/TLS 19x.1xx.0.2xx:60027;branch=z9hG4bK72A5FBC9.AAC299504F0761A1;branched=FALSE;ms-received-port=60027;ms-received-cid=16B9100
Via: SIP/2.0/TLS 19x.1xx.0.1xx:3082;received=2xx.xx.1xx.1xx;ms-received-port=3082;ms-received-cid=12700
ms-diagnostics: 1000;reason="Final handshake failed";HRESULT="0xC3E93EC3(SIP_E_AUTH_UNAUTHORIZED)";source="lyncfe.example.com"
Server: RTC/4.0
Content-Length: 0
Message-Body: –
$$end_record
What is the problem here? Can you give any hints/solutions to solve it?
It most likely due to SSL handshake while end point "https://lyncfe.example.com:443/CertProv/CertProvisioningService.svc". Please check your client certs and also enable SSL debug to see what's happening during handshake.
Thanks, Everyone. My problem has been solved. It was GSS-API-data and auth-token generation problem.