- dovecot - dovecot.org

RFC: HTTP based storage API
by Nagy, Attila 09 Feb '16

09 Feb '16

Hi, Nearly every popular programming language has an LMTP/POP/IMAP implementation, most of them suck in many different ways. I don't know any server or library which provides a well-established, compatible protocol frontend with an open backend API, which could be used to easily make a custom storage backend for the LMTP/POP/IMAP frontend in any language, in any programming paradigm, irregardless of the frontend implementation. Dovecot is very close to this: it speaks IMAP to the backend, but you still have to make a nearly complete IMAP implementation, which is a PITA. Therefore I am curious about your opinion: what about an HTTP-based open backend (lib-storage) API to Dovecot? Some thoughts on this: 1. it should be a simple REST API 2. it should support efficient operations on both sides (client, server), for example listing a multi-million folder shouldn't be a single JSON response, but a JSON stream, which could be produced and parsed individually or in smaller batches efficiently 3. it should support capabilities, somewhat like the current imapc backend, so if the backend service suppports search, it should announce this capability and dovecot could offload these requests to it, but if it doesn't, dovecot could build its indices. 4. only the needed amount of POP/IMAP legacy should appear in the protocol 5. the operations should be asynchronous on Dovecot's side (to be scalable) 6. maybe even Dovecot's index-queries could be offloaded to the backend service (this way the local file system wouldn't be used at all and all caches could be stored in a distributed dictionary), this could also be a capability 7. it could support some kind of push (for IDLE-ing and the like) 8. it should be stateless If Dovecot could make this right, it could be the FUSE of the mail protocols, acting as a glue for experimental or production ready mail storage backends, without the need to write these backends in "Dovecot C" (I mean it's process and API structure). Of course HTTP here is not a strict requirement. It could be anything, which can be easy to implement and understand and is able to fulfill the needs. An example could be Dovecot's own dictionary protocol. What do you think about this?

4 10

autoexpunge - different settings for different users
by Tom Johnson 09 Feb '16

09 Feb '16

I have some users where I'd like to expunge their mail at different times. For example, I may have some users who I want to expunge everything from every folder at 30 days. Others where I'd like to expunge everything at 90 days. And still others where I only want to expunge mail from the Trash and Junk folders, and nowhere else. Is there a way to do some sort of lookup for this? Or is this beyond the ability of the autoexpunge feature? Should I just use a cron job and use "doveadm expunge" on a user-by-user basis? Thanks-

5 9

Dovecot with pam authentication and user@domain
by Christian Schneider 08 Feb '16

08 Feb '16

Hello all, I'm trying to setup dovecot for local users with pam authentication. The passdb and userdb entries are as follows: passdb { args = username_format=%n driver = pam } userdb { args = username_format=%n driver = passwd } Using "doveadm user chriss" returns the user record as expected, but "doveadm user chriss(a)testmail.ch-sc.de" gives an error: field valueuserdb lookup: user chriss(a)testmail.ch-sc.de doesn't exist As far as I understand, username_format=%n should drop the domain part and only search for the user in the userdb, but it doesn't. What am I missing? Greetings Christian

1 1

Permissions issue with Debian 8, dovecot 2.21, vpopmail
by Stephen 08 Feb '16

08 Feb '16

There is a permissions issue in dovecot 2.21 in the ~/run directory (mine is /var/run/dovecot) at least in Debian 8. Files created by dovecot imap: srw------- 1 root root 0 Feb 3 16:46 imap-hibernate srw------- 1 root root 0 Feb 3 16:46 imap-master changed to make work: srw-rw-rw- 1 root root 0 Feb 3 16:46 imap-hibernate srw-rw-rw- 1 root root 0 Feb 3 16:46 imap-master Errors were reported in /var/log/dovecot.log which we use mainly for fail2ban (it gets huge, but ...) vpopmail version 5.4.33 with one patch I don't think this is a Debian issue ... possibly could be a vpopmail issue, but it's probably caused by the fact that imap daemons are running as vpopmail: vpopmail 30182 9187 0 15:02 ? 00:00:00 dovecot/imap

2 1

Released Pigeonhole v0.4.12 for Dovecot v2.2.21
by Stephan Bosch 08 Feb '16

08 Feb '16

Hello Dovecot users, Here is the final v0.4.12 release of Pigeonhole for Dovecot v2.2.21. Nothing changed since the RC. 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/dovecot-2.2-pigeonhole-0.4.12.ta… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.12.ta… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

2 3

"mail_shared_explicit_inbox = no", but shared INBOX has a "\Noselect" tag?
by Rudolf Körner 08 Feb '16

08 Feb '16

Regarding the given information, it seems to me that the option "mail_shared_explicit_inbox=no" does not work as expected. Quote from NEWS-2.2: mail_shared_explicit_inbox setting to specify if a shared INBOX should be accessible as "shared/$user" or "shared/$user/INBOX" Using Dovecot 2.2.13 and Maildir++ Working on the commandline: # doveconf mail_shared_explicit_inbox mail_shared_explicit_inbox = no # service dovecot restart # ls -lda /mail/reader/Shared/owner(a)example.com/.* Shows no (hidden) folders. # telnet 127.0.0.1 143 a0 login reader(a)example.com *** a1 list "" "Shared/owner(a)example.com" * LIST (\Noselect \HasChildren) "/" Shared/owner(a)example.com a1 OK List completed. Is the retrieved "\Noselect" tag correct with the option "mail_shared_explicit_inbox = no"? I would expect the folder "Shared/owner(a)example.com" to be "selectable", because I thought the option "mail_shared_explicit_inbox = no" would make e-mails of a shared INBOX visible directly at the folder "Shared/owner(a)example.com" (which does not work in my case). Note: Shared *sub*folders of an INBOX work as expected. Just to show that the shared INBOX is accessible (note that it is not shown by a list "" "*" here, which is expected with that option): a2 list "" "Shared/owner(a)example.com/INBOX" a2 OK List completed. a3 select Shared/owner(a)example.com/INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 27 EXISTS Using "mail_shared_explicit_inbox = yes" does show the INBOX as a subfolder of "Shared/owner(a)example.com" and allows accessing the e-mails of the shared INBOX. However, it would be nice (and keep users happy at using their known shared folder layout) to see the e-mails of the shared INBOX at the Shared/owner(a)example.com folder. Best Regards, R.Koerner output of (removed irrelevant things like auth,pop,passdb,userdb,ssl,debug) # dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf mail_location = maildir:~/Maildir mail_log_prefix = "%Us(%u): " mail_plugins = acl listescape namespace { hidden = no ignore_on_failure = no inbox = no list = children location = maildir:%%h/Maildir:INDEX=%h/Shared/%%u:CONTROL=%h/Shared/%%u:INDEXPVT=%h/Shared/%%u prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } 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 = INBOX/ separator = / subscriptions = yes type = private } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename } protocols = imap lmtp protocol imap { mail_plugins = acl listescape imap_acl }

1 1

ACL user
by Peter Chiochetti 08 Feb '16

08 Feb '16

How would I go, If I wanted ACL processing to start with %{auth_user} instead of %{user} when determining rights? -- peter

2 2

Send Dovecot logs to rsyslog
by Nicolas Fo 08 Feb '16

08 Feb '16

Hello, I'm trying to send Dovecot logs to a Graylog server. To do this, I'd like to pass logs to rsyslog and rsyslog pass logs to remote Graylog server. I set in dovecot.conf : syslog_facility = local5.info I set in rsyslog.conf : local5.info @192.168.xxx.xxx:5555 Restarted services and it doesn't work. I use nmap to test if port 5555 is opened and this port is open. What missed I ? Thanks Nicolas

4 7

Dovecot (LDAP) quota only if user in backend?
by Andrey Fesenko 08 Feb '16

08 Feb '16

Hello, Is it possible to get the quotas for users served by the backend? My env CentOS, dovecot-2.2.10-5.el7, users in LDAP dn: uid=user,ou=mailboxs,dc=wibble,dc=net cn: Account for server mail sn: User objectClass: top objectClass: person objectClass: posixAccount objectClass: VirtualMailAccount objectClass: Proxying uid: user gidNumber: 3000 uidNumber: 3000 userPassword: {SSHA} homeDirectory: user mailQuota: 1073741824 mailDirectory: maildir:~/Maildir Proxy: yes BackendHost: backend1.wibble.net starttlsProxying: any-cert BackendHost may bee backend1.wibble.net backend2.wibble.net ... if I'm get quota in backend1.wibble.net doveadm -f tab quota get -A If use standart /etc/dovecot/dovecot-ldap.conf user_filter = (&(objectClass=posixAccount)(uid=%u)), dovecot create blank mailboxes for all users, not only BackendHost: backend1.wibble.net If modify (&(objectClass=posixAccount)(uid=%u)(BackendHost=backend1.wibble.net)) doveadm -f tab quota get -u user work fine doveadm -f tab quota get -A doveadm(user1): Info: User no longer exists, skipping doveadm(user2): Info: User no longer exists, skipping doveadm(user3): Info: User no longer exists, skipping ... doveadm: Error: Failed to iterate through some users work for all dovecot user, and crash

1 1

simple bind + X.509 client certificate?
by Heiko Schlittermann 05 Feb '16

05 Feb '16

Hi, using dovecot 2.2.9. The LDAP server requests a client certificate from dovecot. This client certificate will not be used for authentication, but anyway, the server requests it. No SASL is involved. ldapsearch and Exim work as expected, sending the client cert. The slapd is configured: olcTLSVerifyClient: demand For authentication simple bind should be used. Dovecot doesn't seem to send the requested client certificate. If I sniff the connection, the "Certificate" sent to the server is empty. Using ldapsearch it works (and the certificate isn't empty). Any suggestions? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

1 1