similar to: Error: Raw backtrace and index cache

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

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

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 10.54, Maciej Milaszewski IQ PL via dovecot wrote: > Hi > I have "problem" with dovect 2.2.13 from repo debian8 and I don't

Hi I have a question about tunning dovecot-2.2.36.x Mail was stared in storage via nfs in MAILDIR via /home/us/username at domain.ltd/MAILDIR/ I use additionally local dovecot_indexes via SSD disk (/var/dovecot_indexes%h) A few clients have 25K and more e-mail I thinking about use solr like: ?fts = solr ?fts_solr = debug url=http://IP:8983/solr/ (solr in external machine) Does it make sense ?

>> A few clients have 25K and more e-mail >> >> I thinking about use solr like: >> ?fts = solr >> ?fts_solr = debug url=http://IP:8983/solr/ (solr in external machine) >> >> Does it make sense ? use dovecot_indexes and fts ? >> What is the difference in performance? >> > Hi! > > Dovecot indexes are not actually related to FTS that

Hi, On saturday one of our dovecot machines had an OOPS, and we had to powercycle it. When it came up, it did a filesystem fsck (ext4) and fixed a couple things, but nothing in lost+found. Now, about 50 users have a problem where their indexes are corrupted. Dovecot tries to fix them, but for some reason it is failing. The users are seeing their mails duplicated and they cannot delete mails. I

Hello, I'm using dovecot 1.2.10 with mbox format (which implies layout=fs) and I would like to switch to maildir++ layout without changing format in order to implement subfolders for IMAP users. I understand that I should move the INDEX location to avoid some namespace conflict (it would be a good idea anyway: I'll move them on another disc :). Now I have mail_location =

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, I have noticed that during auth cache hits usernames are not updated. (We use ldap backend and change username with user_attrs = uid=user, mailMessageStore=home, mailQuotaSize=quota_rule=*:bytes=%$ cold cache lmtp(14414): Debug: auth input: testmon_testmon home=/vmail/te/testmon_testmon quota_rule=*:bytes=104857600 lmtp(14414): Debug: changed username to testmon_testmon lmtp(14414): Debug:

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 =

On 4.7.2019 12.14, Maciej Milaszewski IQ PL via dovecot wrote: > Hi > I have a question about tunning dovecot-2.2.36.x > > Mail was stared in storage via nfs in MAILDIR via > /home/us/username at domain.ltd/MAILDIR/ > I use additionally local dovecot_indexes via SSD disk > (/var/dovecot_indexes%h) > > A few clients have 25K and more e-mail > > I thinking about use

I have a problem with a physical user that was removed and recreated whith same name and different uid. The home dir, the mailbox file and the index directory where removed and recreated with the new uid/gid. I can feed the mailbox via procmail, though dovecot-lda complains that userids do not match: May 02 15:27:33 lda(alessandro_cmr): Error: stat(/var/spool/mailboxes/alessandro_cmr/INBOX)

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:

Hi Thenx for replay. Finaly for a test in my lab I upgrate to latest 2.2.36 and os debian 10 In this machine is dovecot director But if i tested via telnet root at postfix:~# telnet 46.xxx.xxx.xxx 143 Trying 46.xxx.xxx.xxx... Connected to 46.xxx.xxx.xxx. Escape character is '^]'. * BYE Disconnected: Auth process broken Connection closed by foreign host. In log: Jan 24 16:02:07 postfix

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

Ok, I've ALMOST got this working ... I can run deliver as a user, but when I try using it as the default delivery agent from sendmail, I get deliver(userid): net_connect(/var/run/dovecot/auth-master) failed: Permission denied Does deliver run as root, as the recipient's ID, sendmail's ID or sendmail's GID? (I'm running freebsd) Or am I totally clueless ?? Here is dovecot

Hi I have little problem with debian10 and dovecot 2.2.33.2 ps -ax 21815 ???????? S????? 0:00 dovecot/pop3-login director 21816 ???????? S????? 0:00 dovecot/pop3-login director 21817 ???????? S????? 0:00 dovecot/pop3-login director 21818 ???????? S????? 0:00 dovecot/pop3-login director 21819 ???????? S????? 0:00 dovecot/pop3-login director 21821 ???????? S????? 0:00 dovecot/pop3-login director

Hi Maby stupid question :) It possible to have 3 directors (frontend) but without rings ? All directors connect to this same dovecot (backend) - all backad have this same login_trusted_networks -- Maciej Mi?aszewski IQ PL Sp. z o.o. Starszy Administrator Systemowy

Hi folks, My institute's mail server was upgraded to RHEL5 with dovecot 1.0-2.1rc5 recently. And it uses PAM authentication which points to LDAP server. Now from time to time it gets Error like dovecot: Aug 29 09:23:59 Error: auth(default): pam(joshua,192.168.177.52): pipe() failed: Too many open files and users can not login. My config is like dovecot -n # /etc/dovecot.conf base_dir:

Hello, When I run dsync -u v.shokov -Dv mirror sdbox:/dsync/v.shokov first time, process halting. On second time I receive this error: dsync(root): Debug: auth input: v.shokov system_groups_user=v.shokov uid=10000 gid=100 home=/home/v.shokov dsync(root): Debug: Effective uid=10000, gid=100, home=/home/v.shokov dsync(root): Debug: Namespace : type=private, prefix=, sep=.,