similar to: migrations from 2.2.36

Hi I have dovecot-2.2.36.4 (director) + 5 nodes dovecot (dovecot-2.2.36.4) What version of Solr do you recommend ? -- Maciej Mi?aszewski Starszy Administrator Systemowy IQ PL Sp. z o.o. Biuro Obs?ugi Klienta: e-mail: bok at iq.pl tel.: +48 58 326 09 90 - 94 fax: +48 58 326 09 99 Dzia? pomocy: https://www.iq.pl/pomoc Informacja dotycz?ca przetwarzania danych osobowych:

Hi I use dovecot-2.2.36.4 on Debian 8.11 and plugin dovecot-antispam from http://johannes.sipsolutions.net/Projects/dovecot-antispam All works fine but in roundcube i get two folder: Spam (real: Junk) and SPAM in sieve i have: require ["fileinto","imap4flags"]; # rule:[SPAM Box] if header :contains "X-Spam-Flag" "YES" { setflag "\\Seen";

Hi Thanx for replay. Log: http://paste.debian.net/1117077/ On 20.11.2019 10:07, Aki Tuomi wrote: > Firstly, 2.2.13 is about 5 years old. So there's that. It would be > helpful if you can reproduce this with 2.2.36. > > Also, you forgot to actually include in your log snippet the panic. So > maybe few more lines before the Raw backtrace? > > Aki > > On 20.11.2019

Hi System debian 8.11 dovecot-2.2.36.4 and I have some warnings in log likes: Warning: Inotify watch limit for user exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_watches cat /proc/sys/fs/inotify/max_user_watches 8192 in sysctl i change #fs.inotify.max_user_watches= 8192 #fs.inotify.max_user_instances = 16384 fs.inotify.max_user_watches= 16384 fs.inotify.max_user_instances =

Hi System debian 8.11 and dovecot-2.2.36.4 My webmail is roundcube with imapproxy. I have one problem. My dovecot servers is are in a cluster with keepalived like: dovecot1----VIP-IP--------dovecot2 All works fine I have a problem with imapproxy when a server dovecot1 had a problem (kernel panic sic!) Keepalived works perfecty and moved VIP to dovecot2 - all works fine for normal users but

Hi Maciej, version 6.6.x works fine, but probably also 7.7.x with schema from Dovecot 2.3. Ciao Il 18/08/20 14:00, Maciej Milaszewski ha scritto: > Hi > I have dovecot-2.2.36.4 (director) + 5 nodes dovecot (dovecot-2.2.36.4) > > What version of Solr do you recommend ? > -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice --------------

Another known issue, fixed with https://github.com/dovecot/core/commit/ca4c2579f0456072bdb505932a9cf7602e42afd2.patch Aki > On 24 January 2019 at 20:54 Maciej Milaszewski IQ PL <maciej.milaszewski at iq.pl> wrote: > > > Hi > Like bumerang. > > 2.2.36 works fine on debian10 but connect by telnet like: > > Connected to 46.xxx.xxx.xxx. > Escape character is

This is likely fixed in more recent version, can you try with 2.2.36? Aki On 20.11.2019 11.20, Maciej Milaszewski IQ PL wrote: > Hi > Thanx for replay. > > Log: > > http://paste.debian.net/1117077/ > > > On 20.11.2019 10:07, Aki Tuomi wrote: >> Firstly, 2.2.13 is about 5 years old. So there's that. It would be >> helpful if you can reproduce this with

Hi I Dont understand or? I im thinking wrong: process_limit = 25000 Older: #fs.inotify.max_user_watches= 8192 #fs.inotify.max_user_instances = 16384 New: fs.inotify.max_user_instances = 8192 ? fs.inotify.max_user_watches= process_limit x 2 + fs.inotify.max_user_instances fs.inotify.max_user_watches= 58192 On 31.03.2020 13:44, Aki Tuomi wrote: > I would prefer replies on the list... =)

