April 2010 - dovecot - dovecot.org

[Dovecot] ACLs and public folders
by hyperbatus＠gmx.de 07 May '10

07 May '10

Dear list, I am using dovecot 1.0.15 on Debian Lenny. I have a public folder, I use ACL / vfile (without public ACL), and I use maildir / vmail. Now I have two questions: 1) http://wiki.dovecot.org/ACL states: "Mailboxes in public namespaces don't have owners, so by default no-one can access them." The same document, when explaining the meaning of the k flag in the ACLs, states: "Mailboxes can be created (or renamed) under this mailbox (there is no recursion, so creating a mailbox under this mailbox's child uses only the child's ACLs)" I have placed an ACL (dovecot-ACL) at the root of the public namespace (all rights to anyone). The public namespace was appearing correctly in my IMAP client. Then I have copied a large folder with hundreds of nested subfolders (nesting level > 3) from another account to the root of the public namespace. According to the documentation mentioned above, this should not have been possible (if I got the docs right): The first nesting level of folder should have been created, but not the messages in them and for sure not the deeper nested folders. There is no dovecot-acl within a single of the first level folders (I have verified this), so no one should have access to them. Nevertheless, in addition to the succesful copy, I can see every folder and every message in my IMAP client, I can delete and so on. Could some please explain if I got the docs wrong? 2) If there really is no ACL recursion, how are we supposed to copy large folder structures (perhaps thousands of folders, nested to 5 levels deep) to a public namespace? Do we need to create all folders by hand, then place the dovecot-acl in each folder, and then copy the messages to each folder by hand? Do we need to switch to global ACLs so that we can establish a master user for doing the act of filling the public space? Or is there a dovecot module which, immediately after creating a folder, looks into the parent folder of the new folder and copies the dovecot-acl from the parent folder to the new folder? Currently, I am very happy that dovecot didn't what it should do according to my understanding of the documentation (since I really needed to copy this folder structure to the public namespace), but on the other hand, I am a bit puzzled now not knowing if the documentation is wrong, my understanding of it is wrong or the source code is wrong :-) Thanks you very much for any help, Peter Here is the output of dovecot -n: # 1.0.15: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps listen: 192.168.20.23 ssl_cert_file: /etc/dovecot/imap-ssl.home.omeganet.de.crt ssl_key_file: /etc/dovecot/imap-ssl.home.omeganet.de.key ssl_parameters_regenerate: 24 ssl_cipher_list: ALL:!LOW login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_processes_count: 1 login_max_processes_count: 32 max_mail_processes: 32 mail_privileged_group: mail mail_location: maildir:~/Maildir mail_cache_fields: mail_never_cache_fields: mail_plugins: acl namespace: type: private inbox: yes namespace: type: public prefix: Archive. location: maildir:/home/vmail/archive:INDEX=~/Maildir/archive auth default: cache_size: 1 cache_ttl: 600 worker_max_count: 4 passdb: driver: passwd-file args: /etc/dovecot/passdb userdb: driver: static args: uid=vmail gid=vmail home=/home/vmail/%u socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: root plugin: acl: vfile -- GMX DSL: Internet, Telefon und Entertainment für nur 19,99 EUR/mtl.! http://portal.gmx.net/de/go/dsl02

2 2

[Dovecot] adding users to passwd-file
by Phil Howard 06 May '10

06 May '10

Is there a tool equivalent to the system "passwd" command (or maybe "adduser" or "useradd") that can support a passwd-file by setting a password, encrypting it with the salted MD5 scheme? The system "passwd" command doesn't have an option to "do it to this alternate file instead of /etc/shadow".

4 5

[Dovecot] Expire plugin
by Thomas M Goerger 05 May '10

05 May '10

Hi, I'm testing out the dovecot expire plugin, and not seeing anything go into the database I've got set up. It's a mysql db. I've gone in and verified that the db is set up correctly. The socket is set up so that deliver should be able to talk to the db, but I'm not seeing anything in the expires table when I look. Is there anywhere that expire can log to so I can see what might be happening? It doesn't look like it logs to the dovecot log. Thanks! ************************************************************************* * Tom Goerger - Email/Unix System Administrator * * * * University of Minnesota Email: tmg(a)umn.edu * * Operations, Infrastructure and Architecture Phone: 4-5804 * * Internet Services Office: 626J WBOB * * * *************************************************************************

2 6

[Dovecot] CDB Authentication database
by Luca Corti 04 May '10

04 May '10

Hello, I'd be interested in seeing a CDB based backend for the userdb/passdb lookups. Is anyone working on this? Is there any documentation (other than the wiki Design section and the code itself) on implementing database backends? thanks Luca

