Pavel May writes:
Is the idea of limiting the rate at which a given IP can submit IMAP commands insane (both as a general idea and in the context of dealing with a client generating a ton of I/O in a silly/obscene/stupid fashion)?
Heavy I/O is not necessarily generated by a large number of individual IMAP commands, but rather a "perfect storm" of: certain poor aspects of IMAP's design that makes it difficult to efficiently implement every possible permutation of an IMAP command with an existing mail store (IMAP is heavily biased towards an IMAP-specific mail store, rather than a generic one like a maildir); and badly-designed IMAP clients that do not take advantage of IMAP-specific optimizations, but rather use an IMAP server as either a glorified POP3 server, or as a remote file access server.
But there are IMAP clients which correctly implement IMAP and issue a large number of IMAP commands that complete quickly with a negligible footprint. They should not be penalized for the sins of others.
pgpii2JuytF1Y.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
