- dovecot - dovecot.org

only mark as deleted when deleted as default for some mailboxes
by zucca＠systemschmiede.com 06 May '15

06 May '15

Hi list, i wonder if this is possible with some dovecot configuration. Selected mailboxusers will only mark their mails as deleted, when a mail is being deleted through any client. No automatic expunge. This is default behaviour in Outlook, and i think in Thunderbird too, but unfortunately not in Open-Xchange for example. So i was asking myself if it would be possible to simply turn this feature on maybe globally and as a default for some users. Thank you very much for your reply. Sascha -- Systemschmiede IT-Lösungen Zucca & Teves GbR August-Thyssen-Straße 2-4 52511 Geilenkirchen www.systemschmiede.com Tel.: +49 (0)2451 - 9088390 Fax: +49 (0)2451 - 9124070 Mobil: +49 (0)178 - 4073254 Ust.ID: DE248030393

2 2

dovecot-proxy with managesieve, director and backend dovecot imap
by George Vieira 06 May '15

06 May '15

hi all, I've been tasked to add sieve/managesieve to an existing dovecot cluster running 2.1.7 on debian wheezy which is made up of 2 dovecot-proxy hosts as directors and some back end dovecot imap hosts all running the same version. My problem is that I thought to put the service on the director/proxy hosts since they wouldn't have too much load on it, but when I do I get the following error: Apr 28 11:00:28 master: Info: Dovecot v2.1.7 starting up (core dumps disabled) Apr 28 11:00:28 config: Warning: service auth { client_limit=50000 } is lower than required under max. load (60000) Apr 28 11:00:34 managesieve-login: Error: proxy: host not given: user=<mailchannel(a)mydomain.net>, method=PLAIN, rip=192.168.100.207, lip=192.168.100.119, TLS, session=<3/zPY74UOgDAqGTP> Apr 28 11:00:34 managesieve-login: Info: Aborted login (internal failure, 1 succesful auths): user=<mailchannel(a)mydomain.net>, method=PLAIN, rip=192.168.100.207, lip=192.168.100.119, TLS, session=<3/zPY74UOgDAqGTP> From searching around, only ever saw 1 result which was to add "executable = managesieve-login director" to the managesieve service, but this made no difference at all and the error is the same. So I tried to instead use the back end imap servers, but they throw errors expecting the users password to be the common proxy/director password as below: passdb { driver = static args = user=%u password=crypticpasswordagain } Apr 28 12:03:37 auth: Debug: static(mailchannel(a)mydomain.net,192.168.100.207,<17RTRb8UpADAqGTP>): lookup Apr 28 12:03:37 auth: Info: static(mailchannel(a)mydomain.net,192.168.100.207,<17RTRb8UpADAqGTP>): Password mismatch Apr 28 12:03:37 auth: Debug: static(mailchannel(a)mydomain.net,192.168.100.207,<17RTRb8UpADAqGTP>): PLAIN(85387v92394jks) != 'crypticpasswordagain' Apr 28 12:03:39 auth: Debug: client out: FAIL 1 user=mailchannel(a)mydomain.net So with configs below, how is it best to run managesieve that takes the correct login/password without directing to the cluster (or direct if it's easier but must use real user password)? -- dovecot proxy config -- # dovecot version 2.1.7 instance_name = dovecot-proxy protocols = imap pop3 lmtp sieve mail_location = maildir:~/ #listen = 192.168.101.119 listen = 0.0.0.0 # = dovecot-proxy-1 director_servers = 192.168.101.119 # = dovecot-shared-7 director_mail_servers = 192.168.100.101 base_dir = /var/run/dovecot-proxy login_greeting = Welcome to IMAP. default_internal_user = webmail lmtp_proxy = yes disable_plaintext_auth = no auth_mechanisms = plain login cram-md5 auth_verbose=yes auth_debug=yes auth_debug_passwords=yes mail_debug=yes verbose_ssl=yes auth_verbose_passwords=no #log_path = syslog log_path = /var/log/dovecot.log default_process_limit = 10000 default_client_limit = 50000 ssl = no ssl_cert = </etc/ssl/private/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem director_user_expire = 15 min doveadm_proxy_port = 9292 doveadm_password = somecrypticpassword auth_worker_max_count = 90 passdb { driver = ldap args = /etc/dovecot/dovecot-proxy-ldap.conf.ext } passdb { driver = checkpassword args = /etc/dovecot/checkpassword_migration.py } userdb { driver = prefetch } userdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext } service director { unix_listener login/director { mode = 0666 } fifo_listener login/proxy-notify { mode = 0666 } unix_listener director-userdb { mode = 0600 } inet_listener { port = 9191 } } service imap-login { process_min_avail = 2 service_count = 0 executable = imap-login director inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { process_min_avail = 2 service_count = 0 executable = pop3-login director inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service imap { process_min_avail = 2 process_limit = 0 service_count = 0 } service pop3 { process_min_avail = 2 process_limit = 0 service_count = 0 } service lmtp { inet_listener lmtp { port = 24 } } service auth { client_limit=65000 inet_listener { port = 5451 } } service auth-worker { user = webmail } service doveadm { inet_listener { port = 9292 } } protocol imap { mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 } protocol lmtp { auth_socket_path = director-userdb passdb { driver = ldap args = /etc/dovecot/dovecot-proxy-ldap.conf.ext } } protocol doveadm { auth_socket_path = director-userdb } plugin { # Used by both the Sieve plugin and the ManageSieve protocol sieve = file:~/sieve;active=~/.dovecot.sieve } -- dovecot backend config -- # dovecot version 2.1.7 protocols = imap pop3 lmtp #sieve # OLDTEMP listen = 192.168.100.95 listen = 192.168.100.101 mail_location = maildir:~/ namespace { prefix = INBOX. separator = . inbox = yes } base_dir = /var/run/dovecot/ login_greeting = Dovecot ready. default_login_user = dovenull default_internal_user = webmail mail_access_groups = mail postmaster_address = postmaster(a)mydomain.net disable_plaintext_auth = no auth_mechanisms = plain login auth_verbose=yes auth_debug=yes auth_debug_passwords=yes mail_debug=yes verbose_ssl=yes auth_verbose_passwords=no #log_path = syslog log_path = /var/log/dovecot.log default_process_limit = 10000 default_client_limit = 50000 mmap_disable = yes mail_fsync = always mail_nfs_storage = no mail_nfs_index = no #mail_plugin_dir = /usr/lib/dovecot mail_plugin_dir = /usr/lib/dovecot/modules # OLDTEMP mail_plugins = $mail_plugins quota fts fts_lucene mail_plugins = $mail_plugins quota fts fts_squat sieve ssl = no # OLDTEMP ssl_cert = </usr/local/dovecot/ssl/dovecot.pem # OLDTEMP ssl_key = </usr/local/dovecot/ssl/dovecot.pem ssl_cert = </etc/ssl/private/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem doveadm_password = somecrypticpassword userdb { driver = ldap # OLDTEMP args = /usr/local/dovecot/etc/dovecot/dovecot-ldap.conf.ext args = /etc/dovecot/dovecot-ldap.conf.ext } passdb { driver = static args = user=%u password=crypticpasswordagain } service imap-login { process_min_avail = 2 service_count = 0 inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { process_min_avail = 2 service_count = 0 inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service imap { process_min_avail = 2 process_limit = 0 executable = imap #imap-postlogin vsz_limit = 384M } service pop3 { process_min_avail = 2 process_limit = 0 executable = pop3 #pop3-postlogin vsz_limit = 384M } service lmtp { inet_listener lmtp { port = 24 } vsz_limit = 384M } service doveadm { inet_listener { port = 9292 } } service director { unix_listener director-admin { mode = 0 } } service quota-warning { executable = script /etc/dovecot/quota-warning.sh unix_listener quota-warning { user = webmail } } protocol imap { mail_plugins = $mail_plugins quota imap_quota mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 } plugin { fts = fts_squat fts_squat = partial=4 full=10 # fts_lucene = whitespace_chars=@. quota = maildir:User quota quota_warning = storage=75%% quota-warning 75 %u quota_warning2 = storage=95%% quota-warning 95 %u } -- managesieve config -- service managesieve-login { executable = managesieve-login director service_count = 0 process_min_avail = 0 vsz_limit = 64M } service managesieve { process_count = 100 } # Service configuration protocol sieve { managesieve_max_line_length = 32768 executable = managesieve-login director mail_max_userip_connections = 5 managesieve_max_compile_errors = 5 }

1 0

[sieve] extracting address behavior changes beetwen 2.2.13 and 2.2.16
by Marcin Mirosław 05 May '15

05 May '15

Hi all! After upgrading dovecot from 2.2.13 to 2.2.16 I noticed that my sieve filters doesn't catch some emails. I used sieve-test with tracing (it's great tool!) and I can see as below: part of sieve filter: [...] elsif address :is "From" "backup(a)areda.pl" { [...] dovecot-2.2.13: 36: address test 36: starting `:is' match with `i;ascii-casemap' comparator: 36: extracting `From' headers from message 36: parsing address header value `=?UTF-8?B?QmFjdWxhQEFUTQ==?= <backup(a)areda.pl>' 36: extracting `all' part from address `backup(a)areda.pl' 36: matching value `backup(a)areda.pl' 36: with key `backup(a)areda.pl' => 1 36: finishing match with result: matched 36: jump if result is false 36: not jumping dovecot-2.2.16: 36: address test 36: starting `:is' match with `i;ascii-casemap' comparator: 36: extracting `From' headers from message 36: parsing address header value `Bacula@ATM <backup(a)areda.pl>' 36: extracting `all' part from address `Bacula@ATM' 36: matching value `Bacula@ATM' 36: with key `backup(a)areda.pl' => 0 36: finishing match with result: not matched 36: jump if result is false 36: jumping to line 43 So in newer dovecot sieve uses comment not exact email address. Did I wrongly wrote my sieve script? Thanks, Marcin.

2 2

Dovecot 2.2.16 doesn't rotate mdbox files
by Басов Евгений 04 May '15

04 May '15

Hello, there's setting in my config file: mail_location = mdbox:/var/vmail/%Ld/%Ln:INDEX=/var/indexes/%Ld/%Ln mdbox_rotate_size = 1M mdbox_preallocate_space = yes mdbox_rotate_interval = 1d As I understand, this settings means that file which contains letters with refcount=0 will be rotated after 23:59 today. I remember letter ID and execute grep whith this one in storage directory. Letter was presented. After that, I removed letter over IMAP protocol, checked and find it again. On the next day check with grep was repeated and letter was finded. After doveadm purge -u user@domain letter was expunged. What's wrong in my configuration?

1 0

Crashes in dovecot -hg (86f535375750)
by Reuben Farrelly 04 May '15

04 May '15

Seems there is some breakage with -hg latest - 2.2.16 (86f535375750+). I've just had 4 core files created in short succession on both servers in the replication set. Here's the first... tornado reuben # gdb /usr/libexec/dovecot/imap core GNU gdb (Gentoo 7.9 vanilla) 7.9 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.gentoo.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/libexec/dovecot/imap...done. [New LWP 20929] warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `dovecot/imap'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f186087693a in fts_user_free (fuser=0x0) at fts-user.c:187 187 fts-user.c: No such file or directory. (gdb) bt full #0 0x00007f186087693a in fts_user_free (fuser=0x0) at fts-user.c:187 user_langp = 0x300000008 #1 0x00007f1860876ac2 in fts_mail_user_deinit (user=0x20a3eb0) at fts-user.c:215 fuser = 0x0 #2 0x00007f185d7890f8 in fts_lucene_mail_user_deinit (user=0x20a3eb0) at fts-lucene-plugin.c:99 fuser = 0x20a5550 #3 0x00007f185d994e0c in replication_user_deinit (user=0x20a3eb0) at replication-plugin.c:310 ruser = 0x20a5500 #4 0x00007f18615b565a in mail_user_unref (_user=0x20abc28) at mail-user.c:168 user = 0x20a3eb0 __FUNCTION__ = "mail_user_unref" #5 0x000000000041afef in client_default_destroy (client=0x20abbb0, reason=0x0) at imap-client.c:284 cmd = 0x7ffde3a18960 __FUNCTION__ = "client_default_destroy" #6 0x000000000041ada0 in client_destroy (client=0x20abbb0, reason=0x0) at imap-client.c:236 No locals. #7 0x000000000041ccf4 in client_input (client=0x20abbb0) at imap-client.c:967 cmd = 0x7ffde3a189a0 output = 0x0 bytes = 12 __FUNCTION__ = "client_input" #8 0x00007f18612fc992 in io_loop_call_io (io=0x20c8610) at ioloop.c:501 ioloop = 0x2076740 t_id = 2 __FUNCTION__ = "io_loop_call_io" #9 0x00007f18612fec40 in io_loop_handler_run_internal (ioloop=0x2076740) at ioloop-epoll.c:220 ctx = 0x2077460 events = 0x2078290 event = 0x2078290 list = 0x2078e80 io = 0x20c8610 tv = {tv_sec = 4, tv_usec = 999387} events_count = 5 msecs = 5000 ret = 1 i = 0 j = 0 call = true __FUNCTION__ = "io_loop_handler_run_internal" #10 0x00007f18612fcb2f in io_loop_handler_run (ioloop=0x2076740) Reuben

2 2

SQLite does not depend on zlib, was: Re: [PATCH] Split sql drivers from lib-sql to plugins
by Bernd Kuhls 04 May '15

04 May '15

Tomas Janousek <tjanouse(a)redhat.com> wrote in news:20070413132731.GA8281 @redhat.com: > - SQL_LIBS="$SQL_LIBS -lsqlite3 -lz" > + SQLITE_LIBS="$SQLITE_LIBS -lsqlite3 -lz" Hi, this patch fixes a build error during cross compilation to a system without the libz target package: --- dovecot-2.2.15.org/configure.ac 2014-10-25 05:57:08.000000000 +0200 +++ dovecot-2.2.15/configure.ac 2014-11-08 10:06:23.015570150 +0100 @@ -2293,7 +2293,7 @@ if test $want_sqlite != no; then AC_CHECK_LIB(sqlite3, sqlite3_open, [ AC_CHECK_HEADER(sqlite3.h, [ - SQLITE_LIBS="$SQLITE_LIBS -lsqlite3 -lz" + SQLITE_LIBS="$SQLITE_LIBS -lsqlite3" AC_DEFINE(HAVE_SQLITE,, Build with SQLite3 support) found_sql_drivers="$found_sql_drivers sqlite" Regards, Bernd

2 2

backup mails from alternate storage
by Lars Täuber 04 May '15

04 May '15

Hi there! It seems that # doveadm backup -v backup -fu $MUSER mdbox:"$BKPDIR/$MUSER/mdbox" doesn't backup all messages stored in alternate storage. mail_location = mdbox:~/mdbox:ALT=/srv/mail/slow/vmail/%n/mdbox I don't know how to debug this. The sizes of the mailboxes in the filesystems of user C are strange: ~/mdbox: # du -sm 2169 ALT: # du -sm 25252 backup: # du -sm 2658 This is with dovecot 2.2.9 on Ubuntu x86_64 14.04.2 LTS. Is this a bug or am I doing something wrong? How can I test if messages stored in the alternate storage are successfully backed up? Thanks Lars

1 1

dsync-local(klink): Error: remote: dsync-server: invalid option -- 'l'
by Mathieu ROY 04 May '15

04 May '15

Hello, Since recently (not sure when), dsync stopped working. dsync -u klink mirror XXXX dsync-local(klink): Error: remote: dsync-server: invalid option -- 'l' dsync-local(klink): Error: remote: doveadm dsync-server [-u <user>|-A] [-S <socket_path>] dsync-local(klink): Error: read() from worker server failed: EOF I did not change anything on my setup but dovecot was upgraded (debian stable). On the box I'm starting the command I have: $ dpkg --list | grep dovecot ii dovecot-common 1:2.1.7-7+deb7u1 all Transitional package for dovecot ii dovecot-core 1:2.1.7-7+deb7u1 amd64 secure mail server that supports mbox, maildir, dbox and mdbox mailboxes ii dovecot-imapd 1:2.1.7-7+deb7u1 amd64 secure IMAP server that supports mbox, maildir, dbox and mdbox mailboxes $ doveconf -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 7.8 mail_location = maildir:~/.Maildir:LAYOUT=fs:INBOX=~/.Maildir/INBOX mail_privileged_group = mail 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 { driver = pam } protocols = " imap" ssl = required ssl_cert = </etc/dovecot/certs/XXX.pem ssl_key = </etc/dovecot/certs/XXX.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } On the destination box, I have: $ dpkg --list | grep dovecot ii dovecot-core 1:2.2.13-11 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 1:2.2.13-11 amd64 secure POP3/IMAP server - IMAP daemon $ doveconf -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.0 ext4 mail_location = maildir:/var/maildir/%u:LAYOUT=fs:INBOX=/var/maildir/%u/INBOX mail_privileged_group = mail 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 { driver = pam } protocols = " imap" ssl = required ssl_cert = </etc/dovecot/certs/XXX.pem ssl_key = </etc/dovecot/certs/XXX.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } What is the is invalid option l ? When did I set this? PS: please add me in CC, I'm not on the list. Cheers, -- http://yeupou.wordpress.com/

1 1

Fatal: Unknown scheme: SHA512-CRYPT. On a Mac-mini
by Robert Chalmers 02 May '15

02 May '15

Running postfix+dovecot+mysql on a mac-mini, and trying to solve this puzzle. Is this a Mac issue?, a MySQL issue? or something I haven't configured in? You can see from the output of the samples shows in the first case, that SHA512-CRYPT seems to be Unknown. The code I used is from a Linux based tutorial on setting up Postfix+Dovecot+MySQL on a site. Everything is generally going ok, apart from this bit. There are some others unknown as well. The codes used to create my database of passwords follows these output examples. MacMini:~ robert$ sudo doveadm pw -s SHA512-CRYPT -p 123456 Fatal: Unknown scheme: SHA512-CRYPT MacMini:~ robert$ sudo doveadm pw -s SHA512 -p 123456 {SHA512}ujJTh2rta8ItSm/1PYQGxq2GQZXtFEq1yHYhtsIztUi66uaVbfNG7IwX9eoQ817jy8UUeX7X3dMUVGTioLq0Ew== MacMini:~ robert$ sudo doveadm pw -s SHA256 -p 123456 {SHA256}jZae727K08KaOmKSgOaGzww/XVqGr/PKEgIMkjrcbJI= MacMini:~ robert$ sudo doveadm pw -s MD5 -p 123456 {MD5}$1$.mAQzPhO$6v/WxTUt.Y1lhopkMarEb0 MacMini:~ robert$ sudo doveadm pw -s MD5-CRYPT -p 123456 {MD5-CRYPT}$1$gNkYwx/o$3nQLmUIPOBmZdR/e/EXFV1 MacMini:~ robert$ sudo doveadm pw -s BLF-CRYPT -p 123456 Fatal: Unknown scheme: BLF-CRYPT MacMini:~ robert$ sudo doveadm pw -s SHA512 -p 1pass66U! {SHA512}EuuO6BAt+bgzXIOw7XIdiVBFwdEZ2tGqHOJ/DSTSkD+ikw7GQQo+KtHSta7p3KNv2AEVKtfOuyl5UeCEqnKogg== MacMini:~ robert$ sudo doveadm pw -s SHA256-CRYPT -p 1pass66U! Fatal: Unknown scheme: SHA256-CRYPT MacMini:~ robert$ mysql --version mysql Ver 14.14 Distrib 5.6.19, for osx10.9 (x86_64) using EditLine wrapper MacMini:~ robert$ cd My MySQL Version: mysql Ver 14.14 Distrib 5.6.19, for osx10.9 (x86_64) using EditLine wrapper The MySQL code used to create the user/password table. Which seems to work fine, and creates the table as it should - even though the resulting password doesn't appear to be quite right for SHA512-CRYPT INSERT INTO `mailserver`.`virtual_users` (`id`, `domain_id`, `password` , `email`) VALUES ('1', '1', ENCRYPT('firstpassword', CONCAT('$6$', SUBSTRING(SHA(RAND()), -16))), 'email1(a)example.com'), ('2', '1', ENCRYPT('secondpassword', CONCAT('$6$', SUBSTRING(SHA(RAND()), -16))), 'email2(a)example.com'); What it actually creates is this: This is not a SHA512-CRYPT password?? mysql> SELECT * FROM mailserver.virtual_users; 3 | 1 | $6jxK9DWPBrAc | robert(a)zeus.example.com Just to be clear,. this is the section of the Dovecot configs that deals with handling this. BUT.. On the MAC-Mini, SHA512-CrYPT is unknown. # List of supported schemes is in # http://wiki2.dovecot.org/Authentication/PasswordSchemes # default_pass_scheme = SHA512-CRYPT So the question is, what Encryption should I be using, and is this an Apple thing, or a MySQL thing?

2 1

Postpone email delivery with LMTP and Postfix
by Miloslav Hůla 01 May '15

01 May '15

Hi, is there any way, based on userdb/passwdb attribute, how to postpone an email delivery? The purpose is, I need to freeze an account (Maildir++) for a few minutes and new email must not be delivered. But emails must be delivered when account is unfrozen. I found few things about Postfix filters, but I'm not sure it's a good way. Thank you, Milo

3 3