- dovecot - dovecot.org

[Dovecot] v1.0.12 released
by Timo Sirainen 05 Mar '08

05 Mar '08

http://dovecot.org/releases/1.0/dovecot-1.0.12.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.12.tar.gz.sig - Using mail_privileged_group with dotlock_use_excl=no worked, but it logged "access denied" errors.

2 1

[Dovecot] User Unknown Sendmail Error
by Paul Roberts 05 Mar '08

05 Mar '08

I am totally stumped here. I have setup a dovecot user and I can telnet to port 110 and login no problem with that user. When I try to send mail I get an error from sendmail: Mar 4 13:39:56 flashyhome sendmail[5014]: m24JdtGp005014: <paul(a)fleeky.com>... User unknown Now apparenly I need to setup the sendmail.mc file...which I have: MAILER(smtp)dnl MAILER(procmail)dnl MAILER(dovecot) And: more /usr/share/sendmail-cf/mailer/dovecot.m4 ######################*****############## ### DOVECOT Mailer specification ### ##################*****################## Mdovecot, P=/usr/local/libexec/dovecot/deliver, F=DFMPhnu9, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrFromSMTP, T=DNS/RFC822/X-Unix, A=deliver -d $u If anyone can give me any advice on what I need to do it would be much appreciated. Thanks so much in advance! -Paul

4 4

[Dovecot] different mail_locations
by Antonio Casado Rodríguez 05 Mar '08

05 Mar '08

Hi all I've mounted a cluster ACTIVE-PASIVE, with the mailbox in a SAN. The user's home are: /Correo/mail/foo/home I use: Postfix, dovecot and dovecot_lda. The folder /san/mail is only show in the active node (switch the virtual ip, filesystem and daemons). How i configure dovecot mail_location?? Now i have: mail_location: maildir:/Correo/mail/%n The problem is that the admin mails in pasive node are in enqueued and not arrive. I need a user with mail_location in /var/spool/mail/foo (in aliases, root: foo)and the rest users in /Correo/mail/ I have seen override mail_executable, but it not work with dovecot_lda and postfix (local mailer). I have thinked about: mail_location: maildir:%h/.. Have you any idea? # dovecot -n # 1.0.10: /etc/dovecot.conf log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot.info protocols: imap imaps pop3 managesieve ssl_cert_file: /etc/pki/dovecot/certs/imap.ual.es.crt ssl_key_file: /etc/pki/dovecot/private/imap.ual.es.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login mail_location: maildir:/Correo/mail/%n mail_executable(default): /usr/local/sbin/post-login-imap-dovecot mail_executable(imap): /usr/local/sbin/post-login-imap-dovecot mail_executable(pop3): /usr/local/sbin/post-login-pop3-dovecot mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib64/dovecot/managesieve namespace: type: private separator: / location: maildir:/Correo/mail/%n inbox: yes auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: maildir:storage=1048576

3 5

[Dovecot] dspam+sendmail+virtual users
by Anil 05 Mar '08

05 Mar '08

I want to setup something like this... Sendmail MTA -> DSPAM -> LDA/Dovecot Can someone give me some sendmail.mc configuration examples on how I can set this up? I was having trouble getting sendmail to deliver to dspam and then to dovecot's deliver. Thanks PS: I am not using the IMAP DSPAM integratation libs (yet)... I am using 1.1. When will 1.1 of this come out?

1 0

[Dovecot] multiple namespaces, Mac OS X
by David Koski 05 Mar '08

05 Mar '08

After installing a new server with postfix/dovecot I found that the Mac OS X mail client does not see email in subfolders. It seemed to be related to the namespace. From dovecot.conf: namespace private { separator = . prefix = INBOX. inbox = yes hidden = no } After googling I found that I might need to add a default namespace with an empty prefix so I added this: namespace private { separator = . prefix = inbox = yes hidden = no } Then I was able to access mail in subfolders using the Mac mail client. However, using Kmail I can see both namespaces, where all the folders are listed under the inbox at the same level, and where all folders are listed one level below the inbox. I don't really want to keep my "INBOX." prefix so existing accounts remain unchanged. How do I solve this? The current dovecot.conf is below. Regards, David Koski david(a)kosmosisland.com log_timestamp: %Y-%m-%d %H:%M:%S login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login first_valid_uid: 104 last_valid_uid: 104 mail_extra_groups: mail mail_location: /var/vmail maildir_copy_with_hardlinks: yes mail_plugins: quota imap_quota imap_client_workarounds: outlook-idle delay-newmail namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: mechanisms: PLAIN LOGIN CRAM-MD5 APOP NTLM user: nobody passdb: driver: pam passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: prefetch socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: mail

