- dovecot - dovecot.org

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

21 Jul '10

Hallo Ich habe ein Problem bei der Installation von Sieve: Konfiguration: Opensuse 11.2 64bit, dovecot 1.2.9, postfix, amavis, spamassassin. Wenn ich versucht dovecot sieve zu übersetzen bekomme ich immer folgende Fehlermeldung. Making all in libsieve make[1]: Entering directory `/download/dovecot-sieve-1.1.8/src/libsieve' /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I -I/src/lib -I../../src -g -O2 -DENABLE_REGEX -MT addr.lo -MD -MP -MF .deps/addr.Tpo -c -o addr.lo addr.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I -I/src/lib -I../../src -g -O2 -DENABLE_REGEX -MT addr.lo -MD -MP -MF .deps/addr.Tpo -c addr.c -fPIC -DPIC -o .libs/addr.o In file included from addr.y:35: ../../src/xmalloc.h:19:17: error: lib.h: No such file or directory make[1]: *** [addr.lo] Error 1 make[1]: Leaving directory `/download/dovecot-sieve-1.1.8/src/libsieve' make: *** [all-recursive] Error 1 Wäre echt toll, wenn mir jemand einen Tipp geben könnte. 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

2 1

[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