Hi Thenx. Dump core: Core was generated by `dovecot/auth'. Program terminated with signal SIGSEGV, Segmentation fault. #0? 0x00007fa910394c7a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt full #0? 0x00007fa910394c7a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1? 0x00005604e6f98bc8 in password_scheme_register_crypt () at password-scheme-crypt.c:144

Hi I have some problem with SNI and dovecot 2.2.36.4 Server debian 9.x ad dovecot-2.2.36.4 default server ssl cert is a wildcard like *.domain.com (digicert) ssl_ca = /var/control/cert.pem ssl_cert = </var/control/cert.pem I added for test another domain (in dns to) for another ssl (letsencrypt) from https://wiki.dovecot.org/SSL/DovecotConfiguration like: local_name

I just noticed this error in my logs: director: Error: doveadm not compatible with this server (mixed old and new binaries?) director: Error: director(10.161.192.28:541/right): Wrong protocol in socket (director-doveadm vs director) The first error I removed by changing director_doveadm_port = 541 to director_doveadm_port = 542 Not really sure why that fixed it. The second error I

Hi Thenx for replay - problem solved :) I forget `autoreconf -vi` You are rox :) ?On 24.01.2019 19:10, Aki Tuomi wrote: > You need to do `autoreconf -vi` before configure, won't work otherwise. > > Aki > >> autoreconf -viOn 24 January 2019 at 20:09 Maciej Milaszewski IQ PL <maciej.milaszewski at iq.pl> wrote: >> >> >> Hi >> Thenx. I use your

This has been fixed with https://github.com/dovecot/core/commit/63a74b9e8e0604486a15a879e7f1a27257322400.patch Aki > On 24 January 2019 at 19:26 Maciej Milaszewski IQ PL <maciej.milaszewski at iq.pl> wrote: > > > Hi > Thenx. Dump core: > > Core was generated by `dovecot/auth'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0?

Hi, we have a problem with our director proxy configuration. When we run on proxy server the doveadm command with -A switch, fails with the error: # doveadm -D quota get -A doveadm(user1): Debug: auth input: user=user1 proxy starttls=any-cert doveadm(user1): Error: Proxy is missing destination host doveadm: Error: Failed to iterate through some users If we execute the command with a single

Hi Thenx but maby problem is in ssl or core file and gdb was incorrectly used # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 4.19.0-1-amd64 x86_64 Debian buster/sid Jan 24 16:56:38 thebe-postfix dovecot: master: Dovecot v2.2.36 (1f10bfa63) starting up for imap, pop3, lmtp, sieve Jan 24 16:56:39 thebe-postfix dovecot: master: Error:

Hello, i'm test system dovecot (proxy with director) and backend storage, auth LDAP server (user plain passwords) If i use plain auth, work fine. If connect DIGEST-MD5 or CRAM-MD5 proxy not redirect connection (Requested DIGEST-MD5 scheme, but we have a NULL password) ### Frontend proxy+director # dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.2-RELEASE amd64

Hi, we are running a 4 host setup which each hosts a director+mailbox which is mounted via NFSv4 from a DRBD cluster. * Dovecot upstream release 2.1.16 * Doveadm batch subcommand fix - http://hg.dovecot.org/dovecot-2.1/raw-rev/850b5d8bbcc9 * Pigeonhole release 0.3.4 Now we would like to remove duplicate Mails using the vnd.dovecot.duplicate extension using a SIEVE script like this: require

Hi, we are running a cluster using mdbox on NFS with director+mailbox on each node. After running our daily doveadm purge loop over all users, we got dbox corruption... doveadm user "*" |\ while read username do doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -u "$username" done For one user (which deleted a lot of messages from his mailboxes today), we

Hi I have "problem" with dovect 2.2.13 from repo debian8 and I don't know how to solve it ... Server is a virtual (kvm) with debian 8.11 (postfix + dovecot from repo) and storage is mounting via nfs (I have use only one dovecot with external storage) All works fine but sometime ( after a few hours ) I have got a problem with dovecot cache (i use indexes) logs ->