- dovecot - dovecot.org

No stats under FreeBSD 10.3
by Ruud Boon 04 Dec '16

04 Dec '16

HI, I’m currently testing the stats module of Dovecot (2.2.26.0 (23d1de6)) Looks like there no statistics under FreeBSD. Server isn’t busy yet but got at least a few connection open. Added mail_plugins = $mail_plugins stats plugin { stats_refresh = 30 secs stats_track_cmds = yes } doveadm stats dump global reset_timestamp last_update num_logins num_cmds num_connected_sessions auth_successes auth_master_successes auth_failures auth_db_tempfails auth_cache_hits auth_cache_misses user_cpu sys_cpu clock_time min_faults maj_faults vol_cs invol_cs disk_input disk_output read_count read_bytes write_count write_bytes mail_lookup_path mail_lookup_attr mail_read_count mail_read_bytes mail_cache_hits 1478031539 0.000000 0 0 0 0 0 0 0 0 0 0.0 0.0 0.0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Cheers, Ruud

4 5

CentOS 7
by Eric Broch 04 Dec '16

04 Dec '16

Hello List, I'm building a dovecot-2.2.27 RPM for CentOS 7 and running into some issues The dovecot.spec (http://pkgs.fedoraproject.org/cgit/rpms/dovecot.git/tree/dovecot.spec) file runs 'autoreconf -I . -fiv' for aarch64 support just before the %configure option but is failing This worked fine on <= 2.2.26.0 when there was an m4/*.m4 directory (with *.m4 in it) in the sources. Is there something I should be aware of? Was the m4 directory removed for a reason? As a workaround I created the m4 directory and everything worked out, but is this the best solution? Eric

2 2

Too many references: cannot splice
by Sebastian Köhler 02 Dec '16

02 Dec '16

Hello, multiple times per day one of our Dovecot servers has the problem that it suddenly refuses to accept new connections and then floods the logs with these messages: Dec 2 12:43:06 alfa3201 dovecot: pop3-login: Error: fd_send(pop3, 18) failed: Too many references: cannot splice Dec 2 12:43:07 alfa3201 dovecot: pop3-login: Error: fd_send(pop3, 18) failed: Too many references: cannot splice Dec 2 12:43:07 alfa3201 dovecot: imap-login: Error: fd_send(imap, 16) failed: Too many references: cannot splice Dec 2 12:43:07 alfa3201 dovecot: imap-login: Error: fd_send(imap, 16) failed: Too many references: cannot splice We have to either do a restart of the server or a doveadm kick on all users to make it reachable again. On my search for a solution I found a similar report from March[1] however without a fix. [1] http://dovecot.org/pipermail/dovecot/2016-March/103514.html dovecot -n # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.17-040417-generic x86_64 Debian 8.6 auth_mechanisms = plain login debug_log_path = /var/log/dovecot-debug.log default_client_limit = 8003 default_process_limit = 2000 default_vsz_limit = 512 M disable_plaintext_auth = no listen = * login_greeting = [CENSORED] - ready. mail_location = maildir:~/Maildir:CONTROL=/opt/dovecot/control/%n-control:INDEX=/opt/dovecot/index/%n mail_plugins = " stats quota" namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX. separator = . } passdb { args = dovecot-%s driver = pam } plugin { quota = fs:%n(soft quota) sieve = ~/.dovecot.sieve sieve_dir = ~/sieve stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 16 M stats_refresh = 30 secs stats_session_min_time = 15 mins stats_track_cmds = no stats_user_min_time = 24 hours } protocols = " imap pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imaps { ssl = yes } } service imap-postlogin { executable = script-login /etc/dovecot/post-login/expire.sh } service imap { executable = imap imap-postlogin } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3-postlogin { executable = script-login /etc/dovecot/post-login/expire.sh } service pop3 { executable = pop3 pop3-postlogin } service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota { group = postfix mode = 0660 user = postfix } } service stats { fifo_listener stats-mail { mode = 0666 user = dovecot } } ssl_ca = </etc/ssl.crt/ca-admin.crt ssl_cert = </etc/ssl.crt/admin.crt ssl_key = </etc/ssl.key/admin.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } protocol imap { imap_capability = +XLIST +NAMESPACE METADATA QUOTA imap_idle_notify_interval = 1 mins mail_max_userip_connections = 500 mail_plugins = " stats quota imap_quota imap_stats" } protocol pop3 { mail_max_userip_connections = 500 mail_plugins = " stats quota" pop3_client_workarounds = outlook-no-nuls oe-ns-eoh }

2 2

Defining INDEX target to other location than maildir seems to have no effect.
by Julian Sternberg 02 Dec '16

02 Dec '16

Dovecot Version 2.2.13 Linux Distribution: Debian Jessie CPU Architecture: x64 Filesystem: GlusterFS/NFS, XFS for Base System/Index Files. Two Dovecot/Postfix nodes accessing same GlusterFS/NFS Maildir. Regardless what i choose in mail_location (:INDEX=MEMORY or :INDEX=/var/indexes/%d/%n) all Mailbox index files will still get created within the users mail_location maildir: ~/Maildir My mail_location Maildir directory is shared on GlusterFS mount so i need to get index files away from this share due locking mechanism and faster caching. The weird is, if i set INDEX to /var/indexes, the index files getting created sometimes but then not updated frequently and exist parallel on Maildir which are mostly newer than on /var/indexes. If you delete the dovecot.index* files from Maildir, they will get recreated immediatly on Imap access but not on the alternative set INDEX location, they are getting recreated within Maildir again. Here is doveconf -n Output: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 auth_mechanisms = plain login cram-md5 disable_plaintext_auth = no first_valid_uid = 2000 hostname = censored.hostname.com last_valid_uid = 2000 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = * lock_method = dotlock mail_fsync = always mail_gid = 2000 mail_home = /storage/vmail/%d/%n mail_location = maildir:~/Maildir:LAYOUT=fs:INDEX=MEMORY mail_nfs_storage = yes mail_privileged_group = vmail mail_temp_dir = /var/tmp mail_uid = 2000 maildir_very_dirty_syncs = yes 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 ihave mmap_disable = yes namespace inbox { inbox = yes location = mailbox Archive { auto = no special_use = \Archive } mailbox Archives { auto = no special_use = \Archive } mailbox "Deleted Items" { auto = no special_use = \Trash } mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { auto = no special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = create special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } mailbox virtual/All { auto = no special_use = \All } prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = maildir:User quota quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M quota_rule3 = Sent:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = /storage/vmail/%d/%n/sieve/dovecot.sieve sieve_before = /storage/vmail/sieve/dovecot.sieve sieve_dir = /storage/vmail/%d/%n/sieve sieve_global = /storage/vmail/sieve } postmaster_address = postmaster(a)censored.hostname.com protocols = " imap lmtp sieve pop3" quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imaps { port = 993 ssl = yes } service_count = 0 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl = required ssl_ca = </etc/ssl/censored.hostname.com/ssl-bundle-mail.crt ssl_cert = </etc/ssl/censored.hostname.com/censored_hostname.com.crt ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_key = </etc/ssl/censored.hostname.com/censored.hostname.com.key ssl_protocols = !SSLv2 !SSLv3 ssl_require_crl = no userdb { args = uid=2000 gid=2000 home=/storage/vmail/%d/%n allow_all_users=yes driver = static } protocol lmtp { mail_plugins = " quota sieve" } protocol lda { mail_plugins = " sieve quota" } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = " quota imap_quota" } protocol sieve { mail_max_userip_connections = 10 } protocol pop3 { mail_plugins = " quota" pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv }

3 3

maildir-size-fix.pl - The file command can wrongly detect gzipped mails as being Minix filesystems
by Rarylson Freitas 02 Dec '16

02 Dec '16

Hi, Some days ago, I have used the maildir-size-fix.pl script (cited in this mail thread: http://www.dovecot.org/list/dovecot/2013-January/087942.html, in available here: http://dovecot.org/tools/maildir-size-fix.pl) This is a very good script and helped me a lot! However, some compressed mails where misdetected as non-compressed mail. So I discovered that some versions of the file command (some old versions) can wrongly detect gzipped files as being Minix filesystems. Actually, the error was occurring in about 1 gzipped mail for each 60000 or 100000 mails. I reported this file command bug here: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1646233. But I think it's worth to make a small improvement in maildir-size-fix.pl, making it more error prone. What do you, guys, think about this? This is the patch I'm proposing: ``` --- maildir-size-fix.pl.orig 2016-12-01 14:41:30.044689101 -0200 +++ maildir-size-fix.pl 2016-12-01 14:49:42.971197715 -0200 @@ -37,7 +37,10 @@ return $stat[7]; } - my $type=`file "$path"`; + # Detecting all possible types (keep going) since some versions of the file + # command can wrong detect gzip files as Minix filesystems. + # See: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1646233 + my $type=`file -k "$path"`; my $program = ""; if ($type =~ /gzip/) { $program = "gunzip"; ``` -- *Rarylson Freitas*

2 1

Implementing secondary quota w/ "Archive" namespace
by Fred Turner 01 Dec '16

01 Dec '16

Hello folks— My first post, so please be gentle… :-) I have a client email server using SSDs for primary user mailboxes, but since the number of users keeps growing and they all seem to be very reluctant to delete anything, I’ve implemented an “Archive” namespace that stores its mailboxes on a larger HD RAID. The idea is that, as the users approach their quota, they move messages to the Archive mailboxes to alleviate space in their primary Inbox namespace. This secondary storage part is working well, but I’m having trouble w/ getting the quotas to work right. Here are the basics of the setup: Mac Pro Server 2012 Mac OS X Server 10.6.8 Dovecot 1.1.20apple0.5 Here is how I’ve configured my namespaces (during testing): namespace private { separator = / prefix = inbox = yes } namespace private { separator = / prefix = testArchive/ location = maildir:/Shared Items/MailArchive/%u subscriptions = yes } My quota research has led me to try this: quota = maildir:User quota:ns= quota2 = maildir:ns=testArchive/ quota2_rule = *:storage=20G The first line is already in the default config, with the exception of the added “:ns=“ at the end. The 2nd line in the examples I saw had a middle component w/ the quota name, but when I tried that, like so: quota2 = maildir:Archive quota:ns=testArchive/ my server fails and shows this in the logs: > Fatal: IMAP(*): Quota root test backend maildir: Unknown parameter: ns=testArchive/ Any idea why it doesn’t like that? Also, do I need to add a quota_rule for the primary quota? It does not have one normally in the Mac OS X Server config… Thus far in my testing, I’ve been able to get the 2 quotas to show up in Roundcube and Mac Mail.app. It’s a little messy…the first shows up as “User quota”, the 2nd as “ns=testArchive/“, presumably because I cannot leave the description field in there. Unfortunately, both quotas show the same amount of space in use. If I drop the primary quota to a mere 4MB for testing, and if I have 5.2MB of messages in a testArchive folder, the space used for “User quota” shows as 5.2MB (>100%), as does the “ns=testArchive/“ quota (which is 20GB). In actuality, the Inbox namespace is really only using a few KB— the 5.2MB is in the testArchive namespace. This means that I cannot move messages between either set of namespaces, and new messages are not delivered. So, the quota trouble here is negating the whole point of having the Archive namespace... Is there a way to get Dovecot to “see” the 2 quotas as unique/discrete? It seems like I’m close to accomplishing what I want, but just can’t quite get it to cooperate. And that “Unknown parameter” error is bewildering. Any ideas? Thx, Fred P.S. I can add my Dovecot config to the thread upon request…didn’t want to make this initial message even longer.

4 16

AW: User unknown in local recipient table
by Kalle Erlacher 01 Dec '16

01 Dec '16

