Ale, I write in the context of a business domain, where acceptable emails must be acceptable based on the combination of organizational policy. An organization is likely to block some lists as not acceptable because they are not business-related. You don't need to use the company network to chat with your quilting club, unless your business is quilting-related.
My point was entirely about authentication. When we know that all messages from a list will arrive unauthenticated, it is foolish to use authentication as a reason to block a subset of those messages. Ignoring authentication does not mean whitelisting from all content checks; that is an independent decision. And should be easy for anyone to detect a mailing list, based on a stream of messages, with multiple From domains and a single Mail From domain, all without authentication. It may be a list or an ESP or an auto-forwarder or a fraudster. It is reasonable to investigate and determine which situation applies, then configure filtering rules based on what is learned. The comment about "personal devices" was not essential to the argument. My organization blocks access to personal webmail sites because we assume that they are inadequately protected against spam, so personal email needs to be retrieved on personal devices. If an organization is blocking a mailing list as an unacceptable risk, then it should take measures to prevent that restriction from being circumvented using personal email accounts on in-house computers. I think you are suggesting that organizations should also figure out whether their users have actually subscribed to a list before allowing list messages to penetrate the network. I agree, and I have said as much previously. I have vetted all of the mailing lists that send messages into our network. I have previously observed that GoogleGroups.com and Groups.Outlook.Com are known sources of malicious traffic, and they are blocked by default. Hosting services for organizations could delegate the allow/block rule to their clients. Mailbox Providers for the general public have the hardest problem to solve, butso not need my advice. Doug On Fri, May 15, 2026 at 1:24 PM Alessandro Vesely <[email protected]> wrote: > On Fri 15/May/2026 17:22:59 +0200 Douglas Foster wrote: > > The mailing list problem has always been an evaluator problem. An > evaluator > > who wants to meet the needs of his user needs to figure out which lists > can be > > trusted and then allow all traffic from the list. > > > Coarse-grained authorizations may become unmanageable, especially when > very > large mailbox providers are involved. > > Allowing a mail stream for all users also seems gameable in the case of > free-mail providers. > > > > An alternate approach is to declare the list to be too risky, and block > all > > traffic from the list. Users can participate from personal Gmail > accounts on > > personal devices, as a fallback. > > > So users cannot subscribe to low-reputation lists? > > Also, what does "participate from personal devices" mean in this context? > > > > The only strategy that makes no sense is allowing some traffic because > > authentication failure is ignored, while blocking some traffic because > > authentication is not ignored. > > > Valid authentication remains valid. Authorization is a different matter. > > I can subscribe myself to any list I like, but I cannot subscribe /you/ to > any > list. Why should the same authorization decision cover both cases? > > > Best > Ale > -- > > > > > >
_______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
