[dmarc-ietf] Re: Review of draft-ietf-dmarc-arc-to-historic

Tero Kivinen <kivinen@iki.fi> Tue, 14 July 2026 14:27 UTC

Return-Path: <kivinen@iki.fi>
X-Original-To: dmarc@mail2.ietf.org
Delivered-To: dmarc@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 0BDB0116962B7 for <dmarc@mail2.ietf.org>; Tue, 14 Jul 2026 07:27:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784039276; bh=iq6DgWFZmF/VFSLbluGY2dC48awgUve5C0QQNSVxra0=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=RYIlsUvBQXRfTBXyY4eUii76pls5aeypotp9eyqdGX/RC2C0aIPinm2PK6lYIYR44 EC9Dvj5kt1YBT3RuqIGMNqRL6tNP06Pf+lgkW7BmkMKAx9lE93ddy+mLacqTU6iA/6 lX+7CQFlTcXa1zA2Ih3NozcN34oeRqotHLcQk6w8=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=iki.fi
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lRzqKFI6sq8C for <dmarc@mail2.ietf.org>; Tue, 14 Jul 2026 07:27:55 -0700 (PDT)
Received: from meesny.iki.fi (meesny.iki.fi [IPv6:2001:67c:2b0:1c1::201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 7EDE6116962AF for <dmarc@ietf.org>; Tue, 14 Jul 2026 07:27:55 -0700 (PDT)
Received: from fireball.acr.fi (unknown [IPv6:2001:1bc8:100:100:5::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: kivinen@iki.fi) by meesny.iki.fi (Postfix) with ESMTPSA id 4h01qP0csBzyTf; Tue, 14 Jul 2026 17:27:45 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1784039265; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=X2GaUw5zoz74wajWsej968oEFhCHepj5RoF1Op2p1eE=; b=QaOse2cd3F57ffVRt72Xh5iih1lwq52NpUcjKjy9ZVxLaAVy48s4k/G4vRgac7xGjXSMXL 0XZY2Oqdk/B9spz1LJyGAX0aDNPQHcvO0Z2NsInMSYZpFF7ygc8qM8fj7SuRZHABWnNvJe nxuXs4cluOjJACpiaCUJAJNCaRhLstk=
ARC-Seal: i=1; a=rsa-sha256; d=iki.fi; s=meesny; cv=none; t=1784039265; b=aa2+cz8IY/+Cf//WIYzLBPCkCXc8sG5i35MsFhVlz7d0SV3YTEYsmOzWNrWH1plo+asDd+ 1AcFipGqPkbFS0kW1/+KvYQ78/mNtzW+VWUFQSlliMpGRPl0dAx1Rs/atfmItDHqy3QvXv XpwXLaoBJwp2O0+7uzZ/KHCPQcifc6M=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1784039265; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=X2GaUw5zoz74wajWsej968oEFhCHepj5RoF1Op2p1eE=; b=nRbddkefX9tFmLrGZCK+hUSDL2Lx5NdEwsuMsDd/apdI7//T9+8c4Cn4gWGki65YgRfTCs h0bVPdKPQ8DL6EZjD9ZrqqzCt1gnG0JUF2ntiV40tNt7Y3+S0y7+wFrkSwvxndYqKyhpYU TE/ebKu+kZSUE2r1OOm5w+79kQo8/dk=
ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=kivinen@iki.fi smtp.mailfrom=kivinen@iki.fi
Received: by fireball.acr.fi (Postfix, from userid 15204) id 5988625C139C; Tue, 14 Jul 2026 17:27:44 +0300 (EEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <27222.18272.223503.730629@fireball.acr.fi>
Date: Tue, 14 Jul 2026 17:27:44 +0300
From: Tero Kivinen <kivinen@iki.fi>
To: Alessandro Vesely <vesely@tana.it>
In-Reply-To: <b29f2b01-8a53-41cf-a6fe-96365d332c47@tana.it>
References: <27205.4140.707940.589907@fireball.acr.fi> <CAL0qLwYRBCs8hg=EZ-dg1VXFgQA7q6+X5kpqWz_AkpgwSG3WmA@mail.gmail.com> <27206.31399.682572.492683@fireball.acr.fi> <CAL0qLwZqgTC5jhx+xxfPh6_0MKWNf6G-hs62a=wqp7=chR_3Vg@mail.gmail.com> <CAH48Zfy-wE_KcLq+6DhM19f5tgcksHbepBRMWeCNuXYKgCzFKA@mail.gmail.com> <27215.46247.267513.270087@fireball.acr.fi> <CAH48ZfxC81X097sdSkPgzRC6bSKVdqV4=VAzwoX173nRhG4+MQ@mail.gmail.com> <b29f2b01-8a53-41cf-a6fe-96365d332c47@tana.it>
X-Mailer: VM 8.2.0b under 26.3 (x86_64--netbsd)
X-Edit-Time: 6 min
X-Total-Time: 5 min
Message-ID-Hash: Y2FCRMGHCP6M6DP32E6UH3MHR2NYY73Q
X-Message-ID-Hash: Y2FCRMGHCP6M6DP32E6UH3MHR2NYY73Q
X-MailFrom: kivinen@iki.fi
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dmarc.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: dmarc@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dmarc-ietf] Re: Review of draft-ietf-dmarc-arc-to-historic
List-Id: "Domain-based Message Authentication, Reporting, and Compliance (DMARC)" <dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/zscddxyfKJa7fDDnUKPxajPyGJk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Owner: <mailto:dmarc-owner@ietf.org>
List-Post: <mailto:dmarc@ietf.org>
List-Subscribe: <mailto:dmarc-join@ietf.org>
List-Unsubscribe: <mailto:dmarc-leave@ietf.org>

Alessandro Vesely writes:
> I'd be curious to learn how they do it.  AIUI, iki.fi accepts forwarding 
> requests to a variety of hosts, so it must assume that every host has a 
> mechanism for whitelisting forwarded traffic.  Do they all use the same 
> mechanism or has every one its own way to manage that?

Iki.fi does not do anything, it is up to the users who set up their
forwardings to point specific mail box provider to make sure their
destination is set up in such way it accepts emails.

In lots of cases (gmail etc) there is no way to do that, so they then
use the www-mail backup to find those emails that did not get through.

Quite a lot of them also have their own mail systems, which they then
configure in various ways. For example my own mail system will accept
all emails, and every mail is processed with my own spam filtering
setup, which will give certain amounts of points depending on the
DKIM/ARC/DMARC etc failure / success. 

> Incoming messages with a broken chain should be rejected. Then, only
> the top ARC set can be trusted/ whitelisted. Iki.fi can in turn
> whitelist forwarders it trusts, which appear in the top ARC set of
> inbound traffic. (Does it have its own whitelisting mechanism?)

As we do not do filtering based on the DKIM/DMARC/SPF/ARC we do not
have specific whitelisting mechanism. We do add
ARC-Authentication-Results which do record status of those when the
mail was received by iki.fi, but we leave the filtering to final mail
box providers.

We do have some users who do WANT to get all spam, i.e., they might
use their iki.fi address as spamtrap.
-- 
kivinen@iki.fi