Timo Sirainen wrote:
... currently Dovecot doesn't try to lock mbox for the whole POP3 session. That may create problems if two sessions actually try to access the mailbox concurrently. If message gets expunged by another process, Dovecot replies with -ERR to requests to fetch the message. That might confuse some POP3 clients, or cause them to send errors to user.
Is there currently any way to enforce mbox r/w locking for the entire pop3 session in Dovecot? We're considering migrating from qpopper and need a pop3 server that enforces locking while a session is active. Thanks, Ken A
I don't think normally anyone even tries concurrent POP3 access? Anyway, I have thought before that Dovecot/pop3 should lock the mbox for the whole time, just like all others POP3 servers do (and RFC says too).. I'll add in TODO.