Hallo Liste, hallo Ralf, danke schon mal. Ja die Whitespaces sind beim Rauslöschen entstanden. Ich verstand das so, dass das nun durch die address_verify_map erledigt würde. Muss ich dann entsprechend einfach auf die verweisen? Ich versuchte gerade die address_verify_map = btree:$data_directory/verify_cache auf local_recipient_maps = btree:$data_directory/verify_cache verweisen zu lassen. Leider ohne Erfolg. Bisher ist verify_cache nämlich leider noch unbefüllt. Entsprechend bekomme ich folgende Fehler: Dec 1 16:16:29 test-mail postfix/smtpd[5550]: warning: btree:/var/lib/postfix/verify_cache is unavailable. open database /var/lib/postfix/verify_cache.db: No such file or directory Dec 1 16:16:29 test-mail postfix/smtpd[5550]: warning: btree:/var/lib/postfix/verify_cache lookup error for "juergen @domain.org" Dec 1 16:16:29 test-mail postfix/smtpd[5550]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 451 4.3.0 <juergen.pittorf(a)doag.org>: Temporary lookup failure; from=<kalle(a)domain.org> to=<juergen(a)domain.org> proto=ESMTP helo=<test-mail.domain.org> Auch ein plumpes touch auf /var/lib/postfix/verify_cache.db bringt danach den selben Fehler. Liebe Grüße Kalle -----Ursprüngliche Nachricht----- Von: Dovecot [mailto:dovecot-bounces@listen.jpberlin.de] Im Auftrag von Ralf Hildebrandt Gesendet: Donnerstag, 1. Dezember 2016 15:38 An: dovecot(a)listen.jpberlin.de Betreff: Re: User unknown in local recipient table * Kalle Erlacher <kalle.erlacher(a)doag.org>: > Dec 1 14:38:44 test-mail postfix/smtpd[3366]: NOQUEUE: reject: RCPT > from > localhost[127.0.0.1]: 550 5.1.1 <juergen(a)domain.org>: Recipient > address > rejected: User unknown in local recipient table; > from=<kalle(a)domain.org> to=<juergen @domain.org> proto=ESMTP > helo=<test-mail.domain.org> ... local recipient table = domain ist in mydestination > mydestination = test-mail.domain.org mail. domain.org domain.org > localhost Ich hoffe das Leerzeichen zwischen "mail." und "domain.org" ist nicht wirklich da Explizit ist da nix gesetzt, laut "postconf -n", ergo defaults für local_recipient_maps: local_recipient_maps = proxy:unix:passwd.byname $alias_maps Aber die Domain domain.org soll doch sicher im dovecot landen, oder? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

3 3

Re: dovecot Digest, Vol 163, Issue 34
by J. Nick Koston 01 Dec '16

01 Dec '16

Aki, Multiple local_names would be ideal to accommodate certificates that have multiple names. The way I’m reading the code it looks like its having to pay for the memory for every name on the certificate because a unique CTX is being created for each name even if they are all on a single certificate. This would be a big memory win for anyone using a certificate with multiple names on it. Thanks -Nick cPanel Inc >> > > Dear Aki et al., > > How straightforward would it be to implement the following or similar syntax: > > local_name foo.tld www.foo.tld mail.foo.tld bar.tld { > ... > } > > ?? > > Thank you! > > -FG > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > dovecot mailing list > dovecot(a)dovecot.org > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > > ------------------------------ > > End of dovecot Digest, Vol 163, Issue 34 > ****************************************

2 3

use IMAPSIEVE to update database with last_read date
by KT Walrus 30 Nov '16

30 Nov '16

Just noticed the Dovecot support IMAPSIEVE extension… Could I use this extension to update an external database with the date that the user last read the message? My app sends certain “notification” messages to the user’s dovecot mail address. The user reads the messages in their dovecot mailboxes only using IMAP. I want to update my app’s database to record this read time for all “notification” messages sent by the app. Seems to me I could write a short sieve script to send a “notify” message to an app specific address that my app “watches” and updates the appropriate database record with the last_read time. Is this workable for production deploy? Or, is there a better way for a sender to be notified when the recipient actually reads the message? The sender will be my app and the recipient is a dovecot mailbox accessed by IMAP. Kevin

2 3

Sieve script won't compile. Compiler output isn't helpful.
by Steven Mainor 30 Nov '16

30 Nov '16

Hello! I hope you will forgive my ignorance but I have a problem I have been trying to solve for a week and I'm not sure where else to turn. I'm trying to write a sieve script to sort all of my mail. I was writing this script to replace the one I am currently using but I can't seem to get it to compile. I don't know a lot about sieve or really scripting of any kind and I just can't figure out what I'm doing wrong. The compiler just puts out a bunch of output that doesn't make sense. like "unexpected character" when I know the character works there because I am already running a script with some of the same lines. I'm attaching the script with some names and addresses changed and the sieve output to this email. I would greatly appreciate any help anyone could offer.

5 8

Quota Clone not tracking unlimited quota
by Prakash Autade 30 Nov '16

30 Nov '16

We are configuring 'Count quota' with 'Quota Clone Plugin' Everything is working perfectly when we set limit in quota_rule(quota_rule = *:bytes=500M). In case of unlimited quota(quota_rule = *:bytes=0) - Count quota is updating values * - Quota Clone plugin is not updating values in redis.* We have configured dovecot as mail_plugins = $mail_plugins quota quota_clone mail_log notify mailbox_list_index = yes plugin { quota = count:User quota quota_vsizes = yes quota_rule = *:bytes=0 quota_clone_dict = redis:host=127.0.0.1:port=6379 } -- Sincerely, Prakash P. Autade.

1 0

Dovecot seems to open extra namespaces
by Thorsten Hater 30 Nov '16

30 Nov '16

Dear all, I am slightly confused by the following log entries ...: imap(...): Debug: Namespace inbox: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir ...: imap(...): Debug: maildir++: root=~/Maildir, index=, indexpvt=, control=, inbox=~/Maildir, alt= ...: imap(...): Debug: Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, subscriptions=no location=fail::LAYOUT=none ...: imap(...): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= It seems that Dovecot opens two different namespaces, despite only one being configured in 10-mail.conf/15-mailboxes.conf. Is this normal and intended? Further, what is the purpose of the line starting with 'none'? Best regards, Thorsten Dovecot version: 2.2.26.0 on Debian Jessie

3 4

shared/public mailbox application
by Michael Fox 30 Nov '16

30 Nov '16

I'm new to Dovecot and I need help configuring a shared or public mailbox - I'm not sure which is appropriate. I've read the wiki and Peer's book and neither appears to cover what I'd like to do. So I could use some specific help on how to configure a solution for the following: I'd like to create two real mailboxes, let's call them AAA and BBB. Let's call the domain "mydomain". Anyone user can send mail to them, just like any other address: aaa@mydomain or bbb@mydomain. I'd like all IMAP users in mydomain to be able to read the messages in those mailboxes. I'd like all POP users in mydomain to also see those messages. (But I don't think I need help with the virtual part). I'd like only a few designated IMAP users to be able to delete the messages in those mailboxes, including dummy users AAA and BBB themselves. Ideally, I'd like them to appear in the client under a separate namespace from shared mailboxes. Example: INBOX +--- the normal stuff. Shared +--- user1 +--- user2 Special +--- AAA +--- BBB My confusion: 1) I don't know if this requires a shared namespace or a public namespace. It "feels" like it's "public", since all users would have access. But Peer's book and the wiki describe manually creating folders for public namespaces and controlling the contents with manual file manipulation, which leads me to believe that they can't be used for regular mail (although the book and the wiki never say one way or the other). I don't want to manually control files. I want to send mail to the mailbox and delete (see above) it with a client. 2) There are several examples in Peer's book and the wiki, but none seem to match what I want. (This is the problem with documentation that is predominantly example-based). I guess I need more explanation of the mechanical differences between shared and public and why one would pick one over the other. Can someone help? Please be as specific as you can. Thanks much, Michael

3 8

v2.2.27 release candidate released
by Timo Sirainen 30 Nov '16

30 Nov '16

http://dovecot.org/releases/2.2/rc/dovecot-2.2.27.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.27.rc1.tar.gz.sig Most interestingly there's a new mail_crypt plugin. It would be nice if crypto gurus could check through it for any issues. Director's tagging fix was also quite a large change, but the new code is already used in production and appears to be working fine. * dovecot.list.index.log rotation sizes/times were changed so that the .log file stays smaller and .log.2 is deleted sooner. + Added mail_crypt plugin that allows encryption of stored emails. See http://wiki2.dovecot.org/Plugins/MailCrypt + stats: Global stats can be sent to Carbon server by setting stats_carbon_server=ip:port + imap/pop3 proxy: If passdb returns proxy_not_trusted, don't send ID/XCLIENT + Added generic hash modifier for %variables: %{<hash algorithm>;rounds=<n>,truncate=<bits>,salt=s>:field} Hash algorithm is any of the supported ones, e.g. md5, sha1, sha256. Also "pkcs5" is supported using SHA256. For example: %{sha256:user} or %{md5;truncate=32:user}. + Added support for SHA3-256 and SHA3-512 hashes. + config: Support DNS wildcards in local_name, e.g. local_name *.example.com { .. } matches anything.example.com, but not multiple.anything.example.com. - Fixed crash in auth process when auth-policy was configured and authentication was aborted/failed without a username set. - director: If two users had different tags but the same hash, the users may have been redirected to the wrong tag's hosts. - Index files may have been thought incorrectly lost, causing "Missing middle file seq=.." to be logged and index rebuild. This happened more easily with IMAP hibernation enabled. - Various fixes to restoring state correctly in un-hibernation. - dovecot.index files were commonly 4 bytes per email too large. This is because 3 bytes per email were being wasted that could have been used for IMAP keywords. - Various fixes to handle dovecot.list.index corruption better. - lib-fts: Fixed assert-crash in address tokenizer with specific input. - Fixed assert-crash in HTML to text parsing with specific input (e.g. for FTS indexing or snippet generation) - doveadm sync -1: Fixed handling mailbox GUID conflicts. - sdbox, mdbox: Perform full index rebuild if corruption is detected inside lib-index, which runs index fsck.

1 0

auth client limit versus service count of mail processes
by Christian Balzer 29 Nov '16

29 Nov '16

Hello, We've got a pretty substantial dovecot installation (versions 2.1.7 and 2.2.13 on the backends, but tested with 2.2.24 as well) and this is the relevant config snippet from 10-master.conf: --- default_process_limit = 1024 default_client_limit = 16384 [...] service imap { # Most of the memory goes to mmap()ing files. You may need to increase this # limit if you have huge mailboxes. #vsz_limit = $default_vsz_limit vsz_limit = 512M # Max. number of IMAP processes (connections) #process_limit = 1024 process_limit = 524288 } service pop3 { # Max. number of POP3 processes (connections) process_limit = 2048 # Reduce spawns from hell service_count = 100 } --- The above works fine, no warnings. Since 2 of our mailbox servers get a high number (2million/day) of IMAP logins and resulting mail process spawns, I pondered doing the service count bit for IMAP as well. But adding a "service_count = 100" line (any value larger than 1 really) to the imap section we get the dreaded: --- Nov 28 17:05:40 mbx09 dovecot: config: Warning: service auth { client_limit=16384} is lower than required under max. load (528384) --- And that's quite true, once reaching that limit auth will pile up and fail eventually. Clearly the pop3 part with a max of 2048 processes (we see about 300 at peak times) neatly fits into the client limit of 16384. Now setting the client limit in the auth section to the required value of course will do no real good in this scenario, as the fd limit becomes the next bottleneck and I'm not going to raise that to 500k, thank you very much. ^o^ So basically my questions here are: 1. Where's the difference in Dovecot's logic between a mail service that has a service count of 1 versus one with >1? 2. Any way to get the process recycling for IMAP going w/o setting the fd limit to a ridiculous amount? Thanks, Christian -- Christian Balzer Network/Systems Engineer chibi(a)gol.com Global OnLine Japan/Rakuten Communications http://www.gol.com/

2 2

what user to use for SIS deduplication?
by Jesus Cea 28 Nov '16

28 Nov '16

Running Dovecot 2.2.25. I have the following line in my root crontab: "/usr/local/bin/doveadm sis deduplicate /home/dovecot/buzones/attachments /home/dovecot/buzones/attachments/queue" This line is execute each hour and the plan is to deduplicate attachments stored in the SIS system. This works well most of the time, but from time to time cron complains with this error: """ Error: mkdir(/home/dovecot/buzones/attachments/bb/f8/hashes) failed: No such file or directory """ In those situations I just create the directory by hand and set the right permissions. Interestingly, most of the time everything works fine, dovecot creates the needed directories and everything is fine. But I get that error every few days and I must create the directory by hand. Am I running the deduplication process correctly?. It is launched as "root" and I would expect it to "setgid()" to the right user/group (dovemail). Should I run it in the dovemail cron?. I have a faint memory of getting the very same error in that case, a missing hash directory, but I am not sure I am recalling correctly. Any advice?. Thanks. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea(a)jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz

1 0

Problem with multiple ldap passdb
by Martin Wheldon 28 Nov '16

28 Nov '16

Hi mailing list, I'm currently running dovecot 2.2.13 from Debian Jessie, all is running fine. However I am attempting to merge 2 LDAP authentication sources. I would like to attempt to authenticate against the first authentication source, if that fails either by password fail or user not found, then attempt the next LDAP server. I've added the a passdb and userdb entry for the new ldap server. As you can see from the log below the user isn't found in the first LDAP query, but is in the second one. However the authentication fails: Nov 22 13:59:38 he01-imap-01 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011session=WTLjLuRB9QBRlIlQ#011lip=51.254.222.112#011rip=81.148.137.80#011lport=143#011rport=56821#011resp=AG1hcnRpbi53aGVsZG9uQGdyXWVuaGlsbHMtaXQuY28udWsAQ3JhY2spbk4wdw== (previous base64 data may contain sensitive data) Nov 22 13:59:38 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<WTLjLuRB9QBRlIlQ>): bind search: base=dc=greenhills-it,dc=co,dc=uk filter=(&(&(ukFirmGhITAccSrvcs=Email)(ukFirmGhITAccLocked=Email-FALSE))(|(uidNumber=martin.wheldon at greenhills-it.co.uk)(mail=martin.wheldon at greenhills-it.co.uk))) Nov 22 13:59:38 he01-imap-01 dovecot: auth: Error: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<WTLjLuRB9QBRlIlQ>): ldap_search(base=dc=greenhills-it,dc=co,dc=uk filter=(&(&(ukFirmGhITAccSrvcs=Email)(ukFirmGhITAccLocked=Email-FALSE))(|(uidNumber=martin.wheldon at greenhills-it.co.uk)(mail=martin.wheldon at greenhills-it.co.uk)))) failed: No such object Nov 22 13:59:38 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<WTLjLuRB9QBRlIlQ>): bind search: base=dc=greenhills-it,dc=co,dc=uk filter=(|(uid=martin.wheldon at greenhills-it.co.uk)(mail=martin.wheldon at greenhills-it.co.uk)) Nov 22 13:59:38 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<WTLjLuRB9QBRlIlQ>): result: uid=00000001; uid unused Nov 22 13:59:38 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<WTLjLuRB9QBRlIlQ>): username changed martin.wheldon at greenhills-it.co.uk -> 00000001 Nov 22 13:59:38 he01-imap-01 dovecot: auth: Debug: ldap(00000001,81.148.137.80,<WTLjLuRB9QBRlIlQ>): result: uid=00000001 Nov 22 13:59:40 he01-imap-01 dovecot: auth: Debug: client passdb out: FAIL#0111#011user=00000001#011temp#011original_user=martin.wheldon at greenhills-it.co.uk I know that the password was entered correctly because if I disable the new ldap config and login I get authenticated properly. Nov 22 14:00:38 he01-imap-01 dovecot: auth: Debug: auth client connected (pid=2626) Nov 22 14:00:39 he01-imap-01 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011session=ipKBMuRBBQBRlIlQ#011lip=51.254.222.112#011rip=81.148.137.80#011lport=143#011rport=38149#011resp=AG1hcnRpbi53aGVsZG9uQGdyXWVuaGlsbHMtaXQuY28udWsAQ3JhY2spbk4wdw== (previous base64 data may contain sensitive data) Nov 22 14:00:39 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<ipKBMuRBBQBRlIlQ>): bind search: base=dc=greenhills-it,dc=co,dc=uk filter=(|(uid=martin.wheldon at greenhills-it.co.uk)(mail=martin.wheldon at greenhills-it.co.uk)) Nov 22 14:00:39 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<ipKBMuRBBQBRlIlQ>): result: uid=00000001; uid unused Nov 22 14:00:39 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<ipKBMuRBBQBRlIlQ>): username changed martin.wheldon at greenhills-it.co.uk -> 00000001 Nov 22 14:00:39 he01-imap-01 dovecot: auth: Debug: ldap(00000001,81.148.137.80,<ipKBMuRBBQBRlIlQ>): result: uid=00000001 Nov 22 14:00:39 he01-imap-01 dovecot: auth: Debug: client passdb out: OK#0111#011user=00000001#011original_user=martin.wheldon at greenhills-it.co.uk I've done loads of googling and I believe that this is possible so I must either have misread the documentation or am triggering a bug. Neither of which I seem to be able to confirm. Any help would be much appreciated. My broken configuration is below: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login default_vsz_limit = 512 M lmtp_rcpt_check_quota = yes lmtp_save_to_detail_mailbox = yes mail_location = maildir:~/Maildir mail_plugins = " quota" 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 ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap-new.conf.ext driver = ldap } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap skip = authenticated } plugin { antispam_backend = pipe antispam_pipe_program = /usr/sbin/sendmail antispam_pipe_program_args = -f;%{auth_user};-r;%{auth_user} antispam_pipe_program_notspam_arg = retrain-as-ham(a)greenhills-it.co.uk antispam_pipe_program_spam_arg = retrain-as-spam(a)greenhills-it.co.uk antispam_spam = Spam antispam_trash = Trash quota = maildir:User quota quota_rule = *:storage=1G quota_rule2 = Trash:ignore quota_rule3 = Spam:ignore sieve = ~/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve/move-spam.sieve sieve_dir = ~/sieve } protocols = " imap lmtp sieve pop3" service imap-login { process_min_avail = 20 service_count = 1 } service imap { process_min_avail = 20 } service lmtp { inet_listener lmtp { address = he01-imap-01.greenhills-it.co.uk 127.0.0.1 port = 2003 } } service pop3 { process_min_avail = 20 } ssl = required ssl_cert = </etc/ssl/certs/combined_2015_greenhills-it.co.uk.cert ssl_cipher_list = ALL:HIGH:!MEDIUM:!LOW:!SSLv2:!EXPORT:!PSK:!DES:!3DES:!MD5:!DES+MD5:!RC4:!SEED+SHA:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA:!eNULL:!aNULL:@STRENGTH ssl_dh_parameters_length = 2048 ssl_key = </etc/ssl/private/stripped.2015.greenhills-it.co.uk.pem ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { args = /etc/dovecot/dovecot-ldap-new.conf.ext driver = ldap } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota" } # Working LDAP configuration # /etc/dovecot/dovecot-ldap.conf.ext uris = ldap://he01-auth-01.greenhills-it.co.uk dn = uid=dovecot,ou=people,ou=SRV_Accounts,dc=greenhills-it,dc=co,dc=uk dnpass = VerySecret sasl_bind = no auth_bind = yes ldap_version = 3 base = dc=greenhills-it,dc=co,dc=uk scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,gosaMailQuota=quota_rule=*:storage=%$M user_filter = (|(uid=%u)(mail=%u)(gosaMailAlternateAddress=%u)) pass_attrs = uid=user,userPassword=password pass_filter = (|(uid=%u)(mail=%u)) default_pass_scheme = CRYPT # Non working LDAP configuration # /etc/dovecot/dovecot-ldap-new.conf.ext uris = ldap://dir.greenhills-it.co.uk dn = "cn=dovecot,ou=search accounts,ou=services,dc=greenhills-it,dc=co,dc=uk" dnpass = VerySecret sasl_bind = no tls = yes tls_ca_cert_file = /etc/ssl/certs/GreenhillsCACert.pem tls_require_cert = demand debug_level = -1 auth_bind = yes ldap_version = 3 base = ou=customers,dc=greenhills-it,dc=co,dc=uk scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,ukFirmGhITAccMailQuota=quota_rule=*:storage=%$M user_filter = (&(&(ukFirmGhITAccSrvcs=Email)(ukFirmGhITAccLocked=Email-FALSE))(|(uidNumber=%u)(mail=%u)(ukFirmGhITAccMailAlias=%u))) pass_attrs = uidNumber=user pass_filter = (&(&(ukFirmGhITAccSrvcs=Email)(ukFirmGhITAccLocked=Email-FALSE))(|(uidNumber=%u)(mail=%u))) default_pass_scheme = SSHA Best Regards -- Martin Wheldon Greenhills IT Ltd. Telephone: 01904 238 454 Website: www.greenhills-it.co.uk Greenhills IT Ltd. is a limited company registered in England and Wales. Company Registration No: 06387214 Registered Offices: 2 Greenhills, Claxton, YORK, North Yorkshire, YO60 7SA

