You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Norman Maurer (JIRA)" <se...@james.apache.org> on 2010/10/28 07:12:05 UTC
[jira] Resolved: (JAMES-457) POP3 server doesn't perform an
exlusive-access locks in a transaction required by rcf1939.
[ https://issues.apache.org/jira/browse/JAMES-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer resolved JAMES-457.
---------------------------------
Resolution: Fixed
Assignee: Norman Maurer
With the new code we just "mark" a message deleted in the session until quit is processed. In Quit we then delete the message. So until then its still visible to other session. If the second session try to open the message after the first processed quit it will show an error.
I tried the same thing with dovecot and courier pop3. Both do the same. So I think thats ok now
> POP3 server doesn't perform an exlusive-access locks in a transaction required by rcf1939.
> ------------------------------------------------------------------------------------------
>
> Key: JAMES-457
> URL: https://issues.apache.org/jira/browse/JAMES-457
> Project: JAMES Server
> Issue Type: Bug
> Components: POP3Server
> Affects Versions: 2.2.0
> Environment: windows 2000 server, linux redhat
> Reporter: Marcello Marangio
> Assignee: Norman Maurer
> Fix For: 3.0-M2
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org