- dovecot - dovecot.org

[Dovecot] Best way to push Squat forward
by Asheesh Laroia 15 Feb '08

15 Feb '08

Timo, you mentioned you're getting tired of fighting Squat bugs lately. Does that mean you know all the bugs, and just need time to find and fix them? Or should instead I try harder to find bugs by using Dovecot 1.1 on a daily basis, and then sending you copies of mails that break it, like http://www.dovecot.org/list/dovecot/2007-October/026179.html ? -- Asheesh. -- Parting is such sweet sorrow. -William Shakespeare

1 0

[Dovecot] Deleting messages from MailDir
by Matt Richards 14 Feb '08

14 Feb '08

Hello, I have dovecot running with MailDir as a backend to store email and I would like to remove mail that is older that 30 days. I can do this by running 'find' on the MailDir but will this cause any issues with dovecot? Thanks, Matt. -- Matt Richards

10 25

[Dovecot] Restrict user on IMAP or POP
by Sebastien Roy 14 Feb '08

14 Feb '08

Hey guys, Is it possible to deny a user on POP or IMAP! For example, on the primary server we use POP3 and IMAP but how I can force a user to use POP3 and be unable to authenticate on IMAP ? Thanks Sebastien

1 0

[Dovecot] Apple Mail for 10.4/Shadow/SSL -> Problem.
by Phredd Groves 14 Feb '08

14 Feb '08

I have recently gotten Dovecot running on my Solaris 5.8 mail server in order to replace UW IMAP. I'm currently testing it out with mail clients popular amongst my users. It's been working very well, with one vital exception. Apple Mail on OS X 10.4 is not completing authentication (I don't think it's even getting that far). All I'm seeing in the syslog for attempts with Apple Mail (for both IMAP and POP3) is a single line per attempt: Jan 29 17:20:01 paradox dovecot: [ID 107833 mail.info] imap-login: Disconnected: rip=X.X.X.X, lip=Y.Y.Y.Y, TLS handshake This is even with verbose for auth and for SSL. I know syslog plays well with mail.warning and mail.debug and mail.notice, so I'm not quite sure what's going on there. Nothing shows up in authlog or messages either. The OS X 10.5 Apple mail client works just fine, as do Thunderbird and even Eudora. There did not seem to be any coverage of this when I googled and went through the dovecot archives, so I'm thinking it might be some weird interaction between that particular client and the SSL/shadow implementation in dovecot (Things work in UW IMAP for the client). Any suggestions? thanks! # /usr/local/sbin/dovecot -n # 1.0.10: /usr/local/etc/dovecot.conf protocols: imaps pop3s ssl_listen(default): *:997 ssl_listen(imap): *:997 ssl_listen(pop3): *:998 ssl_cert_file: /usr/local/ssl/certs/imapd.pem ssl_key_file: /usr/local/ssl/certs/imapd.pem verbose_ssl: yes shutdown_clients: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting_capability(default): no login_greeting_capability(imap): no login_greeting_capability(pop3): yes first_valid_uid: 100 mail_location: mbox:~/mail:INBOX=/var/mail/%u mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xv%08Xu pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: verbose: yes passdb: driver: shadow userdb: driver: passwd Phredd Groves -- Systems Administrator Psychology Department Columbia University [212] 854-8167

2 2

[Dovecot] ManageSieve v0.10.0 released for Dovecot 1.1.beta15
by Stephan Bosch 14 Feb '08

14 Feb '08

Hello Dovecot users, I finally managed to upgrade the ManageSieve implementation to dovecot-1.1. This also resulted in major restructuring of the code. The actual ManageSieve implementation is now available as a separate package and the patch now only contains the changes to the dovecot-1.1 tree that are necessary to use the ManageSieve service. The patch and the new package no longer contain another copy of the CMU Sieve code; the package depends on dovecot-sieve-1.1 for the sieve implementation. Change Log v0.10.0 ------------------- (Changed version scheme from vY to vX.Y.Z) * Upgraded to Dovecot 1.1: - The actual managesieve implementation is now a separate package. The dovecot tree still needs to be patched though to make dovecot recognize the new managesieve service. - Incorporated changes to imap/imap-login into the equivalent managesieve processes. - Removed cmusieve implementation from managesieve sources. It is now linked externally from the dovecot-sieve-1.1 package. - Restructured README.managesieve file into separate README, NEWS, TODO, DESIGN and INSTALL files. * Added support for new libsieve implementation (to be released). This package can be compiled with either the new or the old Sieve implementation (autodetected). If the new Sieve becomes stable, this package will be merged with it to make a single package for Dovecot Sieve support. Installation ------------ Patch your dovecot-1.1.beta15 source tree with the following patch: http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.beta15-managesieve-0.10.0.d… The patched Dovecot can be compiled and installed as usual. Download and unpack the dovecot-1.1-managesieve package: http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.0.tar.gz The README and INSTALL files therein should provide enough information to build, install and configure the ManageSieve service. After patching, your Dovecot source tree contains an updated dovecot-example.conf with a configuration example. The documentation is still pretty sparse however, but I intend to build a wiki page in the near future. Have fun testing the Dovecot ManageSieve service. Don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