1 1

Rebuild UIDs for mdbox
by Darac Marjal 28 Nov '16

28 Nov '16

Hello all, I think I'm hitting an issue with overly large UIDs in one of my mailboxes. I initially thought it was a problem with claws-mail hitting an infinite loop. Claws-mail /seems/ to work fine, until it gets to this one mailbox, wherein the following is logged: [20:23:04] IMAP> 86 SELECT LocalCron [20:23:04] IMAP< * OK [CLOSED] Previous mailbox closed. [20:23:04] IMAP< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft Junk NonJunk) [20:23:04] IMAP< * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft Junk NonJunk \*)] Flags permitted. [20:23:04] IMAP< * 399 EXISTS [20:23:04] IMAP< * 0 RECENT [20:23:04] IMAP< * OK [UNSEEN 399] First unseen. [20:23:04] IMAP< * OK [UIDVALIDITY 1163720154] UIDs valid [20:23:04] IMAP< * OK [UIDNEXT 3069273506] Predicted next UID [20:23:04] IMAP< * OK [HIGHESTMODSEQ 120748] Highest [20:23:04] IMAP< 86 OK [READ-WRITE] Select completed (0.000 + 0.000 secs). imap-thread.c:1344:imap select run - end 0 imap-thread.c:388:generic_cb imap-thread.c:372:found imap 0x22c8f60 imap-thread.c:1431:imap select - end imap.c:3961:select: exists 399 recent 0 expunge 0 uid_validity 1163720154 can_create_flags 1 imap-thread.c:2018:imap fetch_uid - begin imap-thread.c:372:found imap 0x22c8f60 imap-thread.c:372:found imap 0x22c8f60 [20:23:04] IMAP- [fetching UIDs...] [20:23:04] IMAP> 87 UID FETCH 1:* (UID) [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< FETCH (UID 3069273244) [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< TCH (UID 3069273313) [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< TCH (UID 3069273382) [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< TCH (UID 3069273451) [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [FETCH data - 551 bytes] imap-thread.c:2008:imap fetch_uid run - end 0 imap-thread.c:388:generic_cb imap-thread.c:372:found imap 0x22c8f60 imap-thread.c:2029:imap fetch_uid - end imap.c:542:unlocking session 0x22e4c00 imap.c:4663:get_num_list: got 399 msgs imap.c:4673:removing old messages from /home/darac/.claws-mail/imapcache/mail.darac.org.uk/darac(a)darac.org.uk/LocalCron imap.c:4677:get_num_list - ok - 399 folder.c:2265:Removed message 2147483647 from cache. That last line (Removed message 2147483647 from cache) is repeated ad infinitum. Now, I happened to spot that that number is 2^31 - 1 so started looking to see if claws-mail was handling UIDs incorrectly. That lead me to http://wiki.dovecot.org/Clients/NegativeUIDs. Firstly, that page states that UIDs should be 32-bit integers. If so, why do there appear to be UIDs greater than 3 billion in the mailbox? Secondly, that page gives instructions on how to fix the problem with mbox and maildir backends. However, my mail is stored in mdboxes. Is there a way to re-generate UIDs for mdbox mailboxes? Thanks in advance!

2 2

CPU for Dovecot
by Miloslav Hůla 28 Nov '16

28 Nov '16

Hi, we are planning to change hardware for our standalone Dovecot instance handling ~5800 IMAP users with 1TB mailboxes on local RAID. Is there some recommendation about CPU? We can choose from: - Intel Xeon E5-2620v4 - 2,1GHz@8,0GT 20MB cache, 8core, HT, 85W, LGA2011 - Intel Xeon E5-2623v4 - 2,6GHz@8,0GT 10MB cache, 4core, HT, 85W, LGA2011 The difference is about more cores vs. hi frequency. Thank you, Miloslav

4 4

Dovecot proxy
by Gandalf Corvotempesta 26 Nov '16

26 Nov '16

