pop.gmail.com sends LOGIN-DELAY, we should honor it, but we don't: 6.5. LOGIN-DELAY capability CAPA tag: LOGIN-DELAY Arguments: minimum seconds between logins; optionally followed by USER in AUTHENTICATION state. Added commands: none Standard commands affected: USER PASS APOP AUTH Announced states / possible differences: both / yes Commands valid in states: n/a Specification reference: this document Discussion: POP3 clients often login frequently to check for new mail. Unfortunately, the process of creating a connection, authenticating the user, and opening the user's maildrop can be very resource intensive on the server. A number of deployed POP3 servers try to reduce server load by requiring a delay between logins. The LOGIN-DELAY capability includes an integer argument which indicates the number of seconds after an "+OK" response to a PASS, APOP, or AUTH command before another authentication will be accepted. Clients which permit the user to configure a mail check interval SHOULD use this capability to determine the minimum permissible interval. Servers which advertise LOGIN-DELAY SHOULD enforce it. If the minimum login delay period could differ per user (that is, the LOGIN-DELAY argument might change after authentication), the server MUST announce in AUTHENTICATION state the largest value which could be set for any user. This might be the largest value currently in use for any user (so only one value per server), or even the largest value which the server permits to be set for any user. The server SHOULD append the token "USER" to the LOGIN-DELAY parameter in AUTHENTICATION state, to inform the client that a more accurate value is available after authentication. The server SHOULD announce the more accurate value in TRANSACTION state. (The "USER" token allows the client to decide if a second CAPA command is needed or not.) Servers enforce LOGIN-DELAY by rejecting an authentication command with or without the LOGIN-DELAY error response. See section 8.1.1 for more information.
Hehe, great. Yesterday I thought about opening a bug about exactly this. Questions are what to do if we encounter that capability in a) normal message retrieval b) biff I don't feel good changing the interval the user has chosen without asking. But in biff state we can't. And is it possible to change the interval setting from POP protocol code? I don't have looked what code starts the request.
No, we'd have to propagate the info to the pop3incoming server and then respect it there, if that makes sense. As far as biff is concerned, this would override it, and when we tried to do the biff, we'd just back out...
seems like a fine idea but I'm not going to be working on it in the near future.
Assignee: bienvenu → nobody
You need to log in before you can comment on or make changes to this bug.