- dovecot - dovecot.org

[Dovecot] The function that returns existance of the user.
by Вострухин Максим 17 Feb '08

17 Feb '08

I'm changing the source code of Dovecot and I need of the function which only returns existanse of the user and doesn't do anything else. What function I should use? Thanks.

2 1

Re: [Dovecot] mailformat troubles (dovecot: stat failed: Not a directory)
by Andrea 17 Feb '08

17 Feb '08

> -----Original Message----- > From: owner-postfix-users(a)postfix.org [mailto:owner-postfix- > users(a)postfix.org] On Behalf Of mouss > Sent: Sunday, February 17, 2008 7:15 PM > Cc: postfix-users(a)postfix.org > Subject: Re: mailformat troubles (dovecot: stat failed: Not a > directory) > > Andrea wrote: > > I have recently installed dovecot on a FreeBSD mailserver running > postfix. > > But when I try to login with imap/pop3, I always get an error "stat > failed: > > Not a directory". > > I guess it is something wrong with the mail format postfix uses to > store the > > message, but I don't seem to find the correct solution. > > > > you deliver to an mbox file, but you want to read from a maildir. > configure postfix to deliver to maildir by appending a slash to your > virtual mailbox maps results. Worked perfectly. Thanks. Andrea

1 0

[Dovecot] stat failed: Not a directory
by Andrea 17 Feb '08

17 Feb '08

