Re: [dmarc-ietf] non-mailing list use case for differing header domains

2020-08-03 Thread Ken O'Driscoll
On 03/08/2020 01:43, Douglas E. Foster wrote:
>
> I am not sure what "Internet Scale" means to you.   Most of the major
> recipients have bulk mailer registration systems.   It does not
> guarantee whitelisting, but it tends to produce that effect.   I have
> had occasion to register with most of them.   So "does not scale" is
> not obvious to me.

This is not correct. In the past some large providers did offer such
lists but these days most have moved away from that model for various
reasons. You'll still find someone offering such as service, and
pay-to-play is a thing too but none of this is a) widespread and b)
based on any type of standard - it's all proprietary. The same goes for
sender certification services such as ReturnPath.

"Internet Scale" means being able to scale to internet level of usage
and platform interoperability.  TCP/IP and DNS are good examples. Data
(e.g. lists of approved senders) maintained internally by individual
organisations can't scale to that level for the same reason that
organisations siloing their own DNS and routing information wouldn't
work. Interoperability.

Organisations publishing information (e.g. an SPF record) in their DNS
zone works because it's based on an existing internet scale
interoperable platform. While the "heavy lifting" of interpreting the
SPF record might be undertaken by a variety of different software and
system platforms, the mechanism is standardised based on the RFC. Again,
interoperability.

Ken.

___
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc


Re: [dmarc-ietf] Apropos of the de-munging draft

2020-08-03 Thread Alessandro Vesely
On 2020-08-02 7:51 p.m., John Levine wrote:
> In article  you write:
>>> Unwrapping a MIME attachment is a lot easier than the proposed DKIM
>>> unmunging but I doubt either is going to show up in MUAs any time
>>> soon. Perhaps you could do it in a mail gateway.
>>
>>
>> Looking at the steps required to carry out the proposed unmunging, "a lot 
>> easier" doesn't seem to be an accurate measurement.
> 
> In python it's about two lines since there are well debugged libraries to 
> handle MIME.  Same in most other languages.


If you use a library, most common operations can be done better than unusual 
ones, the actual complexity notwithstanding.

The steps I outlined for tf=footer[*] can be done adding a few lines to 
Murray's library, in C.


> I still would be amazed if any MUAs did this, also keeping in mind that the 
> changes that MLMs make ARE USEFUL.


Agreed.  IMHO, Murray's lib should do just a virtual unmunge, while 
canonicalizing.

To actually replace From: with the original Author: can be done by the MDA, 
based on trusted A-Rs, after any dot-forward.

Best
Ale
-- 

[*] https://mailarchive.ietf.org/arch/msg/dmarc/2ZN7DS5NktoyEPItZ5vzr-xd0Mc






























___
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc