- dovecot - dovecot.org

doveadm expunge no longer works
by Fabian Groffen 31 Dec '15

31 Dec '15

Heya, Just upgraded from 2.2.19 to dovecot-2.2.21 and noticed expunging mail no longer works. # doveadm expunge -u theuser MAILBOX spam all Fatal: expunge: To avoid accidents, each branch in search query must contain something else besides MAILBOX (e.g. just add "all" if you want everything) Clearly, I've already got all in there, so I tried capitalising, etc. Looking at the code, I see expunge_search_args_is_msgset_or_ok apparently is failing. I'm wondering if this function [1] is actually doing what it is supposed to do, since it uses return, instead a var to figure out whether it is ok or not. In my case, just because it finds MAILBOX it returns without looking whether there is any further arguments. Or am I missing the point here (and how should I expunge a folder of mail?) Thanks, Fabian [1] https://github.com/dovecot/core/blob/6971937a6f3e93844dbd43bdbe903628e21a94… -- Fabian Groffen Gentoo on a different level

1 1

sieve-filter to script fails with SHUT_WR
by Mark Stover 31 Dec '15

31 Dec '15

Trying to make vnd.dovecot.filter to exchange an email with my script. (I have a vnd.dovecot.pipe script working, so I'm pretty sure it's not the configuration...) I'm passing the email using stdin/stdout and _not_ using sockets. My script receives the email and processes it, but the filter process fails: lda(<username>): Error: shutdown(/usr/local/lib/dovecot-sieve/sieve-filter/CleanAttachments.py, SHUT_WR) failed: Socket is not connected lda(<username>): Error: sieve: 20-filter-incoming: line 15: filter action: failed to execute to program `CleanAttachments.py' Not sure, what I'm doing wrong... Thanks, Mark $ doveconf -n # 2.2.21 (5345f22): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Darwin 15.2.0 x86_64 lda_mailbox_autocreate = yes mail_location = maildir:~/Maildir maildir_broken_filename_sizes = yes maildir_very_dirty_syncs = yes plugin { sieve = file:~/.dovecot/sieve;active=~/.dovecot/sieve/user.sieve sieve_before = /usr/local/lib/dovecot-sieve/sieve.d/ sieve_execute_bin_dir = /usr/local/lib/dovecot-sieve/sieve-execute sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.filter +vnd.dovecot.debug sieve_filter_bin_dir = /usr/local/lib/dovecot-sieve/sieve-filter sieve_pipe_bin_dir = /usr/local/lib/dovecot-sieve/sieve-pipe sieve_plugins = sieve_extprograms sieve_user_log = ~/.dovecot/sieve/sieve.log } postmaster_address = mstover(a)cisco.com protocol lda { info_log_path = log_path = mail_plugins = " sieve" } Sieve Script: require [ "variables", "envelope", "vnd.dovecot.debug", "vnd.dovecot.filter" ]; if envelope :matches "to" "*" { set "to" "${1}"; } if envelope :matches "from" "*" { set "from" "${1}"; } debug_log "Received message TO=${to} FROM=${from}"; filter "CleanAttachments.py"; debug_log "Returned from CleanAttachments"; if envelope :matches "to" "*" { set "to" "${1}"; } if envelope :matches "from" "*" { set "from" "${1}"; } debug_log "Returned message TO=${to} FROM=${from}";

2 2

LMTP crashes on Debian with dovecot backports from rename-it.nl
by Christian Schmidt 30 Dec '15

30 Dec '15

Hello dovecot-users, we're running Debian 7.9 with dovecot from Stephan Bosch's repository: deb http://xi.rename-it.nl/debian/ oldstable-auto/dovecot-2.2 main Starting with dovecot 2.2.20-1 build 28, we suddenly discovered that some mails (to be locally delivered) "got stuck". dovecot's log revealed messages like the following one: Dec 29 09:56:50 mailhost dovecot: lmtp(MAILRECIPIENT(a)chemie.uni-hamburg.de): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x8360f) [0x7f58fce4f60f] -> /usr/lib/dovecot/libdovecot.so.0(+0x8366e) [0x7f58fce4f66e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f58fcdf8a3e] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x3cc75) [0x7f58fd107c75] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xabeda) [0x7f58fd176eda] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0xba) [0x7f58fd17723a] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_first_header+0x38) [0x7f58fd108cd8] -> /usr/lib/dovecot/modules/lib20_mail_log_plugin.so(+0x1b5c) [0x7f58fb16cb5c] -> /usr/lib/dovecot/modules/lib20_mail_log_plugin.so(+0x22e9) [0x7f58fb16d2e9] -> /usr/lib/dovecot/modules/lib15_notify_plugin.so(notify_contexts_mail_copy+0x46) [0x7f58fb371576] -> /usr/lib/dovecot/modules/lib15_notify_plugin.so(+0x2750) [0x7f58fb372750] -> /usr/lib/dovecot/modules/lib10_quota_plugin.so(+0xbc20) [0x7f58fb580c20] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x7d) [0x7f58fd11305d] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x171) [0x7f58fd4019c1]-> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x11b) [0x7f58fd401dfb] -> dovecot/lmtp [DATA MAILRECIPIENT(a)chemie.uni-hamburg.de](+0x7263) [0x7f58fd831263] -> dovecot/lmtp [DATA MAILRECIPIENT(a)chemie.uni-hamburg.de](+0x79d9) [0x7f58fd8319d9] -> /usr/lib/dovecot /libdovecot.so.0(io_loop_call_io+0x5b) [0x7f58fce6282b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7f58fce63c07] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f58fce628d5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f58fce62a78] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f58fcdfe443] -> dovecot/lmtp [DATA MAILRECIPIENT(a)chemie.uni-hamburg.de](main+0x19c) [0x7f58fd82f8dc] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f58fca5fead] -> dovecot/lmtp [DATA MAILRECIPIENT(a)chemie.uni-hamburg.de](+0x59ad) [0x7f58fd82f9ad] Dec 29 09:56:50 mailhost dovecot: lmtp(MAILRECIPIENT(a)chemie.uni-hamburg.de): Fatal: master: service(lmtp): child 15897 killed with signal 6 (core dumps disabled) Dec 29 09:56:51 mailhost dovecot: lmtp(MAILRECIPIENT(a)chemie.uni-hamburg.de): Panic: file ../../../src/lib/array.h: line 219 (array_idx_i): assertion failed: (idx * array->element_size < array->buffer->used) All dovecot builds newer than 2.2.20-1~auto+26 show the same behaviour. Is there anything we can do? # doveconf -n # 2.2.20 (): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.10 # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.9 ext4 auth_default_realm = chemie.uni-hamburg.de auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_gid = vmail mail_location = maildir:/mail/%d/%n/Maildir mail_plugins = acl mail_log notify quota zlib mail_uid = vmail 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 imapflags notify namespace { list = children location = maildir:/mail/%%d/%%n/Maildir:INDEX=/mail/%d/%n/shared/%%u:CONTROL=/mail/%d/%n/shared/%%u prefix = SHARED/%%u/ separator = / type = shared } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX/ separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/deny-users deny = yes driver = passwd-file } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = maildir:Mailbox-Quota quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve;active=~/.dovecot.sieve sieve_extensions = +notify +imapflags zlib_save = gz zlib_save_level = 6 } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh postmaster_address = postmaster(a)chemie.uni-hamburg.de protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 8 service_count = 0 vsz_limit = 256 M } service imap { executable = imap postlogin process_limit = 1024 vsz_limit = 512 M } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } unix_listener /var/spool/postfix/private/lmtp-dovecot { group = postfix mode = 0660 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { executable = pop3 postlogin } service postlogin { executable = script-login -d rawlog } ssl = required ssl_ca = </ssl/CA.pem ssl_cert = </ssl/cert.pem ssl_key = </ssl/cert.key ssl_protocols = !SSLv2 !SSLv3 syslog_facility = daemon userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_proctitle = yes protocol lmtp { mail_plugins = acl mail_log notify quota zlib sieve } protocol lda { mail_plugins = acl mail_log notify quota zlib sieve } protocol imap { mail_max_userip_connections = 50 mail_plugins = acl mail_log notify quota zlib imap_acl imap_quota imap_zlib } protocol sieve { mail_max_userip_connections = 100 } protocol pop3 { mail_max_userip_connections = 50 } Thanks & kind regards, Christian Schmidt -- No signature available.

3 6

Re: sieve-filter crashes
by kjonca＠o2.pl 29 Dec '15

29 Dec '15

