chiefteddy

Fehler beim Versenden einer eRechnung per Mail

Hallo,
seit einiger Zeit erhalte ich nach dem Versenden einer eRechnung von einem Empfänger eine Fehler-Rückmeldung:

"This is an authentication failure report for an email message received from IP ............"

Im Anhang wird mir noch ein header-Datei mitgeschickt:

DKIM-Filter: OpenDKIM Filter v2.11.0 mail01a.edicomnet.com D4F592011BE
Received: from pps.filterd (m0144085.ppops.net [127.0.0.1])
	by mx0b-001c3202.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 53H7cBOf022407
	for <de116882402_mb@mailbox.edicomnet.com>; Thu, 17 Apr 2025 06:21:26 -0500
Resent-Date: Thu, 17 Apr 2025 06:21:26 -0500
Resent-Message-Id: <202504171121.53H7cBOf022407@mx0b-001c3202.pphosted.com>
Received: from bn8pr05cu002.outbound.protection.outlook.com (mail-eastus2azlp17011025.outbound.protection.outlook.com [40.93.12.25])
	by mx0b-001c3202.pphosted.com (PPS) with ESMTPS id 462we72dfy-1
	(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT)
	for <de116882402_mb@mailbox.edicomnet.com>; Thu, 17 Apr 2025 06:21:25 -0500 (CDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none;
 b=wCvjawcvWwpzEDcIbfoELHPGPWmWVClc7gZbx+hWeyNy3vsGKdXRgSvZpZOHFX0HzQye2YGlGXtD4ctt+N0VsPG0tS+ygB4e11fditv+o1LxtuP1caqAucGlEAqHiWXKePXRP3fdp1fMyIsJJV5ZORTuU2/Hts2tc7j6Sfma276uoKDlqJ7GbqyA+IxIxOBA7XPpcPq3DiXtjM42xhi6y8zLHpiIp9ScQZeAR5eBLQCDz8NcGluX/v3VgHShdwvspAy/ZR7p7Qs3ZdllTCkwHVFqmZ1XUkFMO1achubVV1O1prq4Z99s+4n4Pvo4CbXNPMehi06bh6gR4FfQl+aiuw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
 s=arcselector10001;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1;
 bh=+DgZkY9WH1NjAqVzBGVtPYdXUhQ1dO+75JJt6/uPovI=;
 b=mrck+lpr2fMFns+QZY4LfhAmOn3XvmgKPlXT3A78Lk1tbxVlO2PtlHY45qtrfHQUVMyUiZlc1SFb/2C+ZEK7yzrBUQCIrDgrSiKUCclIzoeycCcY23dz3PFWQXhjR5Xg+V3mkLrq6HPNmvACJCh55C9zJGRBSAzo31NIlRd3Zz1hjhpKP65rn3eZ+1hbYMYQiFchgewjW1lHOsvve3euQUAaGnpwc267Wi2cIouy8LcNz3LE8UL0FUowfq40bWCmo4bqHSahufonqlGYWOlxQVsFl+kQMeRcs5u9oB0lPn1TyJCVMvz1eB6XZMsSaclMX7WSNXkMu1WUlXNkIcQW/A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is
 AAA.189.45.83) smtp.rcpttodomain=yyyyyyyyyy.com smtp.mailfrom=xxxxxxxxxx.de;
 dmarc=pass (p=quarantine sp=quarantine pct=100) action=none
 header.from= xxxxxxxxxx.de; dkim=fail (body hash did not verify)
 header.d= xxxxxxxxxx.de; arc=none (0)
Resent-From: <e-invoicing_yyyyyyyyyy-gmbh@yyyyyyyyyy.com>
Received: from DM6PR07CA0105.namprd07.prod.outlook.com (2603:10b6:5:330::8) by
 DM6PR04MB6747.namprd04.prod.outlook.com (2603:10b6:5:243::15) with Microsoft
 SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.8632.32; Thu, 17 Apr 2025 11:21:18 +0000
Received: from DS2PEPF0000343B.namprd02.prod.outlook.com
 (2603:10b6:5:330:cafe::1a) by DM6PR07CA0105.outlook.office365.com
 (2603:10b6:5:330::8) with Microsoft SMTP Server (version=TLS1_3,
 cipher=TLS_AES_256_GCM_SHA384) id 15.20.8655.22 via Frontend Transport; Thu,
 17 Apr 2025 11:21:18 +0000
