On Friday, June 5, 2020 5:26:19 PM EDT Jim Fenton wrote:
> On 6/4/20 10:39 PM, Dotzero wrote:
> > The goal of DMARC was (and is) to mitigate direct domain abuse.
> > Nothing more and nothing less. It helps receiving systems identify a
> > (correctly) participating domain's mail. That is why a DMARC
On 6/4/20 10:39 PM, Dotzero wrote:
>
> The goal of DMARC was (and is) to mitigate direct domain abuse.
> Nothing more and nothing less. It helps receiving systems identify a
> (correctly) participating domain's mail. That is why a DMARC policy is
> often described as a sending domain's request and
On Fri 05/Jun/2020 13:45:18 +0200 Hector Santos wrote:
> On 6/5/2020 6:34 AM, Alessandro Vesely wrote:
>>
>
>> For completeness, I'd also mention conditional signatures, as a fifth point.
>> They were specified, implemented and then abandoned in lieu of ARC.
>
> h, interesting. Where was the
On 6/5/2020 1:39 AM, Dotzero wrote:
The goal of DMARC was (and is) to mitigate direct domain abuse.
+1, it was the goal of:
[1] The original proof of concept with DomainKeys' built-in o= policy
tag for 1st party support, and
[2] The original DKIM draft augmented with the original SSP dra
On 6/5/2020 6:34 AM, Alessandro Vesely wrote:
4) Require all recipient systems to make special policy accommodations to grant
trust to messages from List B, simply because it comes from List B. This is
feasible, but specific to each participants incoming email filter.
This is a hindrance t
On 6/4/2020 6:31 AM, Douglas E. Foster wrote:
MAILING LISTS.
The mailing list problem can be stated as follows:
* Domain B wants to operate a mailing list.
* The list owner will accept messages from domain A, alter them,
then re-transmit the altered message to member C.
* List owner B
On Thu 04/Jun/2020 12:31:51 +0200 Douglas E. Foster wrote:
> MAILING LISTS.
>
> The mailing list problem can be stated as follows:
>
> * Domain B wants to operate a mailing list.
> * The list owner will accept messages from domain A, alter them, then
> re-transmit the altered message to m