2 1

[Dovecot] convert-tool, exit code wrong?
by Ingo Rogalsky 13 Feb '08

13 Feb '08

Hello, I use convert-tool regularly for converting mbox based mail accounts to maildir based mail accounts. Today I tuned my convert script around convert-tool. I'm irritated about the exit codes. It seems, they should be inverted or am I wrong? $ /opt/dovecot-1.0.10/bin/convert-tool rogtest1 /home/mail01/rogtest1 mbox:/home/rogtest1/mail maildir:/home/mail01/rogtest1/Maildir 1 Error: Source storage not found $ echo $? 0 $ /opt/dovecot-1.0.10/bin/convert-tool rogtest1 /home/mail01/rogtest1 mbox:/home/rogtest1/mail maildir:/home/mail01/rogtest1/Maildir 1 Info: Successfully converted $ echo $? 1 Ingo

3 2

[Dovecot] Sieve script not seen
by Hervé Hénoch 13 Feb '08

13 Feb '08

Hello, Version : 1.0.10 Dovecot -n : # 1.0.10: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no 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 first_valid_uid: 100 last_valid_uid: 5000 first_valid_gid: 100 last_valid_gid: 5000 mail_extra_groups: mail mail_location: maildir:/mnt/virtual/mail/%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: pam passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: passwd userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail I want to use sieve so the first step I have done is to run "deliver" in master.cf. I'va no problem with this : mail a dropped locally with deliver program. So, I've written a .dovecot.sieve script in the home directory of a user (which is the same of is mailbox directory) , I'be enabled sieve plugin : protocol lda { # Address to use when sending rejection mails. postmaster_address = postmaster(a)testisc84.org # Hostname to use in various parts of sent mails, eg. in Message-Id. # Default is the system's real hostname. hostname = vsmail.isc84.org # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = mail_plugin_dir = /usr/lib/dovecot/modules/lda # Binary to use for sending mails. sendmail_path = /usr/lib/sendmail # UNIX socket path to master authentication server to find users. auth_socket_path = /var/run/dovecot/auth-master # Enabling Sieve plugin for server-side mail filtering mail_plugins = cmusieve } and reloaded dovecot. When I send a mail the script is not compiled (no .dovecot.sievec) and so not executed. An idea ? A question : how can I specify the home directory in dovecot.conf ? Regards.

2 1

[Dovecot] How to log uid and keywords of delivered mail?
by Ron Avriel 13 Feb '08

13 Feb '08

Hi, I’d like to extend the mail_log plugin to log the uid and keywords of a mail delivered by LDA. The keywords are set by the sieve plugin. I added a mail_log_save_finish() function hook listed below. However, the uid of the mail is always zero and trying to get the keywords results in assertion failure, probably because the message is not committed yet: Feb 13 08:07:42 ha-test1 deliver(test1(a)example.com): dest mail seq: 23, uid: 0 Feb 13 08:07:42 ha-test1 deliver(test1(a)example.com): file mail-index-view.c: line 217 (_view_lookup_full): assertion failed: (seq > 0 && seq <= mail_index_view_get_messages_count(view)) Feb 13 08:07:42 ha-test1 deliver(test1(a)example.com): Raw backtrace: /usr/local/libexec/dovecot/deliver(i_syslog_panic_handler+0x21) [0x80965d9] -> /usr/local/libexec/dovecot/deliver [0x8096443] -> /usr/local/libexec/dovecot/deliver [0x80821d0] -> /usr/local/libexec/dovecot/deliver [0x80827c3] -> /usr/local/libexec/dovecot/deliver(mail_index_lookup_keywords+0x32) [0x8082aae] -> /usr/local/libexec/dovecot/deliver(index_mail_get_keywords+0x6c) [0x806f038] -> /usr/local/lib/dovecot/lda/lib20_mail_log_plugin.so [0xcbdac8] -> /usr/local/libexec/dovecot/deliver(mail_storage_copy+0xa8) [0x808a600] -> /usr/local/libexec/dovecot/deliver(maildir_copy+0x3e) [0x805e252] -> /usr/local/lib/dovecot/lda/lib10_quota_plugin.so [0xfc9741] -> /usr/local/lib/dovecot/lda/lib20_mail_log_plugin.so [0xcbd48f] -> /usr/local/libexec/dovecot/deliver(deliver_save+0x192) [0x80559ea] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xaa16bf] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xaaea0d] -> /usr/local/lib/dovecot/lda/lib9 static int mail_log_save_finish(struct mail_save_context *ctx, struct mail *dest_mail) { struct mail_log_mailbox *lbox = MAIL_LOG_CONTEXT(ctx->transaction->box); int ret; ret = lbox->super.save_finish(ctx, dest_mail); if (ret < 0) { return ret; } if (dest_mail != NULL) { const char *const *kw_list; i_info("dest mail seq: %u, uid: %u", dest_mail->seq, dest_mail->uid); kw_list = mail_get_keywords(dest_mail); i_info("dest mail kw: %s", kw_list ? t_strarray_join(kw_list, ",") : "NONE"); } return ret; } Some mail data, such as flags and headers, can be retrieved OK. I'm using dovecot-1.0.10 and dovecot-sieve-1.0.2. Any help in getting the uid and keywords by mail_log plugin will be greatly appreciated. Thanks, Ron ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