5 5

[Dovecot] dovecot user
by Timo Sirainen 04 May '10

04 May '10

Any thoughts on this: The primary use for "dovecot" user has been for login processes. But people keep misunderstanding this and try to use dovecot for accessing mails. For years I've been wondering about renaming this user to something else like dovelogin, but it never really seemed practical. So now with v2.0 there are a bunch of new processes, and for example anvil and dict are now run as dovecot user by default. But it's not really good that login processes can just go and kill those processes. And even worse, if drop_priv_before_exec=yes they could ptrace these processes. So I think we need two Dovecot users for v2.0: 1. Completely untrusted user for login processes. 2. Slightly more trusted internal Dovecot user. So "dovecot" could be reused for 2. And it would no longer be a mortal sin to use dovecot user for owning mail files. For 1. there would be a new user. I'd use "dovelogin", but apparently tools still don't much like usernames that are longer than 8 characters. Like ps could show numeric uid instead of 9 character long username. So .. any suggestions? "dovlogin" could be one possibility I guess. It would be nice if the name somehow reminded of login processes, but maybe something else could be used too, like: dovenil, dovenull, dovezero, dovenone, dovevoid, doveint, dovedown, dovein, dove0

17 33

[Dovecot] zlib Plugin Dovecot 2.0 - ostream
by Alex Baule 03 May '10

03 May '10

Hello Everyone... In zlib save mail have it: struct ostream *output; There is a way to get the file descriptor from output used in ostream zlib plugin ? to get in istream is i_stream_get_fd, but don't have o_stream_get_fd......

2 6

[Dovecot] [SUGGESTION] Managesieve: Transparent home dir creation
by Felix Leimbach 03 May '10

03 May '10

Hi all, I'm using dovecot 2.0-beta4's sieve plugin and it works great but here is an idea for improvement: When creating the first sieve script for an account whose home dir does not yet exist then dovecot *does* create that homedir but the sieve client times out. Tried Thunderbird's sieve addon as well as horde's ingo. The log says: dovecot: managesieve-login: Login: user=<me(a)example.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: managesieve(me(a)example.com): sieve-storage: sieve_storage_verify_dir(/mnt/data/vmail/dovecot-homedirs/example.com/me//s… failed: File exists dovecot: managesieve(me(a)example.com): Fatal: Failed to open Sieve storage. Because the homedir was created (great!) when I retry the same action then all works perfectly well. So why not make that homedir creation transparent so that the clients' first try succeeds instead of the second try? Cheers, Felix

3 3

[Dovecot] What causes dovecot to rebuild dovecot-uidlist?
by Pat 02 May '10

02 May '10

Hello, In what situations will Dovecot 1.2.11 rebuild its uidlist? I am using the maildir storage format, and I am also modifying the uidlist manually (so it's possible I could jack* things up). I have found some related code in maildir-uidlist.c: maildir_uidlist_next. 1) Blank filename or UID 0 2) Any UID not being greater than the proceeding UID 3) Any UID being greater than ~4 billion. 4) Any UID being greater than the suggested next uid. 6) If a filename contains a / 7) General header line sanity checking. Are there any other sections of the code that do sanity checks on dovecot-uidlist (for Maildir type storage)? And optionally do you agree that maildir_uidlist_set_corrupted is the best place to watch to see if I have mangled the uidlist? Thanks in advance, Pat * I insert into dovecot-uidlist manually when I deliver new messages, or discover a message that is not in uidlist for some reason. For compatability reasons I maintain a completely separate cache. If there is a better way to keep the uidlist up to date when the user isn't necessarily accessing the account via dovecot imap, I'm open to suggestions. However my situation is fairly unique I think.

2 2

[Dovecot] zlib Plugin Dovecot 2.0 - ostream
by Alex Baule 30 Apr '10

30 Apr '10

Hello Everyone. There is possible to rename the email saved by a plugin, like zlib ? i explain.... i need to add 1 line in email header, because of that, i want to rewrite the filename to update the S and W flag. Tks !

1 0

[Dovecot] 1.0.15 --> 1.2.11 --> got too little data
by Andre Hübner 30 Apr '10

30 Apr '10

Hello, did updates from 1.0.15 to 1.2.11 and is in most cases succesful. Sometimes dovecot leaves errormessage in Log: IMAP(username): FETCH [HEADER] for mailbox INBOX UID 5106 got too little data (copying): 516 vs 528 Until now only Inbox was effected and no other folders. I delete cachesfiles in ~mail/.imap to solve this but is there a way to do this automatical (self healing)? Dovecot could recreate complete caches if there was a difference in calculation. Thanks, Andre

2 6