similar to: per-user mail_max_userip_connections in userdb extra fields

Can you enable 'verbose_proctitle=yes' and maybe compare with ss -tp output? Aki > On 08/01/2020 11:58 Eirik Rye <rye at domeneshop.no> wrote: > > > On 08/01/2020 10:49, Eirik Rye wrote: > > [...] > > In any case, the biggest issue is the one described in the original > message in this thread, where logins are periodically failing for many > for

Uh. It's not actually supported to access same user concurrently from two servers even if you are using NFS. It will cause problems. You should use dovecot director or some other arrangement to make sure this does not happen. Aki > On 09/01/2020 16:56 Eirik Rye <rye at domeneshop.no> wrote: > > > As a workaround for the titular issue, I have tried enabling the >

Yes, I realize this. That is why we are introducing the directors to the cluster. We are also working on doing Dovecot LDA/LMTP delivery, to improve Dovecot's ability to react to new messages. Currently we are dropping email directly into the Maildir through other facilities, which works -fine-. I realize however that IDLE is most likely not working properly with

On 08/01/2020 10:49, Eirik Rye wrote: > [...] In any case, the biggest issue is the one described in the original message in this thread, where logins are periodically failing for many for users: 2020-01-08T10:54:57.436400+01:00 imap dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable

Hi! ~ dovecot --version 2.2.22 (fe789d2) I am wondering if there is a way to set up virtual users with multiple valid passwords. We want to be able to provide users with device/app-specific passwords for their email accounts, as well as being able to create temporary "access tokens" for technical support when required. I quickly found out that passdb using passwd-file or an

We are unfortunately still seeing a lot of these errors once the machine reaches a high number of concurrent users/logins (just below 20k simultaneous IMAP connections on a powerful 24 core machine with 128GB RAM): 2020-01-14T09:18:58.661349+01:00 dovecot: imap-login: Warning: net_connect_unix(imap) succeeded only after retrying - took 140330 us 2020-01-14T09:18:58.854692+01:00 dovecot:

Hi, We are trying to set up a Dovecot Docker image with dynamic database configuration based on environment variables, however the variables do not appear to be expanded in the "connect=" string of the SQL config. The documentation states that environment variables, being listed under global variables, work "everywhere":

Hi, We have recently started using the director in some tests. We are using the static passdb setup (proxy=y nopassword=y) for now, where authentication is done on the downstream IMAP servers. "dovecot director status" shows a breakdown of proxied connections per backend, but there does not seem to be a similar breakdown of user connections per director. The output of

As a workaround for the titular issue, I have tried enabling the "imap-hibernate" service on a couple of servers to reduce the number of running imap processes. Since ~50-60% of clients are in IDLE at any one time, this allows us to reduce the number of running imap processes to less than half of what it was. After this I have yet to see the "net_connect_unix(imap)

Hi, Dovecot v2.3.11.3 (502c39af9) auth_passdb_request_finished appears to fire twice for an IMAP login using a Redis passdb. auth_request_finished only fires once. In the debug log below, the line "Finished passdb lookup" appears to be logged twice (once by "auth" and once by "auth-worker"). However, the actual passdb lookup against Redis is only performed once.

With proctitles below. Strangely, Dovecot is reporting 12679 imap-login sockets in "pre-login" state, which is about 50% more than there are active TCP connections to the server (8271, of which 7546 are in "imap-login" process according to `ss -tp`). On another server, not currently experiencing this issue, the number of TCP sockets appears to more closely match the

While I not certain that this is related to the problem we are experiencing, we are also (more rarely) seeing these: dovecot: master: Warning: service(imap-login): process_limit (16) reached, client connections are being dropped imap-login was set to process_limit=16, client_limit=1250 (for a total of 20000 concurrent clients) on 2.2.27. We never had any issues with this then. I tried

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 24 Feb 2017, Eirik Rye wrote: > 2. Multiple passdbs(?) Check out http://wiki2.dovecot.org/PasswordDatabase result_failure = continue result_internalfail = continue result_success = return-ok - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWLBJDHz1H7kL/d9rAQLffwf/X7qZCiQ/a/dVYPVLC+Ie+RoFqwl/W96m

On 25.09.2018 16:24, Eirik Rye wrote: > Hi, > > Our organization is currently using a passwd-file user database for > our Dovecot installs. However, we now want to provide simple username > aliases. > > We currently use usernames that are -not- equal to the email address, > but due to the fact that many major email clients/providers do not > even allow you to specifiy a

> On 13 Jun 2019, at 20.15, Eirik Rye via dovecot <dovecot at dovecot.org> wrote: > Is there a way in Dovecot to see which (or even how many) users are connected to a specific director without having to count TCP connections? # ps aux | grep imap-login dovenull 3200 0.0 0.0 44676 3376 ? S Apr16 1:15 dovecot/imap-login dovenull 3208 0.0 0.0 44664 3364 ? S

Version 2.3.7 appears to break director ring sync. After upgrading, our logs are full of these kinds of messages: Jul 14 04:09:20 yyy dovecot: director: Error: director: User xxx host lookup failed: Timeout because ring not synced - queued for 30 secs (Ring not synced for 1410 secs, hash=271838221) Jul 14 04:09:20 yyy dovecot: director: Error: director: User xxx host lookup failed: Timeout

>> doveadm search -A mailbox INBOX.Trash savedbefore 30d >> >> but I'm told not to: >> >> "If the -A option is present, the command will be performed for all >> users. Using this option in combination with system users from userdb >> { driver = passwd } is not recommended, because it contains also users >> with a lower UID than the one

Am 11. M?rz 2017 08:04:28 MEZ schrieb MRob <mrobti at insiberia.net>: > >>> We have a need for some users to have an additional folder created >and >>> subscribed for them. >>> >>> Is is possible to return an override for the default "namespace >inbox" >>> containing the needed mailbox definitions in the userdb lookup for

On 2017-03-10 23:28, MRob wrote: > On 2017-03-10 23:22, Christian Kivalo wrote: >> Am 11. M?rz 2017 08:04:28 MEZ schrieb MRob <mrobti at insiberia.net>: >>> >>>>> We have a need for some users to have an additional folder created >>> and >>>>> subscribed for them. >>>>> >>>>> Is is possible to return an

On 2017-03-13 13:40, Aki Tuomi wrote: > On 2017-03-13 19:31, MRob wrote: >> On 2017-03-10 23:28, MRob wrote: >>> On 2017-03-10 23:22, Christian Kivalo wrote: >>>> Am 11. M?rz 2017 08:04:28 MEZ schrieb MRob <mrobti at insiberia.net>: >>>>> >>>>>>> We have a need for some users to have an additional folder