2 1

[Dovecot] Solaris 10 + Sun Studio 12 + dovecot-1.1.beta15 build problem
by Tomi Vainio 13 Feb '08

13 Feb '08

Hi, I've been using dovecot quite a while but latest beta fails to compile on Solaris using latest Sun Studio compiler. Making all in fts-squat source='fts-backend-squat.c' object='fts-backend-squat.lo' libtool=yes \ DEPDIR=.deps depmode=none /bin/bash ../../../depcomp \ /bin/bash ../../../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib -I../../../src/lib-mail -I../../../src/lib-index -I../../../src/lib-storage -I../../../src/plugins/fts -xO4 -I/usr/sfw/include/mysql -R/usr/sfw/lib -L/usr/sfw/lib -I/usr/sfw/include -c -o fts-backend-squat.lo fts-backend-squat.c cc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib -I../../../src/lib-mail -I../../../src/lib-index -I../../../src/lib-storage -I../../../src/plugins/fts -xO4 -I/usr/sfw/include/mysql -R/usr/sfw/lib -L/usr/sfw/lib -I/usr/sfw/include -c fts-backend-squat.c -KPIC -DPIC -o .libs/fts-backend-squat.o "fts-backend-squat.c", line 196: warning: enum type mismatch: arg #3 "fts-backend-squat.c", line 201: warning: improper pointer/integer combination: op "=" "fts-backend-squat.c", line 204: warning: enum type mismatch: op "=" "fts-backend-squat.c", line 205: too many initializers for scalar cc: acomp failed for fts-backend-squat.c *** Error code 1

2 1

[Dovecot] ACLs - what's the state of play?
by Mike Brudenell 13 Feb '08

13 Feb '08

Greetings - Could someone help me understand what the latest situation id with regard to ACLs and sharing mailboxes, please? Currently we are using Dovecot 1.0.x but will be moving to 1.1 when it comes out of Beta (and hopefully I'll get some time before too long to try building a test setup to play with). So I'm happy to talk only about ACLs and sharing mailboxes in 1.1... We are using Maildir storage format, and separate areas for each of the Control and Index files. We are using real system users with filestore quotas. Currently each user's files and directories are owner by their own uid and gid (but we can change this if need be), and are set to disallow filestore-level access to "group" or "others" (but we can change this too if need be). We need to know (quite urgently) if the following is/will be possible with 1.1: * Can person A have some (a subset) of their folders accessible by others? If so, can this be Read-Only? can it be Read-Write? * Can person A have all of their currently existing folders accessible by others, along with any folders they create in the future? * Is there support for the IMAP ACL extension, enabling users to set and manage access rights themselves from their mail client? * If system username "abc1" has made their top-level folder "Project" accessible by system username "def2", how does def2 actually specify the folder in order to open it? I have rummaged through the archives and Wiki but mostly these still talk about the magical "dovecot-shared" and "dovecot-acl" files, and how these need to be created/maintained by the system administrator. What we're hoping for is the Holy Grail of: * a Manager wanting to give their Secretary read-write (or in some cases read-only) access to some or all of their folders; * a Project Team wanting to access a common set of mail folders; * etc Under the old UW IMAP server you would authenticate as yourself, then specify someone else's folder with something like (the memory is hazy on this now): ~abc1/Project In the Dovecot Wiki I read a lot about namespaces and so on, but can't seem to piece together in my mind what these actually *look* like to the end-user wanting to access someone else's shared mailbox. Nor what can be done by the end-users, and what has to be done by the system administrator. Can anyone offer me advice, please? With many thanks, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

1 0