- dovecot - dovecot.org

02 Feb '17

Dovecot SNI is failing hard today. Server with n domains, each with a startssl certificate of its own, all certificates expired this morning. Decision: move to Letsencrypt. Firsr certificate issued and installed. Other domains in the pipeline. Dovecot server rebooted. Expected result: one domain returning the new cert, and the n-1 domains returning the expiration notification. Actual result: the domain with LE is returning startssl expired notifications. Manual check of the key and pem files is OK...

1 0

Doveadm option for a non-wildcard single-user with userdb
by Ivan Zahariev 02 Feb '17

02 Feb '17

Hello, Most "doveadm" commands accept "[-A|-u user|-F file]" for user selection, or the environment "USER". I'm testing with "doveadm quota recalc". The problem is that there is no way to ask "doveadm" to work in (1) single-user mode with (2) no wildcard support, and at the same time to (3) make a lookup in "userdb", in order to get the user's specific configuration. We have mailboxes which contain "?" and "*" symbols, and we can't work with them using "doveadm" now. * If we use "-A", this works with all users. Not our case at all. * If we use "-F" and provide just one user in the file, this works for a single user + lookup in "userdb", does not interpret wildcard, but "doveadm" works in a "users list" mode and the output is different. What's more problematic is that errors for an mbox do not end up in "doveadm" exiting with a non-zero exit code. * If we use "-u", this works for a single user + lookup in "userdb", but interprets wildcards. Does not work for mailboxes which contain "?" and "*". * If we use the USER environment, this works for a single users and does not interpret wildcards but does not do a lookup in "userdb". Should we add another user-selection argument, for example "-U", which (1) selects a single-user like "-u", does a "userdb" lookup like "-u" does, but does not interpret wildcards unlike "-u" ? Best regards. --Ivan

1 0

Restoring a deleted imap folder from backup to user Maildir
by Kepa Lyman 02 Feb '17

02 Feb '17

Hi, A user accidentally delete a folder from their Maildir (probably while using Thunderbird). The folder was at Archives/Sent/2015 (/.Archives.Sent.2015 in the Maildir format). I attempted to copy the folder from a tar backup into the Maildir folder but the new folder does not show up in Thunderbird or in the Subscribe option. I also copied the .Archives.Sent. folder as well. A "Sent" folder shows up after this in Thunderbird's Subscribe menu but not the 2015 subfolder. Is there some other additional step(s) to undertake when moving Maildir folders around so they show up in Dovecot (or Thunderbird- though I did try deleting Thunderbird's local mail tmp folder). Re: this message about SELinux on CentOS, SELinux is set to permissive: https://dovecot.org/list/dovecot/2009-January/036257.html Thanks! Kepa

2 1

what do you think about that?
by dovecot 02 Feb '17

02 Feb '17

Dear! I just wanted to show you my last article and to ask your opinion about it, please read it here http://gianluigi.bigshowonline.net/0607 dovecot

1 0

dovecot 2.2.27 welcome plugins script
by Carlos R Laguna 01 Feb '17

01 Feb '17

Hello everyone, I am trying to send a mail to newly autocreated users, using the welcome plugins, however, i am get unable to pipe user information correctly to the script, acording to the wiki the scripts are called just as the quota warnig scripts. Also, every time that a try something new i have created a new user...... is a pain. what can i do to test this without to create a new user after any little change? # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.0-59-generic x86_64 Ubuntu 14.04.5 LTS nfs auth_mechanisms = plain login mail_debug = yes mail_gid = vmail mail_location = maildir:/var/nfsvmail/%d/%Ln/ mail_plugins = " quota welcome" mail_uid = vmail 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.conf.ext driver = ldap } plugin { quota = maildir:User quota quota_grace = 10%% quota_rule = *:storage=2M quota_rule2 = Trash:storage=+1M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 El buzón esta lleno quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u welcome_script = welcome %u welcome_wait = yes } postmaster_address = postmaster(a)cubava.cu protocols = " imap lmtp pop3" inet_listener pop3s { port = 0 } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service welcome { executable = script /usr/local/bin/welcome.sh unix_listener welcome { user = vmail } user = dovecot } ssl_cert = </etc/ssl/certs/mailcubava.pem ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol imap { mail_plugins = " quota welcome imap_quota" } -rwxr-xr-x 1 dovecot vmail 397 Jan 31 16:11 welcome.sh #!/bin/sh USER=$1 cat << EOF | /usr/lib/dovecot/dovecot-lda -d $USER From: postmaster(a)example.com Subject: Welcome Message EOF -- Carlos R Laguna Mendoza Esp. Principal NDC TINORED Joven Club de Computación y Electrónica Tel: 52793189, 7863-3174, 7868-4230

1 0

Vacation Sending To Root
by Shaun Forsyth 31 Jan '17

31 Jan '17

Dovecot Version 2.0.9 I am having an issue where all vacation messages are being sent to root. Is any one able to advise. Dovecot Log Shows :- Sieve: msgid=< CAMD5TViw0sSigGm8JY5WOv0ROs1UdCJFnvb9vo-RzcNN74E92Q(a)mail.xxxxxx.com>: sent vacation response to <root> The emails are handed off to dovecot from sendmail using procmail :0 w | $DELIVER The variable $DELIVER is set as DELIVER="/usr/libexec/dovecot/deliver" I do have DROPPRIVS=YES in procmail, however I don't think deliver works without this. Any advice would greatly help. Shaun

2 2

mail_location in userdb inconsistent with imap and pigeonhole
by Ladislav Laska 31 Jan '17

31 Jan '17

Hi! I'm still fighting with lost mails and what I think is a locking problem. As I've lost some pretty important mails already, I decided to mitigate my troubles by moving to maildir format, which should not be susceptible to these problems. I read the docs and wanted to test on my account, before I mess with all the others and possibly break something. The way to do it seems to be to do an override via userdb. I already have a passwd-file authdb, so I uncommented those few lines in configuration, and added this to my passwd-file: krakonos:{SHA256}xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=:1000:100::/home/krakonos:/bin/bash:userdb_mail=maildir:/home/krakonos/Mail Now, I'm not really sure why it has to be prefixed with userdb_, but the example in docs has it, and it seems to work. I've attached the relevant part of a logfile, with some debugging enabled, but in short: Dec 10 18:39:22 ibex dovecot: imap(krakonos): Debug: Added userdb setting: mail=maildir:/home/krakonos/Mail [...] Dec 10 18:39:22 ibex dovecot: imap(krakonos): Debug: maildir++: root=/home/krakonos/Mail, index=, indexpvt=, control=, inbox=/home/krakonos/Mail, alt= [...] Dec 10 18:39:52 ibex dovecot: lda(krakonos): Debug: mbox: INBOX defaulted to /home/krakonos/.mbox/inbox I'm confused why the last line chooses my old mbox over the new location. I'm even more confused by the fact the IMAP works fine, and as I connect from mutt over imap, I can see empty mailboxes (the ~/Mail has only the basic cur/new/tmp structure). However, pigeonhole delivers into the .mbox, and not only if it's for INBOX, but also for spam and others. I read somewhere in the docs that the order is first try userdb, then mail_location and namespaces override the rest. This might be the problem, as I have: mail_location = mbox:~/.mbox 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 = } Due to inbox=yes this would explain why inbox is using the default path in mail_location. But why even the spam is delivered into the old mbox? And how do I solve the problem anyway, should I just remove the namespace? Anyway, it doesn't explain why the IMAP part and pigeonhole apply different rules and show me different inboxes, which is probably a bug. Thanks! ----------------------------------------------------------------------- Here is the rest of my configuration for reference, the log is attached: ----------------------------------------------------------------------- # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.26-gentoo x86_64 Gentoo Base System release 2.2 auth_username_format = %n hostname = ibex.krakonos.org login_greeting = Dovecot(a)krakonos.org ready. mail_debug = yes mail_location = mbox:~/.mbox mbox_read_locks = dotlock fcntl 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 = * driver = pam } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute sieve_execute_socket_dir = sieve-execute sieve_extensions = +vnd.dovecot.filter +editheader sieve_filter_bin_dir = /usr/lib/dovecot/sieve-filter sieve_filter_socket_dir = sieve-filter sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe sieve_pipe_socket_dir = sieve-pipe sieve_plugins = sieve_extprograms } postmaster_address = postmaster(a)krakonos.org protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } ssl_cert = </etc/ssl/dovecot/server.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol lda { mail_plugins = sieve } -- S pozdravem Ladislav "Krakonoš" Láska http://www.krakonos.org/

