[JAMES-457] POP3 server doesn't perform an exlusive-access locks in a transaction required by rcf1939.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 3.0-M2
• Component/s: POP3Server
• Environment: windows 2000 server, linux redhat
• Assignee: Norman Maurer
• Reporter: Marcello Marangio
• Created: 16/Mar/06 16:52
• Updated: 28/Oct/10 05:10
• Resolved: 28/Oct/10 05:10

Description

According to rfc1939 the standard behavoir of a pop3 server is:
1) The client opens a connection and server gets into the AUTORISATION state.
2) The user authenticate himself and the server gets into the TRANSACTION state, "... 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. "
3) The client sends a QUIT command and the server gets into the UPDATE state, updating the repository.

James doesn't perform the exclsive-access lock required by rfc1939