similar to: Dovecot 2, Imap service, client_limit

I?m trying to configure dovecot lmtp in multi-user mode. My error logs are filled with messages saying that an imap process cannot do a setuid to another user: > May 21 22:28:46 imap(pid 17441 user myuser): Fatal: setuid(512(myuser) from userdb lookup) failed with euid=501(adminuser): Operation not permitted (This binary should probably be called with process user set to 512(myuser) instead of

I am wondering if I really need to use dovecot quota functions or not. Assume for the moment, that, each system user has a quota defined using Linux quotas, and that the Maildir is within their quota limited directory. So, any mail (or files created by the user etc) that would exceed the quota obviously can't be created.? In such an environment, is there any advantage to implementing the same

I'll try and break up my questions the other day about extdata that went unanswered into pieces in the hopes it will be more specific and clear. In general, I am trying to figure out the syntax of the map statement and what is allowed in that statement. So, by map statement, I mean for example perhaps the?dovecot-dict-expire.conf.ext file as shown in the doc. Is the syntax the same for the

Hello Since I started up dovecot2 this morning I get this kind of warning message when I start Dovecot Help appreciated thanks doveconf: Warning: service auth { client_limit=4096 } is lower than required under max. load (5720) Stopping dovecot. Waiting for PIDS: 79978, 79978. doveconf: Warning: service auth { client_limit=4096 } is lower than required under max. load (5720) Starting dovecot.

new Dovecot 2.0.8 installation on Opensuse 11.3 I got the error "lmtp (xxx at mydomain.yy): Error: user xxx at mydomain.yy: Initialization failed: Namespace '': mbox: mbox requires client_limit=1 for service" while trying to transfer mails by lmtp from postfix to dovecot. I googled and looked on the dovecot wiki about this client_limit issue, but no success. What's the syntax

Hi, What is the real difference between client and process limit? According to documentation (http://wiki2.dovecot.org/Services#Service_limits): client_limit: Maximum number of simultaneous client connections. If set to 0, default_client_limit is used instead. process_limit: Maximum number of processes that can exist for this service. If set to 0, default_process_limit is used instead. But

Hello, we have the following problem: Nov 3 09:43:33 minerva dovecot: [ID 583609 local0.warning] master: Warning: service(anvil): client_limit reached, client connections are being dropped Nov 3 09:51:33 minerva dovecot: [ID 583609 local0.error] imap-login: Error: net_connect_unix(anvil) failed: Connection refused Nov 3 09:51:33 minerva dovecot: [ID 583609 local0.crit] imap-login: Fatal:

hello guys hello master Timo i build the last release of dovecot on my centos 5 work well and fine but what the correct value for client limit in service auth { client_limit=6000 } and service anvil { client_limit=6000 } my current dovecot -n ks37777 i386]# dovecot -n # 2.1.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31.5-xxxx-rt14-ipv6-32 i686 CentOS release 5.7 (Final) auth_mechanisms =

Hi, our Dovecot proxy started logging about reaching the client_limit once there were about 1000 connections running over it: Feb 14 15:22:02 vmmailproxy1 dovecot: master: Warning: service(anvil): client_limit (100000) reached, client connections are being dropped Feb 14 15:22:18 vmmailproxy1 dovecot: master: Warning: service(ipc): client_limit (100000) reached, client connections are being

Reading the wiki page for dovecot2 and LDA/Postfix, the system users section (all mail delivery goes to system users)... It shows you can simply use postfix mailbox_command. There is this additional comment: "This command doesn't do a userdb lookup. If you want that (e.g. for per-user quota lookups) you need to add -d "$USER" parameter." So, i added that. Once adding it,

Hello Timo, I'm trying to configure dovecot-2.1.15 master correctly regarding imap-login limits. I want to use service_count=0 and I'm starting with something like this : #default_process_limit = 100 #default_client_limit = 1000 service imap-login { [...] service_count = 0 process_min_avail = 8 vsz_limit = 1024M } -> Does it make sense to set a process_limit if

With service imap { client_limit = 5, service_count = 0 }, when the auth process crashes the existing imap processes cannot reconnect to the auth-master socket because they have long ago dropped root privileges. Is the right solution to this: (1) change the perms on the auth-master socket so processes running as vmail:vmail can connect to it, or (2) change the code so that multi-client imap

We recently switched over mail servers to one running dovecot and postfix on RedHat Enterprise 6. The mail store is NFS on a NetApp filer, the index files are on local disk. We have about 6000 total active users, though not all of them access the system at the same time. All goes well for a while, then we start seeing errors like this in the log: dovecot: imap-login: Error:

All, Just move our mail servers over to a new mail server running postfix 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my /var/adm/files. People are complaining of loosing their connections to the mail server. I've been able to google this error but haven't found fix for this yet. NOt sure where to put the drop-priv option in the config files either. Any

I recently upgraded my dovecot from 2.1 to 2.2, and when I started, I received this message: doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (1024) Searching through my configs, I do not have 1024 set anywhere. In order to stop this I set client_limit=1024 in my auth{} block... this seemed odd that the defaults disagreed with each other. However,

Hi, I'm running dovecot 2.1.17 with "Login processes" in "High-performance mode" as explained here: service imap-login { service_count = 1 http://wiki2.dovecot.org/LoginProcess but i thinks I should also set "service dict" in high-performance mode since sometimes the number of dict processes reach the limit of 100 (from default_process_limit=100) and I

I am using Dovecot in two Server environments. My Legacy (5 years+ old) servers are running dovecot 1.1.20, and are responding as expected. These servers are using an NFS based storage for the /home directory structure, and are working beautifully. However, I need to replace these inefficient servers, and get more current. That brings me to the problem, where I am implementing Dovecot

Hi Timo, Upgraded to 2.0.14 last night for the director-related features and I noticed an oddity in the logs: Sep 28 09:53:21 director2 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:53:56 director1 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:54:23 director2 dovecot:

On a W2K machine, I can easily check the correct hard disk space of my share. However, I have a directory on my share which is linked (on the UNIX side) to another device with more storage. My problem is that W2K is having problems checking the disk space over multiple devices. Has anyone seen this problem and/or know of any solutions? Ed Fatula Lockheed Martin M&DS Gaithersburg, MD

Using current Apple mail 4.5 as client to Dovecot 2.0.13 I see lots of these messages in the log file for one machine and account. Near as I can tell, the client still works (it's mine), but, the messages concern me. Is there some known issue with Apple mail, or, if not, how to capture the information needed to debug? Sample log entires for my user matching on the message: Aug 20 16:28:36