- dovecot - dovecot.org

[Dovecot] Sieve Installation
by Carsten Laun-De Lellis 20 Jul '10

20 Jul '10

Hallo Versuche unter OpenSuse11.2, 64bit sieve zu installieren. Konfig: OpensSuse 11.2, dovecot 1.2.9, postfix , spamassassin, amavis, mysql Wenn ich versucht dovecot sieve zu übersetzen bekomme ich immer folgende Fehlermeldung: Mit freundlichem Gruß Carsten Laun-De Lellis Dipl.-Ing. Elektrotechnik Certified Information Systems Auditor (CISA) Hauptstrasse 13 D-67705 Trippstadt Phone: +49 (6306) 992140 Mobile: +49 (151) 27530865 email: carsten.laun-delellis(a)delellis.net

1 0

[Dovecot] Login process connection routing
by Brandon Davidson 20 Jul '10

20 Jul '10

Timo, Just out of curiosity, how are incoming connections routed to login processes when run with: service imap-login { service_count = 0 } I've been playing with this on our test director, and the process connection counts look somewhat unbalanced. I'm wondering if there are any performance issues with having a single process handle so many connections. It seems fine (system load is actually lower than with service_count = 1), but I thought I'd ask. /usr/sbin/dovecot \_ dovecot/imap-login \_ dovecot/imap-login [1 connections (1 TLS)] \_ dovecot/imap-login \_ dovecot/imap-login [5 connections (5 TLS)] \_ dovecot/imap-login [1 connections (1 TLS)] \_ dovecot/imap-login [4 connections (4 TLS)] \_ dovecot/imap-login [1 connections (1 TLS)] \_ dovecot/imap-login [1 connections (1 TLS)] \_ dovecot/imap-login [315 connections (315 TLS)] \_ dovecot/imap-login [63 connections (63 TLS)] \_ dovecot/imap-login [12 connections (12 TLS)] \_ dovecot/imap-login \_ dovecot/imap-login [10 connections (10 TLS)] \_ dovecot/imap-login [2 connections (2 TLS)] \_ dovecot/imap-login [370 connections (370 TLS)] \_ dovecot/imap-login [24 connections (24 TLS)] -Brad

3 2

[Dovecot] Doveadm director flush/remove
by Brandon Davidson 20 Jul '10

20 Jul '10

I've got a couple more issues with the doveadm director interface: 1) If I use "doveadm director remove" to disable a host with active users, the director seems to lose track of users mapped to that host. I guess I would expect it to tear down any active sessions by killing the login proxies, like I'd done 'doveadm direct add HOSTNAME 0 && doveadm director flush HOSTNAME' before removing it? Here's what I see with an active open connection: [root@cc-popmap7 ~]# doveadm director status brandond Current: 10.142.0.179 (expires 2010-07-14 01:26:14) Hashed: 10.142.0.179 Initial config: 10.142.0.161 [root@cc-popmap7 ~]# doveadm director remove 10.142.0.179 [root@cc-popmap7 ~]# doveadm director status brandond Current: not assigned Hashed: 10.142.0.174 Initial config: 10.142.0.161 2) "doveadm director flush" returns the wrong usage: [root@cc-popmap7 ~]# doveadm director flush doveadm director remove [-a <director socket path>] <host> 3) "doveadm director flush" all breaks the ring: [root@cc-popmap7 ~]# doveadm director flush all Jul 14 01:26:33 cc-popmap7 dovecot: director: Error: Director 10.142.0.180:1234/right disconnected Jul 14 01:26:33 cc-popmap7 dovecot: director: Error: Director 10.142.0.180:1234/left disconnected Jul 14 01:26:33 oh-popmap7 dovecot: director: Error: director(10.142.0.162:1234/left): Invalid HOST-FLUSH args Jul 14 01:26:33 oh-popmap7 dovecot: director: Error: director(10.142.0.162:1234/right): Invalid HOST-FLUSH args For some reason, flushing a host address only disconnects one side: [root@cc-popmap7 ~]# doveadm director flush 10.142.0.160 Jul 14 01:28:23 cc-popmap7 dovecot: director: Error: Director 10.142.0.180:1234/right disconnected Jul 14 01:28:23 oh-popmap7 dovecot: director: Error: director(10.142.0.162:1234/left): Invalid HOST-FLUSH args -Brad

4 25

[Dovecot] [dovecot] Dovecot Migration so far
by Mark Moseley 20 Jul '10

20 Jul '10

We've been doing our own beta testing of Dovecot 2.0-beta4 IMAP (both direct IMAP and webmail-fronted), and we've had nothing but glowing compliments from our beta users/victims. I've also been running a lone box with the latest mercurial build and that's been running just fine too. All mail data is on NFS, but I've put indexes on the local disk, which has worked just dandy so far. Everything's been great and all I've seen amiss are a few random problems -- all of which are are barely impacting us and I mention only for the sake of feedback. All boxes are Debian Lenny i386, running 2.6.33.1. One oddity is that I see lots of messages like this (I've obfuscated paths/IPs/usernames, so assume paths are all actually correct) for a variety of different mailboxes prior to their indexes directory getting initially created: Apr 02 13:25:24 imap(mail@box): Error: creat(/var/tmp/Indexes/14/75/mail(a)box/dovecot.mailbox.log) failed: No such file or directory Judging by the mtimes of the containing directories, the directory was created a couple of seconds after the error gets logged, so I'm guessing mailbox_log_alloc is just getting called too early. It obviously just happens that first time. Doesn't seem to actually be hurting anything, that I can tell. One other kind of weird thing I saw was that originally I had my indexes on a dedicated partition with ext4 (Debian Lenny, i386, 2.6.33.1), I was seeing scattered messages like this: Mar 29 18:02:38 imap(mail@box): Error: FETCH [] for mailbox INBOX UID 3244 got too little data: 1116 vs 1087383 Mar 29 18:02:38 imap(mail@box): Error: Corrupted index cache file /var/tmp/Indexes/12/dc/mail(a)box/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 3244 The message corresponding with UID 3244 was around 1116 bytes (+32 bytes, IIRC), so no clue where the 1087383. In all the cases of that error I saw, the lefthand number of bytes was very closer to correct and the righthand was way way off, and the S= flag in the filename was correct too. I'm guessing that the random righthand number was just due to corrupted cache. When I reformatted that partition as ext3, the error went almost completely away (just a few total over the past few days, as opposed to a few per hour when it was on ext4). I don't even have an educated guess as to why that'd happen. A wild guess would be that ext4's delayed allocation was causing problems. Even under ext4, it was still pretty rare and only, say, 1 out of 100 imap logins. And ext3 performance on the indexes partition so far has been just fine, so I don't plan on switching back to ext4 -- though if anyone has any experience with putting indexes on reiserfs and/or xfs versus ext3, I'd love to hear your thoughts. I've also seen a couple of these in the past few days (on beta4, not repo version -- haven't been running repo version long enough to say if it'd do the same): Mar 31 21:52:54 imap(mail@box): Error: fdatasync(/mail/username/mail@box/Maildir/dovecot-uidlist) failed: Input/output error Mar 31 21:52:54 imap(mail@box): Error: Raw backtrace: /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0 [0xb77c0b71] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0 [0xb77c0bef] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0(i_error+0) [0xb77c0ea8] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin_to+0x9a9) [0xb7837ca9] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin+0x56) [0xb7837d56] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(maildir_sync_index_begin+0x51) [0xb78734d1] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0 [0xb78716eb] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_force+0x4d) [0xb78719bd] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(maildir_uidlist_lookup+0x96) [0xb7877646] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0 [0xb787215a] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(maildir_sync_index+0x7f0) [0xb78729d0] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0 [0xb78715b6] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0x162) [0xb7871b92] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x39) [0xb7815759] -> dovecot/imap [mail@box 215.108.28.102 UID](imap_sync_init+0x54) [0x805efa4] -> dovecot/imap [mail@box 215.108.28.102 UID](cmd_sync_delayed+0x223) [0x805f2a3] -> dovecot/imap [mail@box 215.108.28.102 UID](client_output+0xb6) [0x8056de6] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0 [0xb77d5d4a] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xf5) [0xb77cd1d5] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0(io_loop_run+0x30) [0xb77cc220] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0(master_service_run+0x2a) [0xb77b9e1a] -> dovecot/imap [mail@box 215.108.28.102 UID](main+0x1c5) [0x805f8e5] -> /lib/libc.so.6(__libc_start_main+0xe5) [0xb764d455] -> dovecot/imap [mail@box 215.108.28.102 UID] [0x804e621] Mar 31 21:52:54 master: Error: service(imap): child 4500 killed with signal 6 (core dumps disabled) In 4 days of beta testing with a fair number of users, I've seen maybe 4 of these backtraces total, so not exactly a big issue. These are all super minor things. Everything's been fantastic so far.

3 6

[Dovecot] Dovecot v2.0.rc2 (875598cd7e26): Core dump upon client login
by Thomas Leuxner 20 Jul '10

20 Jul '10

Latest HG dies upon client login. Rolling back to 2.0.rc2 (7dd7adba1c9e) restores functionality. Dump attached. Jul 17 07:31:04 spectre dovecot: master: Dovecot v2.0.rc2 (875598cd7e26) starting up […] Jul 17 07:32:06 spectre dovecot: master: Error: service(imap): child 29169 killed with signal 11 (core dumped) GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu"... warning: Can't read pathname for load map: Input/output error. Reading symbols from /usr/lib/dovecot/libdovecot-storage.so.0...Reading symbols from /usr/lib/debug/usr/lib/dovecot/libdovecot-storage.so.0.0.0...done. done. Loaded symbols for /usr/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/lib/dovecot/libdovecot.so.0...Reading symbols from /usr/lib/debug/usr/lib/dovecot/libdovecot.so.0.0.0...done. done. Loaded symbols for /usr/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/librt.so.1...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux-x86-64.so.2...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib/libpthread.so.0...done. Loaded symbols for /lib/libpthread.so.0 Reading symbols from /usr/lib/dovecot/modules/lib01_acl_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib01_acl_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib01_acl_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib02_imap_acl_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib10_quota_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib10_quota_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib10_quota_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib11_imap_quota_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib15_notify_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib15_notify_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib15_notify_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib20_mail_log_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib20_mail_log_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib20_mail_log_plugin.so Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. [New process 29301] #0 notify_transaction_commit (t=0x1ae5a40, changes_r=0x7fff65c9cd10) at notify-storage.c:164 164 notify-storage.c: No such file or directory. in notify-storage.c #0 notify_transaction_commit (t=0x1ae5a40, changes_r=0x7fff65c9cd10) at notify-storage.c:164 lt = (struct notify_transaction_context *) 0x0 #1 0x00007f4518416aed in mailbox_transaction_commit_get_changes (_t=<value optimized out>, changes_r=0x7fff65c9cd10) at mail-storage.c:1194 _data_stack_cur_id = 4 t = (struct mailbox_transaction_context *) 0x1ae5a40 ret = <value optimized out> #2 0x00007f4518416b26 in mailbox_transaction_commit (t=0x28) at mail-storage.c:1178 changes = {pool = 0xbc1, uid_validity = 7456, saved_uids = {arr = {buffer = 0x1ae4960, element_size = 0}, v = 0x1ae4960, v_modifiable = 0x1ae4960}, ignored_modseq_changes = 28149240} ret = <value optimized out> #3 0x0000000000412823 in imap_fetch_deinit (ctx=0x1ad85e0) at imap-fetch.c:568 handler = (const struct imap_fetch_context_handler *) 0x1aedca8 #4 0x000000000040a823 in cmd_fetch_finish (ctx=0x28) at cmd-fetch.c:144 cmd = (struct client_command_context *) 0x1ad83b8 tagged_reply = 0x419c38 "OK Fetch completed." ok_message = 0x419c38 "OK Fetch completed." #5 0x000000000040ad0a in cmd_fetch (cmd=0x1ad83b8) at cmd-fetch.c:236 client = <value optimized out> ctx = (struct imap_fetch_context *) 0x1ad85e0 args = (const struct imap_arg *) 0x1adac10 next_arg = <value optimized out> list_arg = (const struct imap_arg *) 0x7f45181b8c0d search_args = (struct mail_search_args *) 0x1ae49b8 messageset = 0x1adad00 "5195:*" ret = <value optimized out> #6 0x000000000041035c in client_command_input (cmd=0x1ad83b8) at imap-client.c:652 client = (struct client *) 0x1ad7c58 command = <value optimized out> __FUNCTION__ = "client_command_input" #7 0x000000000041040d in client_command_input (cmd=0x1ad83b8) at imap-client.c:702 client = (struct client *) 0x1ad7c58 command = (struct command *) 0x8 __FUNCTION__ = "client_command_input" #8 0x0000000000410585 in client_handle_input (client=0x1ad7c58) at imap-client.c:743 _data_stack_cur_id = 3 ret = 66 remove_io = <value optimized out> handled_commands = false __FUNCTION__ = "client_handle_input" #9 0x0000000000410fb2 in client_input (client=0x1ad7c58) at imap-client.c:794 cmd = <value optimized out> output = (struct ostream *) 0x1ad8238 bytes = <value optimized out> __FUNCTION__ = "client_input" #10 0x00007f45181b3ceb in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:212 ctx = (struct ioloop_handler_context *) 0x1aab7d0 event = (const struct epoll_event *) 0x1aab840 list = (struct io_list *) 0x1ad8310 io = (struct io_file *) 0x1ad82d0 tv = {tv_sec = 1799, tv_usec = 999737} t_id = 2 msecs = <value optimized out> ret = 1 call = <value optimized out> #11 0x00007f45181b2e68 in io_loop_run (ioloop=0x1aab5c0) at ioloop.c:350 No locals. #12 0x00007f45181a27d3 in master_service_run (service=0x1aab490, callback=0x28) at master-service.c:495 No locals. #13 0x0000000000419171 in main (argc=1, argv=0x1aab370) at main.c:358 service_flags = <value optimized out> storage_service_flags = <value optimized out> postlogin_socket_path = 0x0 username = 0x0 c = <value optimized out> set_roots = {0x41c360, 0x0} # dovecot -n (older HG) # 2.0.rc2 (7dd7adba1c9e): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 5.0.5 auth_verbose = yes mail_location = mdbox:~/mdbox mail_plugins = acl quota managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date spamtest spamtestplus virustest namespace { hidden = no inbox = yes location = prefix = separator = / type = private } namespace { list = yes location = maildir:/var/vmail/public:LAYOUT=fs:INDEX=~/public prefix = Public/ separator = / subscriptions = no type = public } passdb { args = username_format=%u /var/vmail/auth.d/%d/passwd driver = passwd-file } plugin { acl = vfile:/var/vmail/conf.d/%d/acls:cache_secs=300 mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename quota = dict:user::file:%h/mdbox/dovecot-quota quota_rule = *:storage=1GB quota_rule2 = Trash:storage=+10%% sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /var/vmail/conf.d/%d/sieve } protocols = imap lmtp service auth-worker { user = doveauth } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = doveauth } service imap-login { inet_listener imap { address = 1.2.3.4 port = 143 } inet_listener imaps { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/host_domain_tld.crt ssl_key = </etc/ssl/private/host_domain_tld.key syslog_facility = local1 userdb { args = username_format=%u /var/vmail/auth.d/%d/passwd driver = passwd-file } verbose_proctitle = yes protocol lmtp { mail_plugins = $mail_plugins sieve } protocol imap { mail_plugins = $mail_plugins imap_acl imap_quota mail_log notify }

2 18

[Dovecot] About Logging
by Henrique Fernandes 20 Jul '10

20 Jul '10

It is possible to make dovecot do not log any request from a determined host? Because, we gonna use ldirectord for foward request and etc and the ldirectord makes an connecting every 2 seconds to find out if the server is ok, and also make a login in imap and pop3 to check this service as well. Is there any how to make dovecot do not log entries for a determined host ? The logs get too many info that we don need! Any ideias ? Thanks! * *i have sent a msg like this, but i got no answer i thought i might have not deliver into the mailist! I am sorry if it already have it!* *[]'sf.rique

2 4

[Dovecot] Unknown column username in where clause
by Daniel Luttermann 20 Jul '10

20 Jul '10

Version: Dovecot 2.0 rc2 I'm testing Dovecot with MySQL quotas but I get always this error for incoming mails: tux dovecot: lmtp(4928): Error: user testuser(a)dlutt.de: Auth USER lookup failed tux dovecot: auth: Error: mysql: Query failed, retrying: Unknown column 'username' in 'where clause' I dont' know where the field "username" should come from because I don't use this field (or query). The relevant files are: dovecot-sql.conf.ext ==================== password_query = SELECT userid AS user, password, \ home AS userdb_home, uid AS userdb_uid, gid AS userdb_gid, \ concat('*:bytes=', quota_bytes) as userdb_quota_rule \ FROM users WHERE userid = '%u' auth-sql.conf.ext ================= passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } userdb { driver = prefetch } userdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } 90-quota.conf ============= plugin { quota = dict:user::proxy::quota quota_rule = *:storage=0 } dovecot-dict-sql.conf.ext ========================= map { pattern = priv/quota/storage table = quota username_field = userid value_field = bytes } map { pattern = priv/quota/messages table = quota username_field = userid value_field = messages } I've grepped through all config files but I can't find any (active) query which uses the above "where username=...". The quota db gets correctly updated if an user logs in so the problem only exists during mail delivery. My SQL tables were crated as follows: CREATE TABLE IF NOT EXISTS `users` ( `userid` varchar(100) NOT NULL, `password` varchar(64) NOT NULL, `home` varchar(255) NOT NULL, `uid` int(11) NOT NULL, `gid` int(11) NOT NULL, `quota_bytes` varchar(10) NOT NULL, PRIMARY KEY (`userid`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1; CREATE TABLE IF NOT EXISTS `quota` ( `userid` varchar(100) NOT NULL, `bytes` bigint(20) NOT NULL default '0', `messages` int(11) NOT NULL default '0', PRIMARY KEY (`userid`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1; -- Daniel

3 4

[Dovecot] Dovecot 1.1 migration to 1.2
by Claudio Prono 20 Jul '10

20 Jul '10

Hello all, Here is my dovecot 1.1 conf: # 1.1.3: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot-err.log info_log_path: /var/log/dovecot-inf.log protocols: imap imaps pop3 pop3s 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: 51 last_valid_uid: 51 first_valid_gid: 51 last_valid_gid: 51 mail_location: maildir:/var/mail/virtual/%d/%u 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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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 imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %Mf auth default: passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: maildir quota: maildir:user quota quota_warning: storage=80%% /usr/bin/quota_warning.sh 80 quota_warning2: storage=90%% /usr/bin/quota_warning.sh 90 quota_warning3: storage=99%% /usr/bin/quota_warning.sh 90 Now, is out the OpenSuSE 11.3, and i have noticed it uses dovecot 1.2.11. My question is: there is any difference or incompatibility in my configuration for the 1.2 serie of dovecot? Any hint for a clean migration to the new dovecot? Cordially, Claudio Prono. -- -------------------------------------------------------------------------------- Claudio Prono OPST System Developer Gsm: +39-349-54.33.258 @PSS Srl Tel: +39-011-32.72.100 Via San Bernardino, 17 Fax: +39-011-32.46.497 10141 Torino - ITALY http://atpss.net/disclaimer -------------------------------------------------------------------------------- PGP Key - http://keys.atpss.net/c_prono.asc

4 4

[Dovecot] namespace trouble
by Kevin Faulkner 20 Jul '10

20 Jul '10

I am having some trouble with dovecot 1.2.12 and some namespace issues, or at least that's what I think is the issue. I setup a virtual mailhosting using mysql and postfix. I can receive email and send email without a problem, but when I use mutt to sign in to dovecot, I can't list any Folders, it see's INBOX but it doesn't see any mail. I generally try to not post my problems online, but I searched around on the Internet and I couldn't find anything similar to this issue. I also used kmail to connect to the and it is able to see the mail, but when I can't create any folders. mutt connecting option: mutt set spoolfile=imaps://server.here/INBOX." Here is the mutt debug (mutt -d 3) 4< a0001 OK Capability completed. 4< * LIST (\Noselect) "." "" 4< a0002 OK List completed. 4> a0003 STATUS "Drafts" (MESSAGES) a0004 SELECT "INBOX" 4< a0003 NO Unknown namespace. 4< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) dovecot.conf (part of it, tell me if you want more) mail_location = maildir:/home/vmail/%d/%n/Maildir log_path = /var/log/dovecot.log namespace private { separator = . prefix = INBOX. inbox = yes hidden = no list = yes } listen = * protocol imap { } protocol pop3 { } protocol lda { log_path = /home/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster@.com mail_plugins = sieve global_script_path = /home/vmail/globalsieverc } auth default { mechanisms = plain userdb static { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } Thank you Very much.

3 2

[Dovecot] Unable to get Dovecot LDA/deliver working
by Frank van Amsterdam 20 Jul '10

20 Jul '10