2 2

Sieve & Public folders issue (2nd episode)
by dovecot＠avv.solutions 31 Jan '17

31 Jan '17

Hello Community, Getting back to my previous post, here a a complement: - Having enabled sieve, I can store mails and create folder under the recipient - Having enabled public folders, I can move mail into them using a client (eg Thunderbird); security is therefore ok (actually I gave full control to the user) eg Public/Newsletters/SomeCompany - *BUT* running a sieve script to store to Public/Newsletters/SomeCompany returns the following in the logs: "failed to store into mailbox 'Public/Newsletters/SomeCompany': Permission denied." Any tip? Thank you for your help. Greetz

2 1

panic when doveadm sieve put between multiple hosts
by Tyler Jachetta 31 Jan '17

31 Jan '17

Dovecot version: 2.2.25 (7be1766) I’m looking into an issue we’re having with a new setup. We have one fronted host with two backend hosts, and we’re attempting to use doveadm to allow us to administer sieve on the frontend and have it replicated to the backend hosts. When I attempt to use doveadm sieve put on the frontend host, i get the following on the frontend host: frontend-machine $ cat /tmp/default.sieve | doveadm sieve put default doveadm(root): Error: doveadm server disconnected before handshake: Connection reset by peer doveadm(root): Error: 10.1.11.82:10993: Command sieve put failed for root: Connection reset by peer when this happens, on the backend, I see this in /var/log/maillog: Jan 9 17:00:35 was-imap1 dovecot: doveadm: Panic: epoll_ctl(add, 0) failed: Operation not permitted (fd doesn't support epoll - instead of '<file', try 'cat file|') Jan 9 17:00:35 was-imap1 dovecot: doveadm: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x8d52e) [0x7f7a86ba952e] -> /usr/lib64/dovecot/libdovecot.so.0(+0x8d60e) [0x7f7a86ba960e] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f7a86b481b6] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_add+0x147) [0x7f7a86bbe067] -> /usr/lib64/dovecot/libdovecot.so.0(+0xa0311) [0x7f7a86bbc311] -> /usr/lib64/dovecot/libdovecot.so.0(io_add+0xd) [0x7f7a86bbc3bd] -> dovecot/doveadm-server(doveadm_mail_get_input+0xde) [0x7f7a875c53de] -> dovecot/doveadm-server(doveadm_mail_single_user+0x73) [0x7f7a875c5633] -> dovecot/doveadm-server(+0x2874d) [0x7f7a875c574d] -> dovecot/doveadm-server(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x27d) [0x7f7a875c65fd] -> dovecot/doveadm-server(doveadm_cmd_run_ver2+0x50c) [0x7f7a875d492c] -> dovecot/doveadm-server(+0x3b223) [0x7f7a875d8223] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7f7a86bbce8c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xff) [0x7f7a86bbe2ef] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f7a86bbcf15] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f7a86bbd0c8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f7a86b4e613] -> dovecot/doveadm-server(main+0x186) [0x7f7a875b6276] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f7a8677bb15] -> dovecot/doveadm-server(+0x19321) [0x7f7a875b6321] Jan 9 17:00:36 was-imap1 dovecot: doveadm: Fatal: master: service(doveadm): child 28542 killed with signal 6 (core dumped) Now, if I log in to either of the backend hosts, I can run the sieve put command and it all works out fine, so it’s something in the communication between the frontend and backend. dovecot -n output for both a frontend and backend below frontend-machine $ dovecot -n # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.15 (97b3da0) # OS: Linux 3.10.0-327.18.2.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_username_format = %Ln director_mail_servers = 10.1.11.82 10.1.11.83 director_servers = 10.1.11.81 director_username_hash = %Ln doveadm_port = 10993 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl 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 = proxy=y nopassword=y ssl=any-cert driver = static } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap pop3 lmtp sieve service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 1109 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 10993 } } service imap-login { executable = imap-login director } service imap { process_limit = 250 } service ipc { unix_listener ipc { user = dovecot } } service managesieve-login { executable = managesieve-login director } service pop3-login { executable = pop3-login director } ssl = required ssl_ca = </etc/pki/CA/ca-cert-***.pem ssl_cert = </etc/pki/tls/certs/dovecot.cert ssl_client_ca_file = </etc/pki/CA/ca-cert-***.pem ssl_key = </etc/pki/tls/private/dovecot.key ssl_protocols = !SSLv2 !SSLv3 ssl_require_crl = no userdb { driver = passwd } protocol doveadm { auth_socket_path = director-userdb } protocol sieve { passdb { args = proxy=y nopassword=y starttls=any-cert driver = static name = } } local 10.1.11.0/24 { doveadm_password = # hidden, use -P to show it } backend-machine $ dovecot -n # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.15 (97b3da0) # OS: Linux 3.10.0-327.18.2.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_username_format = %Ln default_vsz_limit = 2 G lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_location = maildir:~/Maildir mail_plugins = " notify replication" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl 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 = / } passdb { driver = pam } plugin { mail_replica = tcp:10.1.11.82:10993 sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap pop3 lmtp sieve service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service doveadm { inet_listener { port = 10993 } } service lmtp { inet_listener lmtp { port = 24 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_ca = </etc/pki/CA/ca-cert-***.pem ssl_cert = </etc/pki/tls/certs/dovecot.cert ssl_client_ca_file = </etc/pki/CA/ca-cert-***.pem ssl_key = </etc/pki/tls/private/dovecot.key ssl_protocols = !SSLv2 !SSLv3 ssl_require_crl = no userdb { driver = passwd } protocol lmtp { auth_username_format = %Ln info_log_path = /var/log/dovecot/lmtp.log mail_plugins = " notify replication sieve" postmaster_address = postmaster(a)***global.com } protocol sieve { passdb { args = proxy=y nopassword=y starttls=any-cert driver = static name = } } local 10.1.11.0/24 { doveadm_password = # hidden, use -P to show it }

2 1

dovecot 2.2.18 replication I/O Timeout
by Jan Büren 31 Jan '17

31 Jan '17

Dear list, I am having an issue like this http://www.dovecot.org/list/dovecot-cvs/2014-September/024898.html with my current dovecot 2.2.18 Concret: doveadm -Dv replicator replicate -p high -f info throws an I/O Timeout error and the only thing I can see are some lock issues: Error: Couldn't lock /var/vmail/info/.dovecot-sync.lock: Timed out after 30 seconds Can I debug the communication one level deeper? I replicate over a somewhat slow DSL connection. I had the some problem with dovecot 2.2.9 and after upgrading to 2.2.15 everything went smoothly, just a wild guess, maybe the timeout_reset was removed again? Well, doesn't look like it: https://github.com/dovecot/core/blob/master/src/doveadm/dsync/dsync-ibc-str… or https://github.com/dovecot/core/blame/master/src/doveadm/dsync/dsync-ibc-st… Some debug hints would be nice. Thanks! Jan -- Blog http://blog.kivitendo.de/ kivitendo GmbH Jan Büren Kölnstr. 311 53117 Bonn USt-IdNr. DE292363254 Telefon: 0228 92 98 2012 persönliche Durchwahl: 0228 92 97 8965

1 0