January 2008 - dovecot

[Dovecot] Logging to stderr
by Abhijit Hoskeri 10 Jan '08

10 Jan '08

Hi, I am having a bit of a problem with logging to stderr. I am trying to run dovecot as sort of "inetd" install using daemontools. I have daemontools 'services' named dovecot-pop3, dovecot-imap, etc. The service command line looks like tcpsvd -c20 -v -l 0 0 110 /usr/lib/dovecot/pop3-login [--ssl] In dovecot/dovecot.conf, the log_path is set to /dev/stderr. What seems to be happening is that all the log lines (regardless of service) go to the log file of which ever service was first used. Exactly how are these logs written? Is it possible to (easily) make the login process write to its own stderr? Thanks, -Abhijit

2 1

[Dovecot] Trash plugin in 1.0.x
by Ralf Hildebrandt 10 Jan '08

10 Jan '08

Does the Trash plugin in 1.0.x log it's dirty deeds somehow? I'd like to see that it works :) -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Arguing with good advice will result in lack of good advice. -- Victor Duchovni

2 1

[Dovecot] Per user mailbox quota
by Ranjith Kumar 10 Jan '08

10 Jan '08

Hi, How do I setup per user mailbox quota? I am using /etc/passwd database. Thanks BAT

3 2

[Dovecot] Sendmail, procmail, dovecot and quota
by papi mac 10 Jan '08

10 Jan '08

I have Fedora 7 from a standard installation running sendmail, procmail and dovecot 1.0 installed on a single partition. I now need to set up mail quotas for most of the users but not all. Just protecting /var/spool/mail/$LOGNAME is probably good enough for me. Since I just want mail quotas and the installation is on just 1 partition I don't have an easy way to use file system quotas. By reading through the dovecot documentation and list archives I have the feeling that this is possible with the versions and setup I have. I would probably need a main line like this (apart from other lines) per user mailbox that needs to be managed: dirsize:/var/spool/mail/joe-user:storage 10240 to give joe-user a 10 mb limit. Since this server is in production I don't have the luxury of experimenting (extensively) on it. I have a question though that I have not been able to answer yet. If the flow of mail goes from sendmail to procmail to the mailbox, how is it possible for dovecot to implement quotas on the inbox? Or would dovecot write something there that procmail has to honor? Is dovecot the way to do this? Am I misunderstanding what "quotas" mean in dovecot? Thanks for any clues. --------------------------------- Looking for last minute shopping deals? Find them fast with Yahoo! Search.

4 7

[Dovecot] maildir_uidlist_create assertion failure
by Andrew Garner 10 Jan '08

10 Jan '08

I've been getting the following error fairly often, which tends to result in a corrupted dovecot-uidlist. dovecot: IMAP(example(a)example.com): file maildir-uidlist.c: line 1009 (maildir_uidlist_recreate): assertion failed: (file_size == (uoff_t)st.st_size) dovecot: IMAP(example(a)example.com): Raw backtrace: imap [0x80cb740] -> imap [0x80cb64a] -> imap [0x8070e58] -> imap(maildir _uidlist_sync_deinit+0xe8) [0x8072d18] -> imap [0x806e9e2] -> imap(maildir_storage_sync_init+0x66) [0x806edf6] -> imap(imap_sync_init+0x4a) [0x80657da] -> ima p(cmd_sync+0x9d) [0x806590d] -> imap(cmd_store+0x33d) [0x805e1ed] -> imap(cmd_uid+0x57) [0x805e737] -> imap [0x805f009] -> imap [0x805f0ae] -> imap(client_inp ut+0x65) [0x805f6c5] -> imap(io_loop_handler_run+0x162) [0x80d3022] -> imap(io_loop_run+0x28) [0x80d2368] -> imap(main+0x4ab) [0x806723b] -> /lib/tls/i686/cmo v/libc.so.6(__libc_start_main+0xc8) [0xb7dfdea8] -> imap [0x8059551] dovecot: child 17997 (imap) killed with signal 6 dovecot: IMAP(example(a)example.com): rename(/home/vmail/domains/o/example.com/U/example/Maildir/dovecot-uidlist.…, /home/vmail/domains/o/example.com/U/example/Maildir/dovecot-uidlist) failed: No such file or directory dovecot: IMAP(example(a)example.com): unlink(/home/vmail/domains/o/example.com/U/example/Maildir/dovecot-uidlist.… failed: No such file or directory dovecot: IMAP(example(a)example.com): rename(/home/vmail/domains/o/example.com/U/example/Maildir/dovecot-uidlist.…, /home/vmail/domains/o/example.com/U/example/Maildir/dovecot-uidlist) failed: No such file or directory dovecot: IMAP(example(a)example.com): unlink(/home/vmail/domains/o/example.com/U/example/Maildir/dovecot-uidlist.… failed: No such file or directory Followed sometime later by: dovecot: IMAP(example(a)example.com): Invalid data in file /home/vmail/domains/o/example.com/U/example/Maildir/dovecot-uidlist Example of some corruption: ~/Maildir/dovecot-uidlist ... 7879 W193997 1195126451.4452.server023,S=191173:2,aopr :1195126451.4452.server023,S=191173:2,aopr ... 9628 W665454 1197354124.5254.server019,S=651976:2,pr <A0>% :1197354124.5254.server019,S=651976:2,pr # dovecot -n # 1.1.beta11: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login verbose_proctitle: yes mail_uid: 89 mail_gid: 89 mail_location: maildir:~/Maildir mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_executable(default): /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): fts fts_squat mail_plugins(imap): fts fts_squat mail_plugins(pop3): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap/ mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap/ mail_plugin_dir(pop3): /usr/lib/dovecot/modules/ imap_client_workarounds(default): delay-newmail imap_client_workarounds(imap): delay-newmail imap_client_workarounds(pop3): pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %f pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: login plain cram-md5 digest-md5 username_format: %Lu verbose: yes debug: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth user: postfix group: postfix master: path: /var/run/dovecot/auth-master user: vmail group: vmail plugin: quota: maildir quota_rule: *:storage=102400:messages=30000 fts: squat