I want to setup Dovecot LDA, but I don't understand what I'm doing anymore. I have to note that I'm a Linux beginner. I've been trying now for several months and I'm about to give up. Till so far I'm having no result. :-( My current setup is done as described at http://www.linuxmail.info. We use Postfix 2.3.3 (with Postgrey, Spamassassin and ClamAV), Dovecot 1.2.11 and OpenLDAP 2.4.1 on CentOS 5.5. All incoming e-mail are delivered by Postfix in the users' maildir. We use this as a base for SOGo, our groupware solution and it runs smoothly. I have to setup a new mailserver, because we're standardising on Debian. My employer wants to have new functions like out-of-office-replies and forwarding. I want to make use of sieve. Unfortunately I don't know anyone who can help me. My problem is that I don't understand how the delivery process is working. I've read much documentation from Postfix and Dovecot, but I find it too difficult to understand. What do I understand? I know that I have to make changes in /etc/dovecot, /etc/postfix/main.cf and /etc/postfix/master.cf as described at http://wiki.dovecot.org/LDA. /etc/dovecot.conf # OS: Linux 2.6.18-028stab064.7 i686 CentOS release 5.5 (Final) reiserfs base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s managesieve ssl: no version_ignore: yes 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_executable(managesieve): /usr/libexec/dovecot/managesieve-login mail_location: maildir:/home/vmail/%u/Maildir 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_executable(managesieve): /usr/libexec/dovecot/managesieve 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 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): managesieve_logout_format(default): bytes=%i/%o managesieve_logout_format(imap): bytes=%i/%o managesieve_logout_format(pop3): bytes=%i/%o managesieve_logout_format(managesieve): bytes ( in=%i : out=%o ) lda: postmaster_address: postmaster(a)domain.nl mail_plugins: cmusieve mail_plugin_dir: /usr/lib/dovecot/lda deliver_log_format: msgid=%m: %$ -- FROM=%f SUBJECT=%s log_path: /var/log/dovecot-deliver.log info_log_path: /var/log/dovecot-deliver.log syslog_facility: mail sendmail_path: /usr/lib/sendmail rejection_subject: Rejected: %s rejection_reason: Your message to <%t> was automatically rejected:%n%r auth_socket_path: /usr/local/var/run/dovecot-auth-master auth default: mechanisms: plain login username_format: %Lu passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: static args: uid=500 gid=500 home=/home/vmail/%u 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 group: vmail plugin: sieve: /var/sieve-scripts/%u.sieve sieve_dir: %h/sieve sieve_global_dir: /var/lib/dovecot/sieve/global/ /etc/postfix/main.cf virtual_mailbox_domains = /etc/postfix/domains ## Plain text file with the domains virtual_mailbox_base = /home/vmail virtual_mailbox_maps = ldap:/etc/postfix/ldap-users.cf virtual_alias_maps = ldap:/etc/postfix/ldap-groups.cf virtual_uid_maps = static:500 virtual_gid_maps = static:500 dovecot_destination_recipient_limit = 1 #virtual_transport = dovecot ## Commented out to deliver by Postfix /etc/postfix/ldap-users.cf server_host = localhost search_base = dc=domain,dc=com version = 3 query_filter = (&(objectclass=mailUser)(mail=%s)) result_attribute = uid result_format = %s/Maildir/ /etc/postfix/ldap-groups.cf server_host = localhost search_base = dc=domain,dc=com version = 3 query_filter = (&(objectclass=mailGroup)(mail=%s)) leaf_result_attribute = mail special_result_attribute = member /etc/postfix/master.cf dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -d <username> I hope someone can help me, because many people on the internet say that it is easy. If anyone needs more information or anyone can help me, please contact me. Best, Frank --- LS: I know that I'm using Hotmail, but I want to post this anonymously.

4 6

[Dovecot] How to install sieve
by Carsten Laun-De Lellis 19 Jul '10

19 Jul '10

Hi all I do have a problem. I have an installation on opensuse 11.2 with postfix, amavis, spamassassin and dovecot 1.2.9 with a mysql authtentication backend. Everything works fine. I want now to install sieve, but i failed all the time. I downloaded dovecot-1.2-sieve-0.1.17 and followed the installation how-to. First when i tried to ./configure the installation i was always asked for dovecot-config. I managed this problem with a symlink. But when i try to run make i always got the following error message. I would appreciate any help. Kind regards, Carsten Laun-De Lellis ../../sieve-result.h:143: error: expected declaration specifiers or â...â before âboolâ In file included from cmd-vacation.c:27: ../../sieve-message.h:18: warning: empty declaration ../../sieve-message.h:27: error: expected declaration specifiers before âpool_tâ In file included from cmd-vacation.c:29: ext-vacation-common.h:13: error: storage class specified for parameter âvacation_commandâ ext-vacation-common.h:19: error: storage class specified for parameter âvacation_operationâ ext-vacation-common.h:23: error: storage class specified for parameter âvacation_extensionâ cmd-vacation.c:37: error: storage class specified for parameter âvacation_days_tagâ cmd-vacation.c:38: error: storage class specified for parameter âvacation_subject_tagâ cmd-vacation.c:39: error: storage class specified for parameter âvacation_from_tagâ cmd-vacation.c:40: error: storage class specified for parameter âvacation_addresses_tagâ cmd-vacation.c:41: error: storage class specified for parameter âvacation_mime_tagâ cmd-vacation.c:42: error: storage class specified for parameter âvacation_handle_tagâ cmd-vacation.c:53: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_registeredâ cmd-vacation.c:56: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_pre_validateâ cmd-vacation.c:58: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validateâ cmd-vacation.c:60: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_generateâ cmd-vacation.c:63: error: parameter âvacation_commandâ is initialized cmd-vacation.c:63: error: redefinition of parameter âvacation_commandâ ext-vacation-common.h:13: note: previous definition of âvacation_commandâ was here cmd-vacation.c:66: error: âFALSEâ undeclared (first use in this function) cmd-vacation.c:66: error: (Each undeclared identifier is reported only once cmd-vacation.c:66: error: for each function it appears in.) cmd-vacation.c:66: warning: excess elements in struct initializer cmd-vacation.c:66: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:66: warning: excess elements in struct initializer cmd-vacation.c:66: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:67: error: âcmd_vacation_registeredâ undeclared (first use in this function) cmd-vacation.c:67: warning: excess elements in struct initializer cmd-vacation.c:67: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:68: error: âcmd_vacation_pre_validateâ undeclared (first use in this function) cmd-vacation.c:68: warning: excess elements in struct initializer cmd-vacation.c:68: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:69: error: âcmd_vacation_validateâ undeclared (first use in this function) cmd-vacation.c:69: warning: excess elements in struct initializer cmd-vacation.c:69: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:70: error: âcmd_vacation_generateâ undeclared (first use in this function) cmd-vacation.c:70: warning: excess elements in struct initializer cmd-vacation.c:70: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:72: warning: excess elements in struct initializer cmd-vacation.c:72: warning: (near initialization for âvacation_commandâ) cmd-vacation.c:80: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_number_tagâ cmd-vacation.c:83: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_string_tagâ cmd-vacation.c:86: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_stringlist_tagâ cmd-vacation.c:89: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_mime_tagâ cmd-vacation.c:95: error: storage class specified for parameter âvacation_days_tagâ cmd-vacation.c:95: error: parameter âvacation_days_tagâ is initialized cmd-vacation.c:95: error: redefinition of parameter âvacation_days_tagâ cmd-vacation.c:37: note: previous definition of âvacation_days_tagâ was here cmd-vacation.c:97: warning: excess elements in struct initializer cmd-vacation.c:97: warning: (near initialization for âvacation_days_tagâ) cmd-vacation.c:98: error: âcmd_vacation_validate_number_tagâ undeclared (first use in this function) cmd-vacation.c:98: warning: excess elements in struct initializer cmd-vacation.c:98: warning: (near initialization for âvacation_days_tagâ) cmd-vacation.c:99: warning: excess elements in struct initializer cmd-vacation.c:99: warning: (near initialization for âvacation_days_tagâ) cmd-vacation.c:99: warning: excess elements in struct initializer cmd-vacation.c:99: warning: (near initialization for âvacation_days_tagâ) cmd-vacation.c:99: warning: excess elements in struct initializer cmd-vacation.c:99: warning: (near initialization for âvacation_days_tagâ) cmd-vacation.c:102: error: storage class specified for parameter âvacation_subject_tagâ cmd-vacation.c:102: error: parameter âvacation_subject_tagâ is initialized cmd-vacation.c:102: error: redefinition of parameter âvacation_subject_tagâ cmd-vacation.c:38: note: previous definition of âvacation_subject_tagâ was here cmd-vacation.c:104: warning: excess elements in struct initializer cmd-vacation.c:104: warning: (near initialization for âvacation_subject_tagâ) cmd-vacation.c:105: error: âcmd_vacation_validate_string_tagâ undeclared (first use in this function) cmd-vacation.c:105: warning: excess elements in struct initializer cmd-vacation.c:105: warning: (near initialization for âvacation_subject_tagâ) cmd-vacation.c:106: warning: excess elements in struct initializer cmd-vacation.c:106: warning: (near initialization for âvacation_subject_tagâ) cmd-vacation.c:106: warning: excess elements in struct initializer cmd-vacation.c:106: warning: (near initialization for âvacation_subject_tagâ) cmd-vacation.c:107: warning: excess elements in struct initializer cmd-vacation.c:107: warning: (near initialization for âvacation_subject_tagâ) cmd-vacation.c:109: error: storage class specified for parameter âvacation_from_tagâ cmd-vacation.c:109: error: parameter âvacation_from_tagâ is initialized cmd-vacation.c:109: error: redefinition of parameter âvacation_from_tagâ cmd-vacation.c:39: note: previous definition of âvacation_from_tagâ was here cmd-vacation.c:111: warning: excess elements in struct initializer cmd-vacation.c:111: warning: (near initialization for âvacation_from_tagâ) cmd-vacation.c:112: warning: excess elements in struct initializer cmd-vacation.c:112: warning: (near initialization for âvacation_from_tagâ) cmd-vacation.c:113: warning: excess elements in struct initializer cmd-vacation.c:113: warning: (near initialization for âvacation_from_tagâ) cmd-vacation.c:113: warning: excess elements in struct initializer cmd-vacation.c:113: warning: (near initialization for âvacation_from_tagâ) cmd-vacation.c:114: warning: excess elements in struct initializer cmd-vacation.c:114: warning: (near initialization for âvacation_from_tagâ) cmd-vacation.c:116: error: storage class specified for parameter âvacation_addresses_tagâ cmd-vacation.c:116: error: parameter âvacation_addresses_tagâ is initialized cmd-vacation.c:116: error: redefinition of parameter âvacation_addresses_tagâ cmd-vacation.c:40: note: previous definition of âvacation_addresses_tagâ was here cmd-vacation.c:118: warning: excess elements in struct initializer cmd-vacation.c:118: warning: (near initialization for âvacation_addresses_tagâ) cmd-vacation.c:119: error: âcmd_vacation_validate_stringlist_tagâ undeclared (first use in this function) cmd-vacation.c:119: warning: excess elements in struct initializer cmd-vacation.c:119: warning: (near initialization for âvacation_addresses_tagâ) cmd-vacation.c:120: warning: excess elements in struct initializer cmd-vacation.c:120: warning: (near initialization for âvacation_addresses_tagâ) cmd-vacation.c:120: warning: excess elements in struct initializer cmd-vacation.c:120: warning: (near initialization for âvacation_addresses_tagâ) cmd-vacation.c:121: warning: excess elements in struct initializer cmd-vacation.c:121: warning: (near initialization for âvacation_addresses_tagâ) cmd-vacation.c:123: error: storage class specified for parameter âvacation_mime_tagâ cmd-vacation.c:123: error: parameter âvacation_mime_tagâ is initialized cmd-vacation.c:123: error: redefinition of parameter âvacation_mime_tagâ cmd-vacation.c:41: note: previous definition of âvacation_mime_tagâ was here cmd-vacation.c:125: warning: excess elements in struct initializer cmd-vacation.c:125: warning: (near initialization for âvacation_mime_tagâ) cmd-vacation.c:126: error: âcmd_vacation_validate_mime_tagâ undeclared (first use in this function) cmd-vacation.c:126: warning: excess elements in struct initializer cmd-vacation.c:126: warning: (near initialization for âvacation_mime_tagâ) cmd-vacation.c:127: warning: excess elements in struct initializer cmd-vacation.c:127: warning: (near initialization for âvacation_mime_tagâ) cmd-vacation.c:127: warning: excess elements in struct initializer cmd-vacation.c:127: warning: (near initialization for âvacation_mime_tagâ) cmd-vacation.c:128: warning: excess elements in struct initializer cmd-vacation.c:128: warning: (near initialization for âvacation_mime_tagâ) cmd-vacation.c:130: error: storage class specified for parameter âvacation_handle_tagâ cmd-vacation.c:130: error: parameter âvacation_handle_tagâ is initialized cmd-vacation.c:130: error: redefinition of parameter âvacation_handle_tagâ cmd-vacation.c:42: note: previous definition of âvacation_handle_tagâ was here cmd-vacation.c:132: warning: excess elements in struct initializer cmd-vacation.c:132: warning: (near initialization for âvacation_handle_tagâ) cmd-vacation.c:133: warning: excess elements in struct initializer cmd-vacation.c:133: warning: (near initialization for âvacation_handle_tagâ) cmd-vacation.c:134: warning: excess elements in struct initializer cmd-vacation.c:134: warning: (near initialization for âvacation_handle_tagâ) cmd-vacation.c:134: warning: excess elements in struct initializer cmd-vacation.c:134: warning: (near initialization for âvacation_handle_tagâ) cmd-vacation.c:135: warning: excess elements in struct initializer cmd-vacation.c:135: warning: (near initialization for âvacation_handle_tagâ) cmd-vacation.c:139: warning: empty declaration cmd-vacation.c:152: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âext_vacation_operation_dumpâ cmd-vacation.c:155: error: expected declaration specifiers or â...â before âsieve_size_tâ cmd-vacation.c:155: error: storage class specified for parameter âext_vacation_operation_executeâ cmd-vacation.c:157: error: parameter âvacation_operationâ is initialized cmd-vacation.c:157: error: redefinition of parameter âvacation_operationâ ext-vacation-common.h:19: note: previous definition of âvacation_operationâ was here cmd-vacation.c:161: error: âext_vacation_operation_dumpâ undeclared (first use in this function) cmd-vacation.c:161: warning: excess elements in struct initializer cmd-vacation.c:161: warning: (near initialization for âvacation_operationâ) cmd-vacation.c:163: warning: excess elements in struct initializer cmd-vacation.c:163: warning: (near initialization for âvacation_operationâ) cmd-vacation.c:174: error: storage class specified for parameter âact_vacation_check_duplicateâ cmd-vacation.c:181: error: expected declaration specifiers or â...â before âboolâ cmd-vacation.c:181: error: storage class specified for parameter âact_vacation_printâ cmd-vacation.c:182: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âact_vacation_commitâ cmd-vacation.c:188: error: parameter âact_vacationâ is initialized cmd-vacation.c:191: warning: excess elements in struct initializer cmd-vacation.c:191: warning: (near initialization for âact_vacationâ) cmd-vacation.c:192: warning: excess elements in struct initializer cmd-vacation.c:192: warning: (near initialization for âact_vacationâ) cmd-vacation.c:193: warning: excess elements in struct initializer cmd-vacation.c:193: warning: (near initialization for âact_vacationâ) cmd-vacation.c:194: warning: excess elements in struct initializer cmd-vacation.c:194: warning: (near initialization for âact_vacationâ) cmd-vacation.c:195: warning: excess elements in struct initializer cmd-vacation.c:195: warning: (near initialization for âact_vacationâ) cmd-vacation.c:195: warning: excess elements in struct initializer cmd-vacation.c:195: warning: (near initialization for âact_vacationâ) cmd-vacation.c:196: error: âact_vacation_commitâ undeclared (first use in this function) cmd-vacation.c:196: warning: excess elements in struct initializer cmd-vacation.c:196: warning: (near initialization for âact_vacationâ) cmd-vacation.c:198: warning: excess elements in struct initializer cmd-vacation.c:198: warning: (near initialization for âact_vacationâ) cmd-vacation.c:205: error: expected specifier-qualifier-list before âsieve_number_tâ cmd-vacation.c:202: warning: empty declaration cmd-vacation.c:219: error: expected specifier-qualifier-list before âstring_tâ cmd-vacation.c:218: warning: empty declaration cmd-vacation.c:231: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_number_tagâ cmd-vacation.c:259: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_string_tagâ cmd-vacation.c:321: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_stringlist_tagâ cmd-vacation.c:344: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validate_mime_tagâ cmd-vacation.c:363: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_registeredâ cmd-vacation.c:387: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_pre_validateâ cmd-vacation.c:401: error: storage class specified for parameter â_handle_empty_subjectâ cmd-vacation.c:401: error: parameter â_handle_empty_subjectâ is initialized cmd-vacation.c:402: error: storage class specified for parameter â_handle_empty_fromâ cmd-vacation.c:402: error: parameter â_handle_empty_fromâ is initialized cmd-vacation.c:403: error: storage class specified for parameter â_handle_mime_enabledâ cmd-vacation.c:403: error: parameter â_handle_mime_enabledâ is initialized cmd-vacation.c:404: error: storage class specified for parameter â_handle_mime_disabledâ cmd-vacation.c:404: error: parameter â_handle_mime_disabledâ is initialized cmd-vacation.c:406: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_validateâ cmd-vacation.c:459: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âcmd_vacation_generateâ cmd-vacation.c:484: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âext_vacation_operation_dumpâ cmd-vacation.c:544: error: expected declaration specifiers or â...â before âsieve_size_tâ cmd-vacation.c:545: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â{â token cmd-vacation.c:715: error: expected â;â, â,â or â)â before âATTR_UNUSEDâ cmd-vacation.c:734: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â{â token cmd-vacation.c:754: error: expected â;â, â,â or â)â before âATTR_UNUSEDâ cmd-vacation.c:775: error: storage class specified for parameter â_list_headersâ cmd-vacation.c:775: error: parameter â_list_headersâ is initialized cmd-vacation.c:776: warning: initialization from incompatible pointer type cmd-vacation.c:777: warning: excess elements in scalar initializer cmd-vacation.c:777: warning: (near initialization for â_list_headersâ) cmd-vacation.c:778: warning: excess elements in scalar initializer cmd-vacation.c:778: warning: (near initialization for â_list_headersâ) cmd-vacation.c:779: warning: excess elements in scalar initializer cmd-vacation.c:779: warning: (near initialization for â_list_headersâ) cmd-vacation.c:780: warning: excess elements in scalar initializer cmd-vacation.c:780: warning: (near initialization for â_list_headersâ) cmd-vacation.c:781: warning: excess elements in scalar initializer cmd-vacation.c:781: warning: (near initialization for â_list_headersâ) cmd-vacation.c:782: warning: excess elements in scalar initializer cmd-vacation.c:782: warning: (near initialization for â_list_headersâ) cmd-vacation.c:784: warning: excess elements in scalar initializer cmd-vacation.c:784: warning: (near initialization for â_list_headersâ) cmd-vacation.c:789: error: storage class specified for parameter â_my_address_headersâ cmd-vacation.c:789: error: parameter â_my_address_headersâ is initialized cmd-vacation.c:790: warning: initialization from incompatible pointer type cmd-vacation.c:791: warning: excess elements in scalar initializer cmd-vacation.c:791: warning: (near initialization for â_my_address_headersâ) cmd-vacation.c:792: warning: excess elements in scalar initializer cmd-vacation.c:792: warning: (near initialization for â_my_address_headersâ) cmd-vacation.c:793: warning: excess elements in scalar initializer cmd-vacation.c:793: warning: (near initialization for â_my_address_headersâ) cmd-vacation.c:794: warning: excess elements in scalar initializer cmd-vacation.c:794: warning: (near initialization for â_my_address_headersâ) cmd-vacation.c:795: warning: excess elements in scalar initializer cmd-vacation.c:795: warning: (near initialization for â_my_address_headersâ) cmd-vacation.c:797: warning: excess elements in scalar initializer cmd-vacation.c:797: warning: (near initialization for â_my_address_headersâ) cmd-vacation.c:799: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â_is_system_addressâ cmd-vacation.c:819: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â_contains_my_addressâ cmd-vacation.c:857: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â_contains_8bitâ cmd-vacation.c:868: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âact_vacation_sendâ cmd-vacation.c:975: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â{â token cmd-vacation.c:987: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âact_vacation_commitâ ../../rfc2822.h:33: error: old-style parameter declarations in prototyped function definition cmd-vacation.c:1144: error: expected â{â at end of input make[5]: *** [cmd-vacation.lo] Error 1 make[5]: Leaving directory `/download/dovecot-1.2-sieve-0.1.17/src/lib-sieve/plugins/vacation' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/download/dovecot-1.2-sieve-0.1.17/src/lib-sieve/plugins' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/download/dovecot-1.2-sieve-0.1.17/src/lib-sieve' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/download/dovecot-1.2-sieve-0.1.17/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/download/dovecot-1.2-sieve-0.1.17' make: *** [all] Error 2 Mit freundlichem Gruß Carsten Laun-De Lellis Dipl.-Ing. Elektrotechnik Certified Information Systems Auditor (CISA) Hauptstrasse 13 D-67705 Trippstadt Phone: +49 (6306) 992140 Mobile: +49 (151) 27530865 email: carsten.laun-delellis(a)delellis.net

1 0

[Dovecot] Deleting Index Files and Expire Tool
by Tom Goerger 19 Jul '10

19 Jul '10

Hi, In order to periodically deal with corrupted index files in Dovecot, we routinely will remove a users .imap folder in order to have the indexes rebuild. This hasn't ever caused a problem previously. However, removing the user's index files seems to break the ability of the expire plugin to update the expire stamp correctly, or expunge mail from the user folder. This seems logical, with the reliance of expire on the index.cache files. In testing, actually emptying the trash (since we're only concerned about Trash folders) resets the mailbox to a degree that the expire tool functions properly again. My question is, is there a better way to handle corrupted cache files? Is there a more graceful way to rebuild these using Dovecot tools? Or is there a more specific index file that can be removed, rather than removing the entire hierarchy? We're using Dovecot 1.1.6, on Solaris 10. -- Tom Goerger University of Minnesota - Internet Services

2 3

Re: [Dovecot] SSL / TLS Problem
by Leander S. 19 Jul '10

19 Jul '10

Thanks for your reply. What do you mean by "pipe" See, I can even connect via the console from the outside: |Notebook [~]$ openssl s_client -CApath ~/.cert/XYZ.com/ -connect XYZ.com:993 CONNECTED(00000003) depth=0 /C=DE/ST=BW/L=City/O=HomeServer GmbH/OU=WebHosting/CN=XYZ.com/emailAddress=admin@XYZ.com verify error:num=18:self signed certificate verify return:1 depth=0 /C=DE/ST=BW/L=City/O=HomeServer GmbH/OU=WebHosting/CN=XYZ.com/emailAddress=admin@XYZ.com verify return:1 --- Certificate chain 0 s:/C=DE/ST=BW/L=City/O=HomeServer GmbH/OU=WebHosting/CN=XYZ.com/emailAddress=admin@XYZ.com i:/C=DE/ST=BW/L=City/O=HomeServer GmbH/OU=WebHosting/CN=XYZ.com/emailAddress=admin@XYZ.com --- Server certificate -----BEGIN CERTIFICATE----- MIIC6TCCAlKgAwIBAgIJAN4Jfaj9QgEhMA0GCSqGSIb3DQEBBQUAMIGqMQswCQYD VQQGEwJERTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMREwDwYDVQQHEwhO ZXVicm9ubjEWMBQGA1UEChMNTmV0T2NlYW4gR21iSDETMBEGA1UECxMKV2ViSG9z dGluZzEYMBYGA1UEAxMPc2VydmVyLm5ldG9jZWFuMSQwIgYJKoZIhvcNAQkBFhVh ZG1pbkBzZXJ2ZXIubmV0b2NlYW4wHhcNMTAwNzExMTgwMzQ4WhcNMzAwNzA2MTgw MzQ4WjCBqjELMAkGA1UEBhMCREUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVy ZzERMA8GA1UEBxMITmV1YnJvbm4xFjAUBgNVBAoTDU5ldE9jZWFuIEdtYkgxEzAR BgNVBAsTCldlYkhvc3RpbmcxGDAWBgNVBAMTD3NlcnZlci5uZXRvY2VhbjEkMCIG CSqGSIb3DQEJARYVYWRtaW5Ac2VydmVyLm5ldG9jZWFuMIGfMA0GCSqGSIb3DQEB AQUAA4GNADCBiQKBgQDFiBWAJ893Ocm4dooDHHkNRZcvC4N5qjfx1wywoS2DlnV4 GwBQPYcyewx5ptcjqq863r3rvHhbNeJbcnh8jNATTxto8r2NkadwccXw4LtqpfAS A2dhuYt8zKhiI2tlfZNCzSzDmqid4NuxKiNQGNB6OU6/x2vp0ZFTwstIr7TMAwID AQABoxUwEzARBglghkgBhvhCAQEEBAMCBkAwDQYJKoZIhvcNAQEFBQADgYEAtlPa GQ4Weyi9vlIDLL4PgGsNk4sR4Ca2gbYLTd5HaSkww+BKIfz1OkFEmsNozNSo19PJ WaOp7exCN23j5Z/+qfZSGgUAelJHxRJ0Mc8YmtTuLKaNHxWYBJit3T3n1lbuFENe vdh8oCo6GKjjm7RkbkEvTvdzrOdztXZt3Ij4gLE= -----END CERTIFICATE----- subject=/C=DE/ST=BW/L=City/O=HomeServer GmbH/OU=WebHosting/CN=XYZ.com/emailAddress=admin@XYZ.com issuer=/C=DE/ST=BW/L=City/O=HomeServer GmbH/OU=WebHosting/CN=XYZ.com/emailAddress=admin@XYZ.com --- No client certificate CA names sent --- SSL handshake has read 1313 bytes and written 325 bytes --- New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-SHA Server public key is 1024 bit Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1 Cipher : DHE-RSA-AES256-SHA Session-ID: 54DC3526DB721308D460CBAF21D562958D34ED146332F0B4ACBE9E1311633ED1 Session-ID-ctx: Master-Key: 1BCB1FA49855FC38ACB52C2CD8D54594C006116220D66FA0E74F68663AFE3FC09086B9BFB1FE0E515681A2E0DC7C1AFC Key-Arg : None Start Time: 1278952607 Timeout : 300 (sec) Verify return code: 18 (self signed certificate) --- * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=CRAM-MD5] NetOcean MailSystem ^C Notebook [~]$| Am 12.07.10 19:11, schrieb Daniel Petre: > dude, whats the pipe at the end of the mail.key location? > >> It's always the same when it fails ... >> >> >> And this is how my dovecot.conf looks like: >> >> [...] >> >> |## >> ## SSL settings >> ## >> ssl = yes >> ssl_cert_file = /etc/ssl/mail/mail.cert >> ssl_key_file = /etc/ssl/mail/mail.key| >> >> [...] >> >> >> Thank you

4 6

[Dovecot] Plugins/Virtual for save searches & last 30 days incomming Email
by No body ist Perfect 19 Jul '10

19 Jul '10

Hello! How can i configure the virtal-dovecot (virtal folder) file for search the complete Mailbox for email not older as 30 Days ? Thanks a lot

2 1

[Dovecot] Proxy IMAP/POP/ManageSieve/SMTP in a large cluster enviroment
by Aliet Santiesteban Sifontes 19 Jul '10

19 Jul '10

Hi to all in the list, we are trying to do some tests lab for a large scale mail system having this requirements: - Scale to maybe 1million users(Only for testing). - Server side filters. - User quotas. - High concurrency. - High performance and High Availability. We plan to test this using RHEL5 and maybe RHEL6. As a storage we are going to use an HP EVA 8400 FC(8 GB/s) We defined this functional roles. 1- Outgoing SMTP gateway servers. - Load balanced with Piranha LVS using Direct Routing. - ( n servers)RHEL5/6 using Postfix Latest version Amavisd-new Clamav Spamassasin maybe some other filters. 2- Incomming SMTP gateway servers. - Load balanced with Piranha LVS using Direct Routing. - RHEL5/6 using Postfix Latest version Amavisd-new Clamav Spamassasin( n servers) maybe some other filters. 3- Webmail Cluster farm. - Load balanced with Piranha LVS using Direct Routing. - ( n servers)RHEL5/6 using RHCS Active/Active. Apache2 PHP5 Horde. 4- Openldap load balanced openldap cluster. - Load balanced with Piranha LVS using Direct Routing. - ( n servers)RHEL5/6 using Openldap. 5- IMAP/POP/ManageSieve/SMTP Proxy or Director. - Load balanced with Piranha LVS using Direct Routing. - ( n servers)RHEL5/6 using Dovecot - Postfix(Director or Proxy). 6- Mail backend. - ( n servers)RHEL5/6 using Dovecot. Now for functional role 6 "Mail Backend" we have some dilemmas. - Recommended scalable filesystem to use for such scenario(Clustered or not). -GFS2?? We have very bad experiences with GFS1 and maildir, GFS2 doesn't seems to improve this also. Using some techniques for session afinity with a backend server seems to help with the locking problems of GFS and the cache. Using GFS many IMAP SMTP servers can in parallel write or read to user mailboxes, if GFS can perform well we prefer this, will have to proxy o use director for the cache problem. - Ext4, Ext3 well tested with many setups but only one backend server can access one ext4 lun, so we have to proxy a user always to a ip backend address or VIP in a case of failure cluster software has to move the server to another node, the cluster service is formed by a IP Address and one or many Luns wich moves from node to node in a case of failure. - Recommended scalable method for partition divition. - Directory Hashing(How it actually works the theory behind this), we see the wiki but we need to understand the theory to balance the directory structure. - Using some criteria ex Lun1(a-h users), Lun2(i-m users).... - Proxy or Director is a must for a Clustered Filsystem or for the solution of a user belonging to one server. - In case we use a Proxy with dovecot we know we can use it with IMAP/POP but are not sure for ManageSieve and more important for SMTP. The question is, how can we proxy for the same user IMAP/POP/ManageSieve and SMTP delivery to mailbox at the same time, can the incoming mail gateways send the email to the proxy servers and dovecot proxy the request for smtp or lmtp appply the same proxy criteria that uses for the protocols IMAP and POP and send the email to the correct backend server and this server do the final delivery?? I mean proxy all the protocols for a user IMAP/POP/SMTP-LMTP?? Any example... Right now we have doubts on this stuff, we are really going to appreciate any help or advice on this... best regards

4 4

[Dovecot] Haha wow, thats freakin cool... mdbox
by Brandon Lamb 19 Jul '10

19 Jul '10

It didnt really click until I had a "ls -ald *" on watch while I moved messages around folders using mdbox... I moved about 200 first to an Archive folder, and scratched my head wondering why i didnt see any new m.* files being created after the move. So then I moved some 5k other messages from other folders to my archive folder... Then it dawned on me, how damn cool, the data never changes, dovecot just updates its index of what folder the message is in?! That is awesome! Also, I ended up answering my own question on the 2m mdbox_rotate_size, if a 10 meg email comes through it will write a 10 meg file, so thats cool too.

4 4

[Dovecot] dsync segmentation fault
by Brandon Lamb 19 Jul '10

19 Jul '10

dsync -u brandon(a)olypen.com mirror mdbox~/mdbox Segmentation fault Took me 3 tries before I noticed the missing colon after mdbox

2 3

[Dovecot] mdbox, mdbox_rotate_size 2m default
by Brandon Lamb 19 Jul '10

19 Jul '10

Anyone else test using different values? Was 2M chosen as a default based on anything specific? Is there any kind of known range where performance starts to go downhill if its greater than x or less than y? Im curious if there would be any obvious reason why I shouldnt set it to 5-10 megs

2 1

[Dovecot] users can not login
by Daminto Lie 19 Jul '10

19 Jul '10

Hi, I was wondering if I could get some help here. Recently, I decided I want to move from Windows XP Pro OS to a Linux OS such as Ubuntu. I am new to Linux OS but willing to learn. I have installed Ubuntu Server 10.04, Apache2, MySQL5, PHPMyAdmin, Postfix, DoveCot and Squirrelmail on my server. I have checked them all and they are all up and running at the moment. Now, what I am trying to do here is to add a couple of users and see whether they can login to squirrelmail. The result is none of those two users are able to login. I went to check the mail.log and the error message is as follows Ubuntu-MailServer dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=<david.keith>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured My silly question is I do not quite understand what the above error means. How do i enable users to login and test to see if they can send and receive emails. Users can login via squirrelmail. Any help would be greatly appreciated.

2 1

[Dovecot] pam needs root with 2.0rc2 on Solaris?
by Laurent Blume 19 Jul '10

19 Jul '10

Hello all, I have a question using PAM to authenticate on Solaris 10, with 2.0rc2. I need to set the user for auth-worker to root, else it will return "Unknown user". Is that expected? I'm using PAM, so why does it need access to /etc/shadow? TIA! Laurent service auth-worker { # Auth worker process is run as root by default, so that it can access # /etc/shadow. If this isn't necessary, the user should be changed to # $default_internal_user. user = root #user = dovecot } Jul 18 09:59:31 tiphaine dovecot: [ID 583609 mail.info] auth: pam(user,127.0.0.1): unknown user

2 1

[Dovecot] how configure dovecot for not case sensitive login
by Wilberth Perez 19 Jul '10

19 Jul '10

Any knows how can say to dovecot that Login = user and Login = User are the same? Thanks.

2 3

[Dovecot] director service and managesieve
by Xavier Pons 19 Jul '10

19 Jul '10

Hi, the director service have implemented any support for managesieve-login?. I get the error: managesieve-login: Error: proxy: host not given: user=<xxx>, method=PLAIN, ... any workaround? thanks Xavier

2 1

[Dovecot] lda with sieve crash
by Michal Hlavinka 19 Jul '10

19 Jul '10

Hi, my colleague found a crash in dovecot, while he was experimenting with configuration for using dovecot with fetchmail. Backtrace can be found here: http://pastebin.com/XQZqYBpH Let me know if you need any other info. Michal # doveconf -n # 20100716 (26936bdd3801+): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32 auth_debug = yes auth_verbose = yes info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_debug = yes mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator- i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date spamtest spamtestplus virustest mbox_write_locks = fcntl namespace { hidden = no inbox = yes list = yes location = maildir:~/Maildir prefix = INBOX. separator = . subscriptions = yes type = private } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } verbose_ssl = yes protocol lmtp { mail_plugins = sieve } protocol lda { info_log_path = /var/log/dovecot-deliver.log log_path = /var/log/dovecot-deliver-errors.log mail_plugins = sieve } -------------------------- .dovecot.sieve: require ["fileinto", "regex"]; if header :contains "X-BeenThere" "bugzilla(a)redhat.com" { fileinto "redhat.bugzilla"; } elsif header :contains "List-Id" "scm-commits.lists.fedoraproject.org" { fileinto "fedora.fedora-extras-commits"; } elsif header :contains "List-Id" "package-review.lists.fedoraproject.org" { fileinto "fedora.fedora-package-review"; } elsif header :contains "List-Id" "devel.lists.fedoraproject.org" { fileinto "fedora.fedora-devel-list"; } elsif header :contains "List-Id" "brno-list.redhat.com" { fileinto "redhat.brno-list"; } elsif header :regex "Subject" "^Cron <jkastner@" { fileinto "cron"; } else { # The rest goes into INBOX # default is "implicit keep", we do it explicitly here keep; } -------------------------------

2 2

[Dovecot] Arghh, dovecot-2 and lda
by Brandon Lamb 18 Jul '10

18 Jul '10

I cannot seem to get exim/lda working... In my exim log i just see these 2010-07-18 11:51:08 1OaYOJ-0003Vn-2P == brandon(a)olypen.com R=router_pop T=dovecot_deliver defer (2): No such file or directory: failed to chdir to maildir:~/maildir:INDEX=~/maildir/dovecot-index Now I have all the debugging on as far as i can tell, and exim is obviously being returned some value from dovecot because it knows about the maildir that i return from sql, but yet there is zero being logged in debug or anything else. If I run the dovecot-lda from the command line with the same then it works and i get logs entered command = /usr/local/libexec/dovecot/ -e -k -f "$sender_address" -d "$local_part@$domain" -m "$acl_m1" I am returning a home and mail with userdb, the directory does exist, owned by mail.mail... Im stumped dovecot -n # 2.0.rc2: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian squeeze/sid auth_cache_negative_ttl = 30 s auth_cache_size = 4096 auth_cache_ttl = 30 s auth_debug = yes auth_default_realm = olypen.com auth_mechanisms = plain login auth_username_format = %Lu auth_verbose = yes auth_worker_max_count = 60 base_dir = /var/run/dovecot debug_log_path = /var/log/dovecot/debug.log default_client_limit = 1024 default_internal_user = mail default_login_user = mail default_vsz_limit = 1073741824 deliver_log_format = %s from %f %$ dict { expire = mysql:/etc/dovecot/conf.d/dovecot-dict-expire.conf.ext } disable_plaintext_auth = no dotlock_use_excl = yes first_valid_gid = 8 first_valid_uid = 8 info_log_path = /var/log/dovecot/info.log last_valid_gid = 8 last_valid_uid = 8 log_path = /var/log/dovecot/dovecot.log log_timestamp = %Y-%m-%d %H:%M:%S login_log_format = %s login_log_format_elements = (%u) (%r) mail_access_groups = mail mail_debug = yes mail_fsync = never mail_gid = 8 mail_location = maildir:~/:INDEX=~/dovecot-index mail_log_prefix = %Ls <%u>: mail_max_userip_connections = 4 mail_plugins = quota mail_privileged_group = mail mail_uid = 8 mailbox_idle_check_interval = 60 s maildir_very_dirty_syncs = yes mdbox_rotate_size = 10485760 namespace { hidden = no inbox = yes location = prefix = separator = / type = private } passdb { args = /etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } plugin { auth_socket_path = /var/run/dovecot/auth-master autocreate = Trash autocreate2 = Spam autocreate3 = Spam.Delivered autocreate4 = Spam.Removed autocreate5 = Sent autocreate6 = Drafts autosubscribe = Trash autosubscribe2 = Sent expire = Trash 30d expire2 = Trash/* 30d expire3 = Spam 14d expire4 = Spam/Removed 6h expire5 = Spam/Delivered 2d expire6 = Deleted* 30d expire7 = Archive 30d expire_dict = proxy::expire qoute_rule5 = Spam.Delivered:ignore quota = maildir:User quota quota_rule2 = Trash:ignore quota_rule3 = Deleted Items:ignore quota_rule4 = Spam:ignore quota_rule6 = Spam.Removed:ignore quota_warning = storage=95%% /etc/dovecot/quota-warning.sh 95 quota_warning2 = storage=80%% /etc/dovecot/quota-warning.sh 80 trash = /etc/dovecot/conf.d/dovecot-trash.conf.ext zlib_save = bz2 zlib_save_level = 6 } protocols = imap pop3 service auth { executable = /usr/local/libexec/dovecot/auth unix_listener auth-client { group = mail mode = 0666 user = mail } unix_listener auth-master { group = mail mode = 0666 user = mail } unix_listener auth-userdb { group = mail mode = 0666 user = mail } vsz_limit = 536870912 } service imap-login { client_limit = 512 executable = /usr/local/libexec/dovecot/imap-login process_limit = 20 process_min_avail = 4 service_count = 0 user = dovecot vsz_limit = 134217728 } service imap { drop_priv_before_exec = no executable = /usr/local/libexec/dovecot/imap vsz_limit = 536870912 } service pop3-login { client_limit = 512 executable = /usr/local/libexec/dovecot/pop3-login process_limit = 20 process_min_avail = 4 service_count = 0 user = dovecot vsz_limit = 134217728 } service pop3 { drop_priv_before_exec = no executable = /usr/local/libexec/dovecot/pop3 vsz_limit = 536870912 } ssl_cert = </etc/dovecot/ssl/dovecot-cert.pem ssl_key = </etc/dovecot/ssl/dovecot-key.pem userdb { driver = prefetch } userdb { args = /etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } valid_chroot_dirs = /mail verbose_proctitle = yes protocol lda { auth_socket_path = /var/run/dovecot/auth-userdb info_log_path = /var/log/dovecot/deliver.log lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /var/log/dovecot/deliver.log mail_fsync = optimized mail_plugin_dir = /usr/local/lib/dovecot/lda mail_plugins = $mail_plugins postmaster_address = postmaster(a)olypen.com quota_full_tempfail = yes rejection_reason = Your message to <%t> with subject of <%s> was automatically rejected:%n%r rejection_subject = Mailbox Full: %s sendmail_path = /usr/sbin/exim } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep imap_id_log = * imap_logout_format = bytes=%i/%o imap_max_line_length = 65536 mail_max_userip_connections = 20 mail_plugin_dir = /usr/local/lib/dovecot/imap mail_plugins = $mail_plugins imap_quota autocreate } protocol pop3 { mail_max_userip_connections = 2 mail_plugin_dir = /usr/local/lib/dovecot/pop3 mail_plugins = $mail_plugins pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_enable_last = no pop3_lock_session = no pop3_logout_format = retr=%r/%b, del=%d/%m, size=%s pop3_no_flag_updates = yes pop3_reuse_xuidl = no pop3_uidl_format = %08Xu%08Xv }

2 14

[Dovecot] Questions about dbox (sdbox?), mdbox
by Brandon Lamb 18 Jul '10

18 Jul '10

Hello, So ive spent the last 45 minutes or so searching the list for dbox stuff, but Im not seeing anything real definitive. My question is basically whether the dbox format is ready for production environment, is sdbox or mdbox more stable/ready than the other or does it matter? What are people's experience/review with running this format (and if you reply can you tell me which one you're using). Is there any docs/wiki page for migrating from maildir -> dbox? Searching for "dbox" on the wiki only returns two results, and only one is actually for dbox. What I have (maildir format) is working, but who doesnt like shiny new toys? =P I have ~450gigs / 14k pop accounts I would have to migrate. Oh thats another question, I have seen "hybrid" throw around, can I take this to mean dbox/mdbox/both support both formats, maybe only new mail goes into the dbox stuff? And if so (or even if not) is there any way to actually convert from maildir to dbox? If anyone has any links that I cant seem to find by consulting the oracle (google) that would be fantastic =)

3 12

[Dovecot] dovecot 2.0rc2 Cannot delete a folder with Thunderbird (delete, not move to Trash)
by Sven Kirmess 17 Jul '10

17 Jul '10

With Thunderbird 3.1 I can now "delete" a folder which moves it to Trash. But I cannot remove the folder in Trash. The following is from the Thunderbird log file: 248[6814c00]: 8103800:imap.kzone.ch:A:SendData: 64 rename "test10" "Trash/test10" 248[6814c00]: 8103800:imap.kzone.ch:A:CreateNewLineFromSocket: 64 OK Rename completed. 248[6814c00]: 8103800:imap.kzone.ch:S-Trash/test10:SendData: 70 delete "Trash/test10/" 248[6814c00]: 8103800:imap.kzone.ch:S-Trash/test10:CreateNewLineFromSocket: 70 NO Invalid mailbox name: Trash/test10/ I can confirm that dovecot cannot delete a folder if the name is ended with a slash. b list "Trash/x" * * LIST (\HasNoChildren) "/" "Trash/xx" * LIST (\HasNoChildren) "/" "Trash/x" b OK List completed. c delete "Trash/x" c OK Delete completed. d delete "Trash/xx/" d NO Invalid mailbox name: Trash/xx/ Let me know if that's a Thunderbird bug and I'll open a ticket with Thunderbird. (But I hope it's a dovecot bug as dovecot bugs actually get fixed, fast. :-) $ dovecot -n # 2.0.rc2: /etc/opt/dovecot/dovecot/dovecot.conf # OS: SunOS 5.10 i86pc zfs first_valid_uid = 100 mail_location = mdbox:/l/dovecot/%u/dbox passdb { driver = pam } protocols = imap service imap-login { inet_listener imap { port = 0 } } service imap { vsz_limit = 1073741824 } ssl = required ssl_cert = </etc/opt/dovecot/dovecot/certs/dovecot.pem ssl_key = </etc/opt/dovecot/dovecot/private/dovecot.pem userdb { driver = passwd } verbose_proctitle = yes

2 2

[Dovecot] mdbox expunge purge question
by Daniel Luttermann 17 Jul '10

17 Jul '10

Hi, I'm testing Dovecot 2.0rc2 with mdbox mail format and I'm not sure what this exactly means: http://wiki2.dovecot.org/MailboxFormat/dbox Quote from wiki page: ===== Expunging a message only decreases the message's refcount. The space is later freed in "purge" step. This may be done automatically within the session or later in a nightly cronjob when there's less disk I/O. ===== So this means that even if a user deletes a mail the space gets only freed if I run "doveadm purge" manually or an user requests this over his mail client? When the expunge plugin is used the deleted mails are stored in a special mailbox in the users mailbox so it's needed to use the expire plugin too if this should be done automatically? Is it recommend to run "doveadm purge" periodically if mdbox is used? Btw: when I try to run doveadm -Dv expunge -u testuser(a)dlutt.de mailbox Trash savedbefore 30d for example I get such an error: doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm doveadm(root): Error: dlopen(/usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so) failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_lookup doveadm(root): Error: dlopen(/usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so) failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module Plugin expire or expunge is not currently enabled in Dovecot's config. Thanks for any hints. Daniel

3 4

[Dovecot] sieve make test fails
by Eray Aslan 17 Jul '10

17 Jul '10

I am trying out the sieve plugin (commit 843ba8e66e1b) and dovecot-2.0.rc2. Given $ ./configure --with-dovecot=../dovecot-2.0.rc2/ --with-managesieve make test fails with: testuser@linode /tmp/dovecot-2-0-pigeonhole-843ba8e66e1b $ make test testsuite(testuser): Error: user testuser: Initialization failed: mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/testuser testsuite(testuser): Fatal: Invalid user settings. Refer to server log for more information. make: *** [tests/testsuite.svtest] Error 89 /home/testuser and /home/testuser/sieve exists. What am I missing? -- Eray

2 3

[Dovecot] dovecot 2.0 (latest on website), client workarounds?
by Brandon Lamb 17 Jul '10

17 Jul '10

What are the current valid imap_client_workarounds and pop3_client_workarounds? I had a tb-folder one, and outlook-idle i imap, and i kept getting errors. The only one that would seem to not give an error was imap.conf: imap_client_workarounds = delay-newmail pop3.conf: pop3_client_workarounds = outlook-no-nuls oe-ns-eoh

2 1

[Dovecot] Dovecot sieve support
by Daniel L. Miller 17 Jul '10

17 Jul '10

Is sieve going to be merged into the main server source, or at this time is it going to remain an external patch? -- Daniel

4 5

[Dovecot] dovecot 2.0.beta6 dies when I try to delete a folder with thunderbird
by Sven Kirmess 16 Jul '10

16 Jul '10

When I try to delete a folder with Thunderbird 3.1 I get the following log entry and the folder is not deleted. Filesystem is ZFS. Jun 27 15:32:36 azati dovecot: [ID 583609 mail.error] master: Error: service(imap): child 18215 killed with signal 11 (core not dumped - set drop_priv_before_exec=yes) Jun 27 15:32:36 azati dovecot: [ID 583609 mail.error] master: Error: service(imap): child 18213 killed with signal 11 (core not dumped - set drop_priv_before_exec=yes) # 2.0.beta6: /etc/opt/dovecot/dovecot/dovecot.conf # OS: SunOS 5.10 i86pc zfs first_valid_uid = 100 mail_location = mdbox:/l/dovecot/%u/dbox namespace { inbox = yes location = prefix = separator = / type = private } passdb { driver = pam } protocols = imap service imap-login { inet_listener imap { port = 0 } } service imap { vsz_limit = 1073741824 } ssl = required ssl_cert = </etc/opt/dovecot/dovecot/certs/dovecot.pem ssl_key = </etc/opt/dovecot/dovecot/private/dovecot.pem userdb { driver = passwd } verbose_proctitle = yes

2 11

[Dovecot] Dovecot 2.0.rc2 fd passing regression
by Tomi Vainio 16 Jul '10

16 Jul '10

Hi, I've tried to compile 2.0.rc2 and configure fails this which used to work or at least last time when I tried beta4. > configure:19606: checking whether fd passing works > configure:19680: cc -o conftest -xO4 -I./src/lib ./src/lib/fdpass.c -I/usr/sfw/include/mysql -I/usr/sfw/include -R/usr/sfw/lib:/usr/lib/sasl -L/usr/sfw/lib -L/usr/lib/sasl conftest.c -lrt -lnsl -lsocket -lrt >&5 > ./src/lib/fdpass.c: > "./src/lib/fdpass.c", line 100: incomplete struct/union/enum const_iovec: iov > "./src/lib/fdpass.c", line 109: improper member use: iov_base > "./src/lib/fdpass.c", line 109: warning: assignment type mismatch: > pointer to void "=" pointer to const void > "./src/lib/fdpass.c", line 110: improper member use: iov_len > cc: acomp failed for ./src/lib/fdpass.c > conftest.c: Tomppa

2 1

[Dovecot] Temporary files
by Timo Sirainen 16 Jul '10

16 Jul '10

In v1.0 .. v1.1 deliver was writing incoming >128k mail to /tmp file (to avoid reading it all into memory). In v1.2 I moved it to user's home directory. This slowed deliveries for NFS users. Also people with filesystem quota had trouble since now user required twice as much available quota to save a message. The FS quota problem was "solved" by having quota-fs plugin change the default temp file path to /tmp. So why was the move made in the first place? Because a) some people had small (maybe ramfs) /tmp and Dovecot was eating it all up and b) to avoid any potential security issues with storing per-user files to a shared directory. I'm now thinking about a new setting (mail_temp_dir?) for v2.0 where these temp files would be stored (lda, lmtp, some others in future). Maybe the b) problem isn't that huge, so maybe there doesn't need to be a way to store them to user's home. So that leaves a) problem. Maybe the setting could default to /var/tmp instead of /tmp? That probably has more disk space available usually. (I hope /var/tmp is available everywhere?) Any thoughts?

11 17

[Dovecot] Ok, I've given up
by Chuck McManis 15 Jul '10

15 Jul '10

Sigh, In the interest of moving forward on this project I've given up trying to get Dovecot to support mailboxes, rather I've tweaked around in qmail and had it deliver into a mail directory on a disk, that isn't NFS mounted. That got me past the various locking complaints and "operation not supported" on home directories that were mounted from the NetApp filer. Going as vanilla as possible I've managed to both send an email that qmail delivered and fetch the email with my 3 test clients (Eudora, Thunderbird, and Evolution) (I know they are, in a sense, all variations on a theme but MUA monoculture seems to be inevitable these days). So a few questions for the other esteemed system operators here if you know the answer I'd love to hear it. Question 1) Are my user's passwords safe from prying eyes? First, part of this effort was to move off of an APOP infrastructure into something more secure against password eavesdropping. To that end I've configured Dovecot with simply: protocols = pop3 service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } Note that there is NO port = 110 listener and yet Dovecot seems to listen there anyway. My question, can I be sure that it is not accepting non-SSL based connections? Attempts to use plaintext on 110 were rebuffed so that seems to be the case. My intent is that if my user is using this in an airport they won't give away their email password to a bad guy who is sniffing all the packets. Question 2) Is there any way to run dovecot from tcpserver ? One of the things I like is the program tcpserver. I like it because I can simply "not allow" large chunks of the internet to connect at all to certain ports. (I use this for SSH in particular since all the kids love throwing dictionary attacks around). I'd like to give my POP3 ports equivalent protection. I also like the logging facilities of the supervise / multilog service. To use this I'd need Dovecot to accept the connection handed to it, and not do the whole setsid daemon thing since tcpserver will start another one if needed. I can send the logging out to stderr (thanks!) and get the logging stuff but still wondering about the 'hand you a connection.' --Chuck

11 22

[Dovecot] How to Upgrade to dovecot 2.0rc2 from dovecot 1.x
by Wilberth Perez 15 Jul '10

15 Jul '10

Hi: Exists some instructions for /upgrade dovecot/ v1./2 to dovecot v2.0rc2 ? Cheers. /

2 1

[Dovecot] IMAP super user
by Thiago Henrique 15 Jul '10

15 Jul '10

Hello, Is there any directive in Dovecot similar to 'imap_admins' of Cyrus? I plan to migrate from Cyrus to Dovecot. But I need a admin user which is able to obtain information about the quotas of common users. Thank you. -- []'s Thiago Henrique Network Administration Digirati Networks K8 Networks

3 3

[Dovecot] help on migrating some old Maildirs
by Leonardo Rodrigues 15 Jul '10

15 Jul '10

Hi, i need to restore some old mail backups from a system i wasnt the admin. Emails are on Maildir, which i'm using on the actual server, so should be no big deal. I'm just thinking of copying files from the folders i need, from the old backup, to the specific dirs on the actual system. buuuut, watching the backup, i noticed that LOTS of files on the Maildirs do not have the S= parameters on its name nor W=. For example: 1230230396.V80bI4e007fM790805.correio.domain.com.br:2, 1230463524.V80bI4e0080M837823.correio.domain.com.br:2, 1230571206.V80bI4e0081M519106.correio.domain.com.br:2, 1231170098.V80bI4e0083M519957.correio.domain.com.br:2, 1231682500.V80bI4e0084M584988.correio.domain.com.br:2, files from the actual system looks like: 1278311553.M754372P13693.correio.domain.com.br,S=5742,W=5864:2, 1278668323.M110437P31421.correio.domain.com.br,S=4489,W=4590:2, 1278311669.M981814P13835.correio.domain.com.br,S=7404,W=7563:2, 1278669074.M556000P31506.correio.domain.com.br,S=4397,W=4504:2, i've already tested copying those files to a current Maildir and it works just fine, no problem at all on that. There's no problem on the restore of those messages itself. Anyway, my questions are .... 1) do the lack of S= and W= parameters will negatively impact on something ? Quota calculation comes to my head about that .... as i'll have to restore several thousands of messages, i'm worried about negative impacts on anything 2) is there any way of having dovecot to calculating the S= and W= parameters and renaming those files and, thus, avoiding some negative impact caused by the lack of them ? i'm using dovecot 1.2.11 ...... thanks ! -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, NÃO mandem email gertrudes(a)solutti.com.br My SPAMTRAP, do not email it

3 7

[Dovecot] Director proxy timeout
by Brad Davidson 15 Jul '10

15 Jul '10

Timo, Is the director proxy inactivity timeout configurable? I just recently attempted to switch our production webmail's imapproxy system to use a pool of two directors and ran into problems with it apparently disconnecting them unexpectedly. I don't believe that it IDLEs, I think it just UNSELECTs to reset the state and then keeps the connection open until it's used again, or until a configurable delay has elapsed, after which it logs out on its own. I've got the imapproxy inactivity delay set to 300 seconds, and it seems like the director is disconnecting them before that time is up. I haven't had the same problem when imapproxy connects directly to the backend servers, which are running 1.2.12. On the webmail system, imapproxy is logging a LOT of: Jul 11 21:10:21 cc-mailapps1 in.imapproxyd[28477]: IMAP_Line_Read(): connection closed prematurely. The director shows: Jul 11 21:10:14 cc-popmap7p dovecot: imap-login: proxy(jacintha): disconnecting 172.25.142.164 The backend server shows: Jul 11 21:10:14 cc-popmap2p dovecot: imap: user=<jacintha>, rip=10.142.0.162, pid=8629: Connection closed bytes=855/46109 Roundcube seems to handle the disconnects pretty badly, leaving a bunch of Apache processes chewing up CPU time. -Brad

3 7

[Dovecot] pigeonhole, regex, UTF-8
by Trever L. Adams 14 Jul '10

14 Jul '10

Hello, I am just learning about pigeonhole and thinking of using it. I see that regex doesn't supportf UTF-8. Any particular reason for this? If it is a library problem is the library, have you looked at tre? I am using it in a project (I am using it in wchar_t mode because elsewhere all date is converted to wchar_t). It does work with UTF-8. Thanks, Trever

3 3

[Dovecot] Problems with Dovecot + imaptest
by Wilberth Perez 14 Jul '10

14 Jul '10

Hi everyone: I´m trying to install imaptest on my server with Solaris 10, however i´m found in this moment with some instalations problems. Anyone knows what libraries need have installed ? ./configure --with-dovecot=/opt/setup/dovecot-1.2.10 make Error: make all-recursive make[1]: Entering directory `/opt/setup/imaptest-20100630' Making all in src make[2]: Entering directory `/opt/setup/imaptest-20100630/src' if gcc -DHAVE_CONFIG_H -I. -I. -I.. -MT checkpoint.o -MD -MP -MF ".deps/checkpoint.Tpo" -c -o checkpoint.o checkpoint.c; \ then mv -f ".deps/checkpoint.Tpo" ".deps/checkpoint.Po"; else rm -f ".deps/checkpoint.Tpo"; exit 1; fi checkpoint.c:3:17: lib.h: No such file or directory checkpoint.c:4:17: str.h: No such file or directory checkpoint.c:5:19: array.h: No such file or directory checkpoint.c:6:24: mail-types.h: No such file or directory In file included from checkpoint.c:7: settings.h:4:21: network.h: No such file or directory In file included from checkpoint.c:7: settings.h:40: error: syntax error before "ARRAY_TYPE" settings.h:40: warning: no semicolon at end of struct or union settings.h:46: error: syntax error before "random_states" settings.h:46: warning: data definition has no type or storage class settings.h:47: error: syntax error before "no_tracking" settings.h:47: warning: data definition has no type or storage class settings.h:51: error: syntax error before '}' token In file included from checkpoint.c:8: mailbox.h:4:29: seq-range-array.h: No such file or directory In file included from checkpoint.c:8: mailbox.h:13: error: syntax error before "struct" mailbox.h:13: warning: data definition has no type or storage class mailbox.h:18: error: syntax error before "uoff_t" mailbox.h:18: warning: no semicolon at end of struct or union mailbox.h:22: error: syntax error before "sent_date" mailbox.h:22: warning: data definition has no type or storage class mailbox.h:25: error: syntax error before "headers" mailbox.h:25: warning: data definition has no type or storage class mailbox.h:28: error: syntax error before "const" mailbox.h:28: warning: data definition has no type or storage class mailbox.h:32: error: syntax error before "uint32_t" mailbox.h:32: warning: no semicolon at end of struct or union mailbox.h:37: error: syntax error before "ref0_timeout" mailbox.h:37: warning: data definition has no type or storage class mailbox.h:39: error: syntax error before "internaldate" mailbox.h:39: warning: data definition has no type or storage class mailbox.h:48: error: syntax error before ':' token mailbox.h:69: error: syntax error before "uint64_t" mailbox.h:69: warning: no semicolon at end of struct or union mailbox.h:72: error: syntax error before '*' token mailbox.h:72: warning: data definition has no type or storage class mailbox.h:81: error: syntax error before '}' token mailbox.h:82: error: syntax error before "struct" mailbox.h:82: warning: data definition has no type or storage class mailbox.h:100: error: syntax error before "struct" mailbox.h:100: warning: data definition has no type or storage class mailbox.h:107: error: syntax error before "uint64_t" mailbox.h:107: warning: no semicolon at end of struct or union mailbox.h:110: error: syntax error before "struct" mailbox.h:110: warning: data definition has no type or storage class mailbox.h:112: warning: parameter names (without types) in function declaration mailbox.h:112: warning: data definition has no type or storage class mailbox.h:114: error: syntax error before "messages" mailbox.h:114: warning: data definition has no type or storage class mailbox.h:137: error: syntax error before "time_t" mailbox.h:137: warning: no semicolon at end of struct or union mailbox.h:140: error: syntax error before "struct" mailbox.h:140: warning: data definition has no type or storage class mailbox.h:141: error: syntax error before "struct" mailbox.h:141: warning: data definition has no type or storage class mailbox.h:144: error: syntax error before "expunged_uids" mailbox.h:144: warning: data definition has no type or storage class mailbox.h:150: error: syntax error before ':' token mailbox.h:151: error: syntax error before ':' token mailbox.h:152: error: syntax error before ':' token mailbox.h:153: error: syntax error before ':' token mailbox.h:154: error: syntax error before ':' token mailbox.h:163: error: syntax error before "uint64_t" mailbox.h:163: warning: no semicolon at end of struct or union mailbox.h:168: error: syntax error before "keywords" mailbox.h:168: warning: data definition has no type or storage class mailbox.h:171: warning: parameter names (without types) in function declaration mailbox.h:171: warning: data definition has no type or storage class mailbox.h:173: error: syntax error before "messages" mailbox.h:173: warning: data definition has no type or storage class mailbox.h:177: error: syntax error before ':' token mailbox.h:178: error: syntax error before ':' token mailbox.h:191: error: syntax error before "mailbox_view_save_offline_cache" mailbox.h:191: warning: data definition has no type or storage class mailbox.h:196: error: syntax error before "mailbox_view_keyword_find" mailbox.h:197: warning: data definition has no type or storage class mailbox.h:210: warning: parameter has incomplete type mailbox.h:212: error: syntax error before '*' token mailbox.h:214: error: syntax error before '*' token mailbox.h:219: error: syntax error before "uint32_t" mailbox.h:221: error: syntax error before "uint32_t" mailbox.h:228: error: syntax error before "mailbox_global_get_sent_date" mailbox.h:229: error: syntax error before "time_t" mailbox.h:229: warning: data definition has no type or storage class mailbox.h:230: error: syntax error before "mailbox_global_get_subject_utf8" mailbox.h:232: warning: data definition has no type or storage class In file included from client.h:4, from checkpoint.c:9: client-state.h:73: warning: parameter has incomplete type client-state.h:78: error: syntax error before "do_rand" client-state.h:78: warning: data definition has no type or storage class client-state.h:79: error: syntax error before "do_rand_again" client-state.h:79: warning: data definition has no type or storage class client-state.h:81: error: syntax error before "bool" client-state.h:95: warning: parameter has incomplete type client-state.h:97: error: syntax error before "client_get_random_seq_range" client-state.h:98: error: syntax error before "ARRAY_TYPE" client-state.h:99: error: syntax error before "unsigned" client-state.h:103: warning: parameter has incomplete type In file included from checkpoint.c:9: client.h:27: error: `NULL' undeclared here (not in a function) client.h:27: error: initializer element is not constant client.h:27: error: (near initialization for `cap_names[4].name') client.h:27: error: initializer element is not constant client.h:27: error: (near initialization for `cap_names[4]') client.h:42: error: syntax error before "size_t" client.h:42: warning: no semicolon at end of struct or union client.h:54: error: syntax error before "append_offset" client.h:54: warning: data definition has no type or storage class client.h:55: error: syntax error before "literal_left" client.h:55: warning: data definition has no type or storage class client.h:63: error: syntax error before "struct" client.h:63: warning: data definition has no type or storage class client.h:69: error: syntax error before "highest_untagged_modseq" client.h:69: warning: data definition has no type or storage class client.h:78: error: syntax error before "last_io" client.h:78: warning: data definition has no type or storage class client.h:81: error: syntax error before ':' token client.h:82: error: syntax error before ':' token client.h:83: error: syntax error before ':' token client.h:84: error: syntax error before ':' token client.h:85: error: syntax error before ':' token client.h:86: error: syntax error before ':' token client.h:87: error: syntax error before ':' token client.h:88: error: syntax error before ':' token client.h:90: error: syntax error before "struct" client.h:90: warning: data definition has no type or storage class client.h:92: error: conflicting types for 'clients_count' settings.h:42: error: previous declaration of 'clients_count' was here client.h:94: error: syntax error before "clients" client.h:94: warning: data definition has no type or storage class client.h:95: error: syntax error before "stalled" client.h:95: warning: data definition has no type or storage class client.h:98: error: syntax error before "client_unref" client.h:98: error: syntax error before "bool" client.h:98: warning: data definition has no type or storage class client.h:114: error: syntax error before "ATTR_FORMAT" client.h:114: warning: data definition has no type or storage class client.h:116: error: syntax error before "ATTR_FORMAT" client.h:116: warning: data definition has no type or storage class client.h:118: error: syntax error before "ATTR_FORMAT" client.h:118: warning: data definition has no type or storage class checkpoint.c:22: error: syntax error before "ARRAY_DEFINE" checkpoint.c:22: warning: no semicolon at end of struct or union checkpoint.c:23: error: syntax error before "unsigned" checkpoint.c:23: warning: data definition has no type or storage class checkpoint.c:24: error: syntax error before '*' token checkpoint.c:24: warning: data definition has no type or storage class checkpoint.c:30: error: syntax error before ':' token checkpoint.c:31: error: syntax error before ':' token checkpoint.c: In function `keyword_map_update': checkpoint.c:41: error: dereferencing pointer to incomplete type checkpoint.c:42: error: dereferencing pointer to incomplete type checkpoint.c:42: warning: assignment makes pointer from integer without a cast checkpoint.c:43: error: dereferencing pointer to incomplete type checkpoint.c:43: warning: assignment makes pointer from integer without a cast checkpoint.c:50: error: dereferencing pointer to incomplete type checkpoint.c:53: error: dereferencing pointer to incomplete type checkpoint.c:56: error: dereferencing pointer to incomplete type checkpoint.c:58: error: dereferencing pointer to incomplete type checkpoint.c:59: error: dereferencing pointer to incomplete type checkpoint.c:59: warning: assignment makes pointer from integer without a cast checkpoint.c: At top level: checkpoint.c:65: error: syntax error before '*' token checkpoint.c: In function `keywords_remap': checkpoint.c:71: error: `dest' undeclared (first use in this function) checkpoint.c:71: error: (Each undeclared identifier is reported only once checkpoint.c:71: error: for each function it appears in.) checkpoint.c:71: error: `dest_size' undeclared (first use in this function) checkpoint.c:73: error: `ctx' undeclared (first use in this function) checkpoint.c:73: warning: assignment makes pointer from integer without a cast checkpoint.c:75: error: `src' undeclared (first use in this function) checkpoint.c: At top level: checkpoint.c:82: error: syntax error before '*' token checkpoint.c: In function `checkpoint_keywords_to_str': checkpoint.c:85: error: `string_t' undeclared (first use in this function) checkpoint.c:85: error: `str' undeclared (first use in this function) checkpoint.c:88: error: `ctx' undeclared (first use in this function) checkpoint.c:88: warning: assignment makes pointer from integer without a cast checkpoint.c:94: error: `bitmask' undeclared (first use in this function) checkpoint.c:100: warning: return makes pointer from integer without a cast checkpoint.c: In function `checkpoint_update': checkpoint.c:105: error: dereferencing pointer to incomplete type checkpoint.c:107: error: syntax error before '*' token checkpoint.c:108: error: `uint8_t' undeclared (first use in this function) checkpoint.c:108: error: `keywords_remapped' undeclared (first use in this function) checkpoint.c:109: error: storage size of 'this_flags' isn't known checkpoint.c:109: error: storage size of 'other_flags' isn't known checkpoint.c:114: error: dereferencing pointer to incomplete type checkpoint.c:114: warning: assignment makes pointer from integer without a cast checkpoint.c:115: error: dereferencing pointer to incomplete type checkpoint.c:116: error: dereferencing pointer to incomplete type checkpoint.c:116: error: `TRUE' undeclared (first use in this function) checkpoint.c:119: error: dereferencing pointer to incomplete type checkpoint.c:119: error: dereferencing pointer to incomplete type checkpoint.c:122: error: dereferencing pointer to incomplete type checkpoint.c:124: error: dereferencing pointer to incomplete type checkpoint.c:125: error: dereferencing pointer to incomplete type checkpoint.c:127: error: dereferencing pointer to incomplete type checkpoint.c:128: error: dereferencing pointer to incomplete type checkpoint.c:129: error: dereferencing pointer to incomplete type checkpoint.c:129: error: dereferencing pointer to incomplete type checkpoint.c:130: error: dereferencing pointer to incomplete type checkpoint.c:131: error: dereferencing pointer to incomplete type checkpoint.c:132: error: dereferencing pointer to incomplete type checkpoint.c:134: error: dereferencing pointer to incomplete type checkpoint.c:134: error: dereferencing pointer to incomplete type checkpoint.c:135: error: dereferencing pointer to incomplete type checkpoint.c:138: error: dereferencing pointer to incomplete type checkpoint.c:138: warning: assignment makes pointer from integer without a cast checkpoint.c:139: error: dereferencing pointer to incomplete type checkpoint.c:147: error: dereferencing pointer to incomplete type checkpoint.c:148: error: dereferencing pointer to incomplete type checkpoint.c:149: error: dereferencing pointer to incomplete type checkpoint.c:150: error: dereferencing pointer to incomplete type checkpoint.c:153: error: dereferencing pointer to incomplete type checkpoint.c:154: error: dereferencing pointer to incomplete type checkpoint.c:158: error: invalid use of undefined type `struct message_metadata_dynamic' checkpoint.c:158: error: dereferencing pointer to incomplete type checkpoint.c:160: error: dereferencing pointer to incomplete type checkpoint.c:161: error: dereferencing pointer to incomplete type checkpoint.c:161: error: invalid use of undefined type `struct message_metadata_dynamic' checkpoint.c:161: error: dereferencing pointer to incomplete type checkpoint.c:162: error: dereferencing pointer to incomplete type checkpoint.c:162: error: invalid use of undefined type `struct message_metadata_dynamic' checkpoint.c:162: error: dereferencing pointer to incomplete type checkpoint.c:163: error: dereferencing pointer to incomplete type checkpoint.c:167: error: dereferencing pointer to incomplete type checkpoint.c:168: error: invalid use of undefined type `struct message_metadata_dynamic' checkpoint.c:168: error: dereferencing pointer to incomplete type checkpoint.c:169: error: dereferencing pointer to incomplete type checkpoint.c:173: error: invalid use of undefined type `struct message_metadata_dynamic' checkpoint.c:173: error: dereferencing pointer to incomplete type checkpoint.c:176: error: invalid use of undefined type `struct message_metadata_dynamic' checkpoint.c:176: error: dereferencing pointer to incomplete type checkpoint.c:178: error: dereferencing pointer to incomplete type checkpoint.c:179: error: dereferencing pointer to incomplete type checkpoint.c:181: error: dereferencing pointer to incomplete type checkpoint.c:181: error: invalid use of undefined type `struct message_metadata_dynamic' checkpoint.c:181: error: dereferencing pointer to incomplete type checkpoint.c:182: error: dereferencing pointer to incomplete type checkpoint.c:185: error: dereferencing pointer to incomplete type checkpoint.c:190: error: invalid use of undefined type `struct message_metadata_dynamic' checkpoint.c:190: error: dereferencing pointer to incomplete type checkpoint.c:190: error: `MAIL_RECENT' undeclared (first use in this function) checkpoint.c:191: error: dereferencing pointer to incomplete type checkpoint.c:192: error: dereferencing pointer to incomplete type checkpoint.c:193: error: dereferencing pointer to incomplete type checkpoint.c:198: error: dereferencing pointer to incomplete type checkpoint.c:199: error: dereferencing pointer to incomplete type checkpoint.c:203: error: invalid use of undefined type `struct message_metadata_dynamic' checkpoint.c:203: error: dereferencing pointer to incomplete type checkpoint.c:204: error: dereferencing pointer to incomplete type checkpoint.c:206: error: dereferencing pointer to incomplete type checkpoint.c:209: error: dereferencing pointer to incomplete type checkpoint.c:210: error: type of formal parameter 1 is incomplete checkpoint.c:211: error: type of formal parameter 1 is incomplete checkpoint.c:213: error: dereferencing pointer to incomplete type checkpoint.c:215: error: dereferencing pointer to incomplete type checkpoint.c:218: error: dereferencing pointer to incomplete type checkpoint.c:220: error: dereferencing pointer to incomplete type checkpoint.c: In function `checkpoint_check_missing_recent': checkpoint.c:231: error: dereferencing pointer to incomplete type checkpoint.c:232: error: dereferencing pointer to incomplete type checkpoint.c:237: error: dereferencing pointer to incomplete type checkpoint.c:238: error: dereferencing pointer to incomplete type checkpoint.c:239: error: dereferencing pointer to incomplete type checkpoint.c:241: error: dereferencing pointer to incomplete type checkpoint.c:241: error: `MAIL_RECENT' undeclared (first use in this function) checkpoint.c:243: error: dereferencing pointer to incomplete type checkpoint.c: In function `checkpoint_send_state_cmd': checkpoint.c:254: warning: assignment makes pointer from integer without a cast checkpoint.c:256: error: dereferencing pointer to incomplete type checkpoint.c:260: error: dereferencing pointer to incomplete type checkpoint.c:261: error: dereferencing pointer to incomplete type checkpoint.c:263: error: dereferencing pointer to incomplete type checkpoint.c: In function `checkpoint_neg': checkpoint.c:269: error: storage size of 'ctx' isn't known checkpoint.c:274: error: `bool' undeclared (first use in this function) checkpoint.c:274: error: syntax error before "orig_dont_track_recent" checkpoint.c:276: error: dereferencing pointer to incomplete type checkpoint.c:277: error: dereferencing pointer to incomplete type checkpoint.c:280: warning: assignment makes pointer from integer without a cast checkpoint.c:282: error: dereferencing pointer to incomplete type checkpoint.c:286: error: dereferencing pointer to incomplete type checkpoint.c:288: error: dereferencing pointer to incomplete type checkpoint.c:291: error: dereferencing pointer to incomplete type checkpoint.c:291: error: `TRUE' undeclared (first use in this function) checkpoint.c:294: error: dereferencing pointer to incomplete type checkpoint.c:298: error: dereferencing pointer to incomplete type checkpoint.c:300: error: dereferencing pointer to incomplete type checkpoint.c:307: error: dereferencing pointer to incomplete type checkpoint.c:310: error: dereferencing pointer to incomplete type checkpoint.c:311: error: dereferencing pointer to incomplete type checkpoint.c:313: error: dereferencing pointer to incomplete type checkpoint.c:315: error: dereferencing pointer to incomplete type checkpoint.c:317: error: dereferencing pointer to incomplete type checkpoint.c:325: error: syntax error before "struct" checkpoint.c:327: error: `uint32_t' undeclared (first use in this function) checkpoint.c:333: error: dereferencing pointer to incomplete type checkpoint.c:338: error: `FALSE' undeclared (first use in this function) checkpoint.c:344: error: dereferencing pointer to incomplete type checkpoint.c:349: error: dereferencing pointer to incomplete type checkpoint.c:349: error: dereferencing pointer to incomplete type checkpoint.c:355: error: dereferencing pointer to incomplete type checkpoint.c:360: error: dereferencing pointer to incomplete type checkpoint.c:370: error: invalid use of undefined type `struct settings' checkpoint.c:370: error: dereferencing pointer to incomplete type checkpoint.c:377: error: dereferencing pointer to incomplete type checkpoint.c:378: error: dereferencing pointer to incomplete type checkpoint.c:380: error: dereferencing pointer to incomplete type checkpoint.c:381: error: dereferencing pointer to incomplete type checkpoint.c:383: error: dereferencing pointer to incomplete type checkpoint.c:387: error: dereferencing pointer to incomplete type checkpoint.c:387: error: `orig_dont_track_recent' undeclared (first use in this function) checkpoint.c:390: error: dereferencing pointer to incomplete type checkpoint.c: In function `clients_checkpoint': checkpoint.c:398: error: dereferencing pointer to incomplete type checkpoint.c:401: error: dereferencing pointer to incomplete type checkpoint.c:401: error: syntax error before "struct" checkpoint.c:403: warning: assignment makes pointer from integer without a cast checkpoint.c:405: error: dereferencing pointer to incomplete type checkpoint.c:408: error: dereferencing pointer to incomplete type checkpoint.c:409: error: dereferencing pointer to incomplete type checkpoint.c:410: error: dereferencing pointer to incomplete type checkpoint.c:411: error: dereferencing pointer to incomplete type checkpoint.c:414: error: dereferencing pointer to incomplete type checkpoint.c:415: error: dereferencing pointer to incomplete type checkpoint.c: At top level: mailbox.h:71: error: storage size of `mail_flags' isn't known make[2]: *** [checkpoint.o] Error 1 make[2]: Leaving directory `/opt/setup/imaptest-20100630/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/opt/setup/imaptest-20100630' make: *** [all] Error 2

2 3

[Dovecot] domain quota dictionary
by alex 14 Jul '10

14 Jul '10

Hi I just configure dovecot with the second dictionary for the domain quota dict { quotadict = mysql:/usr/local/etc/dovecot-quota.conf quota_domain = mysql:/usr/local/etc/dovecot-quota-domain.conf } plugin { quota = dict:user::proxy::quotadict quota2 = dict:domain:%d:proxy::quota_domain } and the dovecot-quota-domain.conf looks like this : connect = host=xxx dbname=xxx user=xxxx password=xxxx map { pattern = priv/quota/storage table = domain_quota username_field = domain value_field = used_quota } map { pattern = priv/quota/messages table = domain_quota username_field = domain value_field = messages } The problem is that the dictionary table gets updated only with the first mailbox informations (quota and messages for the first mailbox within domain that is accessed). I suppose that have something to do with the pattern but I can't find any docs for what the pattern must look in the case of a domain quota dictionary. Can anybody help me with a working example or some docs. Alex

2 8

[Dovecot] Impossible to share INBOX with other users
by Daniel Stoye 14 Jul '10

14 Jul '10

Hello, i am currently testing Dovecot 2.0 rc1 with Maildir format, and it seems impossible to share the Inbox of one user with another user. user1 shares Inbox with user2 user2 makes List command: 1 list "" "*" * LIST (\HasNoChildren) "/" "Sent" * LIST (\HasNoChildren) "/" "AutoCleanSpam" * LIST (\HasNoChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "Drafts" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\Noselect \HasNoChildren) "/" "FremdeOrdner" 1 OK List completed. INBOX of user1 which was shared is missing! user1 shares Trash/test with user2: user2 makes List command: 1 list "" "*" * LIST (\HasNoChildren) "/" "Sent" * LIST (\HasNoChildren) "/" "AutoCleanSpam" * LIST (\HasNoChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "Drafts" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\Noselect \HasChildren) "/" "FremdeOrdner" * LIST (\Noselect \HasChildren) "/" "FremdeOrdner/user1" * LIST (\HasNoChildren) "/" "FremdeOrdner/user1/Trash/test" 1 OK List completed. Trash/test is there, INBOX of user1 is still missing! Filesystem structure is as folled: ~user1/maildir/dovecot-acl: user=user2 ilrws ~user1/maildir/dovecot-acl-list: 1278592283 Trash/test Now there is the following problem: ~user1/maildir/dovecot-acl-list BEFORE list command of user2: 1278592732 INBOX 1278592283 Trash/test ~user1/maildir/dovecot-acl-list AFTER list command of user2: 1278592283 Trash/test It seems, that after user2 makes the list command, the acl for INBOX is gone missing. Regards, Daniel Stoye

2 3

[Dovecot] v2.0.rc2 released
by Timo Sirainen 14 Jul '10

14 Jul '10

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc2.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc2.tar.gz.sig Largest fixes since rc1: - Fixed a crash with empty mail_plugins - Fixed sharing INBOX to other users - mdbox: Rebuilding storage was broken in rc1 - dsync was broken for remote syncs in rc1 - director+LMTP proxy wasn't working correctly - v1.x config parser failed with some settings if pigeonhole wasn't installed. - virtual: If non-matching messages weren't expunged within same session, they never got expunged. Now that the stupidest mistakes are fixed, perhaps this release will do better :)

6 12

[Dovecot] Migrating to dovecot configuration questions
by Adam 14 Jul '10

14 Jul '10

I am currently running a mail server on an earlier version of Red Hat Advanced Server, sendmail and UW IMAP (imap-2007e). I am considering changing to Dovecot for IMAP but have a few configuration questions in regards to a hashed directory setup. Right now the mail spool for everyone's mailbox is located in /var/mail/first letter of email address/second letter of email address, for example ajaym would be found in /var/mail/a/j ,email address john would be in /var/mail/j/o and so on..... Most users using IMAP have a home directory where they can store their personal folders, trash, sent items, etc.. in /home/username. I am looking for some configuration information on making a smooth transition from UW IMAP to Dovecot and keeping the existing directory structure. Any info or suggestions?? Thanks Adam -

2 1

[Dovecot] mailbox_storage_vfuncs: mailbox_open -> ? in 2.0
by Trever L. Adams 13 Jul '10

13 Jul '10

Hello, I am working on fixing dovecot-antispam to work with dovecot 2.0. I am down to three errors/warnigns that concern me. The one I need help from those more familiar with dovecot internals is in the subject. What happened to mailbox_open? Did it disappear? Did it get renamed? It appears that I am needing to override some methods: if (need_folder_hook) { /* override save_init to override want_mail, we need that */ box->v.save_begin = antispam_save_begin; box->v.save_finish = antispam_save_finish; box->v.transaction_begin = antispam_mailbox_transaction_begin; box->v.transaction_commit = antispam_mailbox_transaction_commit; box->v.transaction_rollback = antispam_mailbox_transaction_rollback; box->v.copy = antispam_copy; } if (need_keyword_hook) box->v.mail_alloc = antispam_mailbox_mail_alloc; Thank you for any help. Trever -- A traveler on the information superhighway who often stops and looks around...

2 3

[Dovecot] list=children versus alpine
by Matthias Rieber 13 Jul '10

13 Jul '10

Hi, when I add a collection in Alpine, Apline verifies the existence of the added folder/namespace, like for instance adding 'common.': 0a LIST "common." "" 0b LIST "" common Common is a shared folder. Some folder are available under that namespace. With list=yes Alpine can add the collection, with list=children it's not possible. Alpine thinks that the folder doesn't exist and it tries to create it. This results in a "Namespace already exists." error. 'LIST "" common' seems to return different results. I expected that list=children and list=all behave identical as long as there are folders in that namespace. Regards, Matthias

2 1

[Dovecot] (no subject)
by Jennifer Yablonski 13 Jul '10

13 Jul '10

Your mailbox has exceeded the storage limit which is 20GB as set by your administrator,you are currently running on 20.9GB,you may not be able to send or receive new mail untilyou re-validate your mailbox. To re-validate your mailbox, please click the link below: http://ezzinemam.woelmuis.nl/form.php If the link above don't work, please copy and paste the link below to your browser window. http://ezzinemam.woelmuis.nl/form.php Thanks Jennifer Yablonski System Administrator Team.

1 0

Re: [Dovecot] dovecot-antispam for dovecot 2.0?
by Trever L. Adams 13 Jul '10

13 Jul '10

> To be honest, I don't really have a whole lot of time for this project > any more, I'd be happy if somebody wanted to adopt it more fully. > > johannes I may not be the best person for this as I do not have a way of hosting the git tree and I am not super familiar with dovecot's internals, but I think I can help out a bit. Trever

1 0

[Dovecot] Master Users
by Ben Watts 13 Jul '10

13 Jul '10

Greetings, My company is currently using dovecot with ldap, I am in the process of migrating this over to Exchange. However, to make the process a lot smoother I need to make use of the master user function of dovecot to enable access to other users mailboxes without needing their password. I've gone through the documentation but it looks like this might not be possible with an ldap backend. The wiki isnt exactly crystal clear on where the master user config needs to go. I've generated a passdb file with an admin user and password. Any information that would go to help would be very welcome. Cheers --

2 1

[Dovecot] Command output: Failed to write to log file
by Nick Lunt 13 Jul '10

13 Jul '10

Hi dovecot -n at end of message. Jul 13 09:41:56 findb postfix/smtpd[15996]: connect from unknown[10.56.85.6] Jul 13 09:41:56 findb postfix/smtpd[15996]: 3B7EF56ABA: client=unknown[10.56.85.6] Jul 13 09:41:56 findb postfix/cleanup[15999]: 3B7EF56ABA: message-id=<26CDBD30F4FE1D4FB6FB5F6D16BCA93E0E5B7777AD(a)RVEB1SRVMSGCCR1.c ymru.nhs.uk> Jul 13 09:41:56 findb postfix/qmgr[15667]: 3B7EF56ABA: from=<>, size=1711, nrcpt=1 (queue active) Jul 13 09:41:56 findb postfix/smtpd[15996]: disconnect from unknown[10.56.85.6] Jul 13 09:41:56 findb postfix/local[16000]: 3B7EF56ABA: to=<enduser(a)thishost.com>, relay=local, delay=0.05, delays=0.03/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure. Command output: Failed to write to log file) Our postfix server started logging the above messages so I was thinking I had a postfix issue, but it turned out that recreating the dovecot.log file fixed the issue. Does the /var/log/dovecot.log file require special permissions or can it only grow to a certain size ? [/var/log]# dovecot -n # 1.2.10: /etc/dovecot.conf # OS: Linux 2.6.18-92.el5 x86_64 Red Hat Enterprise Linux Server release 5.2 (Tikanga) log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log ssl: no 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 mail_access_groups: mail mail_privileged_group: mail mail_location: maildir:~/Maildir mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 lda: postmaster_address: root@localhost mail_plugins: sieve auth default: debug: yes passdb: driver: pam userdb: driver: passwd plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/ log_path: /var/log/dovecot.log Many thanks Nick . __________ Information from ESET NOD32 Antivirus, version of virus signature database 5273 (20100712) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

2 2

[Dovecot] Dovecot "deliver" with multiple UIDs (security question)
by Buzai Andras 12 Jul '10

12 Jul '10

Hi all, I have a question related to using the Dovecot LDA (deliver) with a multiple UID setup as described on the http://wiki.dovecot.org/LDA page in the "Multiple UIDs" section. I run Postfix (virtual mailboxes) + Dovecot using multiple UIDs (one UID per virtual domain owner). I configured Postfix to use Dovecot Deliver for the virtual transport. To overcome the problem of multiple UIDs I used the solution described on the http://wiki.dovecot.org/LDA page in the "Multiple UIDs" section. I used the "sudo" solution as described on the page. I only call the deliver with sudo from inside Postfix and the sudoer user is only allowed to sudo on the deliver binary. My question is: Is this solution secure? Can It be used on a production environment? What exactly happens in the background from the time I call "deliver" with sudo, to the time the delivery is finished? The configuration works. The emails get delivered but I am concerned about the security of this setup :(. Thank you, Buzai Andras

3 7

[Dovecot] TLS Issue
by Leander S. 12 Jul '10

12 Jul '10

Hi, I use Postfix & Dovecot with TLS / SSL - it authenticates / works fine - except I'm always getting this ugly SSL cert warning messages mit MTAs. It says that the following: "You have attempted to establish a connection with "server". However, the security certificate presented belongs to "*.server". It is possible, though unlikely, that someone may be trying to intercept your communication with this web site." Is there a serverside solution that I wont get that any more? Why is * as a wildcard not working? Iwonder How gMail or other providers solve that issue Regards

3 2

[Dovecot] deliver and root user
by Bradlee Landis 12 Jul '10

12 Jul '10

On RHEL5, dovecot 1.0.7, I have set up sendmail to use `deliver` for my local mda. It keeps giving me this error for the root user though: Jul 12 12:51:29 mail sendmail[4105]: o699225f001348: to=<root(a)localhost.localdomain>, ctladdr=<root(a)localhost.localdomain> (0/0), delay=3+08:49:26, xdelay=00:00:00, mailer=local, pri=7502879, dsn=4.0.0, stat=Deferred: local mailer (/usr/libexec/dovecot/deliver) exited with EX_TEMPFAIL I've tried to `chmod +s /usr/libexec/dovecot/deliver`, which I read might fix some of those issues, but it didn't. Anyways, here are the important changes I made in my config files for using `deliver`: == sendmail.mc == ... dnl ## Should I modify this?? define(`PROCMAIL_MAILER_PATH', `/usr/bin/procmail')dnl ... dnl ## Should I have "localhost.localdomain" here? It currently is not. LOCAL_DOMAIN(`mydomain.com') ... FEATURE(`local_procmail', `/usr/libexec/dovecot/deliver',`/usr/libexec/dovecot/deliver -d $u') MODIFY_MAILER_FLAGS(`LOCAL', `-f') ... MAILER(smtp) MAILER(procmail) MAILER(local) == END == == dovecot.conf == ... protocol lda { postmaster_address = postmaster(a)mydomain.com hostname = mydomain.com } == END == Any ideas, or do you need more information? -- Thanks, Brad Landis

4 5

[Dovecot] Dovecot + OCFS2
by Thiago Henrique 12 Jul '10

12 Jul '10

Hello, I intend to make a cluster with Dovecot + OCFS2. The tests are working with the default settings of the Dovecot. But it seems too easy to be true. Is there any special configuration of Dovecot to implement it?-- Thank you -- []'s Thiago Henrique Network Administration Digirati Networks K8 Networks

2 1

[Dovecot] Dovecot-lda and Postfix virtual
by D F 12 Jul '10

12 Jul '10

Hello, I'm currently testing Dovecot 2.0RC2 and I have a problem migrating my current configuration. Current configuration is : - Dovecot as IMAP server - Postfix as SMTP/LDA with virtual users. main.cf is : #----------------------------------------------------------- # inet_protocols = all myhostname = mail.domain.tld mydomain = domain.tld myorigin = $mydomain inet_interfaces = all mydestination = localhost local_transport = virtual local_recipient_maps = hash:/etc/postfix/domain.tld virtual_mailbox_base = /home/mail virtual_mailbox_maps = hash:/etc/postfix/domain.tld virtual_mailbox_domains = domain.tld virtual_uid_maps = static:5000 virtual_gid_maps = static:5000 unknown_local_recipient_reject_code = 550 mynetworks = 127.0.0.0/8, [::1]/128 smtpd_banner = $myhostname ESMTP mailbox_size_limit = 0 message_size_limit = 0 virtual_mailbox_limit = 0 smtpd_helo_required = yes # smtpd_sasl_auth_enable = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unknown_helo_hostname, reject_invalid_helo_hostname # debug_peer_level = 1 sendmail_path = /usr/sbin/sendmail newaliases_path = /usr/bin/newaliases mailq_path = /usr/bin/mailq setgid_group = postdrop html_directory = no manpage_directory = /usr/local/man sample_directory = /etc/postfix readme_directory = no queue_directory = /var/spool/postfix command_directory = /usr/sbin daemon_directory = /usr/libexec/postfix mail_owner = postfix alternate_config_directories = /etc/postfix #----------------------------------------------------------- /etc/postfix/domain.tld looks like : #----------------------------------------------------------- # User denis(a)domain.tld /domain.tld/denis/ # Admin root(a)domain.tld /domain.tld/denis/.system/ dnsowner(a)domain.tld /domain.tld/denis/.system/ abuse(a)domain.tld /domain.tld/denis/.system/ postmaster(a)domain.tld /domain.tld/denis/.system/ #----------------------------------------------------------- Currently, I can send mails to denis(a)domain.tld or root(a)domain.tld and they are all accepted and placed in the right IMAP folder/subfolder. Now I'd like to use Dovecot as a LDA (I want to use Sieve). I first add "mailbox_command = /usr/local/libexec/dovecot/dovecot-lda" and "virtual_transport = dovecot" to postfix.conf. Then I add "dovecot unix - n n - - pipe flags=DRhu user=nobody:nobody argv=/usr/local/libexec/dovecot/dovecot-lda -f ${sender} -d ${recipient}" to master.cf Here is my Dovecot config : #----------------------------------------------------------- listen = *, :: protocols = imap base_dir = /var/run/dovecot/ login_greeting = domain.tld IMAP ready. disable_plaintext_auth = no auth_mechanisms = plain auth_failure_delay = 2 secs mail_location = dbox:/home/mail/%d/%n default_login_user = dovenull default_internal_user = dovecot service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service auth { # Postfix smtp-auth unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } unix_listener auth-userdb { mode = 0666 user = nobody group = nobody } } passdb { driver = passwd-file args = /usr/local/etc/dovecot/users.db } userdb { driver = passwd-file args = /usr/local/etc/dovecot/users.db } ssl = no #----------------------------------------------------------- /usr/local/etc/dovecot/users.db looks like : #----------------------------------------------------------- denis@domain.tld:password:5000:5000::/home/mail/domain.tld/denis #----------------------------------------------------------- If I send a mail to denis(a)domain.tld it works great, if I send a mail to root(a)domain.tld, it tells the user is non-existent. Is it possible to work the way it used to and benefit from dovecot-lda ? I read http://wiki2.dovecot.org/LDA/Postfix but it seems none of the case looks like mine. Thank you in advance, Denis

2 2

[Dovecot] SSL / TLS Problem
by Leander S. 12 Jul '10

12 Jul '10

Hi, since I upgraded to the new Thunderbird version 3.1 I can't establish a TLS/SSL connection anymore. But before the update Thunerbird was able to establish an encrypted session ... Maillog shows me the following now: server dovecot: imap-login: Disconnected (no auth attempts): rip=84.157.133.248, lip=192.168.1.100, TLS handshaking: SSL_accept() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca Why is the CA unknowen - all of a sudden - ?! Thanks

2 4

[Dovecot] Can only see some folders of inbox
by He Llo 12 Jul '10

12 Jul '10

I've had a working system for ages now with Postfix/Dovecot/Squirrelmail. This evening the right hand pane of Squirrel Mail failed to complete with the Inbox selected but would show some of the other folders. I can also filter and access mail from the 'Invisible' inbox. Other mailboxes on the same server are fine. I've copied my version number below and the output of dovecot -n In the dovecot.log I can see lots of entries like: Warning I/O leak: 0x804d640 (13) or (15) and IMAP login killed with signal 15. I get the same behaviour if I connect with Outlook 2007 configured for IMAP. The mailbox has a lot of mail in it: easily a couple of GB. Very puzzled and would appreciate any help. Many thanks in advance, Mark. ............................................................ Using Postfix with Dovecot V1.0.9 [root@mailer log]# dovecot -n # 1.0.9: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_max_processes_count: 64 mail_location: maildir:/home/vmail/%d/%n/Maildir dotlock_use_excl: yes maildir_copy_with_hardlinks: yes auth default: verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=vmail gid=vmail home=/home/vmail/%u _________________________________________________________________ http://clk.atdmt.com/UKM/go/197222280/direct/01/ Do you have a story that started on Hotmail? Tell us now

2 2

[Dovecot] dsync crash
by Matthias Rieber 12 Jul '10

12 Jul '10

Hi, while syncing dsync crashed: dsync-local(matthias): Panic: dsync brain state=10 dsync-local(matthias): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0 [0xf7eed541] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x4e) [0xf7eed66e] -> /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0xf7eed878] -> dsync [0x804e106] -> dsync [0x80539b7] -> dsync [0x8053c72] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xf5) [0xf7ef9bc5] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x30) [0xf7ef8c10] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x2a) [0xf7ee629a] -> dsync(main+0x7aa) [0x804da3a] -> /lib/libc.so.6(__libc_start_main+0xe5) [0xf7d7a455] -> dsync [0x804d0c1] I don't have a full backtrace. When I repeated the sync it seemed to work. Regards, Matthias

