Hi guys,
when I send e-mails to CentOS mailing list centos@centos.org, I received DMARC / DKIM failure reports. Is it possible to solve this problem and if so how?
This is the first report:
This is an email abuse report for an email message received from IP 208.100.23.70 on Tue, 17 Sep 2019 15:56:25 +0200. The message below did not meet the sending domain's DMARC policy. For more information about this format please seehttp://tools.ietf.org/html/rfc6591 .
Feedback-Type: auth-failure User-Agent: Lua/1.0 Version: 1.0 Original-Mail-From:centos-bounces@centos.org Original-Rcpt-To:obodor@vub.sk Arrival-Date: Tue, 17 Sep 2019 15:56:25 +0200 Message-ID:5502e8ac-6b01-18dd-e028-7d2dd666063b@intar.cz Authentication-Results: dmarc=fail (p=none, dis=none) header.from=intar.cz Source-IP: 208.100.23.70 Delivery-Result: smg-policy-action Auth-Failure: dmarc Reported-Domain: intar.cz
------------ This is the seconf report:
This is an authentication failure report for an email message received from IP 208.100.23.70 on Tue, 17 Sep 2019 15:56:32 +0200 (CEST).
Feedback-Type: auth-failure Version: 1 User-Agent: OpenDMARC-Filter/1.3.2 Auth-Failure: dmarc Authentication-Results: mx.bitactive.com; dmarc=fail header.from=intar.cz Original-Envelope-Id: 46Xl5X0Ss6z1ltXM Original-Mail-From:centos-bounces@centos.org Source-IP: 208.100.23.70 (mail.centos.org) Reported-Domain: intar.cz
Authentication-Results: mx.bitactive.com; dkim=fail reason="signature verification failed" (1024-bit key) header.d=intar.czheader.i=@intar.cz header.b="rSnG4eyi" Received: from mail.centos.org (mail.centos.org [208.100.23.70]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.bitactive.com (Postfix) with ESMTPS id 46Xl5X0Ss6z1ltXM formwanat@forall.pl; Tue, 17 Sep 2019 15:56:32 +0200 (CEST) Received: from mail.centos.org (localhost [IPv6:::1]) by mail.centos.org (Postfix) with ESMTP id 011EE3C1F16; Tue, 17 Sep 2019 13:56:03 +0000 (UTC) X-Original-To:centos@centos.org Delivered-To:centos@centos.org Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=81.19.4.73; helo=nirvana.intar.cz;envelope-from=mg@intar.cz; receiver=centos@centos.org Received: from nirvana.intar.cz (nirvana.intar.cz [81.19.4.73]) by mail.centos.org (Postfix) with ESMTPS id 640643C1F0F forcentos@centos.org; Tue, 17 Sep 2019 13:55:59 +0000 (UTC) Received: from larix.intarnet.cz (larix.intarnet.cz [192.168.1.53]) by nirvana.intar.cz (Postfix) with ESMTPS id 74992C045CD1; Tue, 17 Sep 2019 15:55:57 +0200 (CEST) Received: from [192.168.1.176] (nirvana.intar.cz [81.19.4.73]) by larix.intarnet.cz (Postfix) with ESMTPSA id 5EB62104F460; Tue, 17 Sep 2019 15:55:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intar.cz; s=larix; t=1568728557; bh=ezgga1YmsO9WxPgAc+7ouaZ9HJlG9XkA8LJjbiJd0yA=; h=Subject:To:References:From:Date:In-Reply-To; b=rSnG4eyiHg6tTDdBdCJyp1/ACUczgG+9usycftG3BMz1EwN0zPMPyo0gSkpvxwJUf aM/jvd/gzFJVz7Z6MEw1A9iCE0ZzJy931WvXG+rIJR+Set5hb3fMpu1PgaOz1MIYTF 7Z24H3X1KwUPof1RaKHrFQLYFbr011IbEwz613Xo= To: CentOS mailing listcentos@centos.org, Mauricio Tavaresraubvogel@gmail.com References:b3f926b0-711f-4a32-4a61-644e707a8db8@intar.cz CAHEKYV42BVbAiPmCPnDPhQm53=+t6PVpjheXvjEY535kHFttSg@mail.gmail.com ea092741-5941-c49d-7fe2-b4e8df9944ed@intar.cz CAHEKYV5T8UJNB-PVoj=Aujje3MjN-HiAxKp9kcB24ZK6z8d2Kg@mail.gmail.com From: Miroslav Geisselreitermg@intar.cz Organization: INTAR a.s. Message-ID:5502e8ac-6b01-18dd-e028-7d2dd666063b@intar.cz Date: Tue, 17 Sep 2019 15:55:57 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To:CAHEKYV5T8UJNB-PVoj=Aujje3MjN-HiAxKp9kcB24ZK6z8d2Kg@mail.gmail.com Subject: Re: [CentOS] CentOS7 sometimes don't detect NIC after reboot X-BeenThere:centos@centos.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe:https://lists.centos.org/mailman/options/centos, mailto:centos-request@centos.org?subject=unsubscribe List-Archive:http://lists.centos.org/pipermail/centos/ List-Post:mailto:centos@centos.org List-Help:mailto:centos-request@centos.org?subject=help List-Subscribe:https://lists.centos.org/mailman/listinfo/centos, mailto:centos-request@centos.org?subject=subscribe Reply-To: CentOS mailing listcentos@centos.org Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To:centos-bounces@centos.org Sender: "CentOS"centos-bounces@centos.org
On 2019-09-17 09:06, Miroslav Geisselreiter wrote:
Hi guys,
when I send e-mails to CentOS mailing list centos@centos.org, I received DMARC / DKIM failure reports. Is it possible to solve this problem and if so how?
That is why DMARC took 10 years of heated discussions, before it was actually implemented - in first place by big boys who will never hear/listen. DMARC breaks mail forwarding. Period. Breaks normal way mail lists were operating, but mail lists found work around:
I maintain mail lists for the department, mailman is mail list server we use. There is setting: Replace the From: if set to "Munge from" then mail list will replace sender with mail list itself and it will appear as send by ... through mail list. DMARC enforcing folks/servers will be happy.
Just my $0.02
Valeri
This is the first report:
This is an email abuse report for an email message received from IP 208.100.23.70 on Tue, 17 Sep 2019 15:56:25 +0200. The message below did not meet the sending domain's DMARC policy. For more information about this format please seehttp://tools.ietf.org/html/rfc6591%C2%A0 .
Feedback-Type: auth-failure User-Agent: Lua/1.0 Version: 1.0 Original-Mail-From:centos-bounces@centos.org Original-Rcpt-To:obodor@vub.sk Arrival-Date: Tue, 17 Sep 2019 15:56:25 +0200 Message-ID:5502e8ac-6b01-18dd-e028-7d2dd666063b@intar.cz Authentication-Results: dmarc=fail (p=none, dis=none) header.from=intar.cz Source-IP: 208.100.23.70 Delivery-Result: smg-policy-action Auth-Failure: dmarc Reported-Domain: intar.cz
This is the seconf report:
This is an authentication failure report for an email message received from IP 208.100.23.70 on Tue, 17 Sep 2019 15:56:32 +0200 (CEST).
Feedback-Type: auth-failure Version: 1 User-Agent: OpenDMARC-Filter/1.3.2 Auth-Failure: dmarc Authentication-Results: mx.bitactive.com; dmarc=fail header.from=intar.cz Original-Envelope-Id: 46Xl5X0Ss6z1ltXM Original-Mail-From:centos-bounces@centos.org Source-IP: 208.100.23.70 (mail.centos.org) Reported-Domain: intar.cz
Authentication-Results: mx.bitactive.com; dkim=fail reason="signature verification failed" (1024-bit key) header.d=intar.czheader.i=@intar.cz header.b="rSnG4eyi" Received: from mail.centos.org (mail.centos.org [208.100.23.70]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.bitactive.com (Postfix) with ESMTPS id 46Xl5X0Ss6z1ltXM formwanat@forall.pl; Tue, 17 Sep 2019 15:56:32 +0200 (CEST) Received: from mail.centos.org (localhost [IPv6:::1]) by mail.centos.org (Postfix) with ESMTP id 011EE3C1F16; Tue, 17 Sep 2019 13:56:03 +0000 (UTC) X-Original-To:centos@centos.org Delivered-To:centos@centos.org Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=81.19.4.73; helo=nirvana.intar.cz;envelope-from=mg@intar.cz; receiver=centos@centos.org Received: from nirvana.intar.cz (nirvana.intar.cz [81.19.4.73]) by mail.centos.org (Postfix) with ESMTPS id 640643C1F0F forcentos@centos.org; Tue, 17 Sep 2019 13:55:59 +0000 (UTC) Received: from larix.intarnet.cz (larix.intarnet.cz [192.168.1.53]) by nirvana.intar.cz (Postfix) with ESMTPS id 74992C045CD1; Tue, 17 Sep 2019 15:55:57 +0200 (CEST) Received: from [192.168.1.176] (nirvana.intar.cz [81.19.4.73]) by larix.intarnet.cz (Postfix) with ESMTPSA id 5EB62104F460; Tue, 17 Sep 2019 15:55:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intar.cz; s=larix; t=1568728557; bh=ezgga1YmsO9WxPgAc+7ouaZ9HJlG9XkA8LJjbiJd0yA=; h=Subject:To:References:From:Date:In-Reply-To; b=rSnG4eyiHg6tTDdBdCJyp1/ACUczgG+9usycftG3BMz1EwN0zPMPyo0gSkpvxwJUf aM/jvd/gzFJVz7Z6MEw1A9iCE0ZzJy931WvXG+rIJR+Set5hb3fMpu1PgaOz1MIYTF 7Z24H3X1KwUPof1RaKHrFQLYFbr011IbEwz613Xo= To: CentOS mailing listcentos@centos.org, Mauricio Tavaresraubvogel@gmail.com References:b3f926b0-711f-4a32-4a61-644e707a8db8@intar.cz CAHEKYV42BVbAiPmCPnDPhQm53=+t6PVpjheXvjEY535kHFttSg@mail.gmail.com ea092741-5941-c49d-7fe2-b4e8df9944ed@intar.cz CAHEKYV5T8UJNB-PVoj=Aujje3MjN-HiAxKp9kcB24ZK6z8d2Kg@mail.gmail.com From: Miroslav Geisselreitermg@intar.cz Organization: INTAR a.s. Message-ID:5502e8ac-6b01-18dd-e028-7d2dd666063b@intar.cz Date: Tue, 17 Sep 2019 15:55:57 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To:CAHEKYV5T8UJNB-PVoj=Aujje3MjN-HiAxKp9kcB24ZK6z8d2Kg@mail.gmail.com
Subject: Re: [CentOS] CentOS7 sometimes don't detect NIC after reboot X-BeenThere:centos@centos.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe:https://lists.centos.org/mailman/options/centos, mailto:centos-request@centos.org?subject=unsubscribe List-Archive:http://lists.centos.org/pipermail/centos/ List-Post:mailto:centos@centos.org List-Help:mailto:centos-request@centos.org?subject=help List-Subscribe:https://lists.centos.org/mailman/listinfo/centos, mailto:centos-request@centos.org?subject=subscribe Reply-To: CentOS mailing listcentos@centos.org Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To:centos-bounces@centos.org Sender: "CentOS"centos-bounces@centos.org
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 17.09.2019 16:20, Valeri Galtsev wrote:
On 2019-09-17 09:06, Miroslav Geisselreiter wrote:
Hi guys,
when I send e-mails to CentOS mailing list centos@centos.org, I received DMARC / DKIM failure reports. Is it possible to solve this problem and if so how?
That is why DMARC took 10 years of heated discussions, before it was actually implemented - in first place by big boys who will never hear/listen. DMARC breaks mail forwarding. Period. Breaks normal way mail lists were operating, but mail lists found work around:
I maintain mail lists for the department, mailman is mail list server we use. There is setting: Replace the From: if set to "Munge from" then mail list will replace sender with mail list itself and it will appear as send by ... through mail list. DMARC enforcing folks/servers will be happy.
Just my $0.02
Valeri
and any S/MIME signature is broken ... indeed there exist mail lists, that conserve the S/MIME signature ...
-
Miroslav Geisselreiter -
Valeri Galtsev -
Walter H.