similar to: what's the different between the processes dovecot-auth and dovecot -w

hello: What's the parameter -w for dovecot-auth: dovecot -w my service of dovecot-auth always activing two: one is" dovecot-auth" , the other is" dovecot-auth -w" i don't know the diffevent between them amandy thanks!

Hi. On Dovecot 1.2.x it is possible to run multiple auth daemons. Is it possible on dovecot 2.0.x ? (Setting "process_min_avail" for auth service gives this error message: "doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: service(auth): process_min_avail is higher than process_limit") Sample configuration for dovecot 1.2.8: auth default { count =

Hi all, I use dovecot-1.0-alpha2. Way can't auth process shutdown in a clean way. I allways discover lot of zombies for dovecot-auth, in a short time before shootingdown by linux. But everything work fine for client side. Example: dovecot 22931 0.0 0.0 3840 1104 ? S 12:12 0:00 pop3-login dovecot 22932 0.0 0.0 3844 1108 ? S 12:12 0:00 pop3-login root

With 1.0.15 my configuration I a single dovecot-auth process, which is what I want now. Since upgrading to 1.2.10 I have two such processes: root 16992 16990 0 Feb15 ? 00:00:00 dovecot-auth root 16997 16990 0 Feb15 ? 00:00:00 dovecot-auth -w I can't seem to tweak dovecot.conf to get this down to one auth process again. I've tried setting each of these below to 0,

I setup a test machine with 2.0.alpha3 - Linux, Centos 5.4. I'm using Postfix as my MTA with dovecot to do SASL authorization from /etc/{passwd,shadow}. I'm getting 'dovecot/auth -w' processes hanging around, over a few days I've reached into the 100s. As a test I set auth_worker_max_count = 2, didn't make a difference. Attaching with strace, looks like they're in

Hello Timo, I'm running dovecot-1.2.12/Maildir/LDAP-passdb/LDAP-prefetched-userdb and I'm experiencing "random" latency (which even seem to make squirrelmail timeout sometimes) at login without noticing particular load on the server. LDAP backends are running fine as far as I know so I was investigating maybe mistuned limits : Dovecot is configured (for ~3000 users) with .

On 29 Nov 2016, at 2.57, Christian Balzer <chibi at gol.com> wrote: > > service imap { > # Most of the memory goes to mmap()ing files. You may need to increase this > # limit if you have huge mailboxes. > #vsz_limit = $default_vsz_limit > vsz_limit = 512M > > # Max. number of IMAP processes (connections) > #process_limit = 1024 > process_limit = 524288

Dovecot with libwrap doesn't work on FreeBSD for some reason or another. I have these lines in my /etc/hosts.allow: ALL: LOCAL 127.0.0.1: allow pop3: ALL: allow ALL: ALL: deny Yet when you try to telnet to localhost, port 110 this is what happens: Aug 29 22:48:38 dodo dovecot: pop3-login: Error: connect(tcpwrap) failed: Permission denied I also tried auth_debug=yes to see what's wrong

Hello, We've got a pretty substantial dovecot installation (versions 2.1.7 and 2.2.13 on the backends, but tested with 2.2.24 as well) and this is the relevant config snippet from 10-master.conf: --- default_process_limit = 1024 default_client_limit = 16384 [...] service imap { # Most of the memory goes to mmap()ing files. You may need to increase this # limit if you have huge

Hi, I have an RHEL4 machine running dovecot-1.0.3 + postfix-2.3.2 + postfixadmin + mysql-4.1.20-2.RHEL4.1 + amavisd-new-2.5.2-1. The machine only has a gig of memory in it, I am trying to keep it running until I get new hardware to replace it in a couple of weeks. For the most part it works as advertised but every once in a while it stops talking to the auth server. I think I have tracked this

Greetings all, I've got a dovecot server up that works just fine for a few minutes, and then suddenly won't authenticate users. On top of it, it keeps spawning dovecot-auth processes that won't go away. If any one has seen this or knows what's causing it I sure could use some help. Thanks much. I've included my relevant config info below -- Matthew Thorley dovecot

Hi all, I'm stuck on getting dovecot to work for 2 days. Here's the logfile entries from the startup process(es) dovecot: Jun 18 14:48:43 Info: Dovecot starting up dovecot-auth: Jun 18 14:48:44 Fatal: Can't open passwd-file /var/run/dclogin/mail-passwd: No such file or directory dovecot: Jun 18 14:48:44 Error: Auth process died too early - shutting down dovecot: Jun 18 14:48:44

I have recently begun playing with Dovecot (1.0.beta8) and have run into an interesting scenario. The way my email system is set up is that users of different domains have completely different base dn's. For instance, if a user is part of test.com the bind dn would be uid=user,ou=People,dc=test,dc=com. The bind dn for user at domain.com would be uid=user,ou=People,dc=domain,dc=com. I

Hi dovecot when I modify SIEVE_DEFAULT_MAX_REDIRECTS = 25 in sieve-file:dovecot-1.2-sieve-0.1.7/src/lib-sieve/sieve-limits.h I found this problem occurs about once a week,I'm not sure if it was caused by modify SIEVE_DEFAULT_MAX_REDIRECTS = 25 , defaulte is SIEVE_DEFAULT_MAX_REDIRECTS = 4: LOG: Nov 25 11:20:12 imap-login: Info: Login: user=<any at rails.cn>, method=PLAIN,

Hi, The Dovecot wiki states that Dovecot's master restarts all died processes, which is good for availability. But when I kill dovecot/auth (to simulate an error condition which happened on a machine), the authentication fails with: Nov 16 14:32:40 be dovecot: imap: Error: net_connect_unix(auth-master) failed: No such file or directory It seems -albeit it gets restarted- dovecot/auth

Hi, I'm trying to upgrade from dovecot-1.1.x to 2.1.7. We have our own custom auth server process (because we want to do our own password validation and for other reasons) that listens on a UNIX domain socket and speaks the dovecot auth protocol. In dovecot 1.1 we could configure this with auth external { socket connect { master { path = /var/run/dovecot/auth.sock } }

I have limited information at the moment (currently distracted by other projects) but I'm hoping that someone has already found and solved this problem. I have a v1.2.1 installed on my development box waiting for me to tinker with the configuration. On several occasions, I have noticed that all the dovecot processes are listed as "defunct". I don't recall seeing anything

Hello, as mentioned before, we are migrating our mailboxes from a 0.99 cluster to a 1.0.0 one. With 0.99 dovecot-auth (with LDAP as backend) was leaking quite happily and the dovecot-auth processes frequently did hit their size limit and thus were killed and restarted. Which in 0.99 at least lead to authentication failures on a busy server, as the dovecot master process just killed off the auth

I'm trying to get authentication to work without PAM and just use the standard shadow and passwd files. auth default { userdb passwd { } passdb shadow { } } This seems to be valid code to use /etc/passwd and /etc/shadow. My linux distro is using Salted MD5. Though Dovecot keeps telling me that authentication failed. It doesn't give me any error messages regarding the config. Any

Hi. I've noticed that dovecot (using 2.2.26.0 here) starts dovecot/config processes that stay for long time. Example: [root at ixion-pld ~]# service dovecot restart Stopping Dovecot service.......................................................................................................................................[ DONE ] Starting Dovecot