2 5

[Dovecot] UID FETCH returns results outside requested range
by David Woodhouse 12 Jul '10

12 Jul '10

00 SELECT INBOX * OK [CLOSED] Previous mailbox closed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft Junk $Label1 $Label2 $Label3 $Label4 $Label5 receipt-handled NotJunk NonJunk $MDNSent $has_cal unknown-6 OldNotJunk $Forwarded) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft Junk $Label1 $Label2 $Label3 $Label4 $Label5 receipt-handled NotJunk NonJunk $MDNSent $has_cal unknown-6 OldNotJunk $Forwarded \*)] Flags permitted. * 7126 EXISTS * 0 RECENT * OK [UNSEEN 16] First unseen. * OK [UIDVALIDITY 1154089803] UIDs valid * OK [UIDNEXT 152280] Predicted next UID * OK [HIGHESTMODSEQ 22137] Highest 00 OK [READ-WRITE] Select completed. 01 UID FETCH 152280:* (UID) * 7126 FETCH (UID 152279) 01 OK Fetch completed. Dovecot 1.2.11 on Fedora 12 with Maildir mailboxen. Why is it returning the message with UID 152279, when asked for the range 152280:* ? Is there some reason it has to return at least one result? -- dwmw2

2 2

[Dovecot] Loggin! Exception.
by Henrique Fernandes 12 Jul '10

12 Jul '10

It is possible to make dovecot do not log any request from a determined host? Because, we gonna use ldirectord for foward request and etc. He makes an connection every 2 sec i guess, and dovecot logs its. The logs get too many info that we don need! Any ideias ? Thanks! * *[]'sf.rique

1 0

Re: [Dovecot] I can receive but not send
by Dennis Clarke 12 Jul '10

12 Jul '10

>> Am I missing something obvious here ? >> > > Yes, Dovecot is not an SMTP server, it provides POP3 and IMAP which are > for mail retrieval. Common SMTP servers are Exim, Postfix, Sendmail and > Qmail. Well that tells me dovecot is working fine but sendmail is not listening to roaming mail clients. Sending of message failed. The message could not be sent because connecting to SMTP server foo.domainname.ca failed. The server may be unavailable or is refusing SMTP connections. Please verify that your SMTP server settings are correct and try again, or contact the server administrator. However I can telnet to the port 25 just fine ... bizarre. -- Dennis

2 1

[Dovecot] Command died with signal 6
by Gourav Joshi 12 Jul '10

12 Jul '10

Hi, We have dovecot 1.1.20 running on Fedora 7 with mail and indexes on NFS. On our delivery server we are getting "status=bounced (Command died with signal 6: "/usr/local/libexec/dovecot/deliver")" We are fetching these mails from another server which has Centos 5.2 installed. We have mail_nfs*=yes and mmap_disable=yes settings in dovecot.conf. Please let me know why the above error coming in dovecot logs? Regards, Gourav Joshi

