On 05/11/2017 07:39 AM, Sebastian Hagedorn wrote: > > AFAICT the list is only needed to map domain names to corresponding > Organizational Domains in the context of DMARC handling. It looks to me > as if that doesn't cause any problems, but I thought I'd ask ...
Yes, that is what the list is used for. The issue that could result is if a poster is posting From: an address which is a sub-domain (e.g. some.sub.yahoo.com) and which doesn't publish a DMARC policy, but the organizational domain (yahoo.com in this case) publishes say p=reject, dmarc_moderation_action won't be applied in this case. That may or may not be an issue for any particular list depending on the addresses of the posters. Note that you can get rid of the error log messages by putting DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL = '' in mm_cfg.py, but the risk in that is when Python is again able to retrieve the list, you won't be getting it. Also note that the loading of organizational domain data has been made more robust for Mailman 3 including a fallback list if current data can't be loaded. -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
