- dovecot - dovecot.org

[Dovecot] [RFE] A way to encode passwords in the /etc/imap.passwd file
by Răzvan Sandu 03 Feb '10

03 Feb '10

Hello, Is this the proper place to suggest an enhancement for the stock dovecot package ? The enhancement would be the following: For the time being, the dovecotpw utility offers a standardised way to interactively encode a user password in a certain scheme, say: dovecotpw -s CRYPT Enter new passord: Re-enter new password: etc. Given a *valid* /etc/imap.passwd file (passwd-file authentication), dovecotpw should be able to process it non-interactively and output another text file with all {PLAIN} passwords converted in the specified <scheme>, i.e.: dovecotpwd -s CRYPT if=/etc/imap.passwd of=/etc/imap.passwd.converted where /etc/imap.passwd.converted have the previously {PLAIN} passwords converted in scheme CRYPT. Passwords that were previously encrypted in other schemes than {PLAIN} shoud remain untouched. That will allow quick securing of old legacy /etc/imap.passwd files. Thanks a lot, Răzvan

2 1

[Dovecot] [BUG] problem with zlib plugin
by spam＠abma.de 03 Feb '10

03 Feb '10

Hi, i think i've the same problem as described here: http://www.dovecot.org/list/dovecot/2009-June/040687.html when opening a folder without an index (?) and bzip-compressed files i get following error message: 2010-02-03T14:12:10.026452+01:00 server dovecot: IMAP(user): gzread() failed: PARAM_ERROR 2010-02-03T14:12:10.026477+01:00 server dovecot: IMAP(user): FETCH for mailbox folder UID 105 failed to read message input: Invalid argument Matthias -- dovecot -n # 1.2.10: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-vserver-amd64 x86_64 Ubuntu 9.04 listen: *:143 ssl_listen: *:993 ssl_cert_file: /etc/ssl/ssl.crt ssl_key_file: /etc/ssl/ssl.key shutdown_clients: no login_dir: /usr/var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_uid: 97 mail_gid: 97 mail_location: maildir:~/.maildir mail_debug: yes mail_plugins: quota imap_quota zlib lda: postmaster_address: postmaster(a)example.com auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: mail group: mail master: path: /var/run/dovecot/auth-master mode: 384 user: mail group: mail plugin: quota: maildir:User quota quota_rule: *:storage=100M

2 2

[Dovecot] deny=yes in userdb
by Edgar Fuß 03 Feb '10

03 Feb '10

I would like deliver to reject certain users. Since supposedly deliver only uses userdb, not passwd, I can't use deny=yes for that. Or does userdb support deny=yes? Yes, I should rather reject them right in the MTA, but that currently takes too long to implement. Or how to reject gast* in postfix using nss authentication?

3 3

[Dovecot] Restore of individual mail files
by CoolAtt NNA 03 Feb '10

03 Feb '10

Hi. In order for restoration to work fine, I have to create a folder using the interface (e.g RounCube) which also creates the required structures. Then I copied the emailfile e.g xyz:s to /myrestoredemail/cur/ How do i properly create a folder with its structures(index,etc) without using the RoundCube web inteface ? Thanks CoolAtt _________________________________________________________________ Hotmail: Trusted email with powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969

2 3

[Dovecot] disabling mail delivery for a user
by Frank Cusack 02 Feb '10

02 Feb '10

How can I disable mail delivery for a user yet still allow access to their mailbox from another account which their mail is shared to? If I put them in a userdb which has "deny = yes" that just disables their ability to login, yes? And they would still have mail delivered. I want to disable their ability to login AND bounce all mail delivered to them, preferably solely through dovecot configuration. I am using lda, obviously, for mail delivery. (I could configure the MTA to reject mail for them if there is no other option.)

4 13

[Dovecot] v2.0.beta2 released
by Timo Sirainen 02 Feb '10