Received-SPF: Pass (protection.outlook.com: domain of xxxxxxxxxx.de designates
 AAA.189.45.83 as permitted sender) receiver=protection.outlook.com;
 client-ip=AAA.189.45.83; helo=mail. xxxxxxxxxx.de; pr=C
Received: from mx0a-001c3202.pphosted.com (148.163.147.24) by
 DS2PEPF0000343B.mail.protection.outlook.com (10.167.18.38) with Microsoft
 SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.8655.12 via Frontend Transport; Thu, 17 Apr 2025 11:21:18 +0000
Received: from pps.filterd (m0142678.ppops.net [127.0.0.1])
	by mx0b-001c3202.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 53H6W3Z1008718
	for <e-invoicing_yyyyyyyyyy@ aaa.189.45.83.com>; Thu, 17 Apr 2025 06:21:17 -0500
Authentication-Results-Original: ppops.net;	dkim=pass header.s=email
 header.d=xxxxxxxxxx.de;	spf=pass smtp.mailfrom=ar@ xxxxxxxxxx.de;	dmarc=pass
 header.from= xxxxxxxxxx.de
Received: from pps.reinject (localhost [127.0.0.1])
	by mx0b-001c3202.pphosted.com (PPS) with ESMTPS id 461qn7f314-1
	(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT)
	for <e-invoicing_yyyyyyyyyy-gmbh@yyyyyyyyyy.com>; Thu, 17 Apr 2025 06:21:16 -0500 (CDT)
Received: from pps.reinject (m0142678.ppops.net [127.0.0.1])
	by pps.reinject (8.18.0.8/8.18.0.8) with ESMTP id 53HBKFQt010765
	for <e-invoicing_yyyyyyyyyy-gmbh@yyyyyyyyyy.com>; Thu, 17 Apr 2025 06:21:15 -0500
Received: from mail.xxxxxxxxxx.de (mail. xxxxxxxxxx.de [aaa.189.45.83])
	by mx0b-001c3202.pphosted.com (PPS) with ESMTPS id 461qn7f1u4-1
	(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT)
	for <E-invoicing_yyyyyyyyyy-GMBH@yyyyyyyyyy.com>; Thu, 17 Apr 2025 06:18:10 -0500 (CDT)
Received: from zzz-535.management.lokal.zzzzzzzzzz.de ([192.168.175.215]:41317 helo=mail. xxxxxxxxxx.de)
	by mail. xxxxxxxxxx.de with esmtps  (TLS1.3) tls TLS_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <ar@ xxxxxxxxxx.de>)
	id 1u5NFj-000000003Rr-1jeu
	for E-invoicing_yyyyyyyyyy-GMBH@yyyyyyyyyy.com;
	Thu, 17 Apr 2025 13:17:55 +0200
Received: from DO_ xxxxxxxxxx -MTA by mail. xxxxxxxxxx.de
	with Novell_GroupWise; Thu, 17 Apr 2025 13:17:55 +0200
Message-Id: <6800E35E0200003E000245E4@mail. xxxxxxxxxx.de>
X-Mailer: Novell GroupWise Internet Agent 18.2.0 
Date: Thu, 17 Apr 2025 13:17:50 +0200
From: Debitoren <ar@xxxxxxxxxx.de>
To: <E-invoicing_yyyyyyyyyy-GMBH@yyyyyyyyyy.com>
Subject: Rechnung 403571

Außer der Stelle "dkim=fail (body hash did not verify)" [Zeile 21] finde ich keinen weiteren Fehlerhinweis, der eine Ablenung unserer Mails begründen könnte.
Ich kann aber mit dieser Meldung nicht viel anfangen.

Kann mir jemand einen Hinweis zur Fehlerursache bzw. zu deren Beseitigung geben?
Oder ist die Ursache für die Abweisung unserer Mails an einer anderen Stelle zu suchen?

Danke für die Antworten.

Jürgen

PS: Bei unserem mail-Server handelt es sich um ein selbst gehostetes Novell GroupWise-System.
Auf Facebook teilen
Auf X (Twitter) teilen
Auf Reddit teilen
Auf Linkedin teilen

Content-ID: 672736

Url: https://administrator.de/forum/fehler-beim-versenden-einer-erechnung-per-mail-672736.html

Ausgedruckt am: 05.05.2025 um 18:05 Uhr

beidermachtvongreyscull
beidermachtvongreyscull 05.05.2025 um 14:43:33 Uhr
Goto Top
Falls Du in Deiner E-Mailinfrastruktur mehr wie eine Instanz hast, durch die eine gesendete E-Mail durchgeht, so darf nur die letzte den DKIM anbringen.
kpunkt
kpunkt 05.05.2025 um 14:50:28 Uhr
Goto Top
Was sagt denn dkimvalidator.com zu eurer Signatur?
Wie sieht euer Canonicalization-Methode aus? c=simple/simple?

Die Fehlermeldung sagt eigentlich aus, dass die Mail nach der Signierung verändert wurde.
StefanKittel
StefanKittel 05.05.2025 um 15:06:13 Uhr
Goto Top
Hallo,

schicke hier mal eine Mail hin mit dem Test.
https://smartmailflow.de/test

Daran kann man viel sehen.

Wenn Du uns den Link teilst können wir da auch reinschauen.

Stefan
ukulele-7
ukulele-7 05.05.2025 um 15:31:33 Uhr
Goto Top
Und eventuell den Betreff ändern, das Problem ist ja nicht die eRechnung.
chiefteddy
chiefteddy 05.05.2025 um 16:18:03 Uhr
Goto Top
Hallo,
nachfolgend die Ergebnisse von dkimvalidator.com

Original Message:
Received: from mail.xxxxxxxxxx.de (mail.xxxxxxxxxx.de [46.189.45.83])
	by relay-5.us-west-2.tx-prod (Postfix) with ESMTPS id 58E16D590B
	for <V1EZTlbSh0WDcw@dkimvalidator.com>; Mon,  5 May 2025 13:58:27 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=xxxxxxxxxx.de; s=email; h=Content-Type:Mime-Version:Subject:To:From:Date:
	Message-Id:Sender:Reply-To:Cc:Content-Transfer-Encoding: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=Eu7mNuEjxv9lv5LlVO5vYGk9WYrzsHXp7LvyOgz4zgo=; b=cYwe+iHghxujbFoOGk5uiYE/rt
	PHvyRK8YOSpoNYR2CBTmuAtzTxaPnquos3XwY6M0QYynMD2GmnW7xORc/xF/R1hmSIlosihzE4Rqm
	qZ/jj+1CJc/BDk4iv1qoYcCGXEUrmVKEztDZ1zmdBtjKphiH7/HCq3FCVZ6RmwAMhd0um5hIdTiI/
	gTS/ZfLgqz69qVzqFqPHABGwI1lkiPAjQn6JVZdMw/FkhtGm/9AudUijc+GeOJJJLjbuSeB3KjmLV
	ptjCrwBa3KoaCPNvmjd4enNo/c6HpOvM/UVctpTwoPu1oFDnYV7/qXgJQNG3HO0SypQYikvr6MxZ+
	DJXYyvWQ==;
Received: from atk-535.management.lokal.xxxxxxxxxx.de ([192.168.175.215]:32991 helo=mail.xxxxxxxxxx.de)
	by mail.xxxxxxxxxx.de with esmtps  (TLS1.3) tls TLS_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <j.grundmann@xxxxxxxxxx.de>)
	id 1uBwKS-000000005cS-0Iy1
	for V1EZTlbSh0WDcw@dkimvalidator.com;
	Mon, 05 May 2025 15:57:56 +0200
Received: from DO_Xxxxxxxxxx-MTA by mail.xxxxxxxxxx.de
	with Novell_GroupWise; Mon, 05 May 2025 15:57:55 +0200
Message-Id: <6818C3DF020000C80000642C@mail.xxxxxxxxxx.de>
X-Mailer: Novell GroupWise Internet Agent 18.2.0 
Date: Mon, 05 May 2025 15:57:51 +0200
From: "=?UTF-8?Q?J=C3=BCrgen=20Grundmann=20(Xxxxxxxxxx)?="   
 <j.grundmann@xxxxxxxxxx.de>
