I am configuring opendkim+postfix. It is working OK and sent messages are correctly signed but the incomming messages are all marked as dkim=fail reason="signature verification failed"
How con I debug this problem?
Return-Path: <sender#gmail.com>
Delivered-To: recipient#mydomain.com
Received: from localhost (mailserver [127.0.0.1])
by mydomain.com (Postfix) with SMTP id 4DDF93F966
for <recipient#mydomain.com>; Tue, 24 Oct 2017 13:56:43 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 mydomain.com 4DDF93F966
Authentication-Results: mydomain.com;
dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=#gmail.com header.b="jmdDmXQb"
Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=209.85.215.43; helo=mail-lf0-f43.google.com; envelope-from=sender#gmail.com; receiver=recipient#mydomain.com
DMARC-Filter: OpenDMARC Filter v1.3.2 mydomain.com 2DBE03F963
Authentication-Results: mail.mydomain.com; dmarc=pass (p=none dis=none) header.from=gmail.com
Authentication-Results: mail.mydomain.com; spf=pass smtp.mailfrom=sender#gmail.com
The syslog reports this which looks OK
Oct 24 14:08:39 mailz opendkim[3325]: 4A29F3F938: [209.85.215.45] [209.85.215.45] not internal
Oct 24 14:08:39 mailz opendkim[3325]: 4A29F3F938: not authenticated
Oct 24 14:08:39 mailz opendkim[3325]: 4A29F3F938: DKIM verification successful
But later it adds:
Oct 24 14:08:43 mailzener postfix/cleanup[3194]: 6CC243F95E: message-id=<CAMXuvOM+jKLkE=0FrQ+cSqFesmPQujpHoVsfH9G_URg9uYtm1g#mail.gmail.com>
Oct 24 14:08:43 mailzener opendkim[3325]: 6CC243F95E: no signing table match for 'sender#gmail.com'
Oct 24 14:08:43 mailzener opendkim[3325]: 6CC243F95E: bad signature data
My opendkim configuration file is this:
AutoRestart Yes
AutoRestartRate 10/1h
LogWhy Yes
Syslog Yes
SyslogSuccess Yes
Mode sv
Canonicalization relaxed/simple
ExternalIgnoreList refile:/etc/opendkim/TrustedHosts
#InternalHosts refile:/etc/opendkim/TrustedHosts
KeyTable refile:/etc/opendkim/KeyTable
SigningTable refile:/etc/opendkim/SigningTable
SignatureAlgorithm rsa-sha256
Socket inet:8891#localhost
PidFile /var/run/opendkim/opendkim.pid
UMask 022
UserID opendkim:opendkim
TemporaryDirectory /var/tmp
OversignHeaders From
LogWhy Yes
X-Header yes
MilterDebug 9
ResolverTracing Yes
As you can see from the Queue ID 4A29F3F938 vs 6CC243F95E, these are two different mails.
4A29F3F938 is incoming and is verifying OK. 6CC243F95E is outgoing, and I guess opendkim tries to sign the mail. You need to elaborate on your processing of the mail in the lines inbetween :)
Related
I often receive fishing /SPAM emails with multiple received fields.
First, I'd like to understand how one email header can have more than one received field.
Second, I'd like to know if I can use this to fight SPAM.
Here is an example:
Return-Path:
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on myhosting.com
X-Spam-Level:
X-Spam-Status: No, score=0.0 required=3.5 tests=HTML_MESSAGE autolearn=ham
version=3.3.2
X-Spam-ASN:
X-Original-To: my#email.rs
Delivered-To: my#email.rs
Received: from posta.abak.si (posta.abak.si [84.255.212.92])
by myhosting.com (Postfix) with ESMTPS id 522CA80DC8
for ; Wed, 8 May 2019 14:31:59 +0200 (CEST)
Authentication-Results: myhosting.com;
dmarc=none (p=NONE sp=NONE) smtp.from=mk.kema-on.net header.from=mk.kema-on.net;
spf=none (sender IP is 84.255.212.92) smtp.mailfrom=dime.mitreski#mk.kema-on.net smtp.helo=posta.abak.si
Received-SPF: none (myhosting.com: no valid SPF record)
Received: from localhost (localhost [127.0.0.1])
by posta.abak.si (Postfix) with ESMTP id 2C09E1E6A7D7
for ; Wed, 8 May 2019 14:35:06 +0200 (CEST)
Received: from posta.abak.si ([127.0.0.1])
by localhost (posta.abak.si [127.0.0.1]) (amavisd-new, port 10032)
with ESMTP id dw1MvahvfmXL for ;
Wed, 8 May 2019 14:35:05 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
by posta.abak.si (Postfix) with ESMTP id EB2B21E6A3C6
for ; Wed, 8 May 2019 14:30:12 +0200 (CEST)
X-Virus-Scanned: amavisd-new at posta.abak.si
Received: from posta.abak.si ([127.0.0.1])
by localhost (posta.abak.si [127.0.0.1]) (amavisd-new, port 10026)
with ESMTP id luUYSdWOdHLE for ;
Wed, 8 May 2019 14:30:12 +0200 (CEST)
Received: from IP-129-13.dataclub.eu (unknown [84.38.129.13])
by posta.abak.si (Postfix) with ESMTPA id B18CD1E6A7A6
for ; Wed, 8 May 2019 14:25:39 +0200 (CEST)
Content-Type: multipart/alternative; boundary="===============0253676305=="
MIME-Version: 1.0
Subject: Warning: you have (3) Undelivered messesges
To: my#email.rs
From: "Webmaster"
Date: Wed, 08 May 2019 15:25:37 +0300
Message-Id:
Message Body
Every mail server that processes an email adds its own Received field to the header. It is normal for emails to pass through several email servers when traveling across the internet from the sender's computer to the final destination.
https://www.rfc-editor.org/rfc/rfc5321#section-4.4
When an SMTP server receives a message for delivery or further
processing, it MUST insert trace ("time stamp" or "Received")
information at the beginning of the message content,
Looking at the first Received field,
Received: from IP-129-13.dataclub.eu (unknown [84.38.129.13])
by posta.abak.si (Postfix) with ESMTPA id B18CD1E6A7A6
for ; Wed, 8 May 2019 14:25:39 +0200 (CEST)
you will notice that it says which server it received the mail from (the "FROM" clause), and which server received it (the "BY" clause").
As you read through the list of Received fields in the header you posted, you will notice that they are all linked in this fashion.
I have been having a lot of issues with emails from our servers going to SPAM. I cant find out why, I am not on any blacklist and we have the SPF/DKIM records validated.
Below is a transcripts of our emails...
Received: from host.ilovenz.me (host.ilovenz.me [96.30.1.56])
by relay-6.us-west-2.relay-prod (Postfix) with ESMTPS id 34DBA460BBA
for <20g0dnL7Le4vW8#dkimvalidator.com>; Sun, 26 Feb 2017 03:31:39 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ilovenz.me;
s=default; h=MIME-Version:Content-Transfer-Encoding:Content-Type:Date:
Subject:To:Sender:From:Reply-To:Message-ID:Cc:Content-ID:Content-Description:
Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:
In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:
List-Post:List-Owner:List-Archive;
bh=dKce1b0OIqr1iFXsTI1PsQWwBft9eaJeSIwAbZhxRp0=; b=VOkfOW7ftU5bxGSL0Q9D+2tvB2
nGx9pmAcaRGzrFlwOLg8IrYYmU0h8PWqPTQ/4mD26BJCAEUdAYjXaKYl9ovhGWJMW9qAfK4Hy7JXk
aQDJOw6jBKHM5aRbgm9aIuXrPEe4+AngMao85vH9PKRTBQxegl2nJYX+JApr4MHf1S14uCyEYAcD7
nJwlrZJ32VAxn2gz1rDeevkTSptaSqpgX4EURzZDR/2osv53Np2//F+5qCTFabvwr9qe5RyiKsV5g
56TP/Ym1R4a25QzOg4yLiqr0ZlBh4zTB6lIGpfF7NWRtOPW49c02rEO8raOV3lgfXWWi+kD4NO1fy
Xw8Tljtw==;
Received: from host.ilovenz.me ([96.30.1.56]:48972 helo=localhost)
by host.ilovenz.me with esmtpa (Exim 4.88)
(envelope-from <hello#ilovenz.me>)
id 1chpYg-0000eR-6I
for 20g0dnL7Le4vW8#dkimvalidator.com; Sun, 26 Feb 2017 16:31:38 +1300
X-Mailer: Postman SMTP 1.7.2 for WordPress (https://wordpress.org/plugins/postman-smtp/)
From: ilovenz <hello#ilovenz.me>
Sender: hello#ilovenz.me
To: 20g0dnL7Le4vW8#dkimvalidator.com
Subject: [I Love New Zealand] Activate your account
Date: Sun, 26 Feb 2017 03:31:38 +0000
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
MIME-Version: 1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.ilovenz.me
X-AntiAbuse: Original Domain - dkimvalidator.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ilovenz.me
X-Get-Message-Sender-Via: host.ilovenz.me: authenticated_id: hello#ilovenz.me
X-Authenticated-Sender: host.ilovenz.me: hello#ilovenz.me
X-Source:
X-Source-Args:
X-Source-Dir:
Thanks for registering!=0A=0ATo complete the activation of your account,=
go to the following link: https://ilovenz.me/activate/kWwH8aMmTTYQCeii6=
nHDAZ1T3Lxw0QSr/
Probably because you are using an unusual TLD and you have the word 'love' in it. I had a similair problem with a poker site.
Our app sends some messages to our servers via FCM Upstream. We have two servers connected as clients.
Recently, we've noticed that many messages (>50%) are received twice. Often on different servers, but sometimes on the same server.
Unsure where to go from here.
Logs of one message being received twice follow:
Fri, 18 Nov 2016 21:39:17 GMT xmpp:connection receive:
<message to="xxxx#gcm.googleapis.com" from="devices#gcm.googleapis.com" type="normal">
<gcm xmlns="google:mobile:data">
{"data":
{"userInfo":"{}",
"path":"v1\/patient\/checkIn\/usage",
"method":"POST",
"body":"{}",
"dest":"https:\/\/api.stg.triggrhealth.com\/api\/v1"
},
"time_to_live":43200,
"from":"f5LDS516Eu8:APA91bGEkzwXlmXRpfui6T01QM6V3pOY8p3nSkZMUfYkDYjRxu6Xa64Bh0Boc3so8X8royBA1v4PaGjPcUW6JI0pcZL7UK9P4LEqgVThfNQKGW8DZMhTEM-JDodDvUPjGpbPA-zdYYQb",
"message_id":"1479505157658",
"category":"com.triggrhealth.prototype.stage"
}
</gcm>
</message>
Fri, 18 Nov 2016 21:39:17 GMT xmpp:connection send:
<gcm xmlns="google:mobile:data">
{"to":"f5LDS516Eu8:APA91bGEkzwXlmXRpfui6T01QM6V3pOY8p3nSkZMUfYkDYjRxu6Xa64Bh0Boc3so8X8royBA1v4PaGjPcUW6JI0pcZL7UK9P4LEqgVThfNQKGW8DZMhTEM-JDodDvUPjGpbPA-zdYYQb",
"message_id":"1479505157658",
"message_type":"ack"
}
</gcm>
Fri, 18 Nov 2016 21:42:28 GMT xmpp:connection receive:
<message to="xxxx#gcm.googleapis.com" from="devices#gcm.googleapis.com" type="normal">
<gcm xmlns="google:mobile:data">
{"data":
{"userInfo":"{}",
"path":"v1\/patient\/checkIn\/usage",
"method":"POST",
"body":"{}",
"dest":"https:\/\/api.stg.triggrhealth.com\/api\/v1"
},
"time_to_live":43200,
"from":"f5LDS516Eu8:APA91bGEkzwXlmXRpfui6T01QM6V3pOY8p3nSkZMUfYkDYjRxu6Xa64Bh0Boc3so8X8royBA1v4PaGjPcUW6JI0pcZL7UK9P4LEqgVThfNQKGW8DZMhTEM-JDodDvUPjGpbPA-zdYYQb",
"message_id":"1479505157658",
"category":"com.triggrhealth.prototype.stage"
}
</gcm>
</message>
Fri, 18 Nov 2016 21:42:28 GMT xmpp:connection send:
<gcm xmlns="google:mobile:data">
{"to":"f5LDS516Eu8:APA91bGEkzwXlmXRpfui6T01QM6V3pOY8p3nSkZMUfYkDYjRxu6Xa64Bh0Boc3so8X8royBA1v4PaGjPcUW6JI0pcZL7UK9P4LEqgVThfNQKGW8DZMhTEM-JDodDvUPjGpbPA-zdYYQb",
"message_id":"1479505157658",
"message_type":"ack"
}
</gcm>
You may want to check and try sending an ACK message. As mentioned,
In response to an upstream message, the app server must use the same connection to send an ACK message containing the unique message ID. If GCM does not receive an ACK, it may retry sending the message to the app server.
Here's the sample code:
<message id="">
<gcm xmlns="google:mobile:data">
{
"to":"REGID",
"message_id":"m-123"
"message_type":"ack"
}
</gcm>
</message>
Lastly, please also see the XMPP Connection Server Reference for more information about upstream message syntax.
I'm creating the iCal using ical4j and sending it using Java Mail API 1.4.7. When sending it both to google.mail and outlook.com the organizer receives the email textual part only. All other recipients receive the email wrapped with the "Add to calendar" or "RSVP" buttons (for attendees).
If remove the recipient email from the organizer property, then he receives the email with the wrappers, but then the meeting has no organizer...
My problem with this, is that the organizer I created the event on behalf of, does not get the event created on his calendar.
That's the email sent:
Delivered-To: test+JohnDoe1st#woo.io
Received: by 10.202.80.11 with SMTP id e11csp2599297oib;
Wed, 24 Feb 2016 11:28:44 -0800 (PST)
X-Received: by 10.182.165.67 with SMTP id yw3mr33375476obb.45.1456342124175;
Wed, 24 Feb 2016 11:28:44 -0800 (PST)
Return-Path: <bounces+1797494-17b1-test+JohnDoe1st=woo.io#mail.woo.io>
Received: from o1.email.highr.io (o1.email.highr.io. [50.31.35.179])
by mx.google.com with ESMTPS id n205si3660143oib.92.2016.02.24.11.28.43
for <test+JohnDoe1st#woo.io>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Wed, 24 Feb 2016 11:28:44 -0800 (PST)
Received-SPF: pass (google.com: domain of bounces+1797494-17b1-test+JohnDoe1st=woo.io#mail.woo.io designates 50.31.35.179 as permitted sender) client-ip=50.31.35.179;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of bounces+1797494-17b1-test+JohnDoe1st=woo.io#mail.woo.io designates 50.31.35.179 as permitted sender) smtp.mailfrom=bounces+1797494-17b1-test+JohnDoe1st=woo.io#mail.woo.io;
dkim=pass header.i=#woo.io
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=woo.io;
h=from:reply-to:to:subject:mime-version:content-type; s=s1;
bh=wagu2M/f9bJi3poSZhvX4ST1TCs=; b=0coUojPVzsP3yH5mGPTzVsFS5c7h9
pd7uMlc3WLx+2dciB/2w0gG5BoEIYTzdk68c7GLQWj6XhskmS4CWed9y5dQt2CEy
ei3pmJWxoHNMl2hjGW+4nHPSwM5mcbH8BH0YCwXZBAJ1yzc0ymJSwD4+vQzfhOA0
Skj8s1OFPz2EqA=
Received: by filter0422p1mdw1.sendgrid.net with SMTP id filter0422p1mdw1.25440.56CE046718
2016-02-24 19:28:39.292147439 +0000 UTC
Received: from 10.0.0.3 (dynamic-213-57-67-77.hotnet.net.il [213.57.67.77])
by ismtpd0002p1lon1.sendgrid.net (SG) with ESMTP id UWS8Q1EHSTGlRwEBPWD0Jg
for <test+JohnDoe1st#woo.io>; Wed, 24 Feb 2016 19:28:39.206 +0000 (UTC)
Date: Wed, 24 Feb 2016 19:28:52 +0000 (GMT)
From: "(DevEnv) Woo.io" <test+scheduler#woo.io>
Reply-To: "(DevEnv) Woo.io" <test+scheduler#woo.io>
To: test+JohnDoe1st#woo.io
Message-ID: <1211793890.13.1456342132980.JavaMail.User1#JohnK-Laptop>
Subject: A phone call with John Doe has been scheduled
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_12_325908549.1456342132978"
X-SG-EID: eKXc83Aurbu+DQRCT+WAXI9wVN9EN8h4r+iXFZL+oEoeV9DlDScoApg++iQXhvj0VXg9jyy3l1JsyF
PsfdNpdxcM5ze8grHttshgo/s5pOH3DSyhvMx0eioa5nVYxSYH0hO4FSAN+J2/beLbpNQqZNUIe1jo
GAcnhBNsAtYBnw9pDhxr5SW46As/nuflbBvdpkATzhR5NTXgjF0POaXGBJyxRUvOfs1noR0m4IF4D9
0=
X-SG-ID: E59GF+CtKDB+cFOQwHaDXPNahQbunt2rHtUM1rTwltQKUGjmerW2HyowTumyVQQhTgF/leflKriflw
bWodCKpaW63gxumD3qe89wS7l9a+KOifOwoLXTLVFZnXN8+QzO
------=_Part_12_325908549.1456342132978
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
Hey John,<br/>
<br/>
Your phone call with John Doe for the Software Engineer position is scheduled for Thu, Feb 25, 2016 at 08:00 (GMT+2).<br/>
<br/>
We've let the candidate know that you will call them at this number 97211111112.<br/>
<br/>
Cheers,<br/>
The WOO Team<img src="http://maillink.highr.io/wf/open?upn=GdV8Hrdq-2BQbZs-2Fm93FPKckJV25NkkcUaolDJXkLlnpBg0Xbct0oKET0-2FnwIfl-2BW7eIwP1p0BhqiEyHB7UrRv7GqRg7jOp-2BAbQ2UPQH8bOgR-2FU-2FYLgxBsp0t-2BhtjHYTwIYSWbbiCB-2BX9fFdgJLwjjGviXI7Cv1G-2BojfLNKLqM716xBEEEOZt-2FmF05l9JwEHcX4yP1PTaZsbx8eeU2Su6yBDIr28ZQtbVkglHvfp-2BNkqyRWTvbCj8zIiCwlLgdBc069-2Bo7RRFPqYxrxciYHJknt2ealaYUMX52-2BceFyyau8EPxjnbU508-2FI2pd8breJeYGh7khtRHOJYDT5J0SQ9ztqBSFTeNARQ1CHhBpcP04zgk-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
------=_Part_12_325908549.1456342132978
Content-Type: text/calendar; charset=us-ascii
Content-Transfer-Encoding: 7bit
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTAMP:20160224T192852Z
DTSTART:20160225T060000Z
DTEND:20160225T063000Z
SUMMARY:John Doe <> Highr.io - Interview
ORGANIZER;CN=Woo.io:MAILTO:test+scheduler#woo.io
ATTENDEE;CN=John Doe 1st;PARTSTAT=ACCEPTED;RSVP=TRUE:MAILTO:Johnk#hig
hr.io
ATTENDEE;CN=John Doe;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;ROLE=REQ-PARTICI
PANT:MAILTO:Doe#hotmail.com
UID:20160224T192852Z-1#fe80:0:0:0:9c19:bf77:322f:47e5%eth1
END:VEVENT
END:VCALENDAR
------=_Part_12_325908549.1456342132978--
Any idea why it behaves like that and how to solve this?
The iTIP/iMIP protocol does not cover the scenario of "inviting the organizer" via email (see also Change event description for organizer using VCalendar). So it is really up the the IMIP client to choose to offer or not the ability to "import" that event.
Now it is a common practice to include the ORGANIZER also as an ATTENDEE (typically with a PARTSTAT=ACCEPTED) but I suspect that in your case, it wont be enough.
It seems like what you consider the organizer is more of an ATTENDEE with a ROLE=CHAIR and the ORGANIZER is whatever application did put of the meeting together.
Of course, this means that now, REPLYs will go to your 'special/application' organizer and not to the chair of the meeting, which means that you will have to deal with handling those replies, and resend updated versions of your meeting to the various attendees.
All the automated emails sent from woocommerce from my website are marked as spam. Here is the header:
Delivered-To: fontanavideostudios#gmail.com
Received: by 10.64.118.34 with SMTP id kj2csp1351282ieb;
Thu, 2 Apr 2015 05:19:26 -0700 (PDT)
X-Received: by 10.194.176.4 with SMTP id ce4mr94751409wjc.75.1427977166190;
Thu, 02 Apr 2015 05:19:26 -0700 (PDT)
Return-Path: <racebook>
Received: from ns362512.ip-91-121-174.eu ([2001:41d0:1:ef28::1])
by mx.google.com with ESMTP id e5si8490541wjw.70.2015.04.02.05.19.25
for <fontanavideostudios#gmail.com>;
Thu, 02 Apr 2015 05:19:26 -0700 (PDT)
Received-SPF: temperror (google.com: error in processing during lookup of racebook: DNS timeout) client-ip=2001:41d0:1:ef28::1;
Authentication-Results: mx.google.com;
spf=temperror (google.com: error in processing during lookup of racebook: DNS timeout) smtp.mail=racebook;
dkim=temperror (no key for signature) header.i=#
Received: by ns362512.ip-91-121-174.eu (Postfix, from userid 504)
id EA9BA1608B; Thu, 2 Apr 2015 14:16:42 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=racebooking.net;
s=default; t=1427977002;
bh=8Bpk5qKGS/snauZWTEWdgTP8RA8IIyUciiaTtpnN268=;
h=To:Subject:Date:From;
b=uPVvgt52HbS6VIzCMagUSpBDCvF787qIleF13Yw/7E95kuXdVJSdCo5IjbUTmGuBm
TUSe7jiDf4RfGzq2BQJUnFd91RljAVJHxWscY9U/ZFqGU65MjeIIfN7jLa+/k6Aj0/
m2bULvyRjwdU1EInjtl9y3SC593kACANJPR+u8/Y=
To: fontanavideostudios#gmail.com
Subject: Puoi scaricare i files accedendo a questa pagina: https://www.racebooking.net/foto-franciacorta/mio-account/
X-PHP-Originating-Script: 504:class-phpmailer.php
Date: Thu, 2 Apr 2015 12:16:42 +0000
From: Foto Franciacorta <noreply#racebooking.net>
Message-ID: <ddc1208f249c3ad34b96dad0437c49d8#www.racebooking.net>
X-Priority: 3
X-Mailer: PHPMailer 5.2.7 (https://github.com/PHPMailer/PHPMailer/)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
The cause is probably that the Return-Path is wrong. Instead of noreply#racebooking.net (correct) it is racebook, (incorrect). How can i fix it? I couldn't find any setting into Woocommerce options to fix the Return Path.
I fixed that by using this plugin which simply copies the "from" email into the Return Path