Am 13.11.24 um 08:56 schrieb Kai Bojens via Exim-users:
>> Does a run with debug give any better insight? ARC processing uses
>> the acl debug channel, should you want to cut down on the vebiage.
> Sadly, it does not.
FYI: Updating to 4.98 (Debian 12 Backports) fixed the problem and the Google ARC is now verified without any problems.
The debug output is now this (without the noise):
ARC: collecting arc sets
ARC: found AS: ARC-Seal: i=2; a=rsa-sha256; t=1731488604; cv=pass;
ARC: new instance 2
ARC: found AMS: ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
ARC: existing instance 2
ARC: found AAR: ARC-Authentication-Results: i=2; mx.google.com;
ARC: existing instance 2
ARC: found AS: ARC-Seal: i=1; a=rsa-sha256; t=1731488602; cv=none;
ARC: new instance 1
ARC: found AMS: ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
ARC: existing instance 1
ARC: found AAR: ARC-Authentication-Results: i=1; mx.google.com;
ARC: existing instance 1
ARC: AMS header data for verification:
ARC: header hash: 2454974daa6a034b2153185a6a08f58e6c3c4c24a1bd4457f228421c9460d122
ARC: AMS header data for verification:
ARC: header hash: c338e19a336a8bac9523dcde1afea7df2208115760eafa4ae09bd80d65ae1efc
ARC: AS vfy i=2
ARC: AS header data for verification:
ARC: AS vfy i=2 pass
ARC: AS vfy i=1
ARC: AS header data for verification:
ARC: AS vfy i=1 pass
ARC: AS vfy overall pass
DMARC: no authres
ARC: authres 'arc=pass (i=2) header.s=arc-20240605 arc.oldest-pass=1 smtp.remote-ip=209.85.167.171'
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