I tried to post earlier, but something goes wrong. KJ kjonca(a)o2.pl (Kamil Jońca) writes: > I want to refilter my mails in inbox so I tried to use: > > sieve-filter -e -W -D -C -v ~/.dovecot.sieve INBOX > > on three messages I got: > > info: filtering: [Fri, 28 Dec 2012 15:40:33 -0500; 14399 bytes] `[SPAM] Keep Defective by Design fight...'. > sieve-filter(kjonca): Panic: file str.c: line 22 (str_new_const): assertion failed: (str[len] == '\0') > sieve-filter(kjonca): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x82462) [0x7f2012002462] -> /usr/lib/dovecot/libdovecot.so.0(+0x824d9) [0x7f20120024d9] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f2011fa9a01] -> /usr/lib/dovecot/libdovecot.so.0(+0xa9098) [0x7f2012029098] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x5f1dc) [0x7f20128211dc] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_match+0xf1) [0x7f2012807721] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x5fa85) [0x7f2012821a85] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0xe7) [0x7f20127fe657] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_run+0x2b) [0x7f20127fe7db] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x4faca) [0x7f2012811aca] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x47) [0x7f2012812637] -> /usr/bin/sieve-filter(main+0x754) [0x7f2012c96d24] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f20119f4b45] -> /usr/bin/sieve-filter(+0x43ca) [0x7f2012c973ca] > > > # 2.2.19 (a9c75e48cf8c): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.9 > # OS: Linux 3.16.0-4-amd64 x86_64 Debian stretch/sid > > KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html A stitch in time saves nine.

3 3

How to apply the patch for disable SSL3 on Dovecot 2.0.9
by Marco 29 Dec '15

29 Dec '15

Hi,I see on Dovecot 2.0.9 is no possibile disable SSL3 Until I wait the panel of my server will look into this issue and maybe put a more updated version, how I can fix this?I found on the Internet http://askubuntu.com/questions/537196/how-do-i-patch-workaround-sslv3-poodl… also link to the patch http://www.mail-archive.com/dovecot@dovecot.org/msg59945.html I don't know what to do for fix the SSL 3 Issue I AM On CentoOs 6.3Thanks.

2 1

Howto get information about quota used
by Макаров Денис 29 Dec '15

29 Dec '15

Hello guys! I have Dovecot server (version: 2.2.9) with quota and imap_quota plugins. I wanna know how to get information about quota used of current email. I can do this with IMAP client like Thunderbird, but how I can do it on server? doveconf -n | grep quota mail_plugins = quota, antispam quota = maildir:User quota_exceeded_message = Message quota_rule = *:storage=100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u service quota-warning { executable = /usr/local/bin/quota-warning.sh mail_plugins = quota imap_quota mail_plugins = quota sieve For each mailboxes I use quota limits from MySQL. -- С уважением, *Макаров Денис* *почта*: makarovdenis11(a)gmail.com <mailto:makarovdenis11@gmail.com> Best regards, *Makarov Denis* *email*: makarovdenis11(a)gmail.com <mailto:makarovdenis11@gmail.com>

2 1

Query regarding migration from Maillenium to Dovecot mail server
by Sirisha R 29 Dec '15

29 Dec '15

Hi, We have few queries regarding dovecot mail server. Our application used to supported maillenium mail server, but soon this server is going to retire. So we are planning to migrate our application mail server to dovecot for which we seek your help. Previously, the mailboxes that our application used to support were under att domain, then the mailboxes were migrated to maillenium mail server, and aliases of the existing att mailboxes were created by maillenium support group, so that any mail sent to the att mailbox automatically gets redirected to maillenium alias mailbox. For instance, for the mailbox abc.att.com, an alias was created as abc(a)maillenium.att.com<mailto:abc@maillenium.att.com>. Maillenium support group provided us mailServerHost, mailServerUsername and mailServerPassword. We seek your help in migrating from Maillenium mail system to Dovecot. Thanks & Regards, R Sirisha This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp

1 0

Sieve: Invalid/unknown path to storage
by Kay-Michael Voit 25 Dec '15

25 Dec '15

Hi, I have just updated from Ubuntu 15.04 to 15.10. Unfortunately, sieve scripts are not recognized anymore. Here is my version: > dovecot --version > 2.2.18 > apt-cache policy dovecot-sieve > dovecot-sieve: > Installed: 1:2.2.18-2ubuntu2 > Candidate: 1:2.2.18-2ubuntu2 > Version table: > *** 1:2.2.18-2ubuntu2 0 > 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages > 100 /var/lib/dpkg/status And this is the log entry: > Dec 25 09:24:12 home-le dovecot: lda(user1): Warning: sieve: file > storage: Active sieve script symlink /home/user1/.dovecot.sieve is > broken: Invalid/unknown path to storage (points to /home/user1/sieve). > Dec 25 09:24:12 home-le dovecot: lda(user1): > msgid=<567CFD2C.7070301(a)example.org>: saved mail to INBOX > Dec 25 09:24:12 home-le postfix/local[28536]: 70876BD035A: > to=<user1(a)example.org>, relay=local, delay=0.07, > delays=0.02/0.01/0/0.04, dsn=2.0.0, status=sent (delivered to command: > /usr/lib/dovecot/deliver -c /etc/dovecot/dovecot.conf -m "${EXTENSION}") It is not a permission issue (though there should even be one with more restrictive permissions) > otheruser@home-le:~$ cat /home/user1/.dovecot.sieve > require ["variables","date", "include"]; > > include :personal "00-delete"; > include :personal "01-spam"; > include :personal "50-bulk_filter"; It is apparently also not a path normalization issue (also according to the correct "points to" path in the log). I used an absolute path in the symlink: > user1@home-le:~$ ls -la .dovecot.sieve > lrwxrwxrwx 1 user1 user1 33 Dec 25 09:23 .dovecot.sieve -> > /home/kay/sieve/managesieve.sieve Any idea what could be wrong here? Here is my dovecot -n output: > 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 = > separator = . > type = private > } > passdb { > driver = pam > } > plugin { > sieve = file:~/.dovecot.sieve > sieve_dir = ~/sieve > } > postmaster_address = postmaster(a)example.net > protocols = " imap sieve" > service managesieve-login { > inet_listener sieve { > port = 4190 > } > } > ssl_ca = </etc/ssl/certs/startssl.ca.pem > ssl_cert = </etc/ssl/certs/net.example.home-le.pem > ssl_key = </etc/ssl/private/net.example.home-le.key > submission_host = 192.168.153.1 > userdb { > driver = passwd > } > protocol lda { > mail_plugins = " sieve" > } > protocol imap { > mail_max_userip_connections = 50 > }

2 2

Debug Dovecot Plugin (shared library)
by David Becher 24 Dec '15

24 Dec '15

Hey! I was just wondering what would be the best way to debug a plugin I am currently writing for dovecot. The plugin basically registers a new IMAP capability and I want to set a breakpoint to the "cmd_handle_new_capability" function (thats just a function name for better explaining purposes). Right now I have opened a connection via openssl ('openssl s_client -connect example:143 -starttls imap') to be able to mess around with the my server. Then I am able to login into the server via 'a login "username" "password"' and feed the server with my self created IMAP capability command. I know that I can start gdb and attach to an already running process via its PID. But how do I know which process I have to attach to? Looking at the output of 'top' it seems to be an instance of the 'imap' command PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 13413 vmail 20 0 21004 1844 1524 S 0.0 0.0 0:00.00 Iman But its only started the exact moment I issue my IMAP command towards the server, so of course I am not fast enough to track down the PID before the function has returned, so the process handling the command seems to be up only for the short period of time to handle the command, there is no process before which I can attach to. My current workaround is that I put a tail onto /var/log/mail.log and from within my shared library function (cmd_handle_new_capability) I log the PID of the current process, then sleep(10) for 10 seconds, which gives me enough time to have a look at mail.log to get to know the PID which I then can attach to. But isn't there a better way to do this? Maybe attach to the process which originally creates the new process handling the IMAP command and then stepping into it? I hope someone can help me out :) All the best, David

2 2

Dovecot 2.2.20 autoexpunge
by Robert Blayzor 23 Dec '15

23 Dec '15

I have configured autoexpunge on some folders: namespace inbox { inbox = yes location = mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 2 weeks special_use = \Trash } prefix = separator = / } After adding these and restarting, logging in and out several times, I still see messages days/weeks past the autoexpunge setting. I checked the logs but never see any autoexpunge messages logged. Is there something else that needs to be set to trigger this? -- Robert inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu

4 6