similar to: login failure after upgrade to dovecot 2.3.7.2

Hi, I have an issue with dovecot 2.3.7.2. When lmtp stores a message into INBOX, I get this error: 2019-10-29 16:32:53 lmtp(?test at XXXX?)<28874><4IPiEytbuF3KcAAAioI89A>: Error: sieve: Execution of script /config/dovecot/common/default.sieve was aborted due to temporary failure 2019-10-29 16:32:53 lmtp(?test at XXXX?)<23470>: Error: sieve:

Hello. I have problems with duplicate emails when using replication and configured message filters on the client. Looks like when letter comes, it processed by replication and immediately after this processed by filter on client and moved to another folder. When it arrives to slave server into INBOX, it replicated back to master into INBOX and only after that - slave receives MOVE command. The

> On 16/11/2020 13:44 ????? <morikawa-k6 at itec.hankyu-hanshin.co.jp> wrote: > > > We have upgraded dovecot from 2.0.9 (centos6) to 2.2.36 (centos8). > > If more than 1000 users log in, the following error will occur. > ------------------------- > Nov 16 11:33:00 xxxxxxxx dovecot[1361]: imap-login: Error: master(imap): > net_connect_unix(imap) failed: Resource

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:

You need to configure stats service client limit and imap service client limit. Those are different services than imap-login service. Aki > On 17/11/2020 01:28 ????? <morikawa-k6 at itec.hankyu-hanshin.co.jp> wrote: > > > Aki-san > > I have already seen that page. > Is the setting method wrong? > > Is there any other tuning point? > > morikawa >

Hi.. there is supposed to be only at most one (1) stats process. Having multiple stats processes breaks stats. Aki > On 18/11/2020 01:48 ????? <morikawa-k6 at itec.hankyu-hanshin.co.jp> wrote: > > > Aki-san > > Last night We adjusted the "process_limit" in the stats service to get rid of the error. > > "client_limit" is in the blank

> Am 04.09.2019 um 16:58 schrieb Sami Ketola via dovecot <dovecot at dovecot.org>: > > > >> On 4 Sep 2019, at 16.38, R.N.S. via dovecot <dovecot at dovecot.org> wrote: >>> >>> passdb { >>> args = /etc/dovecot/master-users >>> driver = passwd-file >>> master = yes >>> pass = yes >>> } >>>

Dear dovecot developers, I have an issue with the Pigeonhole IMAPSieve Plugin and the order in which administrator scripts are executed. Although I cannot find anything about the order in which the scripts are executed, I would expect they are executed in the order they are defined: the one defined by imapsieve_mailbox1_* before the one defined by imapsieve_mailbox2_* in case both match. I

Hello, I spent the afternoon troubleshooting this, and after hours, I still can't see what I'm missing. On the older version of Dovecot (2.2) it worked fine to create a new user, then Dovecot would create the home folder under the maildir folder as outlined in the documentation, simply by creating a new user in the database, and opening the new user account in the mail client. #

Hi, We've just upgraded a few of our desktops to use Outlook 2019, and the configuration is different from previous versions. There doesn't appear to be any ability to specify a username in addition to the user's email address. The username is different than the username specified in the email address. I had read about setting auth_username_format, but the user login name is

Hi, do you have the same problem with lucene? I collected a strace on the dovecot process during indexing: [pid 31339] execve("/usr/libexec/dovecot/doveadm-server", ["dovecot-devel01/doveadm-server"], [/* 18 vars */] <unfinished ...> [pid 30711] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=30932, si_uid=0, si_status=SIGSEGV, si_utime=3, si_stime=1} ---

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

We have upgraded dovecot from 2.0.9 (centos6) to 2.2.36 (centos8). If more than 1000 users log in, the following error will occur. ------------------------- Nov 16 11:33:00 xxxxxxxx dovecot[1361]: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable (client-pid=1362, client-id=129834, rip=10.10.10.10, created

Op 16-9-2019 om 11:53 schreef Domenico Pastore via dovecot: > > Hi, > > I have other information. > > I analyzed the core dump: > > (gdb) core 22534 > [New LWP 22534] > Reading symbols from /usr/libexec/dovecot/doveadm-server...Reading > symbols from > /usr/lib/debug/usr/libexec/dovecot/doveadm-server.debug...done. > done. > [Thread debugging using

For the record, ever since the last patches for NFS got committed, we don't see locking issues over NFS in general across all our platforms, but it also depends on how you configure your NFS server. You might find that this is not a dovecot issue, but an NFS issue. You might want to post more about your NFS setup(s) and then someone on the list might better assist you. -- Michael -- On

Hi, some of our customers have discovered a replication issue after upgraded from 2.3.7.2 to 2.3.8. Running 2.3.8 several replication connections are hanging until defined timeout. So after some seconds there are $replication_max_conns hanging connections. Other replications are running fast and successful. Also running a doveadm sync tcp:... is working fine for all users. I can't see

Hi, i have a problem with libclucene-core.so.2.3.3.4. I See segfault error to messages log, when dovecot store mail to INBOX. set 12 13:41:21 box02.par-tec.it kernel: doveadm-server[20285]: segfault at 38 ip 00007f575b68fc42 sp 00007ffc0272e750 error 4 in libclucene-core.so.2.3.3.4[7f575b569000+188000] set 12 13:41:22 box02.par-tec.it kernel: doveadm-server[18871]: segfault at 38 ip

Am 02.09.19 um 15:05 schrieb Philipp Faeustlin via dovecot: > The recipients in the vacation :addresses String list are matched > case-sensitive. > > If the recipient gets a mail with wrong case, the message is discarded > with: > "discarding vacation response for implicitly delivered message; no known > (envelope) recipient address found in message headers" >

On 03/10/2019 17:26, Asai via dovecot wrote: > Mr. Timo, > > I would presume you are busy with many responsibilities, but might you > have a few minutes to consider this problem? > > Or is there any other Dovecot expert who may be able to offer advice > on how to get the home directories created?? Thank you for those who > have helped offer advice on this already. >

Is it possible in pigeonhole? I.E. I do a fileinto :create "some/mail/box" How can I make it autosubscribe? doveconf -n: # 2.3.7.2 (3c910f64b): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 (7372921a) # OS: FreeBSD 12.0-STABLE amd64 # Hostname: thebighonker.lerctr.org auth_default_realm = lerctr.org auth_mechanisms = plain login auth_realms = lerctr.org