I have recently installed dovecot on a FreeBSD mailserver running postfix. But when I try to login with imap/pop3, I always get an error "stat failed: Not a directory". I guess it is something wrong with the mail format postfix uses to store the message, but I don't seem to find the correct solution. Here's the postfix log with the successful delivery: Feb 17 08:58:24 mailsrv2 postfix/smtpd[75706]: connect from pc17r2.domain.com[10.0.1.17] Feb 17 08:59:07 mailsrv2 postfix/smtpd[75706]: 290F1B81D: client= pc17r2.domain.com[10.0.1.17] Feb 17 08:59:20 mailsrv2 postfix/cleanup[75710]: 290F1B81D: message-id=<20080217075907.290F1B81D(a)mailsrv2.domain.com> Feb 17 08:59:20 mailsrv2 postfix/qmgr[75703]: 290F1B81D: from=<andrea(a)vp44.net>, size=384, nrcpt=1 (queue active) Feb 17 08:59:21 mailsrv2 postfix/virtual[75711]: 290F1B81D: to=<andrea(a)internal.domain.com>, relay=virtual, delay=39, delays=39/0.26/0/0.24, dsn=2.0.0, status=sent (delivered to mailbox) Feb 17 08:59:21 mailsrv2 postfix/qmgr[75703]: 290F1B81D: removed And here dovecot: Feb 17 09:00:24 mailsrv2 dovecot: imap-login: Login: user=<andrea(a)internal.domain.com>, method=PLAIN, rip=10.0.1.2, lip=10.0.1.17 Feb 17 09:00:24 mailsrv2 dovecot: IMAP(andrea(a)internal.domain.com): stat(/usr/local/virtual/internal.domain.com/andrea/cur) failed: Not a directory Feb 17 09:00:24 mailsrv2 dovecot: IMAP(andrea(a)internal.domain.com): stat(/usr/local/virtual/internal.domain.com/andrea/cur) failed: Not a directory Feb 17 09:00:24 mailsrv2 dovecot: IMAP(andrea(a)internal.domain.com): Connection closed Dovecot -n: # 1.0.10: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 imaps pop3s ssl_cert_file: /etc/ssl/dovecot/cert.pem ssl_key_file: /etc/ssl/dovecot/key.pem disable_plaintext_auth: no login_dir: /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: Internal Server Ready verbose_proctitle: yes first_valid_uid: 125 last_valid_uid: 125 first_valid_gid: 125 last_valid_gid: 125 mail_extra_groups: mail mail_location: maildir:/usr/local/virtual/%d/%n 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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login cram-md5 digest-md5 passdb: driver: pam passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix Postconf -n: mailsrv2# postconf -n broken_sasl_auth_clients = yes command_directory = /usr/local/sbin config_directory = /usr/local/etc/postfix daemon_directory = /usr/local/libexec/postfix debug_peer_level = 2 html_directory = no mail_owner = postfix mailq_path = /usr/local/bin/mailq manpage_directory = /usr/local/man mydomain = domain.com myhostname = mailsrv2.domain.com mynetworks = 10.0.1.0/24, 127.0.0.0/8 mynetworks_style = subnet newaliases_path = /usr/local/bin/newaliases proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $virtual_mailbox_limit_maps queue_directory = /var/spool/postfix readme_directory = no relay_domains = proxy:mysql:/usr/local/etc/postfix/mysql_relay_domains_maps.cf sample_directory = /usr/local/etc/postfix sendmail_path = /usr/local/sbin/sendmail setgid_group = maildrop smtp_tls_note_starttls_offer = yes smtp_use_tls = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unauth_destination, reject_unauth_pipelining, reject_invalid_hostname, reject_rbl_client list.dsbl.org, reject_rbl_client bl.spamcop.net, reject_rbl_client sbl-xbl.spamhaus.org smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks smtpd_tls_CAfile = /etc/ssl/postfix/ca.crt smtpd_tls_cert_file = /etc/ssl/postfix/smtp.purplehat.org.crt smtpd_tls_key_file = /etc/ssl/postfix/smtp.purplehat.org.key smtpd_tls_loglevel = 0 smtpd_tls_received_header = yes smtpd_tls_session_cache_timeout = 3600s smtpd_use_tls = yes soft_bounce = no tls_random_source = dev:/dev/urandom unknown_local_recipient_reject_code = 550 virtual_alias_maps = proxy:mysql:/usr/local/etc/postfix/mysql_virtual_alias_maps.cf virtual_gid_maps = static:125 virtual_mailbox_base = /usr/local/virtual virtual_mailbox_domains = proxy:mysql:/usr/local/etc/postfix/mysql_virtual_domains_maps.cf virtual_mailbox_limit = 51200000 virtual_mailbox_limit_maps = proxy:mysql:/usr/local/etc/postfix/mysql_virtual_mailbox_limit_maps.cf virtual_mailbox_limit_override = yes virtual_mailbox_maps = proxy:mysql:/usr/local/etc/postfix/mysql_virtual_mailbox_maps.cf virtual_maildir_limit_message = Sorry, this user has overdrawn their diskspace quota. Please try again later. virtual_minimum_uid = 125 virtual_overquota_bounce = yes virtual_transport = virtual virtual_uid_maps = static:125

3 2

[Dovecot] --without-linux-quota
by Heiko Schlichting 17 Feb '08

17 Feb '08

Hi, compiling dovecot 1.1.beta16 with configure option "--without-linux-quota" failed in line 444 of quota-fs.c as _LINUX_QUOTA_VERSION is an unquoted "no". Additionally using "--without-linux-quota" does not remove the quota code from dovecot as I expected. This is not a problem to me but it would be more clear if configure failed if "--without-linux-quota" is used and it is not possible to strip the quota code from dovecot. I know that I can use "--with-linux-quota=..." to specify a quota version but for me this option implied that it is possible to remove the filesystem quota code entirely if it is not needed. Heiko Heiko Schlichting | Freie Universität Berlin heiko(a)FU-Berlin.DE | Zentraleinrichtung für Datenverarbeitung (ZEDAT) Telefon +49 30 838-54327 | Fabeckstraße 32 Telefax +49 30 838454327 | 14195 Berlin

1 0

[Dovecot] --disable-ipv6 does not work
by Heiko Schlichting 17 Feb '08

17 Feb '08

