Re: Fwd: I-D Action: draft-melnikov-rfc2088bis-01.txt
Arnt Gulbrandsen <[email protected]>
| Newsgroups | gmane.ietf.imapext |
|---|---|
| Message-ID | <[email protected]> |
Alexey Melnikov wrote: > A client that can append can do all sort of damage. Selecting > INBOX and doing "COPY 1:* INBOX" in a loop is my favourite. That was my favourite way of building a large mailbox for testing ;) A few appends, then a dozen or two copy commands. More relevantly, trying to prevent one thing by blocking another is just whackamole. Tiresome and ultimately fruitless. Multiappend, copy, catenate and SMTP all offer ways to get around the size limit, if that's the game. I sort of like 2088bis, but I think it should state what it tries to achieve and forget the rest. This could be good: "This is intended to limit the resource waste by errant clients, not to enforce any kind of quota (RAM, disk space, I/O or anything else) or to stop malevolent clients. Malevolent clients are considered a task for the system administrator." Arnt _______________________________________________ imapext mailing list [email protected] https://www.ietf.org/mailman/listinfo/imapext