Re: [dmarc-ietf] Do is need a new ptype? Was Re: New authentication method, DNSWL

Alessandro Vesely <> Thu, 08 August 2019 09:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 664EE12011C for <>; Thu, 8 Aug 2019 02:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1152-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Ve1Me6RSQRgJ for <>; Thu, 8 Aug 2019 02:48:43 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 02B7C120044 for <>; Thu, 8 Aug 2019 02:48:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=delta; t=1565257720; bh=v1vOxvG8yCuysxrrSx2B0O6x6OrbHQNVtjGUM1D7fhE=; l=1208; h=To:Cc:References:From:Date:In-Reply-To; b=AOmw8SmI6zcei2bocMXTGXAoAs9dCYixELATPrt51IxzTZslV1iH4ZXzZddWBI5B8 5MhlypBfoiZ4tkRXsTSuUYwQEVEWNuOVIBVSuQmyOHBEoVKdfuJxfhiA1rALHynLRW i53V1/0H+lCFvO96bTGjYiDTn4OctYH6oXmTkTbjINrp7P69kWcNkoDU5Rtt1
Authentication-Results:; auth=pass (details omitted)
Received: from [] ([]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1.2, 128bits, ECDHE-RSA-AES128-GCM-SHA256) by with ESMTPSA id 00000000005DC056.000000005D4BEFF8.0000610C; Thu, 08 Aug 2019 11:48:40 +0200
To: "Murray S. Kucherawy" <>, Matthias Leisi <>
References: <> <> <> <4783309.BXR8ZdE9c3@l5580> <> <> <> <> <> <> <>
From: Alessandro Vesely <>
Openpgp: preference=signencrypt
Message-ID: <>
Date: Thu, 8 Aug 2019 11:48:32 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [dmarc-ietf] Do is need a new ptype? Was Re: New authentication method, DNSWL
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 08 Aug 2019 09:48:44 -0000

On Wed 07/Aug/2019 17:14:22 +0200 Murray S. Kucherawy wrote:
> On Sat, Aug 3, 2019 at 8:28 AM Alessandro Vesely  wrote:
>> IOW, dnswl=pass means the sender was whitelisted.
> If that's the case, why do downstream agents need "policy.ip" at all?

To be whitelisted just means that the sender is a legitimate SMTP
server, AFAICS.  I add Matthias to the recipients list as he can be
much more precise on such criteria, at least for the whitelist he runs.

policy.ip carries more details.  In my use case, "HEURISTIC" viruses
have a significant probability of being false positive.  A downstream
filter extracts the trustworthiness from the policy.ip and makes a
decision based on that value.  Note that this filter runs after the AV
filter, after the end of DATA, while dnswl=pass can be used at HELO to
mitigate SPF forwarding issues.

Some ISPs, albeit whitelisted, either have policies so sloppy as to
tolerate infected customers, or don't spend enough energy to sanitize
them anyway.  The trustworthiness somehow reflects that quality. also reports the category, another octet of policy.ip.