[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: POP3d locking
From: |
Sergey Poznyakoff |
Subject: |
Re: POP3d locking |
Date: |
Tue, 24 Apr 2001 10:15:34 +0300 |
> We could still play it smart and keep the connection alive
> if we know that the mailbox did not __shrank__ but only __grow__
> (new messages delivered).
Yes, it seems to be necessary. I have already come across the situation
where pop3d refused to update user's mailbox after arrival of
some new mail during the session. I am going to implement this.
By the way, by this time pop3d is running 2 days under a rather
heavy load, the only problem I have seen so far is that of grown
mailboxes.
-Sergey
- sieve, and header_t's api, Sam Roberts, 2001/04/22
- Re: sieve, and header_t's api, Alain Magloire, 2001/04/22
- Message not available
- Re: sieve, and header_t's api, Sam Roberts, 2001/04/23
- Re: sieve, and header_t's api, Alain Magloire, 2001/04/23
- Bug in mapfile_stream.c, Sergey Poznyakoff, 2001/04/23
- Sergey(patch mbx_mbox.c), Alain Magloire, 2001/04/23
- POP3d locking, Alain Magloire, 2001/04/23
- Re: POP3d locking,
Sergey Poznyakoff <=
- Re: POP3d locking, Alain Magloire, 2001/04/24
- Re: POP3d locking, Sergey Poznyakoff, 2001/04/24
- Re: POP3d locking, Alain Magloire, 2001/04/24
- Re: POP3d locking, Sergey Poznyakoff, 2001/04/24
- Re: POP3d locking, Alain Magloire, 2001/04/24
- Re: POP3d locking, Sergey Poznyakoff, 2001/04/24
- Re: POP3d locking, Alain Magloire, 2001/04/24
- Re: sieve, and header_t's api, Alain Magloire, 2001/04/24