search for: loginprocess

Hello, We are running dovecot 1.0.5 on a test server, with FreeBSD 6.2 (though I have noticed the same problem since dovecot versions in the 0.99 range). We don't have very many simultaneous pop/imap users, but we have a proliferation of pop3-login processes. Currently we have 128 such processes. We have 11 imap-login processes, but only a few actual imap processes running. Is this normal?

...d to in a proxy or proxy_maybe lookup must be an IP address see: the main PasswordDatabase/ExtraFields/Proxy <http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy> page for more info A patch is available to enable lookups, but it has some imporant caveats due to the nature of the LoginProcess <http://wiki.dovecot.org/LoginProcess> that the proxy function is a part of. This page exists to discuss these. The Problem Proxying is done from the dovecot login processes, both pop3-login & imap-login call code in src/login-common/login-proxy.c to handle the proxying to the...

Hi, I have a question I have not cleared after reading https://wiki.dovecot.org/LoginProcess. I'm developing a proxy server (without director, because the backend server is specified by a ldap lookup). My question is: the limit of imap (or pop3) concurrently users that the proxy can handle is determined by the imap-login limit or the imap one? -- Angel L. Mateo Mart?nez Secci?n...

...r 02 14:34:36 imap-login: Info: Disconnected: *Connection queue full *(auth failed, 1 attempts): user=<//user at example.com/ <mailto:amministrazionevendite at pec.gmatica.it>/>, method=PLAIN, rip=//xx.xx.xx.xx//, lip=//xx.xx.xx.xx//, TLS/ I see this wiki page: http://wiki2.dovecot.org/LoginProcess but i read: It works by using a number of long running login processes, each handling a number of connections. This loses much of the security benefits of the login process design, because in case of a security hole (in Dovecot or SSL library) the attacker is now able to see other users logging in...

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 find these errors in the logs: Sep 25 15:32:24 imap(info at xxxx), session=<z9N2SDXnIQCy71XC>: Error:...

We've been collecting some stats to see what kind of benefits UP/SquirrelMail's IMAP Proxy in for our SOGo webmail users. Dovecot is running in High-performance mode http://wiki2.dovecot.org/LoginProcess with authentication caching http://wiki2.dovecot.org/Authentication/Caching During the weekend two servers (webmail3 and webmail4) has been running with local imapproxy and two servers without (webmail1 and webmail2). Each server has served about 1 million http requests, over 3 days. server...

Hi, I can't find any references to this problem on 2.x. I upgraded to 2.0.8 last night, and now I am getting these errors in the logs (along with the server refusing new connections): > Dec 8 09:46:52 orford dovecot: imap-login: Disconnected: Connection queue full (no auth attempts): rip=x.x.x.x, lip=x.x.x.x, TLS > Dec 8 09:47:16 orford dovecot: imap-login: Disconnected: Connection

After a few hours of running, I get tons of the following errors in my logs: dovecot: Oct 08 07:41:50 Error: auth(default): ldap(user at domain,x.x.x.x): Request queue is full I removed the username and IP, obviously. Any idea how to stop this? I have about 5 Thousand users using horde that login ever 1-5 minutes to refresh their page. I assume it is a setting, but I am confused as to

> On 19 Jan 2016, at 16:04, Nikolaos Milas <nmilas at noa.gr> wrote: > > On 19/1/2016 3:31 ??, Timo Sirainen wrote: > >> Change it the other way around: >> >> remote 127.0.0.1 { >> protocol imap { >> ... >> } >> } > > Thank you for your advice Timo (on "remote" blocks). > > So, the "remote"

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:

First, thanks for this great product. We migrated from Courier last week with only small bumps along the way. We have a few hundred active users with a mix of pop3 and imap clients. The server is running on sparc Solaris 9. We're seeing a problem now with the number of "imap-login" processes rising slowly to it's limit and then (understandably) not letting any more logins

Hi, My dovecot process seam blocked on dovecot/imap [blocking on log write], only restart fix it. How solve that's? Cheers, -- alpha_one_x86/BRULE Herman <alpha_one_x86 at first-world.info> Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server management IT, OS, technologies, research & development, security and business department -------------- next

Greetings - I've now got as far as playing with the imaptest10 test utility to see if I can stress-test our development server. imaptest10 is built against dovecot-1.0rc28 It may just be that I'm excessively heavy handed, but when I let imaptest10 rip with the command... ./imaptest10 user=test%03d host=testserver.imap.york.ac.uk clients=50 mbox=./dovecot.mbox msgs=1000 secs=30

Hello Timo, I've got some questions about dovecot-auth processes which I cannot answer just by reading the doc : [ Note : my problem is that I often see dovecot: pop3-login: Can't connect to auth server at default: Connection refused and I'm looking for a way to tweak dovecot.conf parameters to allow more login <-> auth connections ] - I'm not sure I get the auth

...ts hibernating as possible, as the hibernation > process is much smaller than actual IMAP process. > > You should probably also look at reusing the processes, as this will > probably help your performance, > https://wiki.dovecot.org/PerformanceTuning and > https://wiki.dovecot.org/LoginProcess are probably a good starting > point, although I suspect you've read these already. > > If you are running a dense server, cranking up various limits is rather > expected. > > Aki >

Hello, as some may remember, we're running very dense IMAP cluster here, in excess of 50k IMAP sessions per node (current record holder is 68k, design is for 200k+). The first issue we ran into was that the dovecot master process (which is single thread and thus a bottleneck) was approaching 100% CPU usage (aka using a full core) when trying to spawn off new IMAP processes. This was

hi all We have an ocfs2 cluster compose of 4 Debian lenny serveurs wich have access to an ISCSI LUN we have create a partition on this Lun and formated this partition as OCFS2. 2 serveurs does mail delivery (SMTP) and the two other are pop/imap servers. The smtp servers use dovecot LDA to deliver to mailboxes. La version de dovecot is 1.2.13, ldirectord balance conexion to the

...this > community, every time it has come up over the years, with almost rabid Neither Timo nor dovecot.fi did responded with "use fail2ban", if I remember correctly. I actually wonder, why nobody replied with: "this is what tcpwrapper is for" :-) http://wiki2.dovecot.org/LoginProcess?highlight=%28tcp+wrapper%29 what had been ruled out by the OP with a conditional *if*. If you for instance add a passdb{} driver, that does not interfere with the remaining code base (much), so one can use: passdb { driver = ipdeny args = <host>/matchpattern/action .... *** } in front...

Can anyone share the proper config to get wrappers working in dovecot on FreeBSD? The dovecot examples do not seem to work, and I thought perhaps FBSD needs slightly different configs. I've compiled with: -DHAVE_LIBWRAP which I presume is the first step. The example for dovecot.conf in uncommenting: login_access_sockets = tcpwrap merely causes a log error of "imap-login: Error:

> On April 7, 2017 at 1:26 PM "Angel L. Mateo" <amateo at um.es> wrote: > > > Hi, > > I have a question I have not cleared after reading > https://wiki.dovecot.org/LoginProcess. > > I'm developing a proxy server (without director, because the backend > server is specified by a ldap lookup). > > My question is: the limit of imap (or pop3) concurrently users that the > proxy can handle is determined by the imap-login limit or the imap one? >...