- dovecot - dovecot.org

[Dovecot] selection correct auth with multiple auth methods
by jm 25 Mar '09

25 Mar '09

How do you control which socket or authentication process dovecot's pop3 daemon chooses to use? I've got a user database with two flags one to allow pop3 access and the other to allow the use of auth smtp. There are two authentication instances configed, thus, auth default { .... passdb sql { args = /etc/dovecot-sql-postfix.conf } .... socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = group = } } auth postfix { ..... passdb sql { args = /etc/dovecot-sql-postfix.conf } .... socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } From the logs and testing pop3 is using the postfix authentication instance and not the default as expected. Does anyone out there know how control dovecot's pops daemon authentication choice? This infomation seems to be lacking in the documentation I can find. Jeff.

2 2

[Dovecot] Making changes to dovecot log levels
by Thomas M Goerger 24 Mar '09

24 Mar '09

Hi Timo, Awhile back I'd written about making changes to some of the log levels that dovecot writes to to stop the process from writing these to monitor. I wanted to run a few changes by you for this, just to make sure these won't cause problems somewhere else. And to send this to the list, in case anyone else wants to make similar changes in the future. In the file src/lib-index/mail-index.c: duplicate the function mail_index_set_error to mail_index_set_warning and call this function in /src/lib-index/mail_cache.c instead int mail_index_set_error(struct mail_index *index, const char *fmt, ...) { va_list va; i_free(index->error); if (fmt == NULL) index->error = NULL; else { va_start(va, fmt); index->error = i_strdup_vprintf(fmt, va); va_end(va); i_error("%s", index->error); } return -1; } changing the line : i_error("%s", index->error); to i_warning("%s", index_error); and for the file src/lib-storage/index/mbox/mbox-sync.c changing this code if (rec == NULL && uid < sync_ctx->idx_next_uid) { /* this UID was already in index and it was expunged */ mbox_sync_set_critical(sync_ctx, "mbox sync: Expunged message reappeared in mailbox %s " "(UID %u < %u, seq=%u, idx_msgs=%u)", sync_ctx->mbox->path, uid, sync_ctx->idx_next_uid, sync_ctx->seq, messages_count); ret = FALSE; rec = NULL; } else if (rec != NULL && rec->uid != uid) { /* new UID in the middle of the mailbox - shouldn't happen */ mbox_sync_set_critical(sync_ctx, "mbox sync: UID inserted in the middle of mailbox %s " "(%u > %u, seq=%u, idx_msgs=%u)",sync_ctx->mbox->path, rec->uid, uid, sync_ctx->seq, messages_count); ret = FALSE; rec = NULL; from mbox_sync_set_critical( etc... to mail_storage_clear_error(storage) i_warning("Error text"... mail_storage_set_internal_error(storage) to clear and set the storage pointer Hopefully that's all clear. If you have any questions, please let me know. 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 * * * *************************************************************************

1 0

[Dovecot] Dovecot error: Panic: i_stream_stat()
by PEACEYALL 24 Mar '09

24 Mar '09

Hello! I'm testing the virtual mail boxes using telnet. The telnet seesion completes 100% okay with no errors at all. Though, when postfix has to relay the message to dovecot, i get the following error in my delivery log (/home/vmail/dovecot-delivery): deliver(john): 2009-03-21 16:23:00 Panic: i_stream_stat() used for non-blocking seekable stream deliver(john): 2009-03-21 16:23:00 Error: Raw backtrace: /usr/lib/dovecot/deliver [0x80a4c7a] -> /usr/lib/dovecot/deliver [0x80a4ae9] -> /usr/lib/dovecot/deliver [0x80aa4fc] -> /usr/lib/dovecot/deliver(mbox_sync_has_changed+0x100) [0x806deb0] -> /usr/lib/dovecot/deliver(mbox_sync+0x36b) [0x807103b] -> /usr/lib/dovecot/deliver(mbox_storage_sync_init+0x3e) [0x807160e] -> /usr/lib/dovecot/deliver [0x805794a] -> /usr/lib/dovecot/deliver(main+0xc97) [0x8058937] -> /lib/libc.so.6(__libc_start_main+0xe5) [0xb7e13455] -> /usr/lib/dovecot/deliver [0x8056ef1] degus:/home/vmail# deliver(john): 2009-03-21 16:23:00 Panic: i_stream_stat() used for non-blocking seekable stream Here is the required information: ------------------------------------------------------- degus:/home/vmail# dovecot --version 1.0.15 degus:/home/vmail# degus:/home/vmail# dovecot -n # 1.0.15: /etc/dovecot/dovecot.conf log_path: /var/log/mail.err info_log_path: /var/log/mail.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 pop3s imap imaps 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 mail_privileged_group: mail mail_location: maildir:/home/vmail/%d/%n/Maildir mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/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/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail degus:/home/vmail# degus:/etc/dovecot# grep -v '^ *$#.*$\?$' dovecot-sql.conf driver = mysql connect = host=127.0.0.1 dbname=mailserver user=*****88 password=******** default_pass_scheme = PLAIN-MD5 password_query = SELECT email as user, password FROM view_users WHERE email='%u'; degus:/etc/dovecot# ------------------------------------------------------- Thank you for your help and time.

2 1

[Dovecot] Problem with dovecot + imap idle + qmail-local delivery
by Jochen Schug 24 Mar '09

24 Mar '09

Hi, I've recently switched from courier-imap to dovecot. Everything seemed to work fine, but after I while I noticed that dovecot is occasionaly causing problems with delivery of new incoming mails. System: Gentoo Linux, kernel 2.6.19, qmail 1.03, vpopmail 5.4.26 , dovecot 1.1.11, maildir, mail store on ext3. Symptoms: qmail is having trouble with the mail delivery. First I thought it had something to do with vpopmail or dovecot's quota support, but I tracked it down to qmail-local. I tried two different versions, one with Bill Shupp's maildir++ patch and one without. With the patch, I'm getting "User_over_quota._(#5.1.1)" errors. Mail is delivered once and sender is sent a notification about the exceeded quota. Without the patch, I get "Temporary_error_on_maildir_delivery._(#4.3.0)". Mail is delivered, but delivery is tried again and again. This only happens if a MUA is logged in to the mailbox and IMAP IDLE is being used. If the MUA is disconnected: fine. If dovecot is stopped: fine. I tried a couple of different things, all without success: - upgraded dovecot from 1.1.7 to 1.1.11 - compiled a new kernel with inotify support and recompiled dovecot - migrated mail store from reiserfs to ext3 - disabling quota support in dovecot - tried dovecot's various file locking mechanisms Right now I'm working around this by removing IDLE from the capabilities. This solves the problem, but leaves me with a less functional IMAP server. Any help is greatly appreciated. Jochen dovecot -n: protocols: imaps imap pop3s pop3 listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file: /etc/ssl/dovecot/server.key disable_plaintext_auth: no verbose_ssl: yes 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 first_valid_uid: 89 last_valid_uid: 89 first_valid_gid: 89 last_valid_gid: 89 mail_uid: 89 mail_gid: 89 mail_location: maildir:/var/vpopmail/domains/%d/%n/.maildir maildir_copy_preserve_filename: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_capability(default): IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1 QUOTA imap_capability(imap): IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1 QUOTA imap_capability(pop3): imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login digest-md5 user: vpopmail verbose: yes debug: yes passdb: driver: vpopmail userdb: driver: vpopmail plugin: quota: maildir

4 6

[Dovecot] Staged migration from mbox to maildir
by Stewart Dean 24 Mar '09

24 Mar '09

So much changes in this migration that the ideal way to do it would be to begin with a few users or a department, then migrate the users affinity group by affinity group: first an institute or so, then the faculty, then the staff, then the students, moving to bigger and bigger groupings as the bugs work out of the migration and the move becomes more assured. We use sendmail and procmail. There's no problem there, as the ~./procmailrc can be changed to over-ride the mbox default until all groups are done and it become the default. The problem comes with IMAP. While dovecot can tell if a folder is mbox or maildir, it has to be pointed to the right place (by namespace definitions in the client, IIRC), and the default of putting the inbox under ~/mail is one I'd like to embrace for various reason...but given that that means moved inbox folders and *that* means either making a global change (there goes staged migration) OR changing the namespace definitions on each PC. I can get to the early few and change the namespaces definition, but there doesn't appear to any equivalent (enlighten me, if I'm missing something) to ~/.procmailrc for imap, so that I don't have to get on the client machine. Is this correct or am I (hopefully) wrong and there *is* a way to change things on the server that allows for staged migration? Oh, I would so like to be wrong! IMAP should have an rc file............. -- "Eppur si muove." (But Still it moves) Galileo, leaving the Inquisition, after buckling under the threat of torture and excommunication and recanting from his proof that the heavens do not revolve around the earth -- Stewart Dean, Unix System Admin, Henderson Computer Center, Bard College, Annandale, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

6 8

[Dovecot] dovecot with IMAP and POP3 mixed
by Andreas Meyer 23 Mar '09

23 Mar '09

Hello! I tried to setup dovecot to work with IMAP and POP3 but when I connect with Squirrelmail, I get an error saying CREATE "INBOX.Sent" reason: Mailbox doesn't allow inferior mailboxes # dovecot --version 1.0.5 # dovecot -n # 1.0.5: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot protocols: imap imaps pop3 ssl_disable: yes 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 mail_location: maildir:/var/spool/vhosts/%d/%n mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/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/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/passwd and /etc/dovecot/passwd looks like this: anmeyer@anup.de:{PLAIN}password:5000:5000::/var/spool/vhosts/anup.de/anmeyer::userdb_mail=maildir:~/ user7@anup.de:{PLAIN}password7:5000:5000::/var/spool/vhosts/anup.de/user7::userdb_mail=mbox:~/:INBOX=/var/spool/vhosts/anup.de/%u The mbox of user7 already exists. Can someone help to get both variants working so that dovecot can handle IMAP and POP3 accounts? Kind regards -- Andreas Meyer A man, a miss, a car -- a curve, He kissed the miss and missed the curve -- Burma Shave (1948) Mein öffentlicher GPG-Schlüssel unter: http://gpg-keyserver.de/pks/lookup?search=anmeyer&fingerprint=on&op=index

5 7

[Dovecot] Released Sieve v0.1.4
by Stephan Bosch 23 Mar '09

23 Mar '09

Hello Dovecot users, Not much Sieve development was done in the last five weeks, but some important platform-dependent bugs were found and repaired. The main new feature is the addition of a custom Sieve language extension for debugging in the Sieve command line tools. Changelog Sieve v0.1.4: * Started work on the sieve-filter tool. With this command line tool it will be possible to (re-)apply Sieve filters on a mail folder. It is currently undocumented and far from functional. + Added a custom debug extension that provides the possibility to print debug messages from scripts executed by the Sieve tools. - Fixed issue with opening relative paths as a mail file. Bug reported by Ian P. Christian. - Fixed MAC OSX compile problem. Turns out the extern modifier was missing at multiple places. Bug reported by Edgar Fuss. - Fixed Solaris compile problem: removed unecessary and unportable linker flags that caused compile to fail. Bug reported by Andres Yacopino. The release is available as follows: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.4.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.4.tar.gz.sig Have fun testing the new release and don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

2 1

[Dovecot] v1.1.13 and v1.2.beta3 released
by Timo Sirainen 21 Mar '09

21 Mar '09

http://dovecot.org/releases/1.1/dovecot-1.1.13.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.13.tar.gz.sig http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta3.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta3.tar.gz.sig Looks like Friday the 13th isn't the best day to make releases. :) These releases fix two bad bugs in v1.1.12. - v1.1.12's MAILBOXDIR changes broke accessing mails in some setups - v1.1.12's login_executable -D checking changes caused dovecot to crash at startup if protocols setting contained only pop3. - mbox: pop3_lock_session=yes was broken with mail_privileged_group.

3 2

[Dovecot] Single Instance Storage still on the roadmap?
by Charles Marcus 20 Mar '09

20 Mar '09

Hey Timo, I was curious where Single Instance Storage fits in on the roadmap, now that you are maybe settled in in your new digs... Is it still coming soon? Has it been pushed back by your new employers priorities? Its real high on mine, so if has been back-burnered, I'll need to start looking for alternatives... Thanks, -- Best regards, Charles

2 2

[Dovecot] update of current quota usage
by floss＠pBartels.info 20 Mar '09

20 Mar '09

Hello, I use Dovecot 1.1.11 and store the current quota usage in a Database. As far I can see it, the quota usage is updated each time dovecot performs an action on a mail. For example if a new mail is stored in the inbox, the current quota usage is increased. If a mail is deleted the quota usage is decreased. If there are still existing E-Mails in the inbox, before quota is turned on or if I perfom changes on the "mail storage" myself (for example purging trash or spam, or something) the current quota usage is NOT updated automatically by dovecot. For example I copy some mailboxes to my server, then the current quota for this mailboxes is still zero. Is it correct that dovecot can't do this for me? If yes, it seems I have to write my own (simple) update script and run it sometimes croned (because I don't really trust the actual quota implementation) and/or I have to update the current quota usage each time I perform actions myself. This "workaround" is easy by using a DB storage, but what about other implementations? Wouldn't it be nice if dovecot could do this or provide a tool for it? Thank you! Philipp

2 5