According to this question Is it possible to retrieve the RFC 2822 (or any) headers from an email with the Outlook/Office 365 REST API?
by doing
GET https://outlook.office.com/api/beta/me/mailfolders/inbox/messages$select=InternetMessageHeaders
But I can get the header only for inbox items, I need to retrieve the header for the sent items as well!
You can get it using the $value parameter to get the MIME type of the message and read the entire header!
From Example 4 - Get message
GET https://graph.microsoft.com/v1.0/me/messages/4aade2547798441eab5188a7a2436bc1/$value
Response
HTTP/1.1 200 OK
Content-type: text/plain
Received: from contoso.com (10.194.241.197) by
contoso.com (10.194.241.197) with Microsoft
SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1374.0 via Mailbox
Transport; Mon, 4 Sep 2017 03:00:08 -0700
Received: from contoso.com (10.194.241.197) by
contoso.com (10.194.241.197) with Microsoft
SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1374.0; Mon, 4 Sep
2017 03:00:07 -0700
Received: from contoso.com
(fe80::5bf:5059:4ca0:5017) by contoso.com
(fe80::5bf:5059:4ca0:5017%12) with mapi id 15.01.1374.000; Mon, 4 Sep 2017
03:00:01 -0700
From: Administrator <admin#contoso.com>
To: Administrator <admin#contoso.com>
Subject: This email has attachment.
Thread-Topic: This email has attachment.
Thread-Index: AQHTJWSHSywMzSz8o0OJud48nG50GQ==
Date: Mon, 4 Sep 2017 10:00:00 +0000
Message-ID:
<4aade2547798441eab5188a7a2436bc1#contoso.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 04
X-MS-Exchange-Organization-AuthSource:
contoso.com
X-MS-Has-Attach: yes
X-MS-Exchange-Organization-Network-Message-Id:
0ffdb402-ec03-42c8-5d32-08d4f37bb517
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
MIME-Version: 1.0
The email headers are created by the email servers, these details can
include who sent the message, the software that was used to compose
it, and the email servers that it passed through on its way to the
recipient. Hence you are not able to view the header information for
the sent messages.
Related
I implement an Exchange web mail client using EWS with nodejs. When I tested it by sending an email from my PC to Local Exchange server, everything was fine. All test emails were sent successfully.
But when I deployed the project on Server (VPS on Digial Ocean) and connect to Exchange Online which is part of Office365 subscription (Free Trial). The problem occurs, all emails sent from my server were considered as spam, and cannot be sent to reciepients.
I also change hosting from Digital Ocean to AWS, the result is the same.
Any help would be appreciated
Thanks in advance,
This is Diagnostic information
Authentication-Results: #########.com; dkim=none (message not signed)
header.d=none;########.com; dmarc=none action=none
header.from=exzyoffice.onmicrosoft.com;
Received: from SG2PR01MB0361.apcprd01.prod.exchangelabs.com (10.161.11.156) by
SG2PR01MB0362.apcprd01.prod.exchangelabs.com (10.161.11.16) with Microsoft
SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.649.16; Tue, 4 Oct
2016 16:58:07 +0000
Received: from SG2PR01MB0361.apcprd01.prod.exchangelabs.com ([10.161.11.156])
by SG2PR01MB0361.apcprd01.prod.exchangelabs.com ([10.161.11.156]) with mapi
id 15.01.0649.022; Tue, 4 Oct 2016 16:58:07 +0000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: ###### ######## <#################.onmicrosoft.com>
To: "chanyut##########.com" <chanyut#########.com>, "chanyutx10######.com"
<chanyutx10###########.com>
Subject: Check-in PIN for Test PIN Email - Meeting System
Thread-Topic: Check-in PIN for Test PIN Email - Meeting System
Thread-Index: AQHSHmB6uwXOpaeopUqgpi/eM7C6wA==
Date: Tue, 4 Oct 2016 16:58:06 +0000
Message-ID: <SG2PR01MB03614F6A8834FDB61C01DEF2FDC50#SG2PR01MB0361.apcprd01.prod.exchangelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <SG2PR01MB03614F6A8834FDB61C01DEF2FDC50#SG2PR01MB0361.apcprd01.prod.exchangelabs.com>
MIME-Version: 1.0
X-Originating-IP: [188.166.177.7]
Return-Path: chanthat#exzyoffice.onmicrosoft.com
X-MS-Office365-Filtering-Correlation-Id: 567de66e-0dff-4626-9fa1-08d3ec779d39
X-Microsoft-Exchange-Diagnostics:
1;SG2PR01MB0362;2:zy4eJMXvSbYZweZat1h/FneV4A2yOxpO8vpRdwEwCLWm8QipVnNdHzsBf+KyaetEsivdt7hl30XR0eCUs5T7EL7aar+e5fDuacG0fUm/7j7SH93besRmhZRaLZIup+pZYqzXKS6xnbd+kPd4Nf6gyMcfj0DL8ALLqSmf5b6aI7nuwiOIuO+z9Hw7XAD9vGMIZNSA64aw3BTeAxnxqqY1pw==;3:5BABxsk+E39PYBKVh9pWEKhIMBMLNKyOseakzwXuwPpHSiVt3bS8Ov+hYnw6Qs3Y0GMVQY0wlnaMopAEVphplwf5oy+oT5cLDIXzvg+q1GoAaeCu3TFALwH98FrKZr787qYEFnRV9pV0zqyocM+XBw==;25:ctGAmAQ1cu+BduByl6+MPAKb8/xsxaUIMq7FPDVqzTZDtsDLYREoYwbNlL10iTwrv0ON01j2DfmyRNvh6e6gL2Xcb/qjVqavMTzITJAVuBJlIHNiCgfpnW4mVNkb1dO4vJEZV6CI0KSk3RQH9Dh6/u56/zjv5ESEuuv9EQxcKYC8Mf0TJR+NHAr540/1+7h0yLDm2495YG46kfuJft6Y74HaYFiNVl/L3r31kA84l82qQez2sGGcgHo6kJv3w3QmB5garjK7j0HfceHEogOuofDJwz0Y47YfMaJg1/kyQhDGytMmQxrdJ2aRt8VcbjcKnF7Nfl3KbU/CkU33kZ9Vp3Fa9hustkf7lOD/bL1PsMSH2kOXmolb5ks1kvmF1hZ+pTsNzd0Zz9mNuErtxp7lK5hMfNL+NeLnAjnRZfvqX6/JK4ZRr7IlPw/YSvmMMxPM
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SG2PR01MB0362;
X-Microsoft-Exchange-Diagnostics:
1;SG2PR01MB0362;31:GR+rFHTjFRwfnJTe4nsRPGyP0mSyV+kDu/elZc5VaNeIXHm90HhmKo5Bzt08Yg9rKmPGkbTp2OVLPv8WIMt0ssqobSrA4ZGc44yBtlqefEAI18SF76/RrOxzmXDwUX82fkrubNc2e6IVrlDWQ0HO5cc1AYbatOZEwAfe3OzBg9rhw+u3ef8oBU5E++bzAqdqL0n/o+TrnEhy18ZJrL14yIhXEYsy159STM7O4Szj4pxh02al5tcE0CrpzdET9Wxo;4:0g+YEprdQNgkE9AkEVGWN/VFqIpOq92oDR1yeXN1yQeuGkHuWB6I9KIZSMLZHsjKildUXRPySE/Wv/r61w8hqbz0goIrlvYrEg+tCTDjM/0IsdxhXnGcsmgLIXAu4PRoTlkejJlaNqwtHqT217nzBDlCVu7E/4LwAPUpSk6+wQZhjAUfG/v3t3PNCHpL7hEsaK/KkqyKuJ+TbybDB5D+/JmqfQpzvxsP7pIOntHQmwbakW6g/I474q6I6x34yzVHOsA8tP/70Y6NbpA3P6hAOIh8ioFswLPAKbc/rO3q4pcAyARvVyXmNh6NeVntO1SaFUxqCn9OZSVWN3/pK3rVLDCHDkHisckt4VSGcN54vQcYR79Cod5jgMSjA2aMTtY8wPYf1ZxbU67WgCk9XJ8dpIceUZzF7cxZs78fr5kY7q9IMaYciZB7zR4v2Ds0pdmP36iITdLNHXdxOaqt3gY2g3oktTguQ87whqzg6+RJrO8=
X-Microsoft-Antispam-PRVS:
<SG2PR01MB036291996D70C36ABCD297ECFDC50#SG2PR01MB0362.apcprd01.prod.exchangelabs.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test:
BCL:0;PCL:0;RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6002118)(6000006)(6043046)(6042046);SRVR:SG2PR01MB0362;
X-Forefront-PRVS: 00851CA28B
X-Microsoft-Exchange-Diagnostics:
1;SG2PR01MB0362;23:SGkU+hCO1Me9ul5A85nokDETPc2fvnqIJBuMSsUaizPW5SU30hQ/9h8FERIrUfQlyhOSjKXtfJtRPa7dctubpraPm8t+7i1Tu9MmC3xqJss5m9gdTncr4lcByV677Os8wLvADH/SnogL/EucwxkzNm2M2WVwLpE2sOw9ochCbZuAMN2CQT+XKJnuSefgwHo8tfCdYWSEVRE3gleOfPWMTtYERp11xjY4NRCqU9WTcPLq6OMA+LIwdc8D0wpEPF++UgSfYeQ5Rd+SKnXW/++ZWw==;6:YwRMvgBmAN1rsxVOfmcL8JnjlX63xYoEQRiiRNoehWPk1+mB8M2XiRWLtmuHBVuOmi0CUeuQXuFWGEIS+Z1q8u0ARqjLoVkjHjTsZUMeiliHUg4bNAZfZdZNL2JRsp6zrdY+xNotdkzKO1+QN+yUV5USrfMLPo3eX8p/XAsvCB2MUikXyUyv9Lwpp71jzDsLExLz+AkKi2JKAxquPePw3OyzITh/BEpnxnRBVVAAKwOLg0cdxtcHNFiztVLcHSdqs6ygXQftAh+CbSqWlKLwkXitOLDdwbXVo2RYvT3DDC+8CYyoab8sRGihjxfbFw3M
My emails are delivered to spam folder at gmail and yahoo mail.
PTR, DKIM (1024 bit), SPF are okay. I don't know whether DMARC and ADSP or Domain Key are needed to be configured or else?
In addition, I have checked Bulk Senders Guidelines "support.google.com/ ----> mail/answer/81126" but I think I am in compliance with it, except the Format section of the webpage. I wonder is my email header is ISO-8859-1 compliant as is requested by gmail or my messages are formatted according to RFC 5322 as it is required!?
However, I have checked my email by various tools including:
1- www.brandonchecketts.com/emailtest.php
2- mail-tester.com (my email score: 10/10)
3- toolbox.googleapps.com ----> /apps/messageheader/analyzeheader
and all of them are ok and I can't get it right why my emails are categorised as spam?
By the way, I am not a bulk sender, my ip is clean (not in any of blacklists) and I have just started to configure my new VPS host.
I am confused a bit as it is obvious, Please guide me.
Note: (I have changed email addresses and real IPs in the message header)
Here is the header:
Delivered-To: user#gmail.com
Received: by 10.194.95.197 with SMTP id dm5csp291965wjb;
Fri, 30 Jan 2015 06:02:17 -0800 (PST)
X-Received: by 10.180.206.147 with SMTP id lo19mr5212607wic.32.1422626536876;
Fri, 30 Jan 2015 06:02:16 -0800 (PST)
Return-Path: <user#myemail.com>
Received: from myemail.com (myemail.com. [97.195.90.210])
by mx.google.com with ESMTPS id s3si20803914wjx.75.2015.01.30.06.02.16
for <user#gmail.com>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 30 Jan 2015 06:02:16 -0800 (PST)
Received-SPF: pass (google.com: domain of user#myemail.com designates 97.195.90.210 as permitted sender) client-ip=97.195.90.210;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of user#myemail.com designates 97.195.90.210 as permitted sender) smtp.mail=user#myemail.com;
dkim=pass header.i=#myemail.com
Received: from webmail.myemail.com (localhost.localdomain [127.0.0.1])
by myemail.com (Postfix) with ESMTPA id 0D4A122FAEF
for <user#gmail.com>; Fri, 30 Jan 2015 15:02:14 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=myemail.com;
s=default; t=1422626535;
bh=mg3gRDZT3ck+E3FdH2X4LLdsZ/+WeZuit/DVefJiJWc=;
h=Date:From:To:Subject;
b=NhJPZML/OvA/2LJbvqKxnV7AO3TeGPdDqwBI+iOceZk2bz2flsCun3AqJ4RPY8pqM
is+dlQWTFCmQ2T2He7cKU/nC28FmPY4cqwJgt6oSIW0bIWkh81JdzBZXoIDiBGGlkx
mkrpvKQ4vdFh2R7iIRmUJMJtAGWr7MGoS/J7sdi0=
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 30 Jan 2015 17:32:14 +0330
From: user#myemail.com
To: user#gmail.com
Subject: Hello
Message-ID: <7582a20431ca444b255e5e835e6ee87d#myemail.com>
X-Sender: user#myemail.com
User-Agent: Roundcube Webmail/1.0.0
Regards
Since you've said that you've modified the header records, it's hard to determine a few things. However, the sending mail server seems to be webmail.domain.com --- Are the DNS records set to point to mail.domain.com or webmail.domain.com or both?
Since you've done the rest of the configuration: just enter a dmarc DNS record, it might increase your server's reputation. Speaking of reputation, if your email server only handles a few emails a day from a couple of users - then your reputation as a 'spammy' server can be greatly affected by a just a few unopened or manually spam marked messages. Also, I believe there's a time lag between when you setup a mail server and when it's reputation gets out of the 'default to spam' folder.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question appears to be off-topic because it lacks sufficient information to diagnose the problem. Describe your problem in more detail or include a minimal example in the question itself.
Closed 8 years ago.
Improve this question
I am facing an issue with the DKIM setup. We are sending newsletters which are going to spam in gmail. The dkim & spf passes. Even the reverse dns is setup properly. Below is a copy of mail headers that I see in gmail.
Delivered-To: xyz#gmail.com
Received: by 10.112.29.116 with SMTP id j20csp27976lbh;
Tue, 2 Jul 2013 10:28:18 -0700 (PDT)
X-Received: by 10.50.11.103 with SMTP id p7mr22069045igb.24.1372786097413;
Tue, 02 Jul 2013 10:28:17 -0700 (PDT)
Return-Path:
Received: from mydomain.com (newsletter.mydomain.com. [108.171.163.8])
by mx.google.com with ESMTP id gu10si1702677icb.68.2013.07.02.10.28.16
for ;
Tue, 02 Jul 2013 10:28:17 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of abc#mydomain.com designates 108.171.163.8 as permitted sender) client-ip=108.171.163.8;
Authentication-Results: mx.google.com;
spf=pass (google.com: best guess record for domain of abc#mydomain.com designates 108.171.163.8 as permitted sender)
smtp.mail=abc#mydomain.com; dkim=pass header.i=#mydomain.com
Received: from mydomain.com (mydomain.com [127.0.0.1])
by mydomain.com (Postfix) with ESMTP id 4A47318970;
Tue, 2 Jul 2013 17:30:38 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mydomain.com;
s=default; t=1372786238;
bh=s49+JPD0rpGLWWNhx0l6oMGPXzMHX4Adnh2xr6Q+4Iw=;
h=Date:Message-Id:To:Subject:MIME-Version:From:Content-Type;
b=NCmIyPQwp48nXJBpYdaVcmopJgOoLZ7H9KRcJ/o/HW2ZEZLRXreVwHRPWFI+s0h70
iVZPKVemBlAXtaL9T1hQOC61YVS//k3CEmUR732Axnz96dnJFbe5YtiD+mJN7dRZeL
Z7sf44NVi2E5EMWV7bi/RU7py0LNNo9Lp6KfzZLA=
Received: (from abc#localhost)
by mydomain.com (8.14.5/8.14.5/Submit) id r62HUcoh028894;
Tue, 2 Jul 2013 17:30:38 GMT
Date: Tue, 2 Jul 2013 17:30:38 GMT
Message-Id: <201307021730.r62HUcoh028894#mydomain.com>
To: xyz#gmail.com
Subject: mydomain | Subject Details
MIME-Version: 1.0
From: mydomain
Content-Type: multipart/alternative;boundary=np51d30e1a36dd3
I Think so the Received: (from abc#localhost) is causing the issue.
What I need to know how to resolve it. Instead of localhost it should use mydomain.com This is my first time setting up such kind of server.
This may be the problem with the envelope sender and from address because,an email has two addresses associated with sending it: the envelope sender, and the From: address. The envelope sender is where computers should respond (in the case of bounce messages or errors); the From: address is where people should respond. In most cases, the envelope sender and the From: address match.Some case the Gmail put the mails which the 2 sender field did not match. You may try with the same.
registration email sent from a new website I am building end up in the receivers' spam folders, they are classified as spam. So far I have no idea why this happens. Therefore I am posting the email header of such a registration email. Please note that this email posted here has not been classified as spam, however all registration emails generated and sent are like this one.
Return-Path: c...t#l...friends.net
Received: from relay02.alfahosting-server.de ([109.237.142.238]) by
mx-ha.gmx.net (mxgmx008) with ESMTP (Nemesis) id 0LkCb4-1U3Xb718IM-00cB3P for
<hamstino007990#gmx.de>; Thu, 23 May 2013 23:44:03 +0200
Received: by relay02.alfahosting-server.de (Postfix, from userid 1001)
id CBFAD32C008C; Thu, 23 May 2013 23:44:02 +0200 (CEST)
X-Spam-DCC: :
X-Spam-Level:
X-Spam-Status: No, score=-0.2 required=7.0 tests=BAYES_40,HTML_MESSAGE
autolearn=disabled version=3.2.5
Received: from alfa3060.alfahosting-server.de (alfa3060.alfahosting-server.de [109.237.138.46])
by relay02.alfahosting-server.de (Postfix) with ESMTP id 9EF9232C00C6
for <hamstino007990#gmx.de>; Thu, 23 May 2013 23:44:00 +0200 (CEST)
Received: by alfa3060.alfahosting-server.de (Postfix, from userid 2905)
id 9DDB32FFBE6B; Thu, 23 May 2013 23:44:00 +0200 (CEST)
To: hamstino007990#gmx.de
Subject: =?utf-8?Q?Willkommen_bei_LanguageFriends.net!?=
X-PHP-Script: staging.languagefriends.net/index.php for 77.58.5.166
User-Agent: CodeIgniter
Date: Thu, 23 May 2013 23:44:00 +0200
From: "L...Friends.net" <c...t#L...Friends.net>
Reply-To: "L...Friends.net" <c...t#L...Friends.net>
X-Sender: c...t#L...Friends.net
X-Mailer: CodeIgniter
X-Priority: 3 (Normal)
Message-ID: <519e8da0993a5#L...Friends.net>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="B_ALT_519e8da0993ea"
X-Virus-Status: No
X-Virus-Checker-Version: clamassassin 1.2.4 with ClamAV 0.97.3/17264/Thu May 23 18:12:25 2013
Envelope-To: <hamstino007990#gmx.de>
X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=V3;
X-GMX-Antivirus: 0 (no virus found)
Thanks very much for any support.
Regards
Sebastian
Do you have a proper SPF record set up for your domain? Most domains should respect whatever address your mail is coming from as long as it is in your SPF record. Wikipedia has a pretty good write-up on how SPF works.
I moved one client to Google Apps and it's been crazy! So many problems! And I never had these kind of problems
Client is using Outlook with Imap to manage his Google Apps Gmail account
Now when he sends email he got this kind of errors (for some addresses only):
Delivery to the following recipient failed permanently:
spf-test#openspf.org
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.7.1 <spf-test#openspf.org>: Recipient address rejected: SPF Tests: Mail-From Result="pass": Mail From="nelson#samarfil.com" HELO name="mail-qa0-f45.google.com" HELO Result="none" Remote IP="209.85.216.45" (state 13).
----- Original message -----
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=samarfil.com; s=google;
h=mime-version:x-originating-ip:date:message-id:subject:from:to
:content-type;
bh=bjpej8F5vAhPQFF4gZXUvUHOGuDj2lURhN5uAXH+4o4=;
b=Gvhx7DYYlBFN1b0DQDDTq7Ll0tiGrrzMRGxVnIXOlbr8E3xhtY/lJGNcETSNDIblTT
yQHNyBlnPZxm2AqN8aeJ60lM54QofFtEt4jZe4V0b9WkP8rBXl5KbEfADcJw3kgZQMN/
8I0cpLYALe4YJ0PX8ZCXbtmFtd7m/Jmc/vKEo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-originating-ip:date:message-id:subject:from:to
:content-type:x-gm-message-state;
bh=bjpej8F5vAhPQFF4gZXUvUHOGuDj2lURhN5uAXH+4o4=;
b=fdNJWqcTEv1GE5giglb7CBRbU5+1w0VBF8DGjAN2YlrNH624no/00JcJgu/cyw7eAs
cIUUsU2vjMr7Kjjmc3xKbadMyF3A7b7u36l2t80aknCTdkSQuZ6yKT1EYY3INVUhue4Y
Ml7qNaSiAPhNEHlzEttJn/OFYgPeG0rSC8OM5MyZdY6gE64bqrDLH/3chq/0M+yHclon
hEYO7VytoV3BsNxr/HvEJEyNcHtTeX+WsVmxtNc5qgpxytbtReHEjl94auifz/YN16mg
wyC7LUXIBfF3Tffs0NIL5ITwQIj4rSKNm/4N20bfWa6uPJn/30J1uvVoRjHegDtwYQyK
yt8g==
MIME-Version: 1.0
Received: by 10.224.70.138 with SMTP id d10mr27073000qaj.12.1350404560884;
Tue, 16 Oct 2012 09:22:40 -0700 (PDT)
Received: by 10.49.24.205 with HTTP; Tue, 16 Oct 2012 09:22:40 -0700 (PDT)
X-Originating-IP: [94.133.34.4]
Date: Tue, 16 Oct 2012 17:22:40 +0100
Message-ID: <CACP3cFsLYGus9Sr-cbuEFezBEXhdzSJ6gqGPOJr___UJARaBMw#mail.gmail.com>
Subject:
From: Nelson Santos <nelson#samarfil.com>
To: spf-test#openspf.org
Content-Type: multipart/alternative; boundary=bcaec51a81ec2793fc04cc2f90aa
X-Gm-Message-State: ALoCoQkvxVOP+l0d4ugZSxBkKf6IBmd7UYEWPxtodPNh+L5hBOkQD2zREymT1Eal1lH9JUSgBavX
I've already configured DNS to TXT record v=spf1 include:_spf.google.com ~all
what else can I do to fix this?
It's normal to receive this message, as that SPF test uses the error message to send back results. Are you experiencing errors when sending to other addresses?