POP3 server doesn't perform an exlusive-access locks in a transaction required
by rcf1939.
------------------------------------------------------------------------------------------
Key: JAMES-457
URL: http://issues.apache.org/jira/browse/JAMES-457
Project: James
Type: Bug
Components: POP3Server
Versions: 2.2.0
Environment: windows 2000 server, linux redhat
Reporter: Marcello Marangio
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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
