As I understand how some POP3 implementations work, when you delete a file, it doesn't actually delete the message until the POP3 session ends. The POP3 mailbox is locked for the scope of a POP3 session, otherwise the message number would change.
Right. All RFC-compliant POP3 servers work that way. But the current repository interface does not have a suitable API to perform a batch delete, e.g., delete(Collection keys), hence the queuing "hack."
Ok, I was too generous with my suggestion.
Yes, I think it should work this way, and given as you both say, it's "RFC-mandated", I think we should change the API to reflect this.
-- Serge Knystautas President Lokitech >>> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