Hi, configure option "--disable-ipv6" does not work for me in version 1.1.beta16 (and earlier versions). The following patch fixed this problem for me. Heiko ============================================================ --- configure.in.org 2008-02-16 15:35:53.000000000 +0100 +++ configure.in 2008-02-17 01:30:21.675931789 +0100 @@ -23,8 +23,8 @@ AC_ARG_ENABLE(ipv6, [ --enable-ipv6 Enable IPv6 support (auto)], - if test x$withval = xno || test x$withval = xauto; then - want_ipv6=$withval + if test x$enableval = xno || test x$enableval = xauto; then + want_ipv6=$enableval else want_ipv6=yes fi, ============================================================ Heiko Schlichting | Freie Universität Berlin heiko(a)FU-Berlin.DE | Zentraleinrichtung für Datenverarbeitung (ZEDAT) Telefon +49 30 838-54327 | Fabeckstraße 32 Telefax +49 30 838454327 | 14195 Berlin

2 2

[Dovecot] Dovecot pgsqlauthentication database reconnection/failover problem
by Frank Wang 17 Feb '08

17 Feb '08

Hi, Our mail system uses dovecot-1.0-1.2.rc15.el5 in Centos-5.1 as our imap server. It connects to a pgsql database in another server as authentication backend. It works fine except occasionally fails to reconnect to the database after temporary network block, and dovecot has to be restarted to work again in such case. Since I can't find any specific setting in dovecot.conf to handle this reconnection problem, I opt to build a failover pgsql backend. Google led me to http://www.dovecot.org/list/dovecot/2008-January/027899.html. I followed the thread to modify my dovecot-sql.conf containing "connect = host=pgsql1 host=pgsql2 dbname=xxxx user=xxxx" If both databases are available, dovecot will choose pgsql2 as the default one, and user login works flawlessly. But when I block all traffic to host pgsql2, dovecot will repeatedly try pgsql2 and neglect available host pgsql1. I don't find relevent information in the dovecot wiki either. Can anyone here shed a light on me? Thanks in advance! Regards, Frank Wang

3 6

[Dovecot] v1.1.beta16 released
by Timo Sirainen 16 Feb '08

16 Feb '08

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta16.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta16.tar.gz.sig If all goes well, I'll release v1.1.rc1 in a couple of days. Now's a good time to start testing v1.1 :) Changes since beta15: - Squat is finally working and supports expunging messages from it. I've been stress testing it and can't find any problems anymore. - Some index/cache crashfixes TODO for v1.1.0: - mbox: We write From_-lines to message bodies unescaped and assume Content-Length: header allows us to skip over them. This probably worked in v0.99, but got broken when mbox code was rewritten for v1.0. This should be fixed somehow. - dbox: fsync()ing isn't done for saved messages. - maildir: after rename()ing files from tmp/ to new/ we should probably fsync() the new/ directory. - Squat: NFS support. Check/fix a potential locking problem. - Lucene: It gives all kinds of locking errors which cause other problems. Maybe Dovecot should do the locking itself so Lucene never needs to wait for locks? Has anyone here used Lucene before and knows about these issues?

1 0

[Dovecot] [patch] make <chroot>/./<home> a config option.
by Diego Liziero 16 Feb '08

16 Feb '08

Hi, I think that the wu-ftp style chroot /./ should be a configurable option. In our servers we have some home directories in /chroot-web/./username (where web users can upload their web sites in a chrooted environment) and all imap mail in /mail-disk/username. We are planning a dovecot migration from our modified version of uw-imap and we noticed that the chroot in /chroot-web/ can't be disabled. This patch adds the bool option home_slash_dot_slash_chroot (feel free to change this name to something easier to understand). Setting this to "no" disables the wu-ftp style /./ chroot. I hope this feature can be considered useful and soon included in dovecot. Regards, Diego Liziero.

3 4

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

15 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

3 3

[Dovecot] dovecot rejecting auth after working a few times
by Matthew Thorley 15 Feb '08

15 Feb '08

