From owner-freebsd-questions@freebsd.org Mon Nov 26 16:10:43 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8911113AD9C for ; Mon, 26 Nov 2018 16:10:42 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 84DA57A646 for ; Mon, 26 Nov 2018 16:10:36 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id wAQGARZk083588 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 26 Nov 2018 17:10:27 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id wAQGARSE083585 for ; Mon, 26 Nov 2018 17:10:27 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Mon, 26 Nov 2018 17:10:27 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: FreeBSD questions Subject: Re: Invalid DKIM signatures in this list In-Reply-To: <20181126125259.GB86999@admin.sibptus.ru> Message-ID: References: <20181126125259.GB86999@admin.sibptus.ru> User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.fig.ol.no X-Rspamd-Queue-Id: 84DA57A646 X-Spamd-Result: default: False [-1.62 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.92)[-0.920,0]; NEURAL_HAM_LONG(-0.65)[-0.645,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[fagskolen.gjovik.no]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[smtp.fagskolen.gjovik.no]; NEURAL_HAM_SHORT(-0.02)[-0.019,0]; IP_SCORE(-0.03)[ipnet: 2001:700::/32(-0.01), asn: 224(-0.11), country: NO(-0.01)]; FORGED_SENDER(0.30)[Trond.Endrestol@fagskolen.gjovik.no,trond@fagskolen.gjovik.no]; R_DKIM_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:224, ipnet:2001:700::/32, country:NO]; FROM_NEQ_ENVFROM(0.00)[Trond.Endrestol@fagskolen.gjovik.no, trond@fagskolen.gjovik.no] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2018 16:10:43 -0000 On Mon, 26 Nov 2018 19:52+0700, Victor Sudakov wrote: > Dear Colleagues, > > I have noticed that the Mailman which manages this list keeps the sender's > "DKIM-Signature:" header intact but modifies the body of the message by adding > a footer. Are you sure? When I received your message, the hash was made up using Message-ID, Subject, To, From, Date, and In-Reply-To. I failed to find the latter field. DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=Message-ID:Subject:To:From:Date:In-Reply-To; bh=lVqWu5A0dAGlwfZYAoaU7QQKfWUKOcE/0wgIPuvq06E=; b=oSl0oX15pzIzynwTUSwgm7sFrQ 9MJS9pRl3koZMQRB711V15zyprv+L4UHLfo/zD/iw211sA8weBVito1fZqHekD/VlMb78reY4xSfW UNLY9HH1RP+/pz8gORfMw7OmkB22I7i+Nxspbae5xEExcPr8YIxzhk4nqC+OdGjjQoVE=; > This behavior invalidates the sender's digital signature with > "dkim=fail (body hash mismatch; body probably modified in transit)". > I think, according to the common sense and RFC6377, the Mailman should either > remove the "DKIM-Signature:" when modifying the body, or refrain from > modifying the body, or add its own valid "DKIM-Signature:" from scratch. What > is currently happening does not make sense. > > Whom do I contact about it? > > An example of this behaviour can be seen in the message with Message-Id: > <20181126081310.026376ddcaad286971909626@sohara.org> and others. -- Trond.