in reply to Locking a POP3 Mailbox

Any rfc-compliant (or just written by a sufficiently consious programmer) POP3-server should do transparent locking itself. Look, RFC says locking should take place :) (search for 'lock') Having said that, do you really experience any problems with several pop3 clients accessing the same mailbox in parallel or try to predict possible race condition?

Replies are listed 'Best First'.
Re: Re: Locking a POP3 Mailbox
by exussum0 (Vicar) on May 02, 2004 at 05:12 UTC
    Once the POP3 server has determined through the use of any authentication command that the client should be given access to the appropriate maildrop, the POP3 server then acquires an exclusive- access lock on the maildrop, as necessary to prevent messages from being modified or removed before the session enters the UPDATE state. If the lock is successfully acquired, the POP3 server responds with a positive status indicator. The POP3 session now enters the TRANSACTION state, with no messages marked as deleted.
    Problem is, "should" is the operative word. It's not required. :\

    Humma la beeba la seeba la booba la
    Humma la beeba la seeba la bop
[reply]

In Section Seekers of Perl Wisdom