Thierry,
Had a chance to test this change this morning, and in my test environment,
this does drastically improve the ability to ssh and su during heavy pop3
load (in test environment, change of 10-15sec to 1-2sec login). While this
is better, the popping is still slowing down authentication on
On 30.5.2012, at 20.25, Root Kev wrote:
mail_location = mbox:/var/empty:INBOX=/var/mail/%u
Note that it's not a good idea for different users to share a single directory
for indexes, which is what this does. Preferably /var/empty wouldn't be even
writable to the users so this wouldn't happen
On 2012-05-24 10:54 AM, Root Kev root@gmail.com wrote:
Below is the majority of our configs, it is mostly basic:
protocols = pop3
Pleease don't post copy/pastes from your config files...
Always provide output of doveconf -n
This has multiple benefits - doveconf -n output is easier to
On 25 May 2012, at 20:00, Root Kev root@gmail.com wrote:
So the best way to would be to remove it that part completely, or should it
be stored somewhere on disk?
Thanks again,
Kevin
yes, best is to remove :INDEX=MEMORY part, and it will store indexes in your
INBOX path, which is
Currently cannot use IMAP as our application to access the mailbox
currently is only setup to access pop3 mailboxes. We are currently using
Dovecot 2.1.4. Below is the majority of our configs, it is mostly basic:
protocols = pop3
listen = ***Address here***
base_dir = /var/run/dovecot1/
On 24 May 2012, at 16:54, Root Kev root@gmail.com wrote:
Currently cannot use IMAP as our application to access the mailbox
currently is only setup to access pop3 mailboxes. We are currently using
Dovecot 2.1.4. Below is the majority of our configs, it is mostly basic:
protocols =
Missed CCing on last reply. See below..
Also, would having Nagios checking the number of messages in a mailbox
cause issues with the popping of messages? And/Or would having a user
accessing the mailbox from two different applications cause issues? Ie.
from Outlook and mobile device? I am
Am 23.05.2012 16:01, schrieb Root Kev:
Missed CCing on last reply. See below..
Also, would having Nagios checking the number of messages in a mailbox
cause issues with the popping of messages? And/Or would having a user
accessing the mailbox from two different applications cause issues?
On Fri, 2012-05-18 at 09:21 -0400, Root Kev wrote:
During the last time that the load went up, it became unable to login / su
to root for the entire period that dovecot was running, we had to kill
dovecot and go back to Popa3d until the mailq was cleared up. We are
running CentOS 5.6 server.
During the last time that the load went up, it became unable to login / su
to root for the entire period that dovecot was running, we had to kill
dovecot and go back to Popa3d until the mailq was cleared up. We are
running CentOS 5.6 server. Based on TOP running at the time the CPU usage
was
On 5/18/2012 6:21 AM, Root Kev wrote:
During the last time that the load went up, it became unable to login / su
to root for the entire period that dovecot was running, we had to kill
This sounds more like you are getting I/O bound or swapping heavily.
What does iostat -x, etc, show when this
Hello all,
We have put Dovecot 2.1.4 on several of our production servers (CentOS, on
Dell R710, with 20GB memory, dual CPU Quad-core). We have a single instance
of Dovecot running and currently have several instances of Popa3d. When
there are significant amount of popping from 2 mailboxes that
On 17.5.2012, at 18.22, Root Kev wrote:
We have put Dovecot 2.1.4 on several of our production servers (CentOS, on
Dell R710, with 20GB memory, dual CPU Quad-core). We have a single instance
of Dovecot running and currently have several instances of Popa3d. When
there are significant amount
13 matches
Mail list logo