To: <V1EZTlbSh0WDcw@dkimvalidator.com>
Subject: Test DKIM
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=__Part141D69CF.0__="  
X-Sophos-OBS: success
X-SASI-Version: Antispam-Engine: 6.0.0.1, AntispamData: 2025.5.5.132728
X-SASI-RCODE: 200
X-SASI-SpamProbability: 9%
X-SASI-Hits: BODYTEXTH_SIZE_10000_LESS 0.000000,
 BODYTEXTP_SIZE_3000_LESS 0.000000, BODY_SIZE_4000_4999 0.000000,
 BODY_SIZE_5000_LESS 0.000000, BODY_SIZE_7000_LESS 0.000000,
 FROM_NAME_PHRASE 0.000000, HTML_50_70 0.100000, HTML_ATTACHED_NEG 0.000000,
 HTML_NO_HTTP 0.100000, MIME_LOWER_CASE 0.050000, NO_FUR_HEADER 0.000000,
 NO_URI_HTTPS 0.000000, OUTBOUND 0.000000, OUTBOUND_SOPHOS 0.000000,
 SENDER_NO_AUTH 0.000000, SINGLE_URI_IN_BODY 0.000000, __ANY_URI 0.000000,
 __ATTACH_CTE_8BIT 0.000000, __ATTACH_CTE_QUOTED_PRINTABLE 0.000000,
 __BODY_NO_MAILTO 0.000000, __BODY_TEXT_X4 0.000000, __BULK_NEGATE 0.000000,
 __BUSINESS_SIGNATURE 0.000000, __CT 0.000000, __CTYPE_HAS_BOUNDARY 0.000000,
 __CTYPE_MULTIPART 0.000000, __CTYPE_MULTIPART_MIXED 0.000000,
 __DQ_NEG_DOMAIN 0.000000, __DQ_NEG_HEUR 0.000000, __DQ_NEG_IP 0.000000,
 __FRAUD_CONTACT_NUM 0.000000, __FROM_NAME_NOT_IN_BODY 0.000000,
 __FROM_UTF_Q 0.000000, __FUR_RDNS_SOPHOS 0.000000, __HAS_FROM 0.000000,
 __HAS_HTML 0.000000, __HAS_MSGID 0.000000, __HAS_X_MAILER 0.000000,
 __HIGHBIT_ASCII_MIX 0.000000, __HTML_ATTACHED_BOUND_NEG 0.000000,
 __HTML_ENTITIES_X4 0.000000, __HTML_TAG_DIV 0.000000, __MIME_HTML 0.000000,
 __MIME_TEXT_H 0.000000, __MIME_TEXT_H1 0.000000, __MIME_TEXT_H2 0.000000,
 __MIME_TEXT_P 0.000000, __MIME_TEXT_P1 0.000000, __MIME_TEXT_P2 0.000000,
 __MIME_VERSION 0.000000, __MULTIPLE_URI_TEXT 0.000000,
 __OUTBOUND_SOPHOS_FUR 0.000000, __OUTBOUND_SOPHOS_FUR_IP 0.000000,
 __OUTBOUND_SOPHOS_FUR_RDNS 0.000000, __RCVD_FROM_SUSP_HOSTNAME 0.000000,
 __SANE_MSGID 0.000000, __SINGLE_URI_MPART_BOTH 0.000000,
 __STOCK_CRUFT 0.000000, __SUBJ_ALPHA_END 0.000000, __SUBJ_SHORT 0.000000,
 __TAG_EXISTS_BODY 0.000000, __TAG_EXISTS_HEAD 0.000000,
 __TAG_EXISTS_HTML 0.000000, __TAG_EXISTS_META 0.000000,
 __TO_MALFORMED_2 0.000000, __TO_NO_NAME 0.000000, __URI_IN_BODY 0.000000,
 __URI_MAILTO 0.000000, __URI_NOT_IMG 0.000000, __URI_NO_PATH 0.000000,
 __URI_NS 0.000000, __URI_WITHOUT_PATH 0.000000

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=__Part141D69CF.0__=
Content-Type: multipart/alternative; boundary="=__Part141D69CF.1__="  

DKIM Information:
DKIM Signature