Hi to all I have some *production* pop3/inappropriate server that i would like to move under a proxy Some questions: 1. Keeping the same original hostname on the proxy (in example mail.mydomain.tld) and changing the hostname on the imap server, makes some troubles like MUA redownloading all the messages? Is dovecot (running on the imap server) happy seeing the hostname change? What about maildirs, where the hostname is wrote on the mail file? 2. Dovecot proxy will proxy the whole pop3/imap traffic or only the login auth? I don't want to expose the mailservers to internet, all imap session must be proxied through the proxy. this because I'll use local IPs on each mail server. 3. Performance for the proxy server? The same as the mailserver or higher due to the missing email computation? In example, the proxy doesn't have to access disks or emails data but has only to transmit what the mailserver osd saying 4. Like question 3, any real users for the proxy? I would like to know some info about hardware and userbase (in example: dual quad xeon 5600, 32Gb ram, 10.000 concurrent sessions) In my case I'm planning for about 100 active sessions. Can i use a small EC2 instance?

1 1

Re: (build) crash in dcrypt when "-Bsymbolic-functions" is used on linking
by Aki Tuomi 25 Nov '16

25 Nov '16

On 26.10.2016 13:48, Christian Ehrhardt wrote: > Hi, > I was wondering about a crash when building dovecot 2.2.25 on latest > Ubuntu. > I wondered as I've had the same source building on Debian just fine. > > Some debugging led me to this weird behavior: > Using this gdb command file called autoreportissue in my case: > break dcrypt_initialize > commands > p dcrypt_vfs > p &dcrypt_vfs > watch dcrypt_vfs > c > end > break dcrypt_set_vfs > commands > p dcrypt_vfs > p &dcrypt_vfs > c > end > r > > Running test-crypto on Debian and Ubuntu reported those two behaviours: > gdb -d /root/dovecot-2.2.25/src/ -x autoreportissue ./test-crypto > > Good: > Breakpoint 1, dcrypt_initialize (backend=0x555555587c02 "openssl", > set=0x0, error_r=0x0) at dcrypt.c:15 > 15 if (dcrypt_vfs != NULL) { > $1 = (struct dcrypt_vfs *) 0x0 > $2 = (struct dcrypt_vfs **) 0x555555796370 <dcrypt_vfs> > Hardware watchpoint 3: dcrypt_vfs > Breakpoint 2, dcrypt_set_vfs (vfs=0x7ffff7835020 <dcrypt_openssl_vfs>) > at dcrypt.c:56 > 56 dcrypt_vfs = vfs; > $3 = (struct dcrypt_vfs *) 0x0 > $4 = (struct dcrypt_vfs **) 0x555555796370 <dcrypt_vfs> > Hardware watchpoint 3: dcrypt_vfs > Old value = (struct dcrypt_vfs *) 0x0 > New value = (struct dcrypt_vfs *) 0x7ffff7835020 <dcrypt_openssl_vfs> > dcrypt_set_vfs (vfs=0x7ffff7835020 <dcrypt_openssl_vfs>) at dcrypt.c:57 > 57 } > > Bad: > Breakpoint 1, dcrypt_initialize (backend=0x555555589f02 "openssl", > set=0x0, error_r=0x0) at dcrypt.c:11 > 11 { > $1 = (struct dcrypt_vfs *) 0x0 > $2 = (struct dcrypt_vfs **) 0x555555798370 <dcrypt_vfs> > Hardware watchpoint 3: dcrypt_vfs > Breakpoint 2, dcrypt_set_vfs (vfs=0x7ffff780a020 <dcrypt_openssl_vfs>) > at dcrypt.c:56 > 56 dcrypt_vfs = vfs; > $3 = (struct dcrypt_vfs *) 0x0 > $4 = (struct dcrypt_vfs **) 0x7ffff780a890 <dcrypt_vfs> > Panic: file dcrypt.c: line 34 (dcrypt_initialize): assertion failed: > (dcrypt_vfs != NULL) > Error: Raw backtrace: > /root/dovecot-2.2.25/src/lib-dcrypt/test-crypto(+0x15f7c) > [0x555555569f7c] -> > /root/dovecot-2.2.25/src/lib-dcrypt/test-crypto(default_error_handler+0) > [0x55555556a030] -> > /root/dovecot-2.2.25/src/lib-dcrypt/test-crypto(i_fatal+0) > [0x55555556a2ff] -> > /root/dovecot-2.2.25/src/lib-dcrypt/test-crypto(dcrypt_initialize+0x140) > [0x55555555f030] -> > /root/dovecot-2.2.25/src/lib-dcrypt/test-crypto(main+0x23) > [0x55555556706d] -> > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) > [0x7ffff782d3f1] -> > /root/dovecot-2.2.25/src/lib-dcrypt/test-crypto(_start+0x2a) > [0x55555555edea] > Program received signal SIGABRT, Aborted. > > One can see that in the bad case the pointer of dcrypt_vfs is pointing > to something of the scope of the .libs/libdcrypt_openssl.so file and > not the dcrypt_initialize of test-crypto. > > That made me wonder even more - where would this issue of variable > scope come from. After more debugging I found that the linker flag > "-Bsymbolic-functions" is the reason. This is default on recent > Ubuntu, but not on Debian (?yet?). > > Eventually what happens is that the dcrypt_vfs becomes part of the > .libs/libdcrypt_openssl.so. So the call from there to dcrypt_set_vfs > ends up setting not the expected variable. > I was unable to come up with a reasonable fix since I'm not enough > into your sublib structure. > > For now I assume I'm gonna build the package stripping this flag in > Ubuntu. > But long term I think dovecot should fix it to work with that compiler > flag. > Therefore the report to make you aware. > > > P.S. thanks to the dovecot community for having unit tests that find > this at build time! > > -- > Christian Ehrhardt > Software Engineer, Ubuntu Server > Canonical Ltd Hi! Thank you for reporting this, we'll look into it. Aki Tuomi Dovecot oy

1 1

Could the index of dovecot be stored in database?
by eSX 25 Nov '16

25 Nov '16

Hi dovecot, I have a question about the index of dovecot. I had read the wiki, and saw that I can custom a Input streams to do read/seek/sync...by implementing a istream-*.c file. Thus maybe dovecot can read mail from a http server or any others. But I found that the index of maildir can't extend very well. There is no extern API for developer? For example, I want to put the index to database(maybe, MySQL) or any else, But I found I have no way to implement it, Unless a heavy modification? -- eSX

1 0

Patch for dovecot-antispam-plugin to support IMAP Flags indicating Junk status
by Jonas Wielicki 25 Nov '16

