Query about list policy?
Greetings for a second time today, As a quick query, what is the policy about linking to user-scripts and small addons ? I've used a couple of perl scripts to help me with dspam training from dovecot-antispam and imapsieve triggering for sorting and feeding messages to dspam in the background. They are most likely not the greatest but seem to work at least. I've posted them to github, but just wanted to ask whether it was an issue if i linked them here, or if they would need any review before posting or any other answer? Many thanks, and to Aki Tuomi and the dovecot team also. Andy R.
Re: Replacement for antispam plugin
Greetings to the list :) I've been meaning to ask a couple of questions about the imapsieve for antispam. Firstly, I guess that the example at the bottom of the page "https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve"; is meant to link to the new example at "https://wiki2.dovecot.org/HowTo/AntispamWithSieve"; now? Also... in "imapsieve_mailboxX_name = ${directory}" is the string a literal, or is it working with the 'special use' flagged directories from the xx-mailboxes.conf? I'm asking as though I only have a few users to worry about, different mail clients each have their favourite special folders. IE thunderbird uses "junk" but one Outlook express version likes "Junk E-mail" and I have a different favourite from another version of OE too. So in mailboxes.conf I just added extra special use lines which seemed to make things happy. Otherwise I ended up with the server configured 'spam' folder showing as basic folder, and then each client adding it's own chosen spamfolder each time too. But, if the imapsieve is only matching to literal foldernames, should I just duplicate the trigger lines for each type of junk folder or is there a method to have the sieve script enumerate all the options listed by 'special use' or is there a better method for this? I want to put the spam-mail-filing script as a global sieve script as all users will need it, rather than duplicating out for each user. Many thanks , Andy R On 10/02/2017 09:06, Aki Tuomi wrote: Hi! Since antispam plugin is deprecated and we would really prefer people not to use it, we wrote instructions on how to replace it with IMAPSieve. Comments and suggestions are most welcome. https://wiki.dovecot.org/HowTo/AntispamWithSieve --- Aki Tuomi Dovecot oy
Re: dovecot-lda crash after upgrade to 2.2.28
Thank you. Will be waiting for Dovecot update. Aki Tuomi писал 2017-02-28 20:34: On February 28, 2017 at 7:43 PM Max Kostikov wrote: Got it. Here is full backtrace output. Would appear the bug is in 'Trash' plugin. We'll open an issue about this, thank you for reporting this. Aki -- With best regards, Max Kostikov BBM: 24CA5DF8 | W: https://kostikov.co
Re: dovecot-lda crash after upgrade to 2.2.28
> On February 28, 2017 at 7:43 PM Max Kostikov wrote: > > > Got it. > Here is full backtrace output. > Would appear the bug is in 'Trash' plugin. We'll open an issue about this, thank you for reporting this. Aki
Re: dovecot-lda crash after upgrade to 2.2.28
Got it. Here is full backtrace output. # gdb /usr/local/libexec/dovecot/imap 1 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... Attaching to program: /usr/local/libexec/dovecot/imap, process 1 ptrace: Invalid argument. Core was generated by `imap'. Program terminated with signal 6, Aborted. Reading symbols from /usr/local/lib/dovecot/libdovecot-lda.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot-lda.so.0 Reading symbols from /usr/local/lib/dovecot/libdovecot-storage.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/local/lib/dovecot/libdovecot.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/lib/libkrb5.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libkrb5.so.11 Reading symbols from /usr/lib/libgssapi.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgssapi.so.10 Reading symbols from /usr/lib/libgssapi_krb5.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgssapi_krb5.so.10 Reading symbols from /usr/lib/libasn1.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libasn1.so.11 Reading symbols from /usr/lib/libcom_err.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcom_err.so.5 Reading symbols from /lib/libcrypt.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.5 Reading symbols from /lib/libcrypto.so.8...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypto.so.8 Reading symbols from /usr/lib/libhx509.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libhx509.so.11 Reading symbols from /usr/lib/libroken.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libroken.so.11 Reading symbols from /usr/lib/libwind.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libwind.so.11 Reading symbols from /usr/lib/libheimbase.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libheimbase.so.11 Reading symbols from /usr/lib/libprivateheimipcc.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libprivateheimipcc.so.11 Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /usr/local/lib/dovecot/lib01_acl_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib01_acl_plugin.so Reading symbols from /usr/local/lib/dovecot/lib02_imap_acl_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib02_imap_acl_plugin.so Reading symbols from /usr/local/lib/dovecot/lib10_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib10_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/lib11_imap_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib11_imap_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/lib11_trash_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib11_trash_plugin.so Reading symbols from /usr/local/lib/dovecot/lib90_antispam_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib90_antispam_plugin.so Reading symbols from /usr/local/lib/compat/pkg/nss_winbind.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/compat/pkg/nss_winbind.so.1 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x1117655a in thr_kill () from /lib/libc.so.7 [New Thread 13616000 (LWP 100216/)] (gdb) bt #0 0x1117655a in thr_kill () from /lib/libc.so.7 #1 0x1117652b in raise () from /lib/libc.so.7 #2 0x11176499 in abort () from /lib/libc.so.7 #3 0x10e2af54 in default_error_handler () from /usr/local/lib/dovecot/libdovecot.so.0 #4 0x10e2bc5b in i_set_failure_ignore_errors () from /usr/local/lib/dovecot/libdovecot.so.0 #5 0x10e2b1f9 in i_fatal () from /usr/local/lib/dovecot/libdovecot.so.0 #6 0x10aa190a in mail_namespace_find () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #7 0x1402e7e2 in trash_plug
Re: Scaling to 10 Million IMAP sessions on a single server
On 2/22/2017, 3:46:08 PM, KT Walrus wrote: > I want to use mdbox format but I have heard that these index files do > get corrupted occasionally and have to be rebuilt (possibly using an > older version of the index file to construct a new one). I worry that > using mdbox might cause my users to see the IMAP flags suddenly reset > back to a previous state (like seeing previously read messages > becoming unread in their mail clients). This is the only reason I haven't moved to mdbox myself. I really, really wish there was a way to not have to worry about losing flags.
Re: dovecot-lda crash after upgrade to 2.2.28
Your backtrace would've been informative already if you had issued bt full. Just opening it with gdb is not sufficient. Aki > On February 28, 2017 at 5:55 PM Max Kostikov wrote: > > > Probably I need to compile 2.2.28 from sources with debug flags. > Can you tell me wich flags I need to set for more informative backtrace > in gdb? > > Aki Tuomi писал 2017-02-28 17:42: > > > Can you please issue > > bt full > > in gdb and post the output here? > > -- > With best regards, > Max Kostikov > > BBM: 24CA5DF8 | W: https://kostikov.co > -- > With best regards, > Max Kostikov > > BBM: 24CA5DF8 | W: https://kostikov.co
Re: Dict protocol changes string
On 09/23/2016 08:05 AM, Aki Tuomi wrote: On 29.07.2016 15:35, Nagy, Attila wrote: I use pass and userdb with dict protocol in a similar way: key passdb { key = passdb^MAuth-User: %u^MAuth-Pass: %w^MAuth-Protocol: %s^MClient-IP: %r format = json } (^M is an \r character, inserted with vi CTRL-v + enter) Until 2.2.24 this has worked, but 2.2.25 seems to convert that ASCII 13 into an ASCII 1 and an "r". Python printout from what I get with 2.2.25: 'Lshared/passdb\x01rAuth-User: user\x01rAuth-Pass: pass\x01rAuth-Protocol: pop3\x01rClient-IP: 1.2.3.4' Is this change intentional? Why? Hi! Dict protocol escapes you newlines. You are expected to de-escape them yourself. Following escapes are done, you can de-escape them with your client. \x00 => \x10 \x01 => \x11 \t => \x1t \r => \x1r \n => \x1n Following up on this: dovecot 2.2.27 and 2.2.28 goes even further (2.2.25 was OK). If a user specifies a password with a % in it, dovecot silently truncates it. So for example if I specify (just to check this simple example is also bad): key passdb { key = %w format = json } and a user tries to log in with the password 'Lofasznehogyma%', dovecot sends the following into the dict socket: 'Lshared/Lofasznehogyma' According to user reports, other characters may also be affected. Could you please fix this?
Re: dovecot-lda crash after upgrade to 2.2.28
Probably I need to compile 2.2.28 from sources with debug flags. Can you tell me wich flags I need to set for more informative backtrace in gdb? Aki Tuomi писал 2017-02-28 17:42: Can you please issue bt full in gdb and post the output here? -- With best regards, Max Kostikov BBM: 24CA5DF8 | W: https://kostikov.co -- With best regards, Max Kostikov BBM: 24CA5DF8 | W: https://kostikov.co
Re: dovecot-lda crash after upgrade to 2.2.28
We (FreeBSD) had a user report similar. On 2/28/17, 9:42 AM, "dovecot on behalf of Aki Tuomi" wrote: > On February 28, 2017 at 4:32 PM Max Kostikov wrote: > > > I just recreated configuration of Dovecot 2.2.28 and got the same error > but in imap service (it was there in logs too as for dovecot-lda but I > don't saw it at time). > > Feb 27 20:09:41 beta dovecot: imap(postmas...@peek.ru): Panic: file > > mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns > > != NULL) > > Feb 27 20:09:47 beta dovecot: lda(m...@domain.ru): Panic: file > > mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns > > != NULL) > > So I show you only imap backtrace below. Can you please issue bt full in gdb and post the output here? Aki
Re: dovecot-lda crash after upgrade to 2.2.28
> On February 28, 2017 at 4:32 PM Max Kostikov wrote: > > > I just recreated configuration of Dovecot 2.2.28 and got the same error > but in imap service (it was there in logs too as for dovecot-lda but I > don't saw it at time). > > Feb 27 20:09:41 beta dovecot: imap(postmas...@peek.ru): Panic: file > > mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns > > != NULL) > > Feb 27 20:09:47 beta dovecot: lda(m...@domain.ru): Panic: file > > mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns > > != NULL) > > So I show you only imap backtrace below. Can you please issue bt full in gdb and post the output here? Aki
Re: dovecot-lda crash after upgrade to 2.2.28
I just recreated configuration of Dovecot 2.2.28 and got the same error but in imap service (it was there in logs too as for dovecot-lda but I don't saw it at time). Feb 27 20:09:41 beta dovecot: imap(postmas...@peek.ru): Panic: file mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns != NULL) Feb 27 20:09:47 beta dovecot: lda(m...@domain.ru): Panic: file mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns != NULL) So I show you only imap backtrace below. # gdb /usr/local/libexec/dovecot/imap 1 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... Attaching to program: /usr/local/libexec/dovecot/imap, process 1 ptrace: Invalid argument. Core was generated by `imap'. Program terminated with signal 6, Aborted. Reading symbols from /usr/local/lib/dovecot/libdovecot-lda.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot-lda.so.0 Reading symbols from /usr/local/lib/dovecot/libdovecot-storage.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/local/lib/dovecot/libdovecot.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/lib/libkrb5.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libkrb5.so.11 Reading symbols from /usr/lib/libgssapi.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgssapi.so.10 Reading symbols from /usr/lib/libgssapi_krb5.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgssapi_krb5.so.10 Reading symbols from /usr/lib/libasn1.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libasn1.so.11 Reading symbols from /usr/lib/libcom_err.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcom_err.so.5 Reading symbols from /lib/libcrypt.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.5 Reading symbols from /lib/libcrypto.so.8...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypto.so.8 Reading symbols from /usr/lib/libhx509.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libhx509.so.11 Reading symbols from /usr/lib/libroken.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libroken.so.11 Reading symbols from /usr/lib/libwind.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libwind.so.11 Reading symbols from /usr/lib/libheimbase.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libheimbase.so.11 Reading symbols from /usr/lib/libprivateheimipcc.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libprivateheimipcc.so.11 Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /usr/local/lib/dovecot/lib01_acl_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib01_acl_plugin.so Reading symbols from /usr/local/lib/dovecot/lib02_imap_acl_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib02_imap_acl_plugin.so Reading symbols from /usr/local/lib/dovecot/lib10_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib10_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/lib11_imap_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib11_imap_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/lib11_trash_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib11_trash_plugin.so Reading symbols from /usr/local/lib/dovecot/lib90_antispam_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib90_antispam_plugin.so Reading symbols from /usr/local/lib/compat/pkg/nss_winbind.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/compat/pkg/nss_winbind.so.1 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x1117655a in thr_kill () from /lib/libc.so.7 [New Thread 13616000 (LWP 100455/)] (gdb) quit Aki Tuomi писал 2017-02-28 13:20: On 28.02.2017 13:16, Max Kostikov wrote: Hi! I posted this problem few days ag
Re: Quota usage value shows 140% of actual disk usage
You're right, it's the zlib compression. It works as described here: http://wiki2.dovecot.org/Plugins/Zlib It appends the before-compression size to the file name like S= and uses them for quota usage calculation. So, when I run the following command on a Maildir, the result matches the value on the database. (size value on the quota table) find . -type f | grep S= | awk -F, '{ gsub("S=","",$2); SUM+=$2 } END { print SUM }' And the compression ratios relate to the difference between actual disk space usage and calculated quota usage values when I check like this, on a Maildir: find . -type f -ls | grep S= | awk -F, '{ gsub("S=","",$2); print $2, $1 }' | awk '{ print "file: "$12,"\t orig: ",$1," comp.: ",$8," ratio: ",$1 / $8}' Thanks a lot! 25 Şub 2017 Cmt, 00:07 tarihinde, Karsten Heiken < hei...@luis.uni-hannover.de> şunu yazdı: > Am 24.02.2017 um 16:00 schrieb Steffen Kaiser: > > > > Quota does not count physical useage, but the amount of bytes allocated > by the messages. Maildir may hardlink messages, hence, they count multiple > times for the quota, but once for du. > > And in your case dovecot even compressed the mails: > According to your doveconf, you are using mail_plugins = [...] zlib. > > Dovecot's quota is calculated using the uncompressed size, whereas du > shows you the space actually allocated. > >
Re: dovecot-lda crash after upgrade to 2.2.28
On 28.02.2017 13:16, Max Kostikov wrote: > Hi! > > I posted this problem few days ago in FreeBSD bugtracker > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217364 > So, the problem is in crash of dovecot-lda client while > local mailbox delivery with this message in log >> dovecot: lda(my@email): Panic: file mail-namespace.c: line 709 >> (mail_namespace_find): assertion failed: (ns != NULL) > Core backtrace would help alot! Aki Tuomi Dovecot oy
dovecot-lda crash after upgrade to 2.2.28
Hi! I posted this problem few days ago in FreeBSD bugtracker https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217364 So, the problem is in crash of dovecot-lda client while local mailbox delivery with this message in log dovecot: lda(my@email): Panic: file mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns != NULL) My Dovecot config stills the same from previous 2.2.27 installation to I believe that problem in new Dovecot code related namespace. System: # uname -v FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22 06:12:04 UTC 2017 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC Options: root@beta:/usr/ports/mail/dovecot2 # make showconfig | grep =on DOCS=on: Build and/or install documentation EXAMPLES=on: Build and/or install examples KQUEUE=on: kqueue(2) support LIBWRAP=on: TCP wrapper support LZ4=on: LZ4 compression support MYSQL=on: MySQL database support GSSAPI_BASE=on: Use GSSAPI from base Config: # doveconf -n # 2.2.27 (c0f36b0): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: FreeBSD 11.0-RELEASE-p8 amd64 ufs auth_mechanisms = plain login default_login_user = dovecot dict { sqluserquota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql-user.conf } disable_plaintext_auth = no first_valid_gid = 0 first_valid_uid = 25 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_access_sockets = tcpwrap login_greeting = Dovecot ready! login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_access_groups = mail mail_gid = 6 mail_location = maildir:/var/mail/%d/%n mail_plugins = acl quota trash mail_privileged_group = mail mail_uid = 26 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace { location = maildir:/var/mail/%d/.public:INDEXPVT=/var/mail/%d/%n/public prefix = public. separator = . subscriptions = no type = public } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = . type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } plugin { acl = vfile::cache_secs=300 antispam_backend = mailtrain antispam_mail_notspam = %u-revoke antispam_mail_sendmail = /usr/local/etc/dovecot/move-cmd.sh antispam_mail_sendmail_args = antispam_mail_spam = %u-report antispam_spam = Junk antispam_trash = Trash quota = dict:user_quota::proxy::sqluserquota quota_grace = 10%% quota_rule2 = Trash:storage=+10%% quota_rule3 = Junk:storage=+10%% quota_warning = storage=100%% quota-exceeded 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=75%% quota-warning 75 %u sieve = ~/dovecot.sieve sieve_before = /usr/local/etc/dovecot/default.sieve sieve_dir = ~/sieve sieve_global_path = /usr/local/etc/dovecot/default.sieve trash = /usr/local/etc/dovecot/dovecot-trash.conf } protocols = imap pop3 lmtp sieve service auth { unix_listener auth-client { mode = 0660 user = mailnull } unix_listener auth-master { mode = 0660 user = mailnull } user = root } service dict { unix_listener dict { mode = 0660 user = mailnull } } service imap-login { chroot = login client_limit = 64 executable = /usr/local/libexec/dovecot/imap-login inet_listener imap { port = 143 } inet_listener imaps { port = 993 } process_limit = 32 process_min_avail = 8 service_count = 1 user = $default_login_user vsz_limit = 64 M } service imap { executable = /usr/local/libexec/dovecot/imap } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 1 service_count = 1 user = $default_login_user vsz_limit = 64 M } service managesieve { process_limit = 10 } service pop3-login { chroot = login client_limit = 64 executable = /usr/local/libexec/dovecot/pop3-login inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 } process_limit = 32 process_min_avail = 8 service_count = 1 user = $default_login_user vsz_limit = 64 M } service pop3 { executable = /usr/local/libexec/dovecot/pop3 } service quota-warning { executable = script /usr/local/etc/dovecot/quota_warning.sh unix_listener quota-warning { mode = 0660 user = mailnull } } service tcpwrap { unix_listener login/tcpwrap { mode = 0600 user = $default_login_user } } ssl_ca = ssl_cipher_list = ECDHE-ECDSA-CHACHA20-POLY1305
Re: make check failing in CentOS 6
On 28.02.2017 06:14, Peter Ajamian wrote: > Dovecot builds just fine, but fails the tests in src/lib-index. > > Note that reverting this commit fixes the issue: > https://github.com/dovecot/core/commit/dfa4b048ec9a174a42d6668e94501db2fb70793a > > $ make check > for bin in test-mail-index-map test-mail-index-modseq > test-mail-index-sync-ext test-mail-index-transaction-finish > test-mail-index-transaction-update test-mail-transaction-log-append > test-mail-transaction-log-view; do \ > if ! ./$bin; then exit 1; fi; \ > done > mail index map lookup seq range .. : ok > 0 / 1 tests failed > mail_transaction_log_file_get_modseq_next_offset() ... : ok > 0 / 1 tests failed > mail index sync ext atomic inc ... : ok > 0 / 1 tests failed > mail index transaction finish flag updates n_so_far=0 : ok > mail index transaction finish flag updates n_so_far=1 : ok > mail index transaction finish flag updates n_so_far=2 : ok > mail index transaction finish check conflicts n_so_far=0 . : ok > mail index transaction finish check conflicts n_so_far=1 . : ok > mail index transaction finish check conflicts n_so_far=2 . : ok > mail index transaction finish modseq updates n_so_far=0 .. : ok > mail index transaction finish modseq updates n_so_far=1 .. : ok > mail index transaction finish modseq updates n_so_far=2 .. : ok > mail index transaction finish expunges n_so_far=0 : ok > mail index transaction finish expunges n_so_far=1 : ok > mail index transaction finish expunges n_so_far=2 : ok > 0 / 12 tests failed > mail index append : ok > mail index append with uids .. : ok > mail index flag update fast paths : ok > mail index flag update simple merges . : ok > mail index flag update complex merges : ok > mail index flag update random : ok > mail index flag update appends ... : ok > mail index cancel flag updates ... : ok > mail index transaction get flag update pos ... : ok > mail index modseq update . : ok > mail index expunge ... : ok > test-mail-index-transaction-update.c:649: Assert(#1) failed: > new_hdr.day_stamp == tests[i].new_day_stamp + timezone > test-mail-index-transaction-update.c:652: Assert(#1) failed: > memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, > sizeof(uint32_t) * 8) == 0 > test-mail-index-transaction-update.c:649: Assert(#3) failed: > new_hdr.day_stamp == tests[i].new_day_stamp + timezone > test-mail-index-transaction-update.c:652: Assert(#3) failed: > memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, > sizeof(uint32_t) * 8) == 0 > test-mail-index-transaction-update.c:649: Assert(#4) failed: > new_hdr.day_stamp == tests[i].new_day_stamp + timezone > test-mail-index-transaction-update.c:649: Assert(#5) failed: > new_hdr.day_stamp == tests[i].new_day_stamp + timezone > test-mail-index-transaction-update.c:652: Assert(#5) failed: > memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, > sizeof(uint32_t) * 8) == 0 > test-mail-index-transaction-update.c:649: Assert(#6) failed: > new_hdr.day_stamp == tests[i].new_day_stamp + timezone > test-mail-index-transaction-update.c:652: Assert(#6) failed: > memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, > sizeof(uint32_t) * 8) == 0 > test-mail-index-transaction-update.c:649: Assert(#7) failed: > new_hdr.day_stamp == tests[i].new_day_stamp + timezone > test-mail-index-transaction-update.c:652: Assert(#7) failed: > memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, > sizeof(uint32_t) * 8) == 0 > test-mail-index-transaction-update.c:649: Assert(#8) failed: > new_hdr.day_stamp == tests[i].new_day_stamp + timezone > test-mail-index-transaction-update.c:652: Assert(#8) failed: > memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, > sizeof(uint32_t) * 8) == 0 > test-mail-index-transaction-update.c:649: Assert(#9) failed: > new_hdr.day_stamp == tests[i].new_day_stamp + timezone > test-mail-index-transaction-update.c:652: Assert(#9) failed: > memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, > sizeof(uint32_t) * 8) == 0 > test-mail-index-transaction-update.c:649: Assert(#10) failed: > new_hdr.day_stamp == tests[i].new_day_stamp + timezone > test-mail-index-transaction-update.c:652: Assert(#10) failed: > memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, > sizeof(uint32_t) * 8) == 0 > test-mail-index-transaction-update.c:649:
Index queue
Hi, can i, somehow, list mailboxes which are to be indexed by indexer-worker (=index queue?) ? How can i know what part of all mailboxes was indexed so far? Are there any statistics about Solr data dir size based on emails amount? For example, we have about 5TB of emails, what should i except about index size in Solr? Thank you. azur