On 6/12/14, 9:36 AM, "Terry Zink" <[email protected]> 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.
>
>That was my thinking, too.
>
>I like the idea of DKIM-Delegate but if I had to choose between doing
>Franck's whitelist [1] suggestion above, or DKIM-Delegate, I'd probably
>do the whitelist because it's less code to implement and maintain; as
>someone who fights spam we're already in the business of checking logs
>looking for patterns and doing overrides and so this would simply be one
>more pattern to look for.
Building your whitelist is a fine thing, but it doesn't replace a real
solution to allowing mail to be forwarded.
DKIM-Delegate gives you a hope of controlling whether your mail gets
accepted at other sites.
Figuring out who to whitelist at your site doesn't. And using List-Id or
List-Post only lets
you whitelist mailing lists, which are only part of the forwarder problem
-- there are also all the non-transparent forwarders (for instance,
enterprise systems which do malware filtering on mail).
Elizabeth
>
>-- Terry
>
>[1] whitelist = override the DMARC p=reject/quarantine action, not skip
>all filtering
>
>_______________________________________________
>dmarc mailing list
>[email protected]
>https://www.ietf.org/mailman/listinfo/dmarc
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