1 1

[Dovecot] Mercurial repository
by Timo Sirainen 05 Mar '08

05 Mar '08

I removed "dovecot" repository for now. It was almost the same as dovecot-1.1, with the exception that I had forgotten to commit a few things there and also messed up some other commits ("oh, hg export can export multiple changesets at a time, cool. oh, hg import imported it all in one changeset, not cool."). So for now v1.2 code doesn't exist. I'll clone it again from dovecot-1.1 once I have something real to commit. Although I guess that's probably going to be pretty soon.

1 0

[Dovecot] Security issue #5: mail_extra_groups setting is often used insecurely
by Timo Sirainen 05 Mar '08

05 Mar '08

mail_extra_groups=mail setting is often used insecurely to give Dovecot access to create dotlocks to /var/mail directory. If you don't use mboxes in /var/mail, make sure this setting is cleared. If you do use /var/mail mboxes and Dovecot gives permission errors without it, do one of the following (in the preferred order): a) Upgrade to v1.0.11 and use the new mail_privileged_group setting instead of mail_extra_groups. b) Make /var/mail sticky and world-writable (chmod 01777 /var/mail) and clear mail_extra_groups setting. c) Make /var/mail sticky (chmod +t /var/mail) and keep mail_extra_groups setting. This fixes the main problem but some may be left. The mail_privileged_group setting is also available as a patch: http://dovecot.org/patches/1.0/dovecot-1.0.10.mail_priv_groups.diff mail_extra_groups setting has existed since Dovecot v0.99.10.6. It's never been enabled by default in the distributed dovecot-example.conf, but some distributions enable it by default (at least Debian). A longer explanation: The main problem is that if users have filesystem access to the mail server, they can create symlinks. Dovecot doesn't try to prevent following symlinks (and I don't think it should) and normally it isn't a problem. But when mail_extra_groups=mail is set: 1a) Maildir: Any files readable by mail group can be read by the user by symlinking the file to their ~/Maildir/cur/. 1b) Any mbox files readable by mail group can be read by the user by symlinking the mbox file to their ~/mail/ directory. These are pretty obvious problems and I didn't think they were all that important. Why would anyone have secret files that are mail group-readable? But apparently those do exist in some systems (maybe accidentally). 2a) mbox: Any files/directories under mail group-writable directories can be created/deleted/renamed by symlinking the directory under ~/mail/. For example ln -s /var/mail ~/mail/var, DELETE var/root will happily delete root's mailbox. This I hadn't thought about before. 2b) Maildir: Pretty much the same thing can be done with maildir but with a little less control. mail_privileged_group setting works by keeping the group in process's saved GID while it's not in use and temporarily switching it to effective GID while dotlocks are created. Currently this is done only when: 1. It's only done for INBOX mbox which doesn't exist under the same location as other mailboxes (so typically under /var/mail). 2. It's used only after initial dotlock creation try failed with EACCES error.

7 15

[Dovecot] constant mailbox rebuilding with dovecot 1.0.10
by Philip J. Hollenback 04 Mar '08

04 Mar '08

