A DKIM2 signature's s= list may hold any number of values, and each one is a key lookup and a signature check over the chain's earlier fields, the list itself included, so the work grew with the square of the list: 32,000 values (3.4 MB) took 9 seconds to check, and a message of tens of megabytes would hold a worker for hours. Anyone who can send to port 25 and publish a key for a domain of their own could do this; DKIM2 is checked whenever DKIM is. ARC sets and DKIM2 signatures were limited only to 50 each, with no limit on the size of their fields. Now a DKIM2 chain is left out, and the message has no DKIM2 result, when a signature has more than 4 s= values (real signers use one or two), the chain has more than 20 signatures or message instances, or one of those fields is over 64 KiB. An ARC chain of more than 20 sets, or with a field over 64 KiB, is treated as broken. The same applies to the message a DKIM2-signed DSN returns, and to the admin message analysis and DMARC troubleshooting tools, which use the same helper. DKIM-Signature fields were already limited to 10 per message, so the DMARC alignment check, which may walk the DNS tree once for each passing signature's domain, makes at most 11 such walks. Found in a security review. Test: in the SMTP DKIM2 suite, a valid signature with 5 s= values passed (dkim2=pass); now it has no DKIM2 result, and 1 and 4 values still pass. In crates/smtp, DKIM2 chains with 5 values, 21 links or a 3,000-recipient signature are left out and ones at the limits kept; ARC chains of 21 sets or with a 70,000-byte field are marked broken.