5 9

[Dovecot] Dovecot auth GSSAPI
by Eduardo Sachs 09 Jan '08

09 Jan '08

Hi, I have Heimdal Kerberos with authentication in my Samba PDC, Postfix and OpenLDAP, it is perfect. But, I have problem with authentication GSSAPI of Dovecot. I install a service ticket of the form imap/mailserver.domain.com@REALM, imap/mailserver@REALM, pop/mailserver.domain.com@REALM and pop/mailserver@REALM and /etc/krb5.keytab for this services tickets. Debug in my messages log: Jan 9 15:14:32 mailserver dovecot: auth(default): client in: AUTH^I1^IGSSAPI^Iservice=IMAP^Ilip=192.168.0.71^Irip=192.168.0.212 Jan 9 15:14:32 mailserver dovecot: auth(default): gssapi(?,192.168.0.212): Obtaining credentials for imap@mailserver Jan 9 15:14:32 mailserver dovecot: auth(default): gssapi(?,192.168.0.212): While importing principal name: An invalid name was supplied Jan 9 15:14:33 mailserver dovecot: auth(default): client out: FAIL^I1^Itemp Jan 9 15:14:33 mailserver dovecot: imap-login: Aborted login: method=GSSAPI, rip=192.168.0.212, lip=192.168.0.71 Someone knows solve this problem? Or, it is a bug? Thanks!!!

1 0

[Dovecot] dovecot upgrade
by Paul A 08 Jan '08

08 Jan '08

Hi, I'm currently using Dovecot version 1.0 and I want to update it to the latest version. I know from version .99 to version 1.0 I had to change a few things on the dovecot config. When compiling the latest stable version should I just be able to use the same config I'm using for version 1.0 without making any changes ? Thank you Paul

3 3

[Dovecot] Dovecot too many open files???
by Tim Tyler 08 Jan '08

08 Jan '08

Dovecot experts, We just recently deployed Dovecot 1.0.rc15 on a Redhat 5 system. I have over 1400 users. At first it appeared to work fine. But soon, we had complaints of students that couldn't retrieve their email. I looked in the logs and found this error. Jan 7 22:27:31 stu dovecot: auth(default): pam(pucklisl,<http://144.89.40.6>144.89.40.6): pipe() failed: Too many open files We are running Dovecot to authenticate via pam which authenticates ldap. Below is the output of [root@stu ~]# dovecot -n # /etc/dovecot.conf listen: * ssl_cert_file: /etc/mail/certs/server.pem ssl_key_file: /etc/mail/certs/server.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_process_size: 512 login_max_processes_count: 32 mail_location: mbox:%h/mail:INBOX=/var/spool/mail/%u mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /etc/custom-pop3.sh mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: passdb: driver: pam userdb: driver: passwd Any solutions for this problem? Tim Tyler Network Engineer - Beloit College tyler(a)beloit.edu

2 3

[Dovecot] (somewhat ot?) purging old maildir messages
by Matt LaPlante 08 Jan '08

08 Jan '08

I'm using Dovecot (+postfix) to host some personal imap accounts on a private server (Maildir format). I've got one account that receives mostly automated mails, and I want to be able to purge messages beyond a given date (say 30 days). I know that since maildir uses flat files, I can literally just delete messages doing something similar to the following with bash: for i in $(find /var/spool/vmail/host1/user/cur/ -mtime +30); do rm $i done I dislike this approach for a few reasons. First, and most plainly, it seems crude. When running complex server software, its rarely a good idea in the field of systems administration to be bluntly deleting files out from under the running applications. It feels wrong. How does this affect dovecot's monitoring of the files and indexing? What if the files happen to be open in an email client? Etc. Emotions aside, I also very much dislike running an automated 'rm' that has the power to wipe out a lot of my email if something goes pearshaped with the script. I can think of several possible solutions that don't require subversive operations on the maildirs, but I've never used them and therefore don't know if they're actually feasible: - Use a tool designed to manipulate maildirs. Something akin to postfix's postqueue and postsuper tools come to mind, but I don't know if such an app exists. - Use a setting within dovecot that expires old maildir data. As I understand it this will be available in 1.1 (yay!); unfortunately that's not an option for me until 1.1 is available as stable in my server os. - Use a scriptable mua that has the capability to check mail under said account and automatically delete based on age. I know very little of tools in this area, so again I don't know if such an application exists. Any pointers you might have would be much appreciated. Thanks, Matt

4 4

[Dovecot] Problem with passwords surrounded by curly braces
by Frank Kintrup 08 Jan '08

08 Jan '08

Hello, one of my users set his password to something surrounded by curly braces, and promptly all access to his mailbox was refused. After looking through the logs I found an entry "Unknown password scheme xxxx", where "xxxx" is the user's password, but without the curly braces. I then browsed through the documentation and there was explained that it is possible to prefix the password with the password scheme in curly braces, like "{PLAIN}xxxx" where xxxx is the password itself. Manually altering the users password in the database to "{PLAIN}xxxx" (where "xxxx" is the user's password WITH curly braces) fixed this problem for me at this time, but the time a user chooses such a strange password I would have to edit the table again. So in my opinion the {SCHEME}-prefix is not a useful thing. Why would anyone need it, anyway? Shouldn't all passwords have the same scheme which is set in the dovecot.conf file once? If the feature is indeed used: with a database lookup it should be replaced by an optional database field or, if that's not possible, it should be possible to disable this feature from the config file. Frank

4 3