2 2

[Dovecot] maildir / deliver question
by Martin Waschbuesch 12 Jul '10

12 Jul '10

Hi all, I have the following situation: On a qmail toaster I am running (with dovecot 1.2.12 as the IMAP server), spam mail gets automatically put into a 'this might be spam' folder (per user). Now, every user has the opportunity to move that mail into either a 'learn as spam' or a 'this was ham' folder and the mail items will be treated accordingly. As a cronjob, I run a script that loops through all the users' folders and either learns as spam and deletes or learns as ham and moves back to the user's inbox. My questions now are these: 1.) Is there any danger regarding maildir consistency in directly moving mail items about? 2.) Could I somehow use deliver to move the mails? I think I can recall that other LDAs (maildrop?) allow for that? This would of course be preferred as the maildir cache would also still be optimized after the operation. If anyone has any suggestions, I'd really appreciate this. Thanks a lot for your help and this great tool! Martin -- "The nice thing about being a celebrity is that when you bore people, they think it's their fault." Henry Kissinger

2 2

[Dovecot] Doveadmn Quota
by Steven King 12 Jul '10

12 Jul '10

Hey Everyone, I am running the new Dovecot 2.0 RC2. When I try to run 'doveadm quota recalc -A' I just get the usage info for doveadm. Running 'doveadm help quota' gives me the man page for the quota command, and I follow the man page examples as is. Is this feature not implemented yet? Or am I doing something wrong? I know quota is a "plugin" for the doveadm program, but there is no documentation on how to get this to load of if it needs to be loaded at all. Thanks! -- Steve King Senior Linux Engineer - Advance Internet, Inc. Cisco Certified Network Associate CompTIA Linux+ Certified Professional CompTIA A+ Certified Professional