Message contains this DKIM Signature:
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=xxxxxxxxxx.de; s=email; h=Content-Type:Mime-Version:Subject:To:From:Date:
	Message-Id:Sender:Reply-To:Cc:Content-Transfer-Encoding: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=Eu7mNuEjxv9lv5LlVO5vYGk9WYrzsHXp7LvyOgz4zgo=; b=cYwe+iHghxujbFoOGk5uiYE/rt
	PHvyRK8YOSpoNYR2CBTmuAtzTxaPnquos3XwY6M0QYynMD2GmnW7xORc/xF/R1hmSIlosihzE4Rqm
	qZ/jj+1CJc/BDk4iv1qoYcCGXEUrmVKEztDZ1zmdBtjKphiH7/HCq3FCVZ6RmwAMhd0um5hIdTiI/
	gTS/ZfLgqz69qVzqFqPHABGwI1lkiPAjQn6JVZdMw/FkhtGm/9AudUijc+GeOJJJLjbuSeB3KjmLV
	ptjCrwBa3KoaCPNvmjd4enNo/c6HpOvM/UVctpTwoPu1oFDnYV7/qXgJQNG3HO0SypQYikvr6MxZ+
	DJXYyvWQ==;


Signature Information:
v= Version:         1
a= Algorithm:       rsa-sha256
c= Method:          relaxed/relaxed
d= Domain:          xxxxxxxxxx.de
s= Selector:        email
q= Protocol:        dns/txt
bh=                 Eu7mNuEjxv9lv5LlVO5vYGk9WYrzsHXp7LvyOgz4zgo=
h= Signed Headers:  Content-Type:Mime-Version:Subject:To:From:Date:
	Message-Id:Sender:Reply-To:Cc:Content-Transfer-Encoding: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
b= Data:            cYwe+iHghxujbFoOGk5uiYE/rt
	PHvyRK8YOSpoNYR2CBTmuAtzTxaPnquos3XwY6M0QYynMD2GmnW7xORc/xF/R1hmSIlosihzE4Rqm
	qZ/jj+1CJc/BDk4iv1qoYcCGXEUrmVKEztDZ1zmdBtjKphiH7/HCq3FCVZ6RmwAMhd0um5hIdTiI/
	gTS/ZfLgqz69qVzqFqPHABGwI1lkiPAjQn6JVZdMw/FkhtGm/9AudUijc+GeOJJJLjbuSeB3KjmLV
	ptjCrwBa3KoaCPNvmjd4enNo/c6HpOvM/UVctpTwoPu1oFDnYV7/qXgJQNG3HO0SypQYikvr6MxZ+
	DJXYyvWQ==
Public Key DNS Lookup

Building DNS Query for email._domainkey.xxxxxxxxxx.de
Retrieved this publickey from DNS: v=DKIM1;t=s;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9Q3rNJc/HvyMMQfMveGogDwMAUnAGiwZkW+ox8ZpA6/awFmFNnLaieOqXA0AMSFFKP0YXIb2lI50CS2HZLmSay8FuBfSSG0h+8DCHMPPgLVgzZ0xFqeKpz9lH6hm2stxokwaXa5KdBOh038rbKeAyoTfntIB8jSlGhp2jE8BJm0rrEstoDjOX78W1C/Q9tsCS7GtHIwzzXhqqT78lcfCrSnUSJvv63ffaBshzdw96VW+H3/Nv3oVV5yP4aF4DB5tgCjPoDJYcFzI2pWk5r9QM6xI/DJ3R/msyUrfP+4ZEt0omDtnCD2Uv5bZgED2CyNqoc3EYxE1pEsCHtwN7RKg6QIDAQAB
Validating Signature

result = pass
Details: 

SPF Information:
Using this information that I obtained from the headers

Helo Address = mail.xxxxxxxxxx.de
From Address = "=?UTF-8?Q?J=C3=BCrgen=20Grundmann=20(Xxxxxxxxxx)?="  
From IP      = 46.189.45.83
SPF Record Lookup

Looking up TXT SPF record for 