Greetings all, I've got a dovecot server up that works just fine for a few minutes, and then suddenly won't authenticate users. On top of it, it keeps spawning dovecot-auth processes that won't go away. If any one has seen this or knows what's causing it I sure could use some help. Thanks much. I've included my relevant config info below -- Matthew Thorley dovecot --version 1.0.beta3 grep -v \# /etc/dovecot/dovecot.conf | grep -vE "^$" protocols = imaps pop3s listen = * ssl_disable = no ssl_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem ssl_key_file = /etc/ssl/private/ssl-cert-snakeoil.key disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " login_user = dovecot mail_extra_groups = mail mail_debug = yes default_mail_env = maildir:/var/mail/%u protocol imap { } protocol pop3 { pop3_uidl_format = %v-%u } auth_verbose =yes auth_debug = yes auth_debug_passwords = yes auth_worker_max_count = 10 auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root } plugin { }

3 9

[Dovecot] Managesieve with local accounts
by Michael Baecker 15 Feb '08

15 Feb '08

Hello, I've got a problem using the plugin managsieve in dovecot (1.0.10 on gentoo linux). I use local unix accounts on a linux machine, one for each user with a .maildir in there home directory. Here is a snippet of the logging. Feb 14 20:17:48 obelix dovecot: Dovecot v1.0.10 starting up Feb 14 20:18:00 obelix dovecot: imap-login: Login: user=<michael>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 14 20:18:00 obelix dovecot: imap-login: Login: user=<michael>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 14 20:18:00 obelix dovecot: IMAP(michael): Disconnected: Logged out Feb 14 20:18:00 obelix dovecot: IMAP(michael): Disconnected: Logged out Feb 14 20:18:00 obelix dovecot: imap-login: Login: user=<michael>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 14 20:18:00 obelix dovecot: IMAP(michael): Disconnected: Logged out Feb 14 20:18:00 obelix dovecot: imap-login: Login: user=<michael>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 14 20:18:00 obelix dovecot: IMAP(michael): Disconnected: Logged out Feb 14 20:19:04 obelix dovecot: managesieve-login: Disconnected: user=<michael>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS I don't get the sieve script and can't also save a script. It looks quite ugly "login: Disconnected" in the last line. Here is my config file (without the comments): protocols = imap managesieve listen = * disable_plaintext_auth = yes ssl_disable = no ssl_cert_file = /etc/ssl/dovecot/server.pem ssl_key_file = /etc/ssl/dovecot/server.key mail_location = maildir:~/.maildir mail_debug = no verbose_proctitle = yes first_valid_uid = 10 protocol imap { } protocol pop3 { } protocol managesieve { sieve=~/.dovecot.sieve sieve_storage=~/sieve listen = *:2000 } protocol lda { postmaster_address = postmaster(a)baecker.com mail_plugins = cmusieve } auth default { mechanisms = plain passdb pam { args = "*" } userdb passwd { args = blocking=yes } user = root socket listen { client { path = /var/spool/postfix/auth/dovecot mode = 0666 user = postfix group = postfix } master { path = /var/spool/postfix/auth/auth-master mode = 0666 user = postfix group = postfix } } } dict { } plugin { } The client worked already with pysieved over xinetd (Horde Ingo and squirrelmail with avelsieve worked). But this isn't realy a solution. Can anybody help me? Do you need anything, I didn't wrote her? Thanks in advance Michael Baecker

2 2

[Dovecot] Finding Dovecot 1.1 hg
by Asheesh Laroia 15 Feb '08

15 Feb '08

When I do either: $ hg clone http://hg.dovecot.org/dovecot/1.1/ or $ hg clone http://hg.dovecot.org/dovecot/ and cd into the resulting directory ("1.1/" or "dovecot/") and do autogen.sh and configure, ./configure tells me at the end: NOTE: This is the UNSTABLE development branch of Dovecot v1.2. I wanted Dovecot v1.1, I thought, to help Timo get that out the door! Timo? -- Asheesh. -- Leibowitz's Rule: When hammering a nail, you will never hit your finger if you hold the hammer with both hands.

4 4

[Dovecot] Solaris 10 / 1.1.beta15 imap cores
by Tomi Vainio 15 Feb '08

15 Feb '08

Hi, I've been using 1.0 but moved to beta to see if it works before release. Both b14 and b15 dies sometimes when accessing folders. Last time I fixed this by moving one message from folder to another and then back. Next I'm trying to build this with debugging enabled. Tomppa > Feb 14 11:52:33 dovecot: [ID 107833 mail.crit] IMAP(tomppa): file message-parser.c: line 674: assertion failed: (ctx->part->physical_pos >= ctx->input->v_offset) > Feb 14 11:52:34 genunix: [ID 603404 kern.notice] NOTICE: core_log: imap[5995] core dumped: /v/tmp/core.imap.5995 > Feb 14 11:52:40 dovecot: [ID 107833 mail.crit] IMAP(tomppa): file message-parser.c: line 674: assertion failed: (ctx->part->physical_pos >= ctx->input->v_offset) > Feb 14 11:52:40 genunix: [ID 603404 kern.notice] NOTICE: core_log: imap[5997] core dumped: /v/tmp/core.imap.5997 > Feb 14 11:52:47 dovecot: [ID 107833 mail.crit] IMAP(tomppa): file message-parser.c: line 674: assertion failed: (ctx->part->physical_pos >= ctx->input->v_offset) > Feb 14 11:52:47 genunix: [ID 603404 kern.notice] NOTICE: core_log: imap[5999] core dumped: /v/tmp/core.imap.5999 > )# dbx /usr/local/libexec/dovecot/imap /v/tmp/core.imap.5999 > For information about new features see `help changes' > To remove this message, put `dbxenv suppress_startup_message 7.6' in your .dbxrc > Reading imap > core file header read successfully > Reading ld.so.1 > Reading librt.so.1 > Reading libnsl.so.1 > Reading libsocket.so.1 > Reading libsendfile.so.1 > Reading libc.so.1 > Reading libaio.so.1 > Reading libmd.so.1 > Reading libc_psr.so.1 > Reading 8859-1%UTF-8.so > program terminated by signal ABRT (Abort) > 0xff1c5c14: __lwp_kill+0x0008: bcc,a,pt %icc,__lwp_kill+0x18 ! 0xff1c5c24 > (dbx) where > =>[1] __lwp_kill(0x0, 0x6, 0x0, 0x6, 0xfc00, 0x0), at 0xff1c5c14 > [2] raise(0x6, 0x0, 0x0, 0xff1a8c20, 0xffffffff, 0x6), at 0xff164c44 > [3] abort(0x2, 0x1, 0xe83c4, 0xad324, 0xff1f1318, 0x0), at 0xff1410f8 > [4] 0xaa4f0(0x2, 0x100400, 0xd5400, 0x100ba0, 0xea000, 0xea078), at 0xaa4f0 > [5] i_panic(0xd4a6c, 0xea000, 0x2a2, 0xfeb88, 0xea16c, 0xaa464), at 0xa9de4 > [6] 0xa2ec4(0x157170, 0xffbff544, 0xd4800, 0x0, 0x1380e0, 0xfe800), at 0xa2ec4 > [7] message_parser_parse_next_block(0x157170, 0xffbff544, 0x1, 0x0, 0xfe800, 0xa2d4c), at 0xa3064 > [8] 0xa4554(0x151158, 0x14fc88, 0x138090, 0xffbff534, 0x80000000, 0xd4cc4), at 0xa4554 > [9] message_search_msg(0x151158, 0x14fc88, 0x137ff0, 0x14fc60, 0xe0, 0x60), at 0xa45d4 > [10] 0x67a40(0x10c588, 0x10, 0x10c588, 0x14fb38, 0x151158, 0xffbff6e4), at 0x67a40 > [11] mail_search_args_foreach(0x10c588, 0x679a4, 0xffbff6e4, 0x1, 0x1, 0xffffffff), at 0x6f688 > [12] 0x67d68(0x10c550, 0x137b68, 0x67800, 0xffffffff, 0xffffffff, 0x14fc88), at 0x67d68 > [13] index_storage_search_next_nonblock(0x137b68, 0x137be8, 0x1, 0xffbff81f, 0xea000, 0x113b28), at 0x69368 > [14] 0x26008(0x10c500, 0x40000000, 0x2, 0x10c5c8, 0x80000000, 0xc2000), at 0x26008 > [15] 0x262c8(0x10c500, 0x100550, 0x1, 0xea000, 0xea058, 0x10c2a0), at 0x262c8 > [16] 0xb1c10(0x109518, 0x10a610, 0x3, 0x3e8, 0xea0b8, 0xd64f8), at 0xb1c10 > [17] io_loop_handle_timeouts(0x109518, 0x3, 0x0, 0x10624c00, 0x0, 0x0), at 0xb1c70 > [18] io_loop_handler_run(0x109518, 0x0, 0x2, 0x29414, 0xd6400, 0x10a5b0), at 0xb2380 > [19] io_loop_run(0x80, 0x0, 0x80000000, 0x80000000, 0x10a5b0, 0x109518), at 0xb1cc4 > [20] main(0x100800, 0x10c2a0, 0xe8c00, 0x10000, 0x100978, 0x1008c4), at 0x330ac > (dbx) # /usr/local/sbin/dovecot -n # 1.1.beta15: /usr/local/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 640). Either grow the limit or change login_max_processes_count and max_mail_processes settings base_dir: /var/run/dovecot/ ssl_cert_file: /etc/mail/certs/imapd.pem ssl_key_file: /etc/mail/certs/key.pem disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 100 mail_location: mbox:~/Posti/:INBOX=/var/mail/%u:INDEX=/var/dovecot/indexes/%u auth default: passdb: driver: pam userdb: driver: passwd

3 3

[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

[Dovecot] Postfix, dovecot and sieve - no response from sieve
by Hervé Hénoch 12 Feb '08

12 Feb '08

Os : Linux Debian Etch Version : 1.0.rc15 Config : # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 imap 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: 0 last_valid_uid: 150 first_valid_gid: 0 last_valid_gid: 150 mail_extra_groups: mail mail_location: maildir:/mnt/virtual/mail/%d/%n mail_debug: yes 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: user: vmail verbose: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: static args: uid=vmail gid=mail home=/mnt/virtual/mail/%d/%n userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 511 user: vmail group: mail My problem is the following : I can't get sieve script running but sieve script compile well automatically (i.e the file .dovecot.sieve compile in a file named .dovecot.sievec). I have followed the installation of sieve, postfix, dovecot under a Debian via apt-get. The program deliver is used correctly by Postfix (master.cf). With a reject script I have the following trace (user h.henoch(a)testisc84.org send to test(a)testisc84.org which have a sieve "reject" script), the mail seems to be rejected but I have no notification for the sender. This script run under a old postfix, cyrus installation Feb 12 11:55:33 vsmail deliver(h.henoch(a)testisc84.org): msgid=<dovecot-1202813723-606909-0(a)vsmail.isc84.org>*: rejected* Feb 12 11:55:33 vsmail postfix/cleanup[26150]: C810F174DA7: message-id=<dovecot-1202813728-750522-0(a)vsmail.isc84.org> Feb 12 11:55:33 vsmail postfix/pipe[26151]: ADDDC174DA8: to=<h.henoch(a)testisc84.org>, relay=dovecot, delay=5.2, delays=0.1/0/0/5.1, dsn=2.0.0, status=sent (delivered via dovecot service) Feb 12 11:55:33 vsmail postfix/qmgr[25852]: ADDDC174DA8: removed Feb 12 11:55:33 vsmail postfix/qmgr[25852]: C810F174DA7: from=<>, size=2180, nrcpt=1 (queue active) *Feb 12 11:55:33 vsmail postfix/qmgr[25852]: C810F174DA7: to=<MAILER-DAEMON@>, relay=none, delay=0.13, delays=0.08/0.04/0/0, dsn=5.1.3, status=bounced (bad address syntax)* Feb 12 11:55:33 vsmail postfix/qmgr[25852]: C810F174DA7: removed The script : require ["reject"]; reject " ############################################################################################################################################### ### Nous vous informons que XXX ne travaille plus pour YYYY ### ############################################################################################################################################### "; With a vacation script I have the following trace (same as above), no errors and sieve script seems to be found. This script run under a old postfix, cyrus installation Feb 12 12:00:42 vsmail postfix/smtpd[26277]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled Feb 12 12:00:43 vsmail postfix/smtpd[26277]: connect from unknown[172.18.101.3] Feb 12 12:00:43 vsmail postfix/smtpd[26277]: 2E1B8174DA6: client=unknown[172.18.101.3] Feb 12 12:00:43 vsmail postfix/cleanup[26280]: 2E1B8174DA6: message-id=<47B17C5C.3010203(a)testisc84.org> Feb 12 12:00:43 vsmail postfix/qmgr[25852]: 2E1B8174DA6: from=<h.henoch(a)testisc84.org>, size=564, nrcpt=1 (queue active) Feb 12 12:00:43 vsmail postfix/smtpd[26277]: disconnect from unknown[172.18.101.3] Feb 12 12:00:43 vsmail deliver(test(a)testisc84.org): auth input: test(a)testisc84.org Feb 12 12:00:43 vsmail deliver(test(a)testisc84.org): auth input: uid=150 Feb 12 12:00:43 vsmail deliver(test(a)testisc84.org): auth input: gid=8 Feb 12 12:00:43 vsmail deliver(test(a)testisc84.org): auth input: home=/mnt/virtual/mail/testisc84.org/test Feb 12 12:00:43 vsmail deliver(test(a)testisc84.org): Loading modules from directory: /usr/lib/dovecot/modules/lda Feb 12 12:00:43 vsmail deliver(test(a)testisc84.org): Module loaded: /usr/lib/dovecot/modules/lda/lib90_cmusieve_plugin.so Feb 12 12:00:43 vsmail deliver(test(a)testisc84.org): maildir: data=/mnt/virtual/mail/testisc84.org/test Feb 12 12:00:43 vsmail deliver(test(a)testisc84.org): maildir: root=/mnt/virtual/mail/testisc84.org/test, index=/mnt/virtual/mail/testisc84.org/test, control=, inbox= Feb 12 12:00:43 vsmail deliver(test(a)testisc84.org): *cmusieve: Using sieve path: /mnt/virtual/mail/testisc84.org/test/.dovecot.sieve* Feb 12 12:00:43 vsmail deliver(test(a)testisc84.org): msgid=<47B17C5C.3010203(a)testisc84.org>: saved mail to INBOX Feb 12 12:00:43 vsmail postfix/pipe[26281]: 2E1B8174DA6: to=<test(a)testisc84.org>, relay=dovecot, delay=0.12, delays=0.09/0/0/0.03, dsn=2.0.0, status=sent (delivered via dovecot service) Feb 12 12:00:43 vsmail postfix/qmgr[25852]: 2E1B8174DA6: removed The script : require ["vacation"]; vacation :addresses ["test(a)testisc84.org"] :subject "Absences vacances" "Je serais absente du 01 novembre au 25 novembre merci de me contacter plus tard";

4 3

[Dovecot] Plus sign in usernames: user+domain.com?
by hoZt 12 Feb '08

12 Feb '08

I am migrating from a cpanel server that has usernames in the format "user+domain.com". On the new server I am using the format "user.domain.com" and it all works perfectly with dovecot / postfix. Is there any way that I can allow users to login either with the "." or "+" delimiter? Thanks in advance for any suggestions!

3 3