[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: state of openarc.org


To the original question, at least, my inbound verification (with Rspamd) does not validate the ARC-Seal from this list.  From my previous message via the mailing list headers:

[...]
Received: from dahlem.somaf.de (dahlem.somaf.de [185.183.157.243])
	(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)
	by mailhub-use-1a.convivian.com (Postfix) with ESMTPS id 12B0E1005163
	for <jered@xxxxxxxxxxxxx>; Wed, 31 Jan 2024 13:37:18 +0000 (UTC)
Authentication-Results: mailhub-use-1a.convivian.com;
	dkim=pass header.d=convivian.com header.s=default header.b=Kr2I+ZLk;
	spf=pass (mailhub-use-1a.convivian.com: domain of "openarc-users+bounces-80-jered=convivian.com@xxxxxxxxxxx" designates 185.183.157.243 as permitted sender) smtp.mailfrom="openarc-users+bounces-80-jered=convivian.com@xxxxxxxxxxx";
	arc=reject ("seal check failed: fail, {[1] = sig:dahlem.somaf.de:reject}");
	dmarc=pass (policy=none) header.from=convivian.com
[...]

--Jered


----- On Jan 31, 2024, at 8:37 AM, Jered Floyd jered@xxxxxxxxxxxxx wrote:

> *crickets* Does this mean I'm the only person on the list trying to use OpenARC?
> 
> --Jered
> 
> ----- On Jan 23, 2024, at 5:31 PM, Jered Floyd jered@xxxxxxxxxxxxx wrote:
> 
>> I use OpenARC to sign outgoing messages, but have no evidence that it "does
>> anything".  I've tried for years to figure out how get, for example, google.com
>> to use it as a trust indicator but there is no documentation, way to register,
>> etc.  I'd love to how if it helps or if I'm just burning CPU cycles.
>> 
>> In practice, I've found that despite implementing SRS, ARC, DKIM, SPF, and
>> aggressive inbound spam filtering, any amount of forwarded (e.g. procmail-style
>> bent pipe) messages that are considered spam causes extreme delivery problems
>> to GMail.  It's quite frustrating.
>> 
>> --Jered
>> 
>> ----- On Jan 23, 2024, at 4:33 PM, A. Schulze sca@xxxxxxxxxxxxxxxxx wrote:
>> 
>>> Am 23.01.24 um 00:47 schrieb Pete Holzmann:
>>>> Thanks for doing this. I haven't yet looked at your new version, but this could
>>>> easily be
>>>> due to the bug I reported months ago, showing  that *all* of the OpenZZZ milters
>>>> have a
>>>> long term bug, failing to properly parse a wide variety of valid Auth headers.
>>> 
>>> Pete,
>>> 
>>> I think, you talk about
>>> https://github.com/trusteddomainproject/OpenDKIM/issues/186, right?
>>> Well, yes, that may be a bug. But I don't believe, this is a reason for the
>>> defect I saw.
>>> 
>>> My question to all list participants: does anybody use OpenARC to create ARC
>>> seal data
>>> and has a proof these data could be verified by OpenARC or an other ARC
>>> implementation?
>>> 
> > > Thanks

Follow-Ups:
Re: state of openarc.orgAndrew Beverley <andy@xxxxxxxxxxx>
Re: state of openarc.orgBenny Pedersen <me@xxxxxxx>
References:
state of openarc.org"A. Schulze" <sca@xxxxxxxxxxxxxxxxx>
Re: state of openarc.orgPete Holzmann <webbed.pete@xxxxxxxxx>
Re: state of openarc.org"A. Schulze" <sca@xxxxxxxxxxxxxxxxx>
Re: state of openarc.orgJered Floyd <jered@xxxxxxxxxxxxx>
Re: state of openarc.orgJered Floyd <jered@xxxxxxxxxxxxx>