Bill Cole wrote: > It would require a major change in the nature of reality in order to > work correctly. Stalker probably can't underwrite that.
I'm very disappointed, can't Stalker do the impossible anymore. > This is not about another module locking the mailbox for writing, it > is happening because the user had connected to the POP3 server and > done something but did not disconnect properly. SIMS eventually times > out that other connection, but as long as it remains open and loged > into that mailbox, it is possible that there's still something on the > other end of that first connection which will try to do something > that will change the mailbox, like a DELE command. If SIMS were to > allow 2 POP3 sessions for the same mailbox simultaneously, it would > have no workable way to maintain consistency for that mailbox. How long is the timeout? Can it be changed? Should it be? I'm thinking it might be related to the TCP stack timeout though. RFC1939 gives these 2 messages as examples for the same error: -ERR unable to lock maildrop -ERR maildrop already locked So would a different message than "-ERR Your account is currently in use" provide a friendly notice to the Outlook user instead of asking for the password that was correct in the first place? Clem. ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
