Printed on recycled paper!
> On Jun 12, 2014, at 21:54, "Murray S. Kucherawy" <superu...@gmail.com> wrote:
>
>> On Thu, Jun 12, 2014 at 12:33 PM, Elizabeth Zwicky <zwi...@yahoo-inc.com>
>> wrote:
>>
>>
>> On 6/12/14, 9:36 AM, "Terry Zink" <tz...@exchange.microsoft.com> wrote:
>>
>> >> Franck Martin wrote:
>> >>
>> >> I found that to build the override list for mailing list, I could log
>> >>DMARC rejected
>> >> emails that contained a List-Id or List-Post header. Once reviewing the
>> >>logs
>> >> (once a week, or once a month), you can make an easy decision if you
>> >>want to
>> >> add the found IPs into your override list.
>
> The problem there is that not all lists use the List-* fields.
Well, if they don't use these headers, I don't think they would make any other
modification for any upcoming scheme.
>
> You also have a period of time between which a user wants to start using a
> list and the whitelisting of the list (once a week, or once a month); in
> between, you get the problem we have now.
>
> It also presumes the list sends at least weekly or monthly; many don't. (For
> example, how many ietf.org lists exist but are largely dormant?)
>
> -MSK
>
Sure, this is a stop gap. A solution for today, useable today.
Better scalable solution seems to emerge...
_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc
