Re: OpenARC header info [Solved]

[Seth Blank <seth@xxxxxxxxxxxx>]

Excellent, thanks for the update!

On Mon, Aug 13, 2018 at 2:56 PM, Rolf E. Sonneveld <
R.E.Sonneveld@xxxxxxxxxxxxx> wrote:

> Hi, Seth,
>
> On 11-08-18 12:39, Rolf E. Sonneveld wrote:
>
>> Hi, Seth,
>>
>> On 11-08-18 00:47, Seth Blank wrote:
>>
>>> Gmail does not add ARC header fields to outbound messages that originate
>>> from gmail.
>>>
>>
>> OK, thanks for the info.
>>
>>
>>> OpenARC will only add its own ARC Set to a message in Sealing mode
>>> (either with no mode flag set, or with "s" in the mode flag).
>>>
>>
>> After setting mode to 'sv' I got the ARC header set, so that seems to
>> work OK. Also, after having set it to 'sv' I see the Authentication-Results
>> header you describe. For example, the header of your mail showed:
>>
>> ARC-Filter: OpenARC Filter v0.1.0 mx3.mailtransaction.com
>> 41nKym2tfWz2nGHZ
>> Authentication-Results: mx3.mailtransaction.com; arc=none header.d=
>> mx3.mailtransaction.com
>> ARC-Seal: i=1; a=rsa-sha256; d=mx3.mailtransaction.com; s=201808;
>>     t=1533941281; cv=none; b=J9ik418Z51Ff9y0bwLzsboy1lk4N5EZRpCa7/
>> 8mjRul3O6bNYDBh1cyzvV+bWsgqRns6T3iwRRnqoVwGmy1FUBB1M7dui+/CF
>> Zaf1jiAf65Ev4h6glKsvPAQsKe84q+I60XO3EJza+OmvUzLEOZ3+X0NJm2gf
>> dTW52O/bu0rWxM=
>> ARC-Message-Signature: i=1; a=rsa-sha256; d=mx3.mailtransaction.com;
>>     s=201808; t=1533941281; c=relaxed/simple;
>>     bh=GcKtDQMPXSbnI4A7nObkq9MJvEELbj50qm2KNQuGBdU=;
>>     h=DMARC-Filter:DKIM-Filter:Received:DKIM-Signature:
>> X-Google-DKIM-Signature:X-Gm-Message-State:X-Google-Smtp-Source:
>> X-Received:MIME-Version:Received:In-Reply-To:References:From:Date:
>>      Message-ID:Subject:To:Cc:Content-Type;
>> b=uWC3BvDdr3cjIeuikr1J7ppuNFCgLm87MXhs/Nsz9XLuVj5D3OERZ75zMs
>> dUOmOjOOPpUxlyeSA4h+zEr4wT4qDn7q+OalOQFBvY2ILojoOZ
>> 7ZXgSUEyZKTAzvEMWWzQtYiV76KPiNo+bv9MEhb/JbyIkrW/qRPtIwkNiwHdc+g=
>> ARC-Authentication-Results: i=1; mx3.mailtransaction.com; dmarc=pass
>> header.from=valimail.comspf=pass smtp.mailfrom=seth@valimail.comdkim=pass
>> (2048-bit key; unprotected) header.d=valimail.com header.i=@valimail.com
>> header.b=GboU5tPB; dkim-atps=neutral
>> DMARC-Filter: OpenDMARC Filter v1.3.1 mx3.mailtransaction.com
>> 41nKym2tfWz2nGHZ
>> Authentication-Results: mx3.mailtransaction.com; dmarc=pass header.from=
>> valimail.com
>> Authentication-Results: mx3.mailtransaction.com; spf=pass smtp.mailfrom=
>> seth@xxxxxxxxxxxx
>> DKIM-Filter: OpenDKIM Filter v2.10.3 mx3.mailtransaction.com
>> 41nKym2tfWz2nGHZ
>> Authentication-Results: mx3.mailtransaction.com;
>>     dkim=pass (2048-bit key; unprotected) header.d=valimail.com
>> header.i=@valimail.com header.b=GboU5tPB;
>>     dkim-atps=neutral
>>
>>
>> See the second line. If you want me to send the complete headers, please
>> let me know.
>>
>>
>>> In validation mode, there should be at a minimum an arc
>>> Authentication-Results stamp, that should look like
>>> "Authentication-Results: [authservid]; arc=none"
>>>
>>> Do you see that show up if you're explicitly in mode "v" ?
>>>
>>
>> I can confirm that I do not see this Authentication-Results header when
>> using mode 'v'. So either this is an omission/bug in the code, or it is
>> something wrong with my configuration.
>>
>
> Problem has been solved. It appeared that on one of my systems I had git
> cloned from the wrong location (https://github.com/flowerysong/OpenARC.git
> instead of the trusteddomainproject location). The flowerysong location had
> an outdated/forked version of openarc. After correcting this, I now get the
> proper Authentication-Results header in inbound messages, also when I just
> have 'Mode v'.
>
> Thanks,
> /rolf
>
>


-- 

Seth Blank | Director of Industry Initiatives

E: seth@xxxxxxxxxxxx | P: 415.273.8818