- dovecot - dovecot.org

[Dovecot] namespaces
by jorge martinez 21 Jul '10

21 Jul '10

Hello, i have an issue with vpopmail, this created a sub folder named "0" and all the new users created inside this folder into the domain folder. Weel i don understand why vpopmail do that, but i want to know if the option in dovecot.conf namespaces i can make it to search the Maildir in both directories. name domain/user & name domain/0/name user. CAn you help me??? Any options.

2 1

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

20 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