It appears that Laura Atkins <[email protected]> said: >-=-=-=-=-=- >Right, almost everything that comes out of a commercial ESP is single >recipient already - and many of those actually use unique MAIL FROM: addresses >as well. > >> But mailing lists might be a very different story. This week’s delays on >> IETF mailing lists make me wonder if that might have been significantly >worse if they had to be sent (and signed) individually to each recipient.
Probably not. The delays were due to a combination of a big spike in the amount of mail due to the draft cutoff and a disk failure at the hosting provider. It was I/O congestion, not compute. But to return to the original question, multiple recipients in mailing list mail is an artifact of the fact that the software dates from the last millenuium when networks were slow. A decade ago I set up majordomo2 to do individual deliveries with VERP bounce addresses so it could do precise bounce handling, It worked great. Commercial list services like groups.io do individual deliveries both for bounce handling and so it can put a per-user headers and body footers with subscription management links. Sympa, which I use, does some multiple deliveries and some individual ones for bounce probing. I think mailman does the same. If people are going to complain that single deliveries would be too slow, I would want to see data, because with today's computers on today's Internet, I don't believe it. It would be reasonable to design DKIM2 to make signing multiple messages fast, e.g., if messages only have different headers, reuse the body hash. But that's just an optimization. R's, John _______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