25 Nov '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dear list, I made a patch which extends dovecot-antispam-plugin with support to take the addition and removal of a specific set of flags as trigger for learning. This allows for very tight integration with Thunderbird and KMail, which both set flags for Junk messages (Thunderbird sets "Junk", KMail sets "JUNK"). With this patch and according configuration, dovecot-antispam-plugin can trigger on the addition (learn as spam) and removal (learn as ham) of these flags. Combined with a sieve script which sets these flags for incoming mail which has been classified as spam, this allows for a tight and intuitive feedback loop between users and the server-side spam classification system. I tested that patch with dovecot 2.2 from Debian stretch and so far it works pretty well. I realise that dovecot-antispam-plugin has not been updated since 2013. It also has not been migrated to Github yet. If it is to be migrated there, I would be happy to submit a pull request there for discussion and merging. Otherwise, someone would have to indicate how to go forward with applying this patch to the official version, if that is desired. The patch is based on current tip and feedback is appreciated. I took some inspiration from dovecot-core/src/plugins/notify/notify-storage.c -- this requires the use of struct mail_private to be able to override the vfunc for mail_update_keywords, which I actually do not like. However, when I tried to make this patch base on the use of the notify plugin (via notify_register), I ran into the issue that the transaction is partially freed before the transaction_commit event from notify is emitted, which is unfortunate and breaks at least the mailtrain backend (which I use). This is in theory fixable, but I wanted to keep the patch as small as possible, as I have no idea whether this will eventually end up upstream or whether I’ll have to maintain that for myself. If upstream is not interested in this patch, please let me know! In that case, I would consider making an own plugin, which fewer backends (possibly only a mailtrain-like one) out of this, but frankly, I would consider that a waste of resources. In the hope that this is useful for others and hoping for feedback, Jonas Wielicki -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEG/EPV+Xzd5wEoQQIwGIDJZdiWIoFAlg4Fd0ACgkQwGIDJZdi WIpM3Q//TWVHDFx5LK14y0jOnxzE7kGthc6hakILnWqYgl7B/wlljD1HLrec//hg 9LEancjURnv3sPU/kEEpl6RRDX5kDMbXXKXMq7/1R7bNdmeMz5NEebAo7ktlCii7 ikk7MPL0F8UViY7IoW7y5NxfqMUldYseejn0GwKiVkEyqlyGLRbP7ijyzMWjpIWp eqOg/b5bNX6ARMC1O/hKhvHw4AhvSO2j73da60Xchu39gvDa2kC+MTU/kX4wb6po kPOEgFxGhpxG0+UMzUEBPLYwY3Q9x+R/PzlpUF6xEjYxgE7leVRVfCHiZLsMUGH1 itozwSzoAyDYV+Rbzk8OEBL6EGBJQHqYmNybULZsJkxhUenNeC4GRf7NcJ0jAisG rSfwr/+kD9+ErKNgtNJzfceLYGNWti44whV6kXxRxqGlIfJsJB7ZMdrj8+wSdn0p slXUoyHMUkRkN92tIPqZF5cb+5Ke+O+5hHE07Wohxw3eNoBSqtQWo81aigjaCraC ivcZX3HswTapyKtpgWMzjoWqp982crr+wtAI+AlEUKoCEqF54EnxM1kB1qoe0HcH nMgMdIkXI4VzPaUNUK206ffEtlnKNIqF3SkOkBX263L0ZJgXyCFRRj6W3z78VDdP He62tN/FPPBtmeVrmCj2ZDE+6gqtMQN52FsN4mpaq4BrCYlYB7g= =3+CU -----END PGP SIGNATURE-----

1 0

Updated my Dovecot certificate for the first time
by Steve Litt 25 Nov '16

25 Nov '16

Hi all, I've used Dovecot since February 2012, but because I kept reinstalling Linux with every major version, I never had a Dovecot self-signed certificate go bad on me before. Til now. I started using rolling release Void Linux about a year ago, and my Dovecot self-signed certificate just expired. The solution I used is contained in these documents: http://wiki2.dovecot.org/SSL/CertificateCreation http://wiki2.dovecot.org/SSL/CertificateClientImporting file:///etc/ssl/dovecot-openssl.cnf http://www.faqforge.com/linux/renew-the-dovecot-ssl-certificate-on-ubuntu-l… I basically moved my old /etc/ssl/certs/dovecot.pem and /etc/ssl/private/dovecot.pem, then edited /etc/ssl/dovecot-openssl.cnf specifically to give myself the common name of 192.168.100.2. I had earlier used my hostname, but that produced a conflict, so I just used the ip address. Then I ran dovecot-mkcert.sh to create the new self-signed cert, and finally, configured Claws-Mail to use /etc/ssl/certs/dovecot.pem as its cert. Obviously, if my Claws-Mail were on a different machine than my Dovecot, I would have had Claws-Mail point to a local copy. Alpine still gives me a bad cert warning, saying I should either fix it or disable checking. I haven't yet found a way to get Alpine to discriminate between a valid self-signed cert and a bad one. Anyway, all's good. SteveT Steve Litt November 2016 featured book: Quit Joblessness: Start Your Own Business http://www.troubleshooters.com/startbiz

7 9

Re: Updated my Dovecot certificate for the first time
by Joseph Tam 24 Nov '16

24 Nov '16

On Thu, 24 Nov 2016, Steve Litt wrote >> add the public part of the cert into your system's trusted CA store. > > Silly question, but how would you do that? You didn't say which OS you're running on (alpine runs on Windows as well), but I'll assume *nix. A previous poster showed you how to do it with a real certificate, and the steps are the same. However, the way I found out without too much fuss was to process trace my alpine process and see where it tied to load a cert $ strace -o trace.out alpine ... quit after connection $ grep -F cert traceout /1: open64("/etc/openssl/cert.pem", O_RDONLY) Err#2 ENOENT /1: stat("/etc/openssl/certs/cbf06781.0", 0xFFBF8E54) Err#2 ENOENT ... Your output will be different of course. The first load is the default pre-loaded root CAs (Thawte, etc.) supplied by OpenSSL, and the second, etc. are chained certificate lookups. You would replace the missing cert with your own self-signed public pem file. e.g. cp mypub.pem /etc/openssl/certs/cbf06781.0 For Windows, I don't know where it fetches it from. Joseph Tam <jtam.home(a)gmail.com>

1 0