02 Feb '10

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta2.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta2.tar.gz.sig I tried to keep the configuration and APIs compatible with v2.0.beta1, but unfortunately there were a few things that really had to be changed: 1. passdbs and userdbs have now a separate "driver" setting inside them. So for example if you had: userdb passwd { } You'll now need to use instead: userdb { driver = passwd } 2. Services now have default inet_listeners. You need to either remove your existing ones, or override the defaults by giving the listeners's name like shown in the new example master.conf. For example if you had: service imap-login { inet_listener { port = 1234 .. change it to: service imap-login { inet_listener imap { port = 1234 If you want to disable a default listener, you can set its port to 0. Some new features: - Added auth_verbose_passwords = no|plain|sha1. If authentication fails, this setting logs the used password. If you don't really need to know what the password itself was, but are more interested in knowing if the user is simply trying to use the wrong password every single time or if it's a brute force attack, you can set this to "sha1" and only the SHA1 of the password is logged. That's enough to know if the password is same or different between login attempts. - lazy-expunge: Support a single-namespace configuration. In this setup if mailbox has some expunged messages and then the whole mailbox gets deleted, they get merged into the same deleted mailbox. - protocol !imap { .. } adds configuration to all protocols except imap. - imap/pop3 proxying supports now async DNS lookups for hosts. There's a separate dns-client service doing the lookups using OS's own blocking resolver. - dovecot-config file changed in a way that it'll be easier to create external software linking against dovecot libraries. This made Pigeonhole's configure script a lot simpler. And of course there have been lots of fixes.

3 4

[Dovecot] proxy_maybe regex
by David Halik 02 Feb '10

02 Feb '10

Does anyone know if dovecot support regex lookups for proxy/proxy_maybe, rather than mysql/ldap etc? I've been comparing it with perdition to see which one might be better for us to do layer7 username switching. Perdition supports the ability to not have any auth/db looks, but rather just a regex file that parses the usernames as they come in and forwards to the particular machine on the same port. For example: username:host ^[a-d]: 192.168.xxx.1 ^[e-k]: 192.168.xxx.2 and so on... I didn't think this was supported in dovecot, but I wanted to check first. I think this is going to end up being what we use to avoid NFS problems. It's lightweight, drops into our current setup, and doesn't require a mysql database which adds another point of failure. -- ================================ David Halik System Administrator OIT-CSS Rutgers University dhalik(a)jla.rutgers.edu ================================

3 6

[Dovecot] Want to have some users with Maildir, some with mbox
by Stewart Dean 02 Feb '10

02 Feb '10

Want to have some users with Maildir, some with mbox, as I migrate from mbox format to maildir over the space of a month. After everyone is converted to maildir, I'll change the mail_location in dovecot.conf. During the interim, can I use the Custom mailbox location script (at the bottom of the Mail Location DC Wiki page)? > if [ -d $HOME/.maildir ]; then > export MAIL=maildir:$HOME/.maildir > else > export MAIL=mbox:$HOME/mail:INBOX=/var/mail/$USER > fi > Questions: 1) What does explicitly specifying MAIL this way override? The dovecot.conf mail_location variable? 2) My mail_location var is defined as: mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u and my prospective maildir INBOX and mail folder root is to be ~/Maildir. So would I change the above to: > if [ -d $HOME/Maildir ]; then > export MAIL=maildir:$HOME/Maildir:INDEX=/var/dcindx/$USER > else > export MAIL=mbox:$HOME/mail:INBOX=/var/spool/mail/$USER: > INDEX=/var/dcindx/$USER > fi Question 3: When converting existing users from mbox to maildir, should I delete the index contents? Thanks in advance! dovecot -n output # 1.2.8: /usr/local/etc/dovecot.conf # OS: AIX 3 0001378F4C00 listen: *:143 ssl_listen: *:993 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 774 max_mail_processes: 1280 mail_max_userip_connections: 12 verbose_proctitle: yes first_valid_uid: 200 mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u mbox_write_locks: fcntl mbox_dirty_syncs: no lda: postmaster_address: postmaster(a)example.com auth default: passdb: driver: pam userdb: driver: passwd -- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 9

[Dovecot] index location
by Dave Brenner 01 Feb '10

01 Feb '10

Greetings. We are testing with 1.2.9 and have found that with mail_full_filesystem_access set to 'yes', we cannot force indexes for folders under ~/mail to be stored in /var/dovecot/indexes/%u. /var/dovecot/indexes/%u/.imap/INBOX/dovecot.index* is created just fine, but everything else ends up in ~mail/.imap. If I change mail_full_filesystem_access to 'no', then all indexes are created in the expected location: $ ls -la /var/dovecot/indexes/blitz/ total 4 drwxr-xr-x 4 blitz popuser 512 Jan 25 11:46 . drwxrwxr-x 5 root popuser 512 Jan 22 16:16 .. drwxr-xr-x 3 blitz popuser 512 Jan 22 16:16 .imap drwxr-xr-x 3 blitz popuser 512 Jan 25 11:46 mail (I probably need to set the sticky bit for this, but for testing this is OK) We are setting the index location from /etc/passwd-dove: blitz:x:14267:500::/usr/users/dialups/blitz::userdb_mail=mbox:~/:INBOX=/var/mail/%u:INDEX=/var/dovecot/indexes/%u Is there a way to get this to function the way we'd like, with all indexes stored in /var/dovecot/indexes/u% ? My apologies if I missed an explanation about this in the list archive. Dave

2 9

[Dovecot] Extraneous information
by Michael M. Slusarz 01 Feb '10

01 Feb '10

Not technically a bug, but a small waste of bandwidth: it seems (at least as of 1.2.10) that if neither CONDSTORE/QRESYNC are enabled dovecot still sends HIGHESTMODSEQ info: a examine Testing.AAA * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $Forwarded impflag0 impflag1 impflag2) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 309 EXISTS * 0 RECENT * OK [UNSEEN 5] First unseen. * OK [UIDVALIDITY 1225053009] UIDs valid * OK [UIDNEXT 387] Predicted next UID * OK [HIGHESTMODSEQ 136] Highest a OK [READ-ONLY] Select completed. I'm guessing this would only happen if using a client that supports QRESYNC (like IMP) and then switching later to a client that doesn't support.

2 2