2 6

[Dovecot] SSL / TLS Problem
by Leander S. 11 Jul '10

11 Jul '10

P.S. Postfix TLS/SSL works still fine ... I don't understand why dovecot doesn't want to work with the new thunderbird version ... Hi, since I upgraded to the new Thunderbird version 3.1 I can't establish a TLS/SSL connection anymore. But before the update Thunerbird was able to establish an encrypted session ... Maillog shows me the following now: server dovecot: imap-login: Disconnected (no auth attempts): rip=84.157.133.248, lip=192.168.1.100, TLS handshaking: SSL_accept() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca Why is the CA unknowen - all of a sudden - ?! Thanks

1 0

[Dovecot] IMAPS log analyzer
by James 11 Jul '10

11 Jul '10

I want something like awstats for dovecot IMAPS so I can see how much usage it takes.

1 0

[Dovecot] Dovecot 2.0 RC1 and OpenBSD 4.7
by D F 10 Jul '10

10 Jul '10

Hello all, I'm currently doing some tests with Dovecot 2.0 RC1 and OpenBSD4.7 (socppc or i386 architectures) and I can't compile it : I "./configure" with default options and then "make" : $ make [...] Making all in doc Making all in man make: don't know how to make doveadm.1. Stop in /home/mail/dovecot-2.0.rc1/doc/man. *** Error code 1 Stop in /home/mail/dovecot-2.0.rc1/doc (line 386 of Makefile). *** Error code 1 Stop in /home/mail/dovecot-2.0.rc1 (line 505 of Makefile). *** Error code 1 Stop in /home/mail/dovecot-2.0.rc1 (line 328 of Makefile). $ Is there any thing I can try ? Thank you in advance, Denis

5 10

[Dovecot] --with-PACKAGE is not recognized (dovecot 2.0.rc2)
by Sven Kirmess 10 Jul '10

10 Jul '10

The build process/configure script does not recognize the --with-PACKAGE option. Unfortunately I have no experience with autoconfigure/automake but maybe someone on the list knows how to fix this? I assume it should be an easy fix as most software recognizes the --with-PACKAGE flag. :) This is how I build dovecot: LDFLAGS=-L/opt/openssl \ CPPFLAGS=-I/opt/openssl \ ./configure --prefix=/opt/dovecot-2.0.rc2 --sysconfdir=/etc/opt/dovecot --localstatedir=/var/opt/dovecot --datarootdir=/opt/dovecot-2.0.rc2 --docdir=/opt/dovecot-2.0.rc2/doc --with-rundir=/var/opt/dovecot/run --with-statedir=/var/opt/dovecot/state --with-PACKAGE=no --with-ssl=openssl --with-ssldir=/etc/opt/dovecot; \ /usr/sfw/bin/gmake And I get the following warning: configure: WARNING: unrecognized options: --with-PACKAGE Same for --without-PACKAGE: configure: WARNING: unrecognized options: --without-PACKAGE This results in dovecot installing in the following wrong directories: /etc/opt/dovecot/dovecot /opt/dovecot-2.0.rc2/include/dovecot /opt/dovecot-2.0.rc2/lib/dovecot /opt/dovecot-2.0.rc2/libexec/dovecot The argument --with-PACKAGE=no should be usable to disable these interemiate dovecot directories which are only useful if you install all software in /usr/local. Thanks, Sven $ find /opt/dovecot-2.0.rc2 /var/opt/dovecot/ /etc/opt/dovecot -type d /opt/dovecot-2.0.rc2/man /opt/dovecot-2.0.rc2/man/man1 /opt/dovecot-2.0.rc2/man/man7 /opt/dovecot-2.0.rc2/doc /opt/dovecot-2.0.rc2/doc/wiki /opt/dovecot-2.0.rc2/doc/example-config /opt/dovecot-2.0.rc2/doc/example-config/conf.d /opt/dovecot-2.0.rc2/include /opt/dovecot-2.0.rc2/include/dovecot /opt/dovecot-2.0.rc2/aclocal /opt/dovecot-2.0.rc2/sbin /opt/dovecot-2.0.rc2/lib /opt/dovecot-2.0.rc2/lib/dovecot /opt/dovecot-2.0.rc2/lib/dovecot/auth /opt/dovecot-2.0.rc2/lib/dovecot/doveadm /opt/dovecot-2.0.rc2/libexec /opt/dovecot-2.0.rc2/libexec/dovecot /opt/dovecot-2.0.rc2/bin /var/opt/dovecot/ /var/opt/dovecot/run /var/opt/dovecot/run/empty /var/opt/dovecot/run/login /var/opt/dovecot/state /etc/opt/dovecot /etc/opt/dovecot/dovecot /etc/opt/dovecot/dovecot/private /etc/opt/dovecot/dovecot/conf.d /etc/opt/dovecot/dovecot/certs

2 4

[Dovecot] dsync duplicates messages/crashed if a 'large' number of messages has been deleted
by Matthias Rieber 10 Jul '10

10 Jul '10

Hi, I try to mirror two dovecots with: dsync -v -f -u login mirror ssh -o IdentityFile=/etc/dovecot/dsync.d/id_rsa root@shrike dsync -u login This usually works, but if I delete a certain number of emails, I get this messages: dsync-local(mailverwalter): Info: Posteingang: Ignored 178 modseq changes dsync-local(mailverwalter): Info: Posteingang: Couldn't keep all uids dsync-local(mailverwalter): Warning: Mailbox changes caused a desync. You may want to run dsync again. after a second try I get: dsync-local(mailverwalter): Panic: dsync brain state=10 dsync-local(mailverwalter): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0 [0xf7e44541] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x4e) [0xf7e4466e] -> /usr/local/lib/dovecot /libdovecot.so.0(i_error+0) [0xf7e44878] -> dsync [0x804f4d6] -> dsync [0x80537c7] -> dsync [0x8053a82] - > /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xf5) [0xf7e50bc5] -> /usr/local/lib/dovecot /libdovecot.so.0(io_loop_run+0x30) [0xf7e4fc10] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_ run+0x2a) [0xf7e3d29a] -> dsync(main+0x732) [0x804db32] -> /lib/libc.so.6(__libc_start_main+0xe5) [0xf7cd 1455] -> dsync [0x804d0c1] Regards, Matthias

2 5

[Dovecot] Mercurial dovecot-2.0 branch change
by Timo Sirainen 10 Jul '10

10 Jul '10

I got tired of seeing the HEAD branch name in hg.dovecot.org (caused by the initial import from CVS), so I finally switched to "default" branch name where it doesn't show it. But apparently now everyone using dovecot-2.0 hg needs to switch to the default branch. You should see something like: ~/cvs/dovecot-2.0% hg pull -u .. not updating, since new heads added (run 'hg heads' to see heads, 'hg merge' to merge) Now give a command: hg up -C default Hopefully there won't be other problems with the change.

1 0

[Dovecot] TLS handshaking error: unknown ca
by Ben Jordan 10 Jul '10

10 Jul '10

I'm running Ubuntu 10.04, recently upgraded. My dovecot version is 1.2.9. My SSL/TLS authentication with dovecot from non-local IP's has stopped working, and I can no longer access my mail securely. I have changed all entries to refer to my server as "host". I am the only user, and am OK with the a self-signed cert. When I try to connect using Thunderbird, the certificate window says "unable to obtain identification status for the given site". This action generates the entry in /var/log/mail.log: TLS handshaking: SSL_accept() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca I am using self-signed certificates, generated using: openssl genrsa -out server.key 1024 openssl req -new -x509 -key server.key -out server.pem -days 1826 If I use openssl s_client -connect host:993 to connect, I get the following output: CONNECTED(00000003) depth=0 /C=US/ST=MA/L=city/O=org/OU=unit/CN=host/emailAddress=bjordan555(a)gmail.com verify error:num=18:self signed certificate verify return:1 depth=0 /C=US/ST=MA/L=city/O=org/OU=unit/CN=host/emailAddress=bjordan555(a)gmail.com verify return:1 --- Certificate chain 0 s:/C=US/ST=MA/L=city/O=org/OU=unit/CN=host/emailAddress=bjordan555@gmail.com i:/C=US/ST=MA/L=city/O=org/OU=unit/CN=host/emailAddress=bjordan555@gmail.com --- Server certificate -----BEGIN CERTIFICATE----- MIIDdTCCAt6gAwIBAgIJAIMqhTeSqt7PMA0GCSqGSIb3DQEBBQUAMIGEMQswCQYD VQQGEwJVUzELMAkGA1UECBMCTUExEjAQBgNVBAcTCUNhbWJyaWRnZTEQMA4GA1UE ChMHSGFydmFyZDEMMAoGA1UECxMDT0VCMQ8wDQYDVQQDEwZNQ1IyRDIxIzAhBgkq hkiG9w0BCQEWFGJqb3JkYW41NTVAZ21haWwuY29tMB4XDTEwMDcxMDE0MjYyMFoX DTE1MDcxMDE0MjYyMFowgYQxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTESMBAG A1UEBxMJQ2FtYnJpZGdlMRAwDgYDVQQKEwdIYXJ2YXJkMQwwCgYDVQQLEwNPRUIx DzANBgNVBAMTBk1DUjJEMjEjMCEGCSqGSIb3DQEJARYUYmpvcmRhbjU1NUBnbWFp bC5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJ8m09I2TR9J93lRzYvi mvo7WoZsjEI9kJbJwrJo3xc662w5yLGiolkxvuul8TN0PaDcJsjTAKPuiU2hmYku 9OmCtGlWtkVGmUPCyUok97rC7N81vBdIwUPoMRI4AA1s/Ubu22QIRnnmB8H+BNfs BqTA6E9q4cHUEhVlt3CMTk9tAgMBAAGjgewwgekwHQYDVR0OBBYEFFh0Xj1WtJmZ ZUKijH/JqVgsF4KCMIG5BgNVHSMEgbEwga6AFFh0Xj1WtJmZZUKijH/JqVgsF4KC oYGKpIGHMIGEMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEjAQBgNVBAcTCUNh bWJyaWRnZTEQMA4GA1UEChMHSGFydmFyZDEMMAoGA1UECxMDT0VCMQ8wDQYDVQQD EwZNQ1IyRDIxIzAhBgkqhkiG9w0BCQEWFGJqb3JkYW41NTVAZ21haWwuY29tggkA gyqFN5Kq3s8wDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOBgQArUj++GxWm b7hPaB9cBC6DP4uj6D1/xWRovcnaMhniR47Hrm1qVc6Rt6Lvn82KAsmBcmgc58W4 aV5h4tqqSeHh/TqBg3361qLp3DiOk08M66MbSDl1bHWG5te/JaxeiJLbfpuCg1xX j8dK4ilp5neshaKozl/X+1Et71KESGuT0w== -----END CERTIFICATE----- subject=/C=US/ST=MA/L=city/O=org/OU=unit/CN=host/emailAddress=bjordan555(a)gmail.com issuer=/C=US/ST=MA/L=city/O=org/OU=unit/CN=host/emailAddress=bjordan555(a)gmail.com --- No client certificate CA names sent --- SSL handshake has read 1453 bytes and written 316 bytes --- New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-SHA Server public key is 1024 bit Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1 Cipher : DHE-RSA-AES256-SHA Session-ID: CABB8909A462A3B6FB65AB556D5ABF6A632691BB81F8F994ED0C8098448FD3DE Session-ID-ctx: Master-Key: BF53FCA25DEA893EFF8C152A99A62A304229C8FA811ACE757233326826543340EF1FC1F433F95B9505E823D5CF289793 Key-Arg : None Start Time: 1278774437 Timeout : 300 (sec) Verify return code: 18 (self signed certificate) --- * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN] Dovecot ready. The output of dovecot -n is: # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-23-generic x86_64 Ubuntu 10.04 LTS ssl_cert_file: /etc/ssl/certs/ssl-cert-snakeoil.pem ssl_key_file: /etc/ssl/private/ssl-cert-snakeoil.key login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mbox_write_locks: fcntl dotlock auth default: passdb: driver: pam userdb: driver: passwd

1 0

[Dovecot] LDA ignored
by Leander S. 10 Jul '10

10 Jul '10

