August 2017 - dovecot

Quota-status service on Director
by Michael Kliewe 27 Sep '17

27 Sep '17

Hello, I'm trying to configure the quota-status service, but it seems I'm not successful with my director setup (2.2.9). I activate the quota-status service like this on my director server: $ cat 91-quota-status.conf ## ## Quota-Status configuration. ## # Load Module quota-status and listen on TCP/IP Port for connections. service quota-status { executable = quota-status -p postfix inet_listener { address = 10.0.1.44 port = 12340 } client_limit = 1 } # Plugin configuration. # Return messages for requests by quota status: success, nouser and overquota. plugin { quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is over quota" } After restarting the director service I try to query the quota status service: printf "recipient=user(a)domain.de\nsize=100000\n\n" | nc 10.0.1.44 12340 The output is: action=DEFER_IF_PERMIT Invalid user settings. Refer to server log for more information. In the debug log of the director I see this: Feb 23 03:03:09 director01 dovecot: auth: Debug: userdb out: USER 1 user(a)domain.de mail=mdbox:/mnt/data01/domain.de/user/maildir home=/mnt/data01/domain.de/user proxy=Y master=<hidden> pass=<hidden> uid=5000 gid=1 quota_rule=*:storage=60593 quota_rule2=*:messages=100000 Feb 23 03:03:09 director01 dovecot: quota-status(user(a)domain.de): Error: user user(a)domain.de: Initialization failed: Namespace '': mkdir(/mnt/data01/domain.de/user/maildir/mailboxes) failed: Permission denied (euid=5000(vmail) egid=1(daemon) missing +w perm: /mnt, dir owned by 0:0 mode=0755) So the quota status service tries to access the mailbox of the user ON THE DIRECTOR. But the director has not mounted the mailboxes of the users, that's what the backend dovecots are for (proxy=Y). So the quota-status query is not proxied to the dovecot backend server I would assume. Does that mean I have to start the quota-status service on the dovecot backend servers and access it from the Postfix server directly? Currently the Postfixes can only reach the directors, not the backend servers. Is it possible to use the quota-status service on the director? Thanks for any hints and help Michael

3 4

Per-user quota (passwd)
by Evgeniy Korneechev 11 Sep '17

11 Sep '17

Hello! We have passwd=pam, userdb=passwd. passdb { driver = pam #server was entered domain Active Directory } userdb { driver = passwd override_fields = home=/var/vmail/glu_vrem/%u } How can i use per-user quota? Only passwd-file? I tried: userdb { args = /etc/imap.passwd driver = passwd-file override_fields = home=/var/vmail/glu_vrem/%u } /etc/imap.passwd: administrator:*:95400500:95400513:Administrator:/home/DOM/administrator:/bin/bash::userdb_quota_rule=*:bytes=10G Authentication and quota - now OK. But doesn't work sending and receiving mail... postfix say 'Unknown user'... Is there "extra_field" in passwd-file for email? What generally will be advice on quotas in our case? dovecot -n: # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.39-std-def-alt0.M80P.1 x86_64 ALT 8.1 Server auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 auth_socket_path = /var/run/dovecot/auth-userdb auth_username_chars = auth_verbose = yes auth_verbose_passwords = plain base_dir = /var/run/dovecot/ debug_log_path = /var/log/dovecot disable_plaintext_auth = no first_valid_gid = 502 first_valid_uid = 502 last_valid_gid = 268999999 last_valid_uid = 268999999 log_path = /var/log/dovecot login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_access_groups = vmail mail_debug = yes mail_gid = 502 mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_plugins = " quota autocreate" mail_privileged_group = vmail mail_uid = 502 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 imapflags notify mbox_write_locks = fcntl namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { inbox = yes location = prefix = separator = / type = private } passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota_rule = *:storage=5G recipient_delimiter = + sieve = /etc/dovecot/sieves/default.sieve sieve_default = /etc/dovecot/sieves/default.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags sieve_max_redirects = 8 } protocols = imap pop3 lmtp sieve service auth-worker { user = root } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } } service imap { process_limit = 1024 vsz_limit = 256 M } service lmtp { unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } vsz_limit = 64 M } service pop3-login { inet_listener pop3 { port = 110 } } service pop3 { process_limit = 1024 } ssl_ca = </usr/share/ca-certificates/ca-bundle.crt ssl_cert = </etc/dovecot/server.crt ssl_key = # hidden, use -P to show it userdb { driver = passwd override_fields = home=/var/vmail/glu_vrem/%u } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " quota autocreate sieve" } protocol lda { mail_plugins = " quota autocreate sieve quota" plugin { quota = dict:user::file:/var/vmail/glu_vrem/%n/.quotausage } } protocol imap { mail_plugins = " quota autocreate autocreate imap_quota" plugin { autocreate = INBOX autocreate2 = Sent autocreate3 = Trash autocreate4 = Drafts autocreate5 = Junk autosubscribe = INBOX autosubscribe2 = Sent autosubscribe3 = Trash autosubscribe4 = Drafts autosubscribe5 = Junk quota = dict:user::file:/var/vmail/glu_vrem/%n/.quotausage } } protocol sieve { mail_max_userip_connections = 10 managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } -- WBR, Korneechev Evgeniy BaseALT/ALTLinux Team

2 11

Hide public mailboxes from some users
by Arie Peterson 08 Sep '17

08 Sep '17

Hi all, I'm trying to set up public mailboxes for a subset of my users. This is on dovecot 2.2.27. I've created a new public namespace, and the new mailboxes indeed show up for everyone. So far so good. Now I want to restrict access: these mailboxes shouldn't be visible at all except to a fixed list of users. This part I can't seem to get working. I've added acl data along these lines: ``` pubbox anyone pubbox/* anyone pubbox user=me(a)example.com lrwstipekxa pubbox/* user=me(a)example.com lrwstipekxa ``` However, other users can still see "pubbox" and its subfolders, although they can't actually view the contents. This is corroborated by some of the output of `doveadm mailbox list`: ``` # doveadm -D mailbox list -u other(a)example.com … doveadm(other(a)example.com): Debug: Namespace : type=public, prefix=pubbox/, sep=/, inbox=no, hidden=no, list=children, subscriptions=no … doveadm(other(a)example.com): Debug: Mailbox 'pubbox/Drafts' matches global ACL pattern 'pubbox/*' doveadm(other(a)example.com): Debug: Mailbox 'pubbox/Drafts' matches global ACL pattern 'pubbox/*' doveadm(other(a)example.com): Debug: acl vfile: reading file /mnt/data/mail/example.com/public/pubbox/mail/Drafts/dovecot-acl doveadm(other(a)example.com): Debug: acl: No lookup right to mailbox: pubbox/Drafts doveadm(other(a)example.com): Debug: Mailbox 'pubbox/Sent' matches global ACL pattern 'pubbox/*' doveadm(other(a)example.com): Debug: Mailbox 'pubbox/Sent' matches global ACL pattern 'pubbox/*' doveadm(other(a)example.com): Debug: acl vfile: reading file /mnt/data/mail/example.com/public/pubbox/mail/Sent/dovecot-acl doveadm(other(a)example.com): Debug: acl: No lookup right to mailbox: pubbox/Sent doveadm(other(a)example.com): Debug: Mailbox 'pubbox' matches global ACL pattern 'pubbox' doveadm(other(a)example.com): Debug: Mailbox 'pubbox' matches global ACL pattern 'pubbox' doveadm(other(a)example.com): Debug: acl vfile: reading file /mnt/data/mail/example.com/public/pubbox/mail/dovecot-acl pubbox pubbox/Drafts pubbox/Sent INBOX ``` Why do these "pubbox/*" mailboxes show up in the `mailbox list` output, even though the debug messages say that the user has no lookup right for them? `doveadm acl rights` seems to confirm that `other(a)example.com` does not have the lookup right for these mailboxes. So why do they show up in their email clients anyway? Thanks for any advice!

1 2

v2.2.32 released
by Timo Sirainen 04 Sep '17

04 Sep '17

https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz.sig Two more fixes since rc2. And repeating: There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level line is logged every time when successfully connected to the remote server. This includes local/remote IP/port, which can be useful for matching against external logs. * config: Log a warning if plugin { key=no } is used explicitly. v2.3 will support "no" properly in plugin settings, but for now any value at all for a boolean plugin setting is treated as "yes", even if it's written as explicit "no". This change will now warn that it most likely won't work as intended. + Various optimizations to avoid accessing files/directories when it's not necessary. Especially avoid accessing mail root directories when INDEX directories point to a different filesystem. + mail_location can now include ITERINDEX parameter. This tells Dovecot to perform mailbox listing from the INDEX path instead of from the mail root path. It's mainly useful when the INDEX storage is on a faster storage. + mail_location can now include VOLATILEDIR=<path> parameter. This is used for creating lock files and in future potentially other files that don't need to exist permanently. The path could point to tmpfs for example. This is especially useful to avoid creating lock files to NFS or other remote filesystems. For example: mail_location=sdbox:~/sdbox:VOLATILEDIR=/tmp/volatile/%2.256Nu/%u + mail_location's LISTINDEX=<path> can now contain a full path. This allows storing mailbox list index to a different storage than the rest of the indexes, for example to tmpfs. + mail_location can now include NO-NOSELECT parameter. This automatically deletes any \NoSelect mailboxes that have no children. These mailboxes are sometimes confusing to users. + mail_location can now include BROKENCHAR=<char> parameter. This can be useful with imapc to access mailbox names that aren't valid mUTF-7 charset from remote servers. + If mailbox_list_index_very_dirty_syncs=yes, the list index is no longer refreshed against filesystem when listing mailboxes. This allows the mailbox listing to be done entirely by only reading the mailbox list index. + Added mailbox_list_index_include_inbox setting to control whether INBOX's STATUS information should be cached in the mailbox list index. The default is "no", but it may be useful to change it to "yes", especially if LISTINDEX points to tmpfs. + userdb can return chdir=<path>, which override mail_home for the chdir location. This can be useful to avoid accessing home directory on login. + userdb can return postlogin=<socket> to specify per-user imap/pop3 postlogin socket path. + cassandra: Add support for result paging by adding page_size=<n> parameter to the connect setting. + dsync/imapc, pop3-migration plugin: Strip also trailing tabs from headers when matching mails. This helps with migrations from Zimbra. + imap_logout_format supports now %{appended} and %{autoexpunged} + virtual plugin: Optimize IDLE to use mailbox list index for finding out when something has changed. + Added apparmor plugin. See https://wiki2.dovecot.org/Plugins/Apparmor - virtual plugin: A lot of fixes. In many cases it was also working very inefficiently or even incorrectly. - imap: NOTIFY parameter parsing was incorrectly "fixed" in v2.2.31. It was actually (mostly) working in previous versions, but broken in v2.2.31. - Modseq tracking didn't always work correctly. This could have caused imap unhibernation to fail or IMAP QRESYNC/CONDSTORE extensions to not work perfectly. - mdbox: "Inconsistency in map index" wasn't fixed automatically - dict-ldap: %variable values used in the LDAP filter weren't escaped. - quota=count: quota_warning = -storage=.. was never executed (try #2). v2.2.31 fixed it for -messages, but not for -storage. - imapc: >= 32 kB mail bodies were supposed to be cached for subsequent FETCHes, but weren't. - quota-status service didn't support recipient_delimiter - acl: Don't access dovecot-acl-list files with acl_globals_only=yes - mail_location: If INDEX dir is set, mailbox deletion deletes its childrens' indexes. For example if "box" is deleted, "box/child" index directory was deleted as well (but mails were preserved). - director: v2.2.31 caused rapid reconnection loops to directors that were down.

2 1

Mixed Autehtnication and password schemes
by Raymond Sellars 04 Sep '17

04 Sep '17

Hi Looking for some confirmation/direction on how to achieve the following. We have a requirement to support both SASL PLAIN and DIGEST-MD5 authentication (certification reasons). In addition to this we have an application (webmail) that utilises a master password pattern for access, as the contain web portal provides the necessary authentication. I have access to users passwords in PLAIN text and looking to utilise the dict lookup mechanism for passwords. Problem #1 https://wiki2.dovecot.org/Authentication/MultipleDatabases - "Currently the fallback works only with the PLAIN authentication mechanism." The above not suggests I can't use DIGEST-MD5 with master password configuration, if using more than one passdb setup. I don't understand why there would be a restriction as the password validation should just fall through irrespective. Problem #2 How do I enforce some kind of account access policy Currently we're backing the authentication with an Identity and Authentication system. I would like to block IMAP access if a user's account is locked out, expired, or inactive. Similarly if there are too many IMAP attempts with the incorrect password I would like the account system wide to be locked out. With Dict lookup I don't seem a mechanism to keep the IDM system aware of login attempt/failures, since it pulls the plaintext password and validates internally. Is this possible? As a worse case does Dovecot implement any type of account access policies? Out IT security reviewers are hot on account policies, i.e. lockouts, expiries, and back off attempts. Thanks Raymond Solution Architect - Orion Health

2 4

Pigeonhole 0.4.20 source archive based on v. 0.4.20-rc1?
by Markus Schönhaber 02 Sep '17

02 Sep '17

Hi, looking at the source archive of pigeonhole 0.4.20 <https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.20.t…> I noticed that the contained ChangeLog mentions v0.4.20.rc1 as first entry and pigeonhole-version.h defines git revision 7cd71ba as version where I'd expect 4a55e6c. This is probably no big deal. But since Makefile.in and install-sh also differ (see attached diff) from the patch contained in <http://xi.rename-it.nl/debian.new/pool/jessie-rc-auto/dovecot-2.2/dovecot_2…> I thought I'd ask whether this is something without importance or something which should be changed. -- Regards mks

2 2

Re: General IMAP question
by Joseph Tam 01 Sep '17

01 Sep '17

"Scott Techlist" <techlist06(a)msws.org> writes: > Currently my POP users have a max mbox size but that is how much it > will store before they "come get it". I ensure they have at least one > device set to delete from the server periodically (i.e. 1 week). So > users with multiple devices get their mail duplciated on their devices > and at least one devices keeps the server emptied so their mbox does > not hit any limits. Traditionally, POP was a store and forward protocol. The client would download all the message in INBOX, them empty the mailbox. Nowadays, many POP users configure their clients to "Leave on server mode", which essentially accumulate on the server. The client may or may not also keep a cached copy. > As I understand it, when using IMAP, the user's messages are > perpetually stored on the server. IMAP is oriented as a remote mail service (client fetches and manipulate mail data on a remote server), so yes, messages are meant to remain on the server until deleted. There are probably some clients that cache local copies, but the remote server is considered canonical, so that local copies are deleted if the remote copies disappear. > How do other's deal with this? Am I misunderstanding something? As > popular as it seems to be, these seem like big hurdles to overcome. > Appreciate some help for a IMAP noob. What problem are you trying to solve? Is there a particularly compelling reason for you to move to IMAP (if not, stay with POP3)? You want to curtail space usage by users? You want to force users to retain client side copies of the messages? (Mind you, you'll still could have the same problem with POP -- there's nothing you can do to enforce the client to download/delete messages. Whether you use IMAP or POP3, you'll probably need some client side set up.) Joseph Tam <jtam.home(a)gmail.com>

1 0

RE: Iterate All Dovecot Users !
by Nick Lekkas 31 Aug '17

31 Aug '17

Hi Thomas ! So simple.... But you save my ass ..... And yes it works ! Thanks a lot ! Really ! I appreciate it ! Thanks Nick -----Original Message----- From: Thomas Reifferscheid [mailto:thomas@reifferscheid.org] Sent: Thursday, August 31, 2017 10:49 PM To: nlekkas(a)gmail.com Subject: Re: Iterate All Dovecot Users ! Am 31.08.2017 um 18:18 schrieb Nick Lekkas: > Hello to all ! > > I am trying to write a script that iterate all users that are created in > dovecot and postfix .... > Is there any way ..? > Hi Nick for user in $(doveadm user -u '*'); do echo $user; done Thomas __________ Information from ESET Endpoint Antivirus, version of detection engine 16008 (20170831) __________ The message was checked by ESET Endpoint Antivirus. part000.txt - is OK http://www.eset.com __________ Information from ESET Endpoint Antivirus, version of detection engine 16008 (20170831) __________ The message was checked by ESET Endpoint Antivirus. Email message - is OK http://www.eset.com

1 0

Iterate All Dovecot Users !
by Nick Lekkas 31 Aug '17

31 Aug '17

Hello to all ! I am trying to write a script that iterate all users that are created in dovecot and postfix .... Is there any way ..? Thanks in advance for your time ! Nick __________ Information from ESET Endpoint Antivirus, version of detection engine 16007 (20170831) __________ The message was checked by ESET Endpoint Antivirus. Email message - is OK http://www.eset.com

2 1

General IMAP question
by Scott Techlist 31 Aug '17

31 Aug '17

My server is a limited space mailserver set up to filter spam. Most of it's mail is passed on ot an exchange server so it is not stored locally. I have a handful of pop accounts that are stored locally. For years I've used mbox type mailboxes that I'm familiar with and can access on the server when needed using the old mailx program. They use a variety of clinets, typically Outlook and smartphones. I'm considering changing to IMAP because I need a single IMAP mailbox for an unrelated reason. But I am concerned about user storage issues at least.. Currently my POP users have a max mbox size but that is how much it will store before they "come get it". I ensure they have at least one device set to delete from the server periodically (i.e. 1 week). So users with multiple devices get their mail duplciated on their devices and at least one devices keeps the server emptied so their mbox does not hit any limits. As I understand it, when using IMAP, the user's messages are perpetually stored on the server. So if the user is not moving their messages from their inbox to some other place (e.g. a different Outlook pst file), that all the messages will remain on the server. All messages are "synced" in the user's inbox or other user created folders. Is that right? This would pretty quickly cripple those normal non-computer types that have years of emails in their inboxes. And I don't have the storage space to allow storing years of their mail. I also understand if they exceed their storage limit, mail starts bouncing which is what's I'd expect. At first I started googling how to expire the old mail, but then realized that won't work because if I delete on the server, I understand that will delete on their devices, too. How do other's deal with this? Am I misunderstanding something? As popular as it seems to be, these seem like big hurdles to overcome. Appreciate some help for a IMAP noob. Thanks, Scott

2 1