I've recently upgraded to 1.0.10 in hopes that this problem would go away but no luck. I've got some users at my company with large inboxes on maildir (say 22,000 messages). Their mailboxes are hosted on nfs and dovecot is configured to do dotlocking. Still I see messages like this continually in the logs (sometimes every hour or so): server dovecot: IMAP(user): dotlock /home/user/Maildir/dovecot.index.log.lock was immediately recreated under us server dovecot: IMAP(user): file_dotlock_create() failed with file /home/user/Maildir/dovecot.index.log: No such file or directory server dovecot: IMAP(user): Our dotlock file /home/user/Maildir/dovecot-uidlist.lock was overridden (kept it 0 secs) server dovecot: IMAP(user): Duplicate file in uidlist file /home/user/Maildir/dovecot-uidlist: 1162416499.010493.mbox:2,Sa server dovecot: IMAP(user): Maildir /home/user/Maildir sync: UID inserted in the middle of mailbox (48573 > 1, file = 1162416499.010493.mbox:2,Sa) or this: server dovecot: IMAP(user): dotlock /home/user/Maildir/dovecot.index.log.lock was immediately recreated under us server dovecot: IMAP(user): file_dotlock_create() failed with file /home/user/Maildir/dovecot.index.log: No such file or directory server dovecot: IMAP(user): Duplicate file in uidlist file /home/user/Maildir/dovecot-uidlist: 1167674195.83666_2.tandoori.schrodinger.com:2,Sklwv server dovecot: IMAP(user): Maildir /home/user/Maildir sync: UID inserted in the middle of mailbox (34969 > 1, file = 1167674195.83666_2.server.com:2,Sklwv) server dovecot: IMAP(user): Corrupted transaction log file /home/user/Maildir/dovecot.index.log.2: invalid indexid (1204046496 != 1204055346) it seems that every time this sort of thing happens the mail client (thunderbird) sits and rebuilds it's mailbox info for as long as 20-30 minutes, during which time it is unusable. I suspect this happens with other users as well but since they have smaller inboxes they don't notice the long delays. Also this is not linked to version 1.0.10, I've been seeing on and off with the previous version (1.0rc17). Here's the 'dovecot -n' output. I should add that the default is for users to use mbox but some users (like the above one) use maildir via a separate dovecot.passwd file. Server is FreeBSD 4.7. # 1.0.10: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imaps ssl_cert_file: /usr/local/openssl/certs/server.crt ssl_key_file: /usr/local/openssl/private/server.key login_dir: /var/run/dovecot//login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting_capability: yes verbose_proctitle: yes first_valid_uid: 700 last_valid_uid: 9999 first_valid_gid: 100 last_valid_gid: 200 mail_extra_groups: mail default_mail_env: mbox:%h/mail:INBOX=/var/mail/%u mail_location: mbox:%h/mail:INBOX=/var/mail/%u mmap_disable: yes lock_method: dotlock mbox_read_locks: dotlock mbox_write_locks: dotlock imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep auth default: passdb: driver: pam passdb: driver: passwd-file args: /usr/local/etc/dovecot.passwd passdb: driver: passwd userdb: driver: passwd-file args: /usr/local/etc/dovecot.passwd userdb: driver: passwd -- Phil Hollenback hollenba(a)schrodinger.com Schrodinger, Inc.

2 3

[Dovecot] v1.0.11 released
by Timo Sirainen 04 Mar '08

04 Mar '08

http://dovecot.org/releases/1.0/dovecot-1.0.11.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.11.tar.gz.sig * mail_extra_groups setting was commonly used insecurely. This setting is now deprecated. Most users should switch to using mail_privileged_group setting, but if you really need the old functionality use mail_access_groups instead. - mbox: Dropped some of the physical size fetch optimizations added in v1.0.8. This makes some commands slower, but should fix the rest of the problems. - IMAP: SEARCH BEFORE/ON/SINCE didn't handle timezones correctly. - ldap: auth_bind was doing lookups using subtree scope instead of the scope specified in config file. - zlib plugin crashfixes by Richard Platel - master passdbs: pass=yes setting was broken with blocking passdbs (e.g. MySQL)

3 2

[Dovecot] Missing IMAP folders
by Willem Jan Withagen 04 Mar '08

04 Mar '08

Hi, I'm fresh starting to use dovecot. Before this I used bincimap, mainly because it was very simple to config. I've tried to find the FAQ's and tried searching the archives, but little came up. My current config: server FreeBSD i386, postfix 2.4 dovecot 1.0.10 client: windows 2000 thunderbird 2.0.0.12 after some inital config this starts up, and I even have the advantage that I can save in the Sent folder on the server. However I have over 3500 folders and most of them are more than 3 levels deep. And I only get to see the first top level of directories. Searching and/or subscribing does not bring anything. Does somebody have pointers on how to fix this, other than manually trying to recreate al subscriptions. --WjW

2 3