SpamAssassin Score: -0.092
Message is NOT marked as spam
Points breakdown: 
 0.0 URIBL_DBL_BLOCKED_OPENDNS ADMINISTRATOR NOTICE: The query to
                            dbl.spamhaus.org was blocked due to usage
                            of an open resolver. See
                            https://www.spamhaus.org/returnc/pub/
                            [URIs: xxxxxxxxxx.de]
 0.0 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED RBL: ADMINISTRATOR NOTICE:
                            The query to Validity was blocked.  See
                            https://knowledge.validity.com/hc/en-us/articles/20961730681243
                             for more information.
                            [AAA.189.45.83 listed in sa-accredit.habeas.com]
 0.0 RCVD_IN_VALIDITY_RPBL_BLOCKED RBL: ADMINISTRATOR NOTICE: The
                            query to Validity was blocked.  See
                            https://knowledge.validity.com/hc/en-us/articles/20961730681243
                             for more information.
                            [AAA.189.45.83 listed in bl.score.senderscore.com]
 0.0 RCVD_IN_ZEN_BLOCKED_OPENDNS RBL: ADMINISTRATOR NOTICE: The query
                             to zen.spamhaus.org was blocked due to
                            usage of an open resolver. See
                            https://www.spamhaus.org/returnc/pub/
                            [AAA.189.45.83 listed in zen.spamhaus.org]
 0.0 RCVD_IN_DNSWL_BLOCKED  RBL: ADMINISTRATOR NOTICE: The query to
                            DNSWL was blocked.  See
                            http://wiki.apache.org/spamassassin/DnsBlocklists#DnsBlocklists-dnsbl-block
                             for more information.
                            [AAA189.45.83 listed in list.dnswl.org]
 0.0 URIBL_ZEN_BLOCKED_OPENDNS ADMINISTRATOR NOTICE: The query to
                            zen.spamhaus.org was blocked due to usage
                            of an open resolver. See
                            https://www.spamhaus.org/returnc/pub/
                            [URIs: xxxxxxxxxx.de]
 0.0 SPF_HELO_NONE          SPF: HELO does not publish an SPF Record
 0.0 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from
                            author's domain  
 0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily
                            valid
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature

MfG

Jürgen
chiefteddy
chiefteddy 05.05.2025 um 16:27:19 Uhr
Goto Top
Ergebnis https://smartmailflow.de/test

clipboard-image

MfG

Jürgen
chiefteddy
chiefteddy 05.05.2025 um 16:40:11 Uhr
Goto Top
Hallo,

zwischen Mail-Server und Internet ist eine Sophos-Firewall (XG1...).
Dort ist DKIM eingerichtet.

Jürgen
chiefteddy
chiefteddy 05.05.2025 um 16:46:02 Uhr
Goto Top
Hallo,

der Fehler bzw. die Zurückweisung tritt nur bei diesem Kunden auf.
Alle sonstig mit eMail verschickten Rechnungen haben keine Probleme.

Ansonsten habe ich eher das umgekehrte Problem, dass meine Firewall Mails anderer Kunden bzw. Lieferanten aus Sicherheitsgründen ablehnt, weil dort SPF oder DKIM nicht korrekt konfiguriert ist. Das ist aber mit entsprechenden Ausnahme-Regel gelöst.

Jürgen
Dragon0001
Dragon0001 05.05.2025 um 18:09:37 Uhr
Goto Top
Ich gehe von einer Fehlkonfiguration beim Kunden aus. Hier an der Stelle passt offenbar noch alles:
Received: from pps.filterd (m0142678.ppops.net [127.0.0.1])
	by mx0b-001c3202.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 53H6W3Z1008718
	for <e-invoicing_yyyyyyyyyy@ aaa.189.45.83.com>; Thu, 17 Apr 2025 06:21:17 -0500
Authentication-Results-Original: ppops.net;	dkim=pass header.s=email
 header.d=xxxxxxxxxx.de;	spf=pass smtp.mailfrom=ar@ xxxxxxxxxx.de;	dmarc=pass
 header.from= xxxxxxxxxx.de
Received: from pps.reinject (localhost [127.0.0.1])
	by mx0b-001c3202.pphosted.com (PPS) with ESMTPS id 461qn7f314-1
	(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT)
	for <e-invoicing_yyyyyyyyyy-gmbh@yyyyyyyyyy.com>; Thu, 17 Apr 2025 06:21:16 -0500 (CDT)
Zwischen diesem Schritt und der finalen Prüfung wird vermutlich irgendwas an der Mail verändert, wodurch es zum "body hash did not verify" kommt.