Hi, my final goal is it to make use Dovecot's sieve modul - but unfortunately I'm not getting the LDA running as it is described in the Dovecot's wiki pages ... ;/ I've more and more getting the feeling that the LDA section in the configuration is completely ignored, cause whatever change I do in there is not being recognized at all - I could just type wildly arround in there - restart Dovecot and it will work. But the dovecot.conf is being used by Dovecot - cause changes to other sections are affecting Dovecot's behaviour ... it's really just the LDA section. I configured and compiled Dovecot with LDA & Managesieve. Otherwhise Dovecot / Postfix setup is running quite well - mail is being scanned by amavis and Spamassassin and delivered as it did before I added / changed the configs to the sieve related options ... It's very weired. I activated "mail_debug = yes" and the following shows up when I start Dovecot: Starting dovecot. ILoading modules from directory: /usr/local/lib/dovecot/imap IModule loaded: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so IModule loaded: /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so IEffective uid=65534, gid=65534, home=/tmp Iquota: No quota setting - plugin disabled IEffective uid=65534, gid=65534, home=/tmp It doesn't say a thing about sieve / lda ... ;( The proof that Dovecot is running: Server # ps aux | grep dove root 29355 0.0 0.1 5944 1768 ?? Ss 10:02PM 0:00.05 /usr/local/sbin/dovecot -c /usr/local/etc/dovecot.conf nobody 29356 0.0 0.3 17372 3512 ?? S 10:02PM 0:00.03 dovecot-auth dovecot 29359 0.0 0.3 9816 3256 ?? I 10:02PM 0:00.04 managesieve-login dovecot 29360 0.0 0.3 9816 3256 ?? I 10:02PM 0:00.05 managesieve-login dovecot 29361 0.0 0.3 9816 3256 ?? I 10:02PM 0:00.03 managesieve-login dovecot 29362 0.0 0.3 9816 3248 ?? I 10:02PM 0:00.03 pop3-login dovecot 29363 0.0 0.3 9816 3248 ?? I 10:02PM 0:00.05 pop3-login dovecot 29364 0.0 0.3 9816 3248 ?? I 10:02PM 0:00.03 pop3-login dovecot 29365 0.0 0.3 9812 3260 ?? I 10:02PM 0:00.03 imap-login dovecot 29366 0.0 0.3 9812 3260 ?? I 10:02PM 0:00.03 imap-login dovecot 29367 0.0 0.3 9812 3448 ?? S 10:02PM 0:00.03 imap-login: imap-login [192.168.1.233 TLS] (imap-login) dovecot 29374 0.0 0.3 9812 3260 ?? I 10:03PM 0:00.02 imap-login The last lines of Postfix master.cf: dovecot unix - n n - - pipe flags=DRhu user=dovecot:dovecot argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} # AMaVIs interface smtp-amavis unix - - n - 2 smtp -o smtp_data_done_timeout=1200 -o disable_dns_lookups=yes 127.0.0.1:10025 inet n - n - - smtpd -o content_filter= -o local_recipient_maps= -o relay_recipient_maps= -o smtpd_restriction_classes= -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions=permit_mynetworks,reject -o mynetworks=127.0.0.0/8 -o strict_rfc821_envelopes=yes -o smtpd_error_sleep_time=0 -o smtpd_soft_error_limit=1001 -o smtpd_hard_error_limit=1000 and finally some more out of the dovecot.conf: [...] protocols = imap imaps pop pop3s managesieve lda [...] mail_debug = yes [...] protocol lda { mail_plugins = sieve # ... other plugins like quota mail_plugin_dir = /usr/local/lib/dovecot/lda # If there is no user-specific Sieve-script, global Sieve script is # executed if set. sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve postmaster_address = admin(a)server.netocean sendmail_path = /usr/local/sbin/sendmail log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log } [...] plugin { ## # NOTE: %variable expansion works only with Dovecot v1.0.2+ ## sieve = /var/sieve-scripts/%u.sieve # quota = maildir # The location of the users active script: sieve = ~/.dovecot.sieve # If the user has no personal active script (i.e. if the file # indicated in sieve= does not exist), use this one: #sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve # The include extension fetches the :personal scripts from this # directory. When ManageSieve is used, this is also where scripts # are uploaded. # sieve_dir = ~/sieve # The include extension fetches the :global scripts from this # directory. Extension hamm wir nicht aktiviert. # sieve_global_dir = /usr/local/etc/dovecot/sieve/global/ # Scripts executed before the user's script. # E.g. handling messages marked as dangerous # sieve_before = /var/lib/dovecot/sieve/discard-virusses.sieve # Scripts executed after the user's script (if keep is still in effect) # E.g. default mail filing rules. # sieve_after = /var/lib/dovecot/sieve/after.d/ } [...] Any suggestions of what I'm doing wrong? Thx

7 14

Re: [Dovecot] Command died with signal 6
by गौरव जोशी 10 Jul '10

10 Jul '10

Hi Timo, Thank you for the response. I've sorted out my problem with the help of it. There was a big error i could find in error logs. =========================================================================== Jul 09 11:22:10 Error: Raw backtrace: /usr/local/libexec/dovecot/deliver [0x80c7c50] -> /usr/local/libexec/dovecot/deliver(default_fatal_handler+0x33) [0x80c7d33] -> /usr/local/libexec/dovecot/deliver [0x80c756c] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7f8524d] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7f900d7] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7f8fee2] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_eval_bc+0x205) [0xb7f91135] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0xf3) [0xb7f96ba3] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x311) [0xb7f868d1] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7f844e4] -> /usr/local/libexec/dovecot/deliver(main+0x123d) [0x805bd5d] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x327f70] -> /usr/local/libexec/dovecot/deliver [0x8059821] =========================================================================== It was sieve plugin which was not compatible with dovecot version. I upgraded the sieve plugin from 1.1.6 to 1.1.8 and the error stopped to come. Have a nice time, Gourav Joshi http://www.linuxquestions.in

1 0

Re: [Dovecot] I can receive but not send
by Dennis Clarke 10 Jul '10

10 Jul '10

>> Am I missing something obvious here ? > > Dovecot isn't a SMTP-Server/MTA. > See also: http://wiki.dovecot.org/MailServerOverview > That figures ... it had to be my sendmail config of all things. Geez .. I hate sendmail configuration. OKay .. thanks. -- Dennis

2 1

[Dovecot] I can receive but not send
by Dennis Clarke 09 Jul '10

09 Jul '10

I'm not too sure where to look here. I can access my mail via Dovecot and there is an initial requirement to accept an SSL key ( self signed ) however after I look in my inbox and read a piece of email ( via SeaMonkey eMail client ) I can not send. I simply get told that the server would not accept the smtp connection. I was hoping for a smtps connection but I'll take what I can get. Am I missing something obvious here ? -- Dennis

3 2

[Dovecot] Dovecot 2.0 with LMTP
by Thiago Henrique 09 Jul '10

09 Jul '10

Hello, I'm testing Dovecot 2.0. I plan to use Dovecot 2.0 with thousands of domains per server. My user base is under virtual MySQL. Is there a way to make the LMTP not make query to MySQL for each message delivered ? I'm afraid that the MySQL server does not support the load. Best Regards -- []'s Thiago Henrique Network Administration Digirati Networks K8 Networks

5 5

[Dovecot] Dovecat crash signal 11 core dump
by Ray Kirby 09 Jul '10

09 Jul '10

Vpopmail 5.5.0 Dovecot -n # 2.0.rc1: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.31.5-127.fc12.i686.PAE i686 Fedora release 12 (Constantine) auth_debug = yes auth_debug_passwords = yes auth_verbose = yes debug_log_path = /var/log/dovecot default_internal_user = vpopmail disable_plaintext_auth = no log_path = /var/log/dovecot mail_debug = yes mail_gid = 508 mail_location = maildir: /home/vpopmail/domains/%d/%n/Maildir mail_uid = 508 passdb { args = cache_key=%u%s:backend=%q driver = vpopmail } service auth { unix_listener auth-userdb { group = vpopmail user = vpopmail } } ssl = no userdb { driver = vpopmail } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 20 } Problem: Jul 08 12:35:08 auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth Jul 08 12:35:08 auth: Debug: new auth connection: pid=5514 Jul 08 12:35:08 auth: Debug: client in: AUTH 1 PLAIN service=imap lip=30.30.14.22 rip=192.168.0.100 lport=143 rport=53112 Jul 08 12:35:08 auth: Debug: client out: CONT 1 Jul 08 12:35:08 auth: Debug: client in: CONT 1 AHJraXJieaBteUxprmV1cC5jb20AYWJzcmNr Jul 08 12:35:08 auth: Debug: vpopmail(user(a)mydomain.com,192.168.0.100): lookup user=user domain=mydomain.com Jul 08 12:35:08 auth: Debug: client out: OK 1 user=user(a)mydomain.com Jul 08 12:35:08 auth: Debug: master in: REQUEST 1 5514 1 4a87d9ed9185eb0794667c5f7adb724f Jul 08 12:35:08 auth: Debug: vpopmail(user(a)mydomain.com,192.168.0.100): lookup user=user domain=mydomain.com Jul 08 12:35:08 master: Error: service(auth): child 5516 killed with signal 11 (core dumped) Jul 08 12:35:08 master: Error: service(auth): command startup failed, throttling Jul 08 12:35:08 imap-login: Info: Internal login failure (auth failed, 1 attempts): user=<user(a)mydomain.com>, method=PLAIN, rip=192.168.0.100, lip=30.30.14.22, mpid=5517 Thanks

3 2

Re: [Dovecot] Sieve user info log (was: problems with sieve under 2.0)
by Stephan Bosch 08 Jul '10

08 Jul '10

Hi Perry, Perry E. Metzger wrote: > By the way, I've noticed that there doesn't seem to be a good way for > the user to get information on what email message gets filed where by > sieve -- syslog information seems to be the sole data source > available. > Right. There is a per-user <main-script>.log file (e.g. .dovecot.sieve.log), but that will only be written when there are any errors. Info logging is indeed only available in the syslogs. > procmail has a facility where you can ask it to log every action it > takes. I looked around for a similar facility for sieve and I didn't > seem to see it. Did I miss something, or is it absent? > I DO see the merit of this. However, configuring this behavior is an interesting issue. If the user log verbosity is configured in the Dovecot userdb, it may in many cases still only be configurable by the administrator. An alternative solution would be to provide the logging configuration directly in the Sieve script; analogous to the way Procmail handles this. This would give users direct control. However, the Sieve specification and its extensions currently define no such facility. In fact, both Sieve and ManageSieve don't provide any means for the user to control what is logged during script execution. This would require some new or custom (vnd.dovecot.) Sieve or ManageSieve extension. However, defining a new extension like that is rarely useful unless clients implement support for it. Another problem is that users need filesystem access or some other custom (HTTP) interface to read the logs. This can be problematic when virtual users are involved. This too could be mended with an extension to the ManageSieve protocol. Alternatively, the Pigeonhole TODO list mentions a solution that writes logs as messages in a special IMAP-accessible folder, but I'm still not sure how practical that is. The above considerations may warrant starting a draft RFC on controlling and accessing Sieve runtime logs. But, I'm deviating from the original issue... what is it that you truly need right now? And for the Dovecot list, any other ideas on the above? Regards, Stephan.

2 1

[Dovecot] trash folder (again)
by Holger Hegmanns 08 Jul '10

08 Jul '10

Hi, I read very intently all the issues related to imap trash folders, but either I didn't unerstand them or my problem is slightly different. I plan to migrate from cyrus to dovecot. I've executed the perl script cyrus2dovecot successfully with the substitution flag "-E 's/^\./.INBOX./'" cause I want to have all folders as subfolders of the INBOX. The vmail dir looks like this afterwards: drwxr-xr-x 11 vmail vmail 4096 Jul 8 14:19 . drwxr-xr-x 3 vmail vmail 4096 Jul 8 14:19 .. drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Drafts drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Sent drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Templates drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Trash drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.blah drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.blub drwxr-xr-x 2 vmail vmail 4096 Jul 8 14:19 cur -rw-r--r-- 1 vmail vmail 119 Jul 8 14:19 dovecot-uidlist drwxr-xr-x 2 vmail vmail 4096 Jul 8 14:19 new -rw-r--r-- 1 vmail vmail 80 Jul 8 14:19 subscriptions drwxr-xr-x 2 vmail vmail 4096 Jul 8 14:19 tmp After the first access with Thunderbird, regardless of the version (TB2x or TB3x) and regardless of using TB with an empty profile or a well filled up, the directory looks different: drwxr-xr-x 12 vmail vmail 4096 Jul 8 14:21 . drwxr-xr-x 3 vmail vmail 4096 Jul 8 14:19 .. drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Drafts drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Sent drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Templates drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Trash drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.blah drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.blub drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:21 .Trash drwxr-xr-x 2 vmail vmail 4096 Jul 8 14:19 cur -rw-r--r-- 1 vmail vmail 119 Jul 8 14:21 dovecot-uidlist -rw-r--r-- 1 vmail vmail 17408 Jul 8 14:21 dovecot.index.cache -rw-r--r-- 1 vmail vmail 448 Jul 8 14:21 dovecot.index.log drwxr-xr-x 2 vmail vmail 4096 Jul 8 14:19 new -rw-r--r-- 1 vmail vmail 86 Jul 8 14:21 subscriptions drwxr-xr-x 2 vmail vmail 4096 Jul 8 14:19 tmp A Trash folder was added by TB, I guess. The related lines of the local TB imap logfile (beginning chars are cutted): mydovedomain.lan:A:CreateNewLineFromSocket: * LIST (\HasChildren) "." "INBOX" ReadNextLine [stream=4ecf8a10 nb=22 needmore=0] mydovedomain.lan:A:CreateNewLineFromSocket: 5 OK List completed. mydovedomain.lan:A:SendData: 6 list "" "Trash" ReadNextLine [stream=4ecf8a10 nb=22 needmore=0] mydovedomain.lan:A:CreateNewLineFromSocket: 6 OK List completed. mydovedomain.lan:A:SendData: 7 create "Trash" ReadNextLine [stream=4ecf8a10 nb=24 needmore=0] mydovedomain.lan:A:CreateNewLineFromSocket: 7 OK Create completed. mydovedomain.lan:A:SendData: 8 subscribe "Trash" ReadNextLine [stream=4ecf8a10 nb=27 needmore=0] mydovedomain.lan:A:CreateNewLineFromSocket: 8 OK Subscribe completed. mydovedomain.lan:A:SendData: 9 list "" "Trash" ReadNextLine [stream=4ecf8a10 nb=37 needmore=0] mydovedomain.lan:A:CreateNewLineFromSocket: * LIST (\HasNoChildren) "." "Trash" Maybe it's a namespace related problem, cause the advanced TB preference panel looks like that: private namespace "" and the other both input fields are empty. In opposite to cyrus. The preexisting Trash folder (I created all the standard folders with cyradm by hand) below the INBOX seems sufficient to TB, no further Trash can was created and here all input fields are filled up as followed: private namespace "INBOX." shared "" other users "user." (only translated by me, it's a localized german version of TB) I tried hard to understand the namespace wiki page of dovecot, but without success. Finally my dovecot.conf, dovecot version is 1.2.11: protocols = imap managesieve protocol imap { listen = mydovedomain.lan:10143 } protocol managesieve { listen = mydovedomain.lan:12000 } disable_plaintext_auth = no log_path = /var/log/imap/dovecot.log ssl = no ssl_cert_file = /etc/ssl/dovecot/server.pem ssl_key_file = /etc/ssl/dovecot/server.key mail_location = maildir:~/Maildir mail_privileged_group = mail mail_debug = yes protocol imap { } protocol pop3 { } protocol managesieve { } protocol lda { postmaster_address = postmaster at mydovedomain.lan mail_plugins = cmusieve acl } auth_verbose = yes auth default { mechanisms = plain cram-md5 passdb passwd-file { args = /etc/dovecot/passwd } passdb pam { } userdb static { args = uid=vmail gid=vmail home=/var/spool/dovecot/vmail/%u } user = root } dict { } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append } Please don't punish me, if my problem is already solved. And sorry for my poor English Holgerr

2 4

[Dovecot] Thunderbird and shared mailboxes
by Keith Edmunds 08 Jul '10

08 Jul '10

I'm setting up shared mailboxes as in http://wiki.dovecot.org/SharedMailboxes/Shared, and have set ACLs as described on that page to share one folder of user A's mailbox with User B. However, I'm struggling to get Thunderbird for userb(a)example.com to read the shared folder of usera(a)example.com. Has anyone done this? Thunderbird 3.0, Dovecot 1.2.11 Thanks, Keith

2 10

[Dovecot] Eronious comment in sample Director configuration
by Brad Davidson 08 Jul '10

08 Jul '10

The sample Director configuration (10-director.conf) says that director_servers and director_mail_servers can be lists of either IPs or hostnames: # List of IPs or hostnames to all director servers, including ourself. # Ports can be specified as ip:port. The default port is the same as # what director service's inet_listener is using. #director_servers = # List of IPs or hostnames to all backend mail servers. Ranges are allowed # too, like 10.0.0.10-10.0.0.30. #director_mail_servers = However, if I use hostnames, it bails out with an "Invalid IP address" error. It also seems to be confusing the dashes in my hostnames for address range specifications. Obviously hostnames are not currently supported, but I thought I'd mention it so the documentation could be updated. -Brad

2 1

[Dovecot] Director error during sync
by Brad Davidson 08 Jul '10

08 Jul '10

Just an FYI - if I have a two-node director ring, I get this when I start up the second node: Jul 7 16:59:38 oh-popmap7 dovecot: director: Error: Received SYNC from 10.142.0.162:1234/left (seq=6) while already synced Totally expected since it's already received the same SYNC from the right side, but since I thought I heard you say that "any errors that Dovecot logs are bugs" I thought I'd report it ;) For that matter, it also logs errors when I shut down / restart the second node: Jul 7 16:59:37 oh-popmap7 dovecot: director: Error: Director 10.142.0.162:1234/left disconnected Jul 7 16:59:37 oh-popmap7 dovecot: director: Error: Director 10.142.0.162:1234/right disconnected Jul 7 16:59:37 oh-popmap7 dovecot: director: Error: director(10.142.0.162:1234/out): connect() failed: Connection refused -Brad

2 2

[Dovecot] Patch for second fs quota under solaris
by Juergen Obermann 08 Jul '10

08 Jul '10

Hallo. We use dovecot 1.2.12 running under Solaris 9 and wanted to set up a second filesystem quota root because the mail folders are in the users home directories and the inboxes of all users are in /var/mail. This is defined in dovecot.conf: quota = fs:Home-Verzeichnis:noenforcing quota2 = fs:INBOX:noenforcing:mount=/var/mail This second quota did not work, but now I found the reason why. The mountpoint_get in src/lib/mountpoint.c needs to call resetmnttab to find the filesystem for the second quota root (see man resetmnttab). The following patches correct this and also adds some debugging code to src/plugins/quota/quota-fs.c to show the processing of quota2. These patches are only needed for Solaris with filesystem quotas. dovecot-1.2.12 ############## *** ./src/lib/mountpoint.c.orig Mon Jan 25 00:14:17 2010 --- ./src/lib/mountpoint.c Thu Jul 8 11:21:11 2010 *************** *** 164,169 **** --- 164,170 ---- i_error("fopen(%s) failed: %m", MTAB_PATH); return -1; } + resetmnttab(f); while ((getextmntent(f, &ent.ext, sizeof(ent.ext))) == 0) { if (hasmntopt(&ent.ent, MNTOPT_IGNORE) != NULL) continue; *** ./src/plugins/quota/quota-fs.c.orig Sat Jun 19 00:12:44 2010 --- ./src/plugins/quota/quota-fs.c Wed Jul 7 16:54:20 2010 *************** *** 249,256 **** continue; mount = fs_quota_mountpoint_get(root->storage_mount_path); ! if (mount != NULL) fs_quota_mount_init(root, mount); } } --- 249,263 ---- continue; mount = fs_quota_mountpoint_get(root->storage_mount_path); ! if (mount != NULL) { ! if (quota->set->debug) { ! i_info("fs quota2 add storage dir = %s", root->storage_mount_path); ! i_info("fs quota2 block device = %s", mount->device_path); ! i_info("fs quota2 mount point = %s", mount->mount_path); ! i_info("fs quota2 mount type = %s", mount->type); ! } fs_quota_mount_init(root, mount); + } } } dovecot-2.0.rc1 ############### *** ./src/lib/mountpoint.c.orig Mon Jan 25 00:16:12 2010 --- ./src/lib/mountpoint.c Thu Jul 8 11:24:10 2010 *************** *** 164,169 **** --- 164,170 ---- i_error("fopen(%s) failed: %m", MTAB_PATH); return -1; } + resetmnttab(f); while ((getextmntent(f, &ent.ext, sizeof(ent.ext))) == 0) { if (hasmntopt(&ent.ent, MNTOPT_IGNORE) != NULL) continue; *** ./src/plugins/quota/quota-fs.c.orig Fri Jul 2 21:32:40 2010 --- ./src/plugins/quota/quota-fs.c Wed Jul 7 12:52:38 2010 *************** *** 264,271 **** continue; mount = fs_quota_mountpoint_get(root->storage_mount_path); ! if (mount != NULL) fs_quota_mount_init(root, mount); } } --- 264,278 ---- continue; mount = fs_quota_mountpoint_get(root->storage_mount_path); ! if (mount != NULL) { ! if (quota->set->debug) { ! i_debug("fs quota2 add mailbox dir = %s", root->storage_mount_path); ! i_debug("fs quota2 block device = %s", mount->device_path); ! i_debug("fs quota2 mount point = %s", mount->mount_path); ! i_debug("fs quota2 mount type = %s", mount->type); ! } fs_quota_mount_init(root, mount); + } } } Greetings, Jürgen Obermann -- Hochschulrechenzentrum der | Mail: Juergen.Obermann(a)hrz.uni-giessen.de Justus-Liebig-Universitaet | WWW: http://www.uni-giessen.de/obermann Heinrich-Buff-Ring 44 | Tel: 0641-99-13054 (0641-99-13001) D-35392 Giessen, Germany | Fax: 0641-99-13009

2 1

[Dovecot] dovecot 2.0 rc1 missing folder INBOX
by Burckhard Schmidt 08 Jul '10

08 Jul '10

Hello, I have maildir format, and usually I found a folder "INBOX" in older versions of dovecot. Now I get this folder structure: ~user/maildir with folder new tmp cur Drafts (auto generated) Sent (auto) Trash (auto) This happens if a first email arrives or the user logs in the first time. If I connect direct to the server and send the command 1 list "" "*" * LIST (\HasNoChildren) "/" "Sent" * LIST (\HasNoChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "Drafts" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\Noselect \HasNoChildren) "/" "FremdeOrdner" 1 OK List completed. Here "INBOX" is listed. Is this correct no folder "INBOX"? -- Regards --- Burckhard Schmidt

2 1

[Dovecot] expire
by Papp Tamás 08 Jul '10

08 Jul '10

hi! $ dovecot --exec-mail ext /usr/lib/dovecot/expire-tool.sh /usr/lib/dovecot/expire-tool.sh: 9: Bad substitution What's the problem, do I miss something? This is the first time, I trying to use expire. This is an Ubuntu 10.04 . Thank you, tamas

7 8

[Dovecot] problems with sieve under 2.0...
by Perry E. Metzger 08 Jul '10

08 Jul '10

I'm experimenting with a 2.0 setup, using the sieve plugin for 2.0 from mercurial. Without sieve, everything seems to work fine. Once I put in a .dovecot.sieve file, though, nothing gets delivered, with the only hint of what's going wrong being this mess in syslog: Jul 7 13:18:00 bellman dovecot: lda(perry): Panic: file index-transaction.c: line 70 (index_transaction_init): assertion failed: (box->opened) Jul 7 13:18:00 bellman dovecot: lda(perry): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0 [0x7f55e07fedd2] -> /usr/local/lib/dovecot/libdovecot.so.0(i_syslog_fatal_handler+0x2b) [0x7f55e07fee7b] -> /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f55e07ff1e3] -> /usr/local/lib/dovecot/libdovecot-storage.so.0 [0x7f55e0cbdc31] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_transaction_begin+0x3f) [0x7f55e0cbdc7f] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_begin+0x13) [0x7f55e0c750d3] -> /usr/local/lib/dovecot/libdovecot-sieve.so.0 [0x7f55df800724] -> /usr/local/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x173) [0x7f55df7f9183] -> /usr/local/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x7d) [0x7f55df807b5d] -> /usr/local/lib/dovecot/lib90_sieve_plugin.so [0x7f55dfa3bbed] -> /usr/local/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x44) [0x7f55e0a41e84] -> /usr/local/libexec/dovecot/dovecot-lda(main+0x692) [0x402f72] -> /lib/libc.so.6(__libc_start_main+0xe6) [0x7f55e00831a6] -> /usr/local/libexec/dovecot/dovecot-lda [0x402819] Ideas? -- Perry E. Metzger perry(a)piermont.com

4 7

[Dovecot] Thunderbird problem
by Frank Bonnet 08 Jul '10

08 Jul '10

Hello Some users had occasionally a problem with Thunderbird , some random emails with attachement(s) cannot be read anymore the email appears empty and TB seems to enter in an infinite loop saying it is downloading the message The only solution I found was : 1 - stop thunderbird on the client machine 2 - remove the .imap user's directory 3 - restart thunderbird on the client machine After doing that all emails re-appear normally and attachements are readable/downloadable again. ALL our clients use the IMAP(S) protocol. Anyone had the same problem ? Thanks F

19 61

[Dovecot] Australian Internet Filtering Position
by Ryan Halloway 08 Jul '10

08 Jul '10

List, With sites like this appearing everywhere: http://www.dontfilterme.com and http://nocleanfeed.com/ Just trying to get a general opinion with what everyone thinks of the filtering situation in Australia. Whether you believe its a good thing or a bad thing or you don't really care. I'm writing a letter to an Australian MP (Member of Parliament) and I want to get some actual opinions of what other systems administrators think of the internet filter, even if they are not in Australia. Not only at a technical aspect but at an opinion aspect as well. Either reply on list or pm me. I just want to get a general idea. Thanks, Ryan.

2 1

[Dovecot] OT: Sieve + Forward as Attachment
by Jerry 08 Jul '10

08 Jul '10

I know that this is technically not a Dovecot problem; however, I was wondering if anyone knew if 'sieve' had been updated with the ability to 'forward as attachment' a received document. I believe it has the ability to forward a document; however, I need the ability to forward it as an attachment if possible. Also I believe, somewhat due to my asking for them, that sieve exits with appropriate error codes. Is there a listing of these codes, other than in the actual program code itself, of what those exit codes are? -- Jerry ✌ Dovecot.user(a)seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ Imagine me going around with a pot belly. It would mean political ruin. Adolf Hitler

5 11

[Dovecot] sieve not respecting userdb_mail setting?
by Perry E. Metzger 07 Jul '10

07 Jul '10

It appears that the lda + sieve does not respect the userdb_mail setting, though the imap server does(!?). Is this expected behavior? Perry -- Perry E. Metzger perry(a)piermont.com

2 4

[Dovecot] Manually creating folders from terminal
by A. J. Giurato 07 Jul '10

07 Jul '10

I'm trying to use a script to create a mailbox structure. I'm aware that the structure should look like: ~/.maildir/.INBOX/{cur,tmp,new} ~/.maildir/.INBOX.Subfolder1/{cur,tmp,new} ~/.maildir/.INBOX.Subfolder2/{cur,tmp,new} ~/.maildir/.INBOX.Subfolder2.Subsubfolder1/{cur,tmp,new} ... I have tried manually making those directories and using the "maildirmake.dovecot" command that my system has. I feel that in the past, folders I have made this way worked. However, now none are showing up in my clients. In Thunderbird, they aren't even listed on the "Subscribe" window for me to enable. Using Squirrelmail doesn't show them either. Essentially what I am doing is taking my current IMAP dir structure, and making a copy in a subfolder called ".INBOX.Archive.<year>" to archive my old mail. Thus, .INBOX.Subfolder1.Subfolder2 becomes .INBOX.Archive.2009.Subfolder1.Subfolder2. My system: Ubuntu 8.04 # 1.0.10: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S ssl_listen: * disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mail_access_groups: mail default_mail_env: ~/.maildir mail_location: ~/.maildir auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix

4 10

[Dovecot] Director service for LMTP in 2.0rc1
by Oliver Eales 07 Jul '10

07 Jul '10

Hello, has anyone a running setup for LMTP proxy and the director service ? pop3/imap/managesieve is properly working, but i have problems with LMTP. I set it up as described in the conf.d/10-director.conf From the user_db i get proxy=y and no proxyhost as described for imap/pop3 But lmtp is complaining about the missing host: Jul 07 15:00:48 auth: Debug: master in: PASS 1 user56(a)domain.de service=lmtp lip=::1 lport=30025 rip=::1 rport=41992 Jul 07 15:00:48 auth: Debug: ldap(user56@domain.de,::1): pass search: base=ou=mailboxes,ou=vfag,c=de,o=top scope=subtree filter=(&(objectClass=uco)(mail=user56(a)domain.de)) fields=mailboxname,userpassword,myproxy Jul 07 15:00:48 auth: Debug: auth(user56@domain.de,::1): username changed user56(a)domain.de -> 1000000000032 Jul 07 15:00:48 auth: Debug: ldap(1000000000032,::1): result: mailboxname(user)=1000000000032 userpassword(password)=<hidden> myproxy(proxy)=y Jul 07 15:00:48 auth: Debug: master out: PASS 1 proxy Jul 07 15:00:48 lmtp(18537): Debug: auth input: proxy Jul 07 15:00:48 lmtp(18537): Error: proxy: host not given Jul 07 15:00:48 auth: Debug: master in: USER 2 user56(a)domain.de service=lmtp lip=::1 rip=::1 Jul 07 15:00:48 auth: Debug: ldap(user56@domain.de,::1): user search: base=ou=mailboxes,ou=vfag,c=de,o=top scope=subtree filter=(&(objectClass=uco)(mail=user56(a)domain.de)) fields=homeDirectory,uidNumber,gidNumber,quotaBytes Jul 07 15:00:48 auth: Debug: ldap(user56@domain.de,::1): result: homeDirectory(home)=/mail/001/32/00/00/1000000000032 quotaBytes(quota_rule=*:storage=%$B)=*:storage=1073741824B Jul 07 15:00:48 auth: Debug: master out: USER 2 user56(a)domain.de home=/mail/001/32/00/00/1000000000032 quota_rule=*:storage=1073741824B Do i still have have to set lmtp_proxy=yes ? My config: # 2.0.rc1 (056c3240a912): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.27.42-0.1-default x86_64 SUSE Linux Enterprise Server 11 (x86_64) auth_debug = yes auth_default_realm = domain.de auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes director_mail_servers = 10.189.34.99 10.189.34.100 director_servers = 10.189.34.38 151.189.34.59 disable_plaintext_auth = no dotlock_use_excl = yes lmtp_proxy = yes log_path = /var/log/dovecot.log mail_debug = yes mail_gid = 60001 mail_location = mdbox:%h:INDEX=%h/index mail_nfs_storage = yes mail_uid = 60001 managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date spamtest spamtestplus virustest namespace type=private { inbox = yes location = prefix = separator = . } passdb { args = /usr/local/etc/dovecot/dovecot-ldap-pw.conf driver = ldap } protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix } unix_listener auth-userdb { group = mode = 0600 user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 13459 } unix_listener director-userdb { mode = 0666 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director } service lmtp { inet_listener { port = 30025 } } service managesieve-login { executable = managesieve-login director inet_listener managesieve { port = 2000 } } service pop3-login { executable = pop3-login director } ssl = no userdb { args = /usr/local/etc/dovecot/dovecot-ldap-pw.conf driver = ldap } protocol lmtp { auth_socket_path = director-userdb }

2 1

[Dovecot] post 2.0rc1 compilation issue
by Michal Hlavinka 07 Jul '10

07 Jul '10

Hi, I was just updating dovecot to nightly snapshot for Fedora rawhide, but got following issue: fts-backend-solr.c: In function 'fts_box_name_get_root': fts-backend-solr.c:60: error: 'NAMESPACE_FLAG_INBOX' undeclared (first use in this function) fts-backend-solr.c:60: error: (Each undeclared identifier is reported only once and once again on line 750 seems the change http://hg.dovecot.org/dovecot-2.0/rev/07353259bb41 is not complete Michal

2 3

[Dovecot] Logging subjects of messages
by Sandu cucereanu 07 Jul '10

07 Jul '10

Dear Sirs, I want to know if there is any possibility to log the subjects of the messages downloaded from ther server. We use dovecot 1.0.15 with POP3S and IMAP and we want to keep a trace of the reading of messages by the users of our mail server (who, when and what are the subjects of the e-mail messages read) because some users complain that they did not read some messages but in the logs of the server (maillog files( those messages appear to be delivered to their inboxes. Thank you very much for your help Best regards Alexandru Cucereanu

2 1

[Dovecot] dovecot2 rc1: symbol hook_client_created: referenced symbol not found
by Burckhard Schmidt 07 Jul '10

07 Jul '10

Hello, by accident I had configured inside 15-lda.conf protocol lda { mail_plugins = autocreate imap_acl acl } (I only wanted autocreate sieve.) There ist a problem with the symbol hook_client_created: lda: Error: dlopen(/usr/dovecot-2.0.rc1/lib/dovecot/lib02_imap_acl_plugin.so) failed: ld.so.1: dovecot-lda: fatal: relocation error: file /usr/dovecot-2.0.rc1/lib/dovecot/lib02_imap_acl_ lugin.so: symbol hook_client_created: referenced symbol not found lda: Fatal: Couldn't load required plugins ) -- Burckhard Schmidt

2 1

[Dovecot] dsync convert Maildir -> mdbox, separators in subscriptions file
by Frode Nordahl 06 Jul '10

06 Jul '10

Hello, I'm playing around with Dovecot 2.0 beta 4. If I use dsync to convert a users mail stored in Maildir format to mdbox format, the subscriptions file in the new mdbox is created using the wrong mailbox separator ('.') leading to folders within folders not being readable by clients using the subscription feature. Excerpt from IMAP: . LIST "" "*" * LIST (\HasChildren) "/" "Spam" * LIST (\HasNoChildren) "/" "Spam/Test" . LSUB "" "*" * LSUB () "/" "Spam" * LSUB () "/" "Spam.Test" I am not currently using Maildir, and have no plans to either, so I am very pleased with mdbox using '/' as seperator. I am considering to use Maildir as a transition format so that I can use allready available scripts to do the job (uw2dovecot.pl first, then dsync). So the question is, is this a bug in dsync? At the time of conversion mail_location = maildir:~/Maildir I used the following command to do the conversion: # dsync -u username convert mdbox:~/mdbox -- Frode Nordahl

3 3

[Dovecot] how to setup a simplest travel-mode read-only IMAP
by Seetamraju Uday Bhaskar Sarma 06 Jul '10

06 Jul '10

Hi All, I don't use gmail/hotmail etc... I have been a Mozilla/SeaMonkey/Thunderbird user for ever now... The mail and folders are all on my private fileserver. But on certain tours, I do know in advance that I would like IMAP access to my mail folders. Nothing but the simplest read-only access to the years of accumulated email. (All that email was soft-mounted onto /mnt/mail for safety and simplicity.) I have read the FAQ and Wiki. I even created the /cur /new /tmp folders under /mnt/mail... (after noting errors in dovecot logs) But when I test from another machine as :- # mutt -f imap://sarma@10.0.1.10/Inbox mutt comes up blank. I did check that /mnt/mail/Inbox exists, and has read permissions to all. Ideally, I don't want dovecot updating my mail files. I just simply want to read my old mail, while my new mail will continue to reside-on/be-accessible via the webmail. Thanks in advance! # /usr/sbin/dovecot --version 1.0.15 # /usr/sbin/dovecot -n # 1.0.15: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_processes_count: 1 login_max_processes_count: 2 mail_privileged_group: mail mail_location: maildir:/mnt/mail:INDEX=/var/mail/dovecot/index:CONTROL=/var/mail/dovecot/lib:LAYOUT=fs mbox_dirty_syncs: no mbox_lazy_writes: no auth default: passdb: driver: pam userdb: driver: passwd

2 1

[Dovecot] Correct folder permissions for maildir....
by Donovan J. Edye 06 Jul '10

06 Jul '10

G'Day, I am trying to find a definitive answer to what the directory permissions should be for my configuration under Centos 5.5. I see a number of the following error messages in the maillog as a consequence of permissions errors. After reading the FAQ, Wiki etc. and browsing the web I am unable to determine just exactly what the user security settings should be for the offending folders. If anyone could point me in the right direction I would appreciate it. Should you require additional diagnostic information let me know and I will source it. The error messages: Jun 17 19:50:14 moe dovecot: POP3(carolyn.spyseebiz): mkdir_parents(/home/spyseebiz/homes/carolyn/mail/.imap/INBOX) failed: Permission denied Jun 17 19:53:09 moe dovecot: POP3(marnie.capitel): mkdir_parents(/home/capitel/homes/marnie/mail/.imap/INBOX) failed: Permission denied dovecot -n # 1.0.7: /etc/dovecot.conf protocols: imap pop3 imaps pop3s listen: 116.212.71.194 ssl_listen: 116.212.71.194 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 mail_location: mbox:~/mail/:INBOX=/var/mail/%u mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %v.%u namespace: type: private separator: / prefix: #mbox/ location: mbox:~/mail:INBOX=/var/mail/%u inbox: yes hidden: yes namespace: type: private separator: / location: maildir:~/Maildir auth default: passdb: driver: pam userdb: driver: passwd ps aux | grep dovecot root 3457 0.0 0.0 1880 508 ? Ss Jun13 0:20 /usr/sbin/dovecot root 5650 0.0 0.1 7952 1460 ? S 03:28 0:04 dovecot-auth dovecot 15591 0.0 0.1 4992 1760 ? S 19:26 0:00 imap-login dovecot 15598 0.0 0.1 4992 1752 ? S 19:26 0:00 imap-login dovecot 15627 0.0 0.1 4992 1508 ? S 19:26 0:00 imap-login dovecot 16596 0.0 0.1 4988 1748 ? S 19:45 0:00 pop3-login dovecot 16615 0.0 0.1 4988 1744 ? S 19:46 0:00 pop3-login dovecot 16720 0.2 0.1 4988 1500 ? S 19:47 0:00 pop3-login root 16726 0.0 0.0 4000 700 pts/0 S+ 19:48 0:00 grep dovecot -- --Donovan J. Edye Calico Communications - "All your marketing, communication & web needs." Home To: daisyndandelion.com.au, natiki.com.au, themarketingcoach.com.au w: calicom.com.au t: +61-2-6292-1573 f: +61-2-6292-1592 p: PO Box 165, Erindale Centre, ACT 2903, Australia

4 6

[Dovecot] Dovecot 2.0 beta4 and Expire Plugin
by Burckhard Schmidt 06 Jul '10

06 Jul '10

Hello, there seems to be an error writing into the expire database defined by dict. dict { expire = sqlite:/usr/dovecot/etc/dovecotbeta-dict-expire.conf } ... plugin { ... expire = AutoCleanSpam 1d expire_dict = proxy::expire } with dovecotbeta-dict-expire.conf: connect = /test/addons/expire/expiresbeta.db map { pattern = shared/expire/$user/$mailbox table = expires value_field = expire_stamp fields { username = $user mailbox = $mailbox } } sqlite shows schema: CREATE TABLE expires ( username varchar(100) not null, mailbox varchar(255) not null, expire_stamp integer not null, primary key (username, mailbox) ); CREATE TRIGGER mergeexpires BEFORE INSERT ON expires FOR EACH ROW BEGIN UPDATE expires SET expire_stamp=NEW.expire_stamp WHERE username = NEW.username AND mailbox = NEW.mailbox; SELECT raise(ignore) WHERE (SELECT 1 FROM expires WHERE username = NEW.username AND mailbox = NEW.mailbox) IS NOT NULL; END; Delivering of an email into folder AutoCleanSpam via sieve script works fine. error-log: Apr 08 12:57:05 lda(account1): Debug: sieve: executing compiled script /addons/sieve/account1.sieve Apr 08 12:57:05 lda(account1): Debug: expire: Mails expire in 86400 secs in mailbox: AutoCleanSpam Apr 08 12:57:05 dict: Error: sqlite: exec(INSERT INTO expires (expire_stamp,username,mailbox) VALUES ('1270810625','account1','AutoCleanSpam')) failed: unable to open database file (14) Apr 08 12:57:05 master: Error: service(dict): child 10936 killed with signal 11 (core not dumped - set drop_priv_before_exec=yes) Apr 08 12:57:05 master: Error: service(dict): command startup failed, throttling deliver-log: Apr 08 12:57:05 lda(account1): Error: read(/var/run/dovecot//dict) failed: Remote disconnected Apr 08 12:57:05 lda(account1): Info: sieve: msgid=<4BBDB681.10003(a)hu-berlin.de>: stored mail into mailbox 'AutoCleanSpam' If I use a non existing database filename in dovecotbeta-dict-expire.conf like connect = /test/addons/expire/expiresbeta.dbbbbb I see in the log dict: Error: sqlite: open(/test/addons/expire/expiresbeta.dbbbbb) failed: unable to open database file So I'm sure, having the rigth config file. Moreover how to start expire-tool now? dovecot --exec-mail ... is no more valid. Additional: /usr/dovecotbeta/sbin/dovecot --build-options Build options: ioloop=poll ipv6 openssl Mail storages: cydir dbox maildir mbox mdbox raw shared SQL drivers: sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap passwd prefetch passwd-file sql static /usr/dovecotbeta/sbin/dovecot -n # 2.0.beta4: /usr/dovecotbeta/etc/dovecot/dovecot.conf # OS: SunOS 5.9 sun4u auth_debug = yes auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ012345 67890 auth_verbose = yes base_dir = /var/run/dovecot/ debug_log_path = /var/log/dovecot-error default_client_limit = 6144 dict { expire = sqlite:/usr/dovecot/etc/dovecotbeta-dict-expire.conf } first_valid_gid = 20 first_valid_uid = 20 info_log_path = /var/log/dovecot-error listen = 172.19.5.17 log_path = /var/log/dovecot-error mail_access_groups = sysdov mail_debug = yes mail_gid = sysdov mail_location = dbox:%h:INDEX=/addons/index/%u:CONTROL=~/Control:LAYOUT=fs mail_privileged_group = sysdov mail_uid = sysdov mbox_write_locks = fcntl passdb { args = dovecot driver = pam } plugin { autocreate = AutoCleanSpam autocreate1 = Junk autocreate2 = Trash autocreate3 = Sent autocreate4 = Drafts autosubscribe = AutoCleanSpam autosubscribe1 = Junk autosubscribe2 = Trash autosubscribe3 = Sent autosubscribe4 = Drafts expire = AutoCleanSpam 1d expire_dict = proxy::expire sieve = /addons/sieve/%u.sieve } service pop3 { process_limit = 0 } ssl_cert = </opt/csw/etc/ssl/certs/mail.pem ssl_key = </opt/csw/ssl/priv/mail.key syslog_facility = local2 userdb { args = /usr/dovecot/etc/sybldap.conf driver = ldap } verbose_proctitle = yes protocol imap { log_path = /var/log/imap.log mail_plugin_dir = /usr/dovecotbeta/lib/dovecot mail_plugins = autocreate expire } protocol lda { auth_socket_path = /var/run/dovecot/auth-master info_log_path = /var/log/deliver.log log_path = /var/log/deliver.log mail_plugin_dir = /usr/dovecotbeta/lib/dovecot mail_plugins = sieve autocreate expire postmaster_address = postmaster(a)hu-berlin.de sendmail_path = /opt/csw/sbin/sendmail } -- Burckhard Schmidt

2 6

[Dovecot] ACL, forced INBOX subscription
by Matthias Rieber 06 Jul '10

06 Jul '10

Hi, I've two accounts 'matthias' and 'mailverwalter'. Mailverwalter want's to share the Spam folder: This is the situation in the beginning: (matthias) a LIST (SUBSCRIBED) "common." "*" a OK List completed. a LIST (SUBSCRIBED) "common.mailverwalter" "*" a OK List completed. (mailverwalter) a GETACL Spam * ACL "Spam" "mailverwalter" lrwstipekxacd a OK Getacl completed. a GETACL INBOX * ACL "INBOX" "mailverwalter" lrwstipekxacd a OK Getacl completed. So far so good. Mailverwalter sets the list permission: (mailverwalter) a SETACL "Spam" "matthias" l a OK Setacl complete. a GETACL "Spam" * ACL "Spam" "matthias" l "mailverwalter" lrwstipekxacd a OK Getacl completed. a GETACL "INBOX" * ACL "INBOX" "mailverwalter" lrwstipekxacd a OK Getacl completed. That's ok as well and I want to make sure that the INBOX doesn't have any other permission. After that, some listing: (matthias) a LIST (SUBSCRIBED) "common." "*" a OK List completed. a LIST (SUBSCRIBED) "common.mailverwalter." "*" a OK List completed. That's also ok, nothing subscribed. (matthias) a LIST "common.mailverwalter." "*" * LIST (\Noselect \HasChildren) "." "common.mailverwalter" * LIST (\HasNoChildren) "." "common.mailverwalter.Spam" a OK List completed. This normal folder listing seems to be ok, too, and then listing of the subcribed folders again: (matthias) a LIST (SUBSCRIBED) "common.mailverwalter." "*" * LIST (\Subscribed \NonExistent) "." "common.mailverwalter.INBOX" a OK List completed. And then, the INBOX is subscribed and \NonExistent because I don't have permissions on it. The folder stays subscribed as long as I'm connected to the server. When I disconnect and do the LIST (SUBSCRIBED) again, the folder is not subscribed as long I do not 'normal' list it. Happens with dovecot 1.2.11, haven't tried 2.0 yet. I assume that's not the intended behaviour. This INBOX folder confuses the Nokia n900 email client a lot, but it doesn't matter if it can be accessed or not. Regards, Matthias

2 4