- dovecot - dovecot.org

Re: [Dovecot] expire plugin no delete 1.2.1 / 1.2.2
by Robert Schetterer 12 Aug '09

12 Aug '09

Timo Sirainen schrieb: > On Aug 3, 2009, at 3:26 AM, Robert Schetterer wrote: > >> Timo Sirainen schrieb: >>> On Fri, 2009-07-31 at 17:21 +0200, Robert Schetterer wrote: >>>> Hi Timo, >>>> so now its clear, the mail >>>> did not got deleted if i now do >>>> >>>> Info: robert(a)schetterer.com/Trash: no messages left >>> >>> So, it worked? "no messages left" means if you didn't give --test it >>> would have deleted all messages from the mailbox. >>> >> Hi Timo, no it didnt work >> i repeated the test since then twice >> the mail was not deleted > > Well, that message says that at the time there was no messages left in > the Trash. Do you mean that there were? Show me now what it says with: > > - expire-tool --test > - FETCH 1 X-SAVEDATE shows in a mailbox that should have expired messages > - SELECT * FROM .. showing the database row for the mailbox that should > have expired messages > Ok Timo, i start a new test to make sure mysql> select mailbox, from_unixtime(expire_stamp), username from expireplugin; +---------+-----------------------------+-----------------------+ | mailbox | from_unixtime(expire_stamp) | username | +---------+-----------------------------+-----------------------+ | Trash | 2009-08-04 09:40:21 | robert(a)schetterer.com | +---------+-----------------------------+-----------------------+ 1 row in set (0.00 sec) 1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH ACL RIGHTS=texk QUOTA] Logged in 2 select Trash * FLAGS (\Answered \Flagged \Deleted \Seen \Draft nonjunk Junk) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft nonjunk Junk \*)] Flags permitted. * 1 EXISTS * 0 RECENT * OK [UIDVALIDITY 1240758078] UIDs valid * OK [UIDNEXT 89] Predicted next UID * OK [HIGHESTMODSEQ 123] 2 OK [READ-WRITE] Select completed. 3 fetch 1:* (internaldate x-savedate) * 1 FETCH (INTERNALDATE "03-Aug-2009 09:40:16 +0200" X-SAVEDATE "03-Aug-2009 09:40:21 +0200") 3 OK Fetch completed. /usr/lib/dovecot/expire-tool.sh #!/bin/bash MAIL_PLUGINS=${MAIL_PLUGINS//imap_quota/} MAIL_PLUGINS=${MAIL_PLUGINS//mail_log/} MAIL_PLUGINS=${MAIL_PLUGINS//imap_acl/} exec ${0%.sh} "$@ /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf --exec-mail ext /usr/lib/dovecot/expire-tool.sh --test Info: Loading modules from directory: /usr/lib/dovecot/modules/imap Info: Module loaded: /usr/lib/dovecot/modules/imap/lib01_acl_plugin.so Info: Module loaded: /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so Info: Module loaded: /usr/lib/dovecot/modules/imap/lib20_autocreate_plugin.so Info: Module loaded: /usr/lib/dovecot/modules/imap/lib20_expire_plugin.so Info: Module loaded: /usr/lib/dovecot/modules/imap/lib20_fts_plugin.so Info: Module loaded: /usr/lib/dovecot/modules/imap/lib20_virtual_plugin.so Info: Module loaded: /usr/lib/dovecot/modules/imap/lib21_fts_squat_plugin.so Info: Quota root: name= backend=dict args=:proxy::quotadict Info: Quota warning: bytes=0 (95%) messages=0 command=/usr/local/bin/quota-warning.sh 95 Info: Quota warning: bytes=0 (80%) messages=0 command=/usr/local/bin/quota-warning.sh 80 Info: expire: pattern=Trash type=expunge secs=86400 Info: robert(a)schetterer.com/Trash: stop, expire time in future: Tue Aug 4 09:40:21 2009 /etc/crontab 45 9 * * * root /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf --exec-mail ext /usr/lib/dovecot/expire-tool.sh so lets see what happens tommorow and repeat the --test as well as the mysql test and internal savedate test after deletion time -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 13

[Dovecot] sieve/managesieve and spam filtering
by Charles Sprickman 11 Aug '09

11 Aug '09

Hello all, I've got a test environment setup in preparation for a move from qmail/vpopmail/courier to postfix/padmin/dovecot. I have a number of questions that seem to span multiple pieces of software, and this is one of them... Our policy with spam filtering is that a user should be able to turn it off (ie: not put tagged spam into a spam folder, but deliver to their inbox) if they want to. Currently qmailadmin and a custom squirrelmail plugin give people the option to do this by dumping a .qmail file in their directory that calls a common maildrop script that will deliver spam to the spam folder. It looks like I can emulate this with sieve and something that can speak to Dovecot's managesieve server. Where I'm stuck is that if I want users to be able to do other custom filtering using sieve, how do I go about making sure that my common spam delivery rule does not get clobbered? This really has me a bit stumped. I see there's a global sieverc that can be included, but I need something along the lines of a per-user include that brings in the spam filtering rule that will "stick" until the user explicitly deletes it. Any ideas? Thanks, Charles ___ Charles Sprickman NetEng/SysAdmin Bway.net - New York's Best Internet - www.bway.net spork(a)bway.net - 212.655.9344

2 2

[Dovecot] Index cache file problems in Dovecot 1.2.0
by Chris Wakelin 11 Aug '09

11 Aug '09

I've been seeing lots of index cache file errors (using mbox on Solaris 8 sparc 64-bit, but with 32-bit Dovecot) since I switched my account to Dovecot 1.2.0 (we're still on 1.0.15 mostly, but I'm hoping to upgrade to 1.1.17+ this summer, or 1.2.x if it's stable enough). e.g. Error: Corrupted index cache file <path>/.imap/INBOX/dovecot.index.cache: field index too large (47 >= 25) I've tried renaming/removing the .imap/INBOX directory, but the "Corrupted index cache file" errors return within a day or so. This morning, Thunderbird got itself in a mess retrying something that caused multiple core dumps: > Jul 14 08:52:53 dovecot: Error: child 17694 (imap) killed with signal 10 (core dumped) > Jul 14 08:52:54 dovecot: Error: child 17697 (imap) killed with signal 10 (core dumped) > Jul 14 08:52:55 dovecot: Error: child 17700 (imap) killed with signal 10 (core dumped) Here's a backtrace > #0 mail_cache_get_record (cache=0x124e28, offset=289, rec_r=0xffbeeb6c) > at mail-cache-lookup.c:30 > 30 if (rec->size < sizeof(*rec)) { > (gdb) bt > #0 mail_cache_get_record (cache=0x124e28, offset=289, rec_r=0xffbeeb6c) > at mail-cache-lookup.c:30 > #1 0x84e2c in mail_cache_lookup_iter_next_record (ctx=0xffbeeb60) > at mail-cache-lookup.c:186 > #2 0x84f14 in mail_cache_lookup_iter_next (ctx=0xffbeeb60, field_r=0xffbeeb50) > at mail-cache-lookup.c:219 > #3 0x85650 in mail_cache_lookup_headers_real (view=0x128510, dest=0x129728, > seq=11416, field_idxs=0xffbeec74, fields_count=2) > at mail-cache-lookup.c:500 > #4 0x85848 in mail_cache_lookup_headers (view=0x128510, dest=0x129728, > seq=11416, field_idxs=0xffbeec74, fields_count=2) > at mail-cache-lookup.c:555 > #5 0x6ba94 in index_mail_get_raw_headers (mail=0x128f20, > field=0xff142ee8 "Message-ID", value_r=0xffbeecfc) > at index-mail-headers.c:614 > #6 0x6c084 in index_mail_get_first_header (_mail=0x128f20, > field=0xff142ee8 "Message-ID", decode_to_utf8=false, value_r=0xffbeede4) > at index-mail-headers.c:771 > #7 0x7893c in mail_get_first_header (mail=0x128f20, > field=0xff142ee8 "Message-ID", value_r=0xffbeede4) at mail.c:118 > #8 0xff1419a0 in mail_log_add_hdr (mail=0x128f20, str=0x10edc8, > name=0xff142d68 "msgid", header=0xff142ee8 "Message-ID") > at mail-log-plugin.c:277 > #9 0xff141c5c in mail_log_action (dest_trans=0x128f20, mail=0x128f20, > event=MAIL_LOG_EVENT_DELETE, data=0x0) at mail-log-plugin.c:318 > #10 0xff141e5c in mail_log_mail_update_flags (_mail=0x128f20, > modify_type=MODIFY_ADD, flags=12) at mail-log-plugin.c:376 > #11 0x78af8 in mail_update_flags (mail=0x128f20, modify_type=MODIFY_ADD, > flags=12) at mail.c:184 > #12 0x2ab3c in cmd_store (cmd=0x11bec8) at cmd-store.c:192 > #13 0x2b5f8 in cmd_uid (cmd=0x11bec8) at cmd-uid.c:27 > #14 0x2ccc4 in client_command_input (cmd=0x11bec8) at client.c:611 > #15 0x2cb68 in client_command_input (cmd=0x11bec8) at client.c:660 > #16 0x2cd4c in client_handle_next_command (client=0x11bc40, > remove_io_r=0xffbef23f) at client.c:701 > #17 0x2ce40 in client_handle_input (client=0x11bc40) at client.c:713 > #18 0x2cf78 in client_input (client=0x11bc40) at client.c:752 > #19 0xc6c04 in io_loop_handler_run (ioloop=0x1186d8) at ioloop-poll.c:203 > #20 0xc63f4 in io_loop_run (ioloop=0x1186d8) at ioloop.c:338 > #21 0x369f4 in main (argc=1107968, argv=0xffbef484, envp=0xffbef494) > at main.c:323 I didn't have these problems with 1.1.x. I guess I ought to get out the imaptest tool and see if I can reproduce this reliably ... Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 3

[Dovecot] % in Usernames (dovecot 1.1.18)
by Michal Hlavinka 11 Aug '09

11 Aug '09

Hi, I'm forwarding feature request from one Fedora user: <snip> Shortly before suicide after migration to dbmail/postfix from Eudora Mailserver because we use % in Usernames as fallback and Apple-Mail does no Plaintext- Auth if CRAM-MD% was used before i installed dovecot as proxy BUT it allows no % in Username Please could be the following patch included? --- dovecot-1.1.18/src/master/master-settings.c 2009-07-27 03:56:32.000000000 +0200 +++ dovecot-1.1.18-patched/src/master/master-settings.c 2009-08-10 22:57:09.728065279 +0200 @@ -310,7 +310,7 @@ MEMBER(executable) PKG_LIBEXECDIR"/dovecot-auth", MEMBER(user) "root", MEMBER(chroot) "", - MEMBER(username_chars) "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@", + MEMBER(username_chars) "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@%", MEMBER(username_translation) "", MEMBER(username_format) "", MEMBER(master_user_separator) "", </snip> Would it be possible or is there any reason why this is a wrong idea? Regards, Michal Hlavinka

2 1

[Dovecot] dovecot-1.2.3 (managesieve) crash with backtrace
by Ralf Hildebrandt 11 Aug '09

11 Aug '09

>From the log: Aug 11 09:07:23 postamt dovecot: IMAP(zensy): Panic: file mail-index-transaction-view.c: line 106 (tview_apply_flag_updates): assertion failed: (map->hdr.record_size <= tview->record_size) Aug 11 09:07:23 postamt dovecot: IMAP(zensy): Raw backtrace: imap [0x80f0411] -> imap [0x80f0482] -> imap [0x80efe29] -> imap [0x80c839b] -> imap [0x80cea95] -> imap [0x80c85cf] -> imap(mail_index_lookup_ext_full+0x36) [0x80cda46] -> imap(mail_cache_lookup_cur_offset+0x49) [0x80bbad9] -> imap [0x80bbb5d] -> imap(mail_cache_lookup_iter_init+0x55) [0x80bbc05] -> imap(mail_cache_field_exists+0xaf) [0x80bc51f] -> imap(mail_cache_field_want_add+0x48) [0x80bcd98] -> imap(index_mail_parse_header_init+0x1c3) [0x80a4a33] -> imap(index_mail_parse_headers+0x60) [0x80a4c40] -> imap [0x80a500f] -> imap(index_mail_get_first_header+0x22) [0x80a5372] -> imap(mail_get_first_header+0x25) [0x80b0a85] -> /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so [0xb7e72bfb] -> /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so [0xb7e72f95] -> /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so [0xb7e73494] -> imap(cmd_store+0x475) [0x8065e95] -> imap [0x806769c] -> imap [0x8067743] -> imap(client_handle_input+0x2d) [0x806789d] -> im Aug 11 09:07:23 postamt dovecot: IMAP(zensy): io_loop_handler_run+0xe0) [0x80f9000] -> imap(io_loop_run+0x20) [0x80f8470] -> imap(main+0x5d2) [0x8070b52] Aug 11 09:07:23 postamt dovecot: dovecot: child 16960 (imap) killed with signal 6 (core dumped) Backtrace: 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 "i486-linux-gnu"... Reading symbols from /lib/i686/cmov/libdl.so.2...Reading symbols from /usr/lib/debug/lib/i686/cmov/libdl-2.9.so...done. done. Loaded symbols for /lib/i686/cmov/libdl.so.2 Reading symbols from /lib/i686/cmov/librt.so.1...Reading symbols from /usr/lib/debug/lib/i686/cmov/librt-2.9.so...done. done. Loaded symbols for /lib/i686/cmov/librt.so.1 Reading symbols from /lib/i686/cmov/libc.so.6...Reading symbols from /usr/lib/debug/lib/i686/cmov/libc-2.9.so...done. done. Loaded symbols for /lib/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...Reading symbols from /usr/lib/debug/lib/ld-2.9.so...done. done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /lib/i686/cmov/libpthread.so.0...Reading symbols from /usr/lib/debug/lib/i686/cmov/libpthread-2.9.so...done. done. Loaded symbols for /lib/i686/cmov/libpthread.so.0 Reading symbols from /usr/local/lib/dovecot/imap/lib10_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib10_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib11_trash_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib11_trash_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib20_autocreate_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib20_autocreate_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib20_fts_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib20_fts_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/libbz2.so.1.0...done. Loaded symbols for /lib/libbz2.so.1.0 Reading symbols from /usr/local/lib/dovecot/imap/lib21_fts_squat_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib21_fts_squat_plugin.so Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Core was generated by `imap [zensy 141.42.4.251]'. Program terminated with signal 6, Aborted. [New process 16960] #0 0xb801d424 in __kernel_vsyscall () #0 0xb801d424 in __kernel_vsyscall () No symbol table info available. #1 0xb7ecf3d0 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 resultvar = <value optimized out> pid = -1207963660 selftid = 16960 #2 0xb7ed2a85 in *__GI_abort () at abort.c:88 act = {__sigaction_handler = {sa_handler = 0x940d238, sa_sigaction = 0x940d238}, sa_mask = {__val = {3214463400, 135192458, 3087001312, 0, 3214463520, 3214463508, 512, 0, 0, 3214463584, 3087251056, 134566650, 1131, 0, 0, 0, 1, 135265534, 512, 1, 3214463508, 155243032, 69, 3214463636, 3214463480, 135194054, 155244195, 3214463508, 3214463512, 1132, 155243064, 3086442259}}, sa_flags = 1132, sa_restorer = 0x81059a9 <write_full+57>} sigs = {__val = {32, 0 <repeats 31 times>}} #3 0x080f0425 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:160 backtrace = 0x940ca08 "imap [0x80f0411] -> imap [0x80f0482] -> imap [0x80efe29] -> imap [0x80c839b] -> imap [0x80cea95] -> imap [0x80c85cf] -> imap(mail_index_lookup_ext_full+0x36) [0x80cda46] -> imap(mail_cache_lookup_cur_"... #4 0x080f0482 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x81084ec "file %s: line %d (%s): assertion failed: (%s)", args=0xbf98d2f4 "�X\021\bj") at failures.c:440 No locals. #5 0x080efe29 in i_panic ( format=0x81084ec "file %s: line %d (%s): assertion failed: (%s)") at failures.c:207 No locals. #6 0x080c839b in tview_lookup_full (view=0x9425230, seq=1, map_r=0xbf98d3f8, expunged_r=0xbf98d3c7) at mail-index-transaction-view.c:106 rec = (const struct mail_index_record *) 0x9434838 #7 0x080cea95 in view_lookup_ext_full (view=0x9425230, seq=1, ext_id=4, map_r=0xbf98d3f8, data_r=0xbf98d3f4, expunged_r=0xbf98d3c7) at mail-index-view.c:414 rec = <value optimized out> #8 0x080c85cf in tview_lookup_ext_full (view=0x9425230, seq=1, ext_id=4, map_r=0xbf98d3f8, data_r=0xbf98d3f4, expunged_r=0xbf98d3c7) at mail-index-transaction-view.c:408 ext_buf = (const union array__seq_array *) 0x0 data = <value optimized out> idx = <value optimized out> __PRETTY_FUNCTION__ = "tview_lookup_ext_full" #9 0x080cda46 in mail_index_lookup_ext_full (view=0x6, seq=1, ext_id=4, map_r=0xbf98d3f8, data_r=0xbf98d3f4, expunged_r=0x0) at mail-index-view.c:596 expunged = false #10 0x080bbad9 in mail_cache_lookup_cur_offset (view=0x9425230, seq=1, reset_id_r=0xbf98d42c) at mail-cache-lookup.c:65 cache = (struct mail_cache *) 0x94233b8 map = <value optimized out> data = (const void *) 0x4 offset = <value optimized out> #11 0x080bbb5d in mail_cache_lookup_offset (cache=0x94233b8, view=0x6, seq=16960, offset_r=0xbf98d498) at mail-cache-lookup.c:87 offset = <value optimized out> reset_id = 155333560 ret = <value optimized out> #12 0x080bbc05 in mail_cache_lookup_iter_init (view=0x9425410, seq=1, ctx_r=0xbf98d480) at mail-cache-lookup.c:154 ret = <value optimized out> #13 0x080bc51f in mail_cache_field_exists (view=0x9425410, seq=1, field=12) at mail-cache-lookup.c:292 __PRETTY_FUNCTION__ = "mail_cache_field_exists" #14 0x080bcd98 in mail_cache_field_want_add (ctx=0x9427af0, seq=1, field_idx=12) at mail-cache-transaction.c:1009 decision = MAIL_CACHE_DECISION_NO #15 0x080a4a33 in index_mail_parse_header_init (mail=0x94264b8, _headers=0x94319b0) at index-mail-headers.c:189 _data_stack_cur_id = 5 i = <value optimized out> field_idx = <value optimized out> __PRETTY_FUNCTION__ = "index_mail_parse_header_init" #16 0x080a4c40 in index_mail_parse_headers (mail=0x94264b8, headers=0x94319b0) at index-mail-headers.c:431 input = (struct istream *) 0x9423900 old_offset = 0 #17 0x080a500f in index_mail_get_raw_headers (mail=0x94264b8, field=0xb7e736f4 "Message-ID", value_r=0xbf98d608) at index-mail-headers.c:625 headers = {0xb7e736f4 "Message-ID", 0x0} value = <value optimized out> headers_ctx = (struct mailbox_header_lookup_ctx *) 0x0 data = <value optimized out> field_idx = 12 dest = (string_t *) 0x942cbf8 i = <value optimized out> len = <value optimized out> ret = <value optimized out> __PRETTY_FUNCTION__ = "index_mail_get_raw_headers" #18 0x080a5372 in index_mail_get_first_header (_mail=0x94264b8, field=0xb7e736f4 "Message-ID", decode_to_utf8=false, value_r=0xbf98d65c) at index-mail-headers.c:771 list = (const char * const *) 0x108 ret = 155239272 i = 0 #19 0x080b0a85 in mail_get_first_header (mail=0x94264b8, field=0xb7e736f4 "Message-ID", value_r=0xbf98d65c) at mail.c:118 No locals. #20 0xb7e72bfb in mail_log_add_hdr (mail=0x0, str=0x940c368, name=0xb7e736ff "msgid", header=0xb7e736f4 "Message-ID") at mail-log-plugin.c:277 value = 0xb7e72bdc "\201ô\035" #21 0xb7e72f95 in mail_log_action (dest_trans=<value optimized out>, mail=0x94264b8, event=MAIL_LOG_EVENT_DELETE, data=0x0) at mail-log-plugin.c:318 size = <value optimized out> str = (string_t *) 0x940c368 #22 0xb7e73494 in mail_log_mail_update_flags (_mail=0x94264b8, modify_type=MODIFY_ADD, flags=MAIL_DELETED) at mail-log-plugin.c:376 _data_stack_cur_id = 16960 lmail = <value optimized out> old_flags = <value optimized out> new_flags = <value optimized out> #23 0x08065e95 in cmd_store (cmd=0x9419688) at cmd-store.c:192 client = (struct client *) 0x94193f8 args = (const struct imap_arg *) 0x941e718 search_args = (struct mail_search_args *) 0x0 search_ctx = (struct mail_search_context *) 0x9427890 t = (struct mailbox_transaction_context *) 0x9427a50 mail = (struct mail *) 0x94264b8 ctx = {cmd = 0x9419688, max_modseq = 18446744073709551615, flags = MAIL_DELETED, keywords = 0x0, modify_type = MODIFY_ADD, silent = false} modified_set = {arr = {buffer = 0x9427b90, element_size = 8}, v = 0x9427b90, v_modifiable = 0x9427b90} uids = {arr = {buffer = 0x941e788, element_size = 3214464872}, v = 0x941e788, v_modifiable = 0x941e788} flags = <value optimized out> imap_sync_flags = <value optimized out> reply = <value optimized out> tagged_reply = <value optimized out> str = <value optimized out> ret = <value optimized out> #24 0x0806769c in client_command_input (cmd=0x9419688) at client.c:611 client = (struct client *) 0x94193f8 command = <value optimized out> __PRETTY_FUNCTION__ = "client_command_input" #25 0x08067743 in client_command_input (cmd=0x9419688) at client.c:660 client = (struct client *) 0x94193f8 command = <value optimized out> __PRETTY_FUNCTION__ = "client_command_input" #26 0x0806789d in client_handle_input (client=0x94193f8) at client.c:701 _data_stack_cur_id = 3 ret = false remove_io = <value optimized out> handled_commands = false __PRETTY_FUNCTION__ = "client_handle_input" #27 0x080681df in client_input (client=0x94193f8) at client.c:752 cmd = <value optimized out> output = (struct ostream *) 0x94195ac bytes = <value optimized out> __PRETTY_FUNCTION__ = "client_input" #28 0x080f9000 in io_loop_handler_run (ioloop=0x94149b0) at ioloop-epoll.c:208 ctx = (struct ioloop_handler_context *) 0x9414ab8 event = (const struct epoll_event *) 0x9414af8 list = (struct io_list *) 0x9419630 io = (struct io_file *) 0x9419608 tv = {tv_sec = 1, tv_usec = 575794} t_id = 2 msecs = <value optimized out> ret = 1 i = 0 j = 0 call = <value optimized out> #29 0x080f8470 in io_loop_run (ioloop=0x94149b0) at ioloop.c:338 No locals. #30 0x08070b52 in main (argc=) at main.c:327 No locals. $1 = {prev = 0x0, next = 0x0, client = 0x94193f8, pool = 0x9419670, tag = 0x9419700 "A004", name = 0x9419710 "UID STORE", args = 0x9419720 "1:* +FLAGS (\\Deleted)", cmd_flags = COMMAND_FLAG_BREAKS_SEQS, func = 0x8065a20 <cmd_store>, context = 0x0, module_contexts = {arr = {buffer = 0x94196c8, element_size = 4}, v = 0x94196c8, v_modifiable = 0x94196c8}, parser = 0x941e678, state = CLIENT_COMMAND_STATE_WAIT_INPUT, sync = 0x0, uid = 1, cancel = 0, param_error = 0, search_save_result = 0, temp_executed = 0} (gdb) quit -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

1 0

[Dovecot] Problems with Dovecot 1.2.3 + IMAP (SSL) + iPhone OS 3.0
by Sascha Scandella 11 Aug '09

11 Aug '09

Hello Has anyone else problems with Dovecot 1.2.3? For clients such as Thunderbird, Outlook 2007 everything works perfect. When I use an iPhone the child process is killed: Aug 11 08:08:44 imap-login: Info: Login: user=<username>, method=PLAIN,rip=1.2.3.4, lip=4.3.2.1, TLS Aug 11 08:08:44 dovecot: Error: child 5382 (imap) killed with signal 11 (core dumps disabled) Currently I have downgraded again to the working 1.2. I wonder if this problem is known or anyone is looking for it.

2 1

[Dovecot] RFC: Storing indexes in a (remote) database to increase dovecot scalability
by Mark Zealey 10 Aug '09

10 Aug '09

Hi all, This is just an idea I had over the weekend; I was wondering if instead of storing the indexes/caches on disk, it would be possible to have an option to store them in a remote database (eg mysql). There are several issues that we currently have with scaling dovecot, and I think that if it could store indexes in an external database we could alleviate most of these issues. In no particular order: 1) One major issue we have with dovecot is the number of iops it requires to keep its files in sync on our big disk arrays. If this were a mysql database, we'd have better ways of keeping these in sync, for example switching the speed at which it flushes the updates to disk, growth using partitioning/sharding, read-only slave instances etc, specific ssd storage for indexes/caches. I know that we could create a separate ssd disk array and export that over nfs too, but see issue (2) below. If indexes were stored in a mysql database we could choose to have a different reliability for the indexes (ie if the database server crashes we have 1 second of index changes lost, whereas for the email itself we can ensure it is always kept in sync on our other disk arrays). 2) nfs locking issues. No matter how hard we try, we always find there are some issues with concurrency over nfs. It really doesn't seem designed to handle these issues very well. I've not tried with nfsv4 and I believe there are some improvements there, but at the same time nfs wasn't really designed to store databases and have heavy concurrency. A proper database server (eg mysql, postgres) on the other hand thrives in this type of environment, especially when coupled with a transactional storage backend such as innodb which includes support for deadlock handling etc. 3) As we store all of our mail systems over nfs, effectively each export is a single-threaded connection to the server. No matter how fast the central nfs server you can realistically not go above 10k nfs ops/sec on the fastest of local networks due to latency issues. With mysql you could have multiple parallel connections to the central database store (1 per process?) which would mean more nfs ops available for actually serving the files. 4) Caching. Much more tuneable on a database server than in a filesystem. Eg in mysql there are loads of options to tune the various innodb/query/key caches, on nfs there are very few even on advanced netapps etc I know some of you store all your indexes on a single server locally & then store the emails on a remote central filestore. Whilst this is a good idea, it doesn't scale very well in that if the one server fails then everything has to be reindexed as clients login which causes incredible load as dovecot has to re-read most of the messages (in pop3 mode at least) in order to work out size counts etc. In my experience this reindexing would take out our email system for the best part of a day. I'm sure we could set something up with drbd mirroring or a central san array with ssd's for the index data, but this intrinsically does not scale with as much ease as a replicating database cluster could. There are also failover issues which can be very easily solved with a database system (eg mysql with an active/passive dual-master setup). Also, I know that most of these points refer to nfs; and I know that there are alternative methods (eg san + gfs or some other scalable filesystem) however most of these are relatively new technologies whereas nfs is pretty much the standard for remote file storage; certainly I'd consider it a lot more reliable when compared to the likes of gfs or lustre. Your typical large scale mail setup would be over nfs and this is the sort of environment that I've run into these scaling issues in. I've heard that gfs also doesn't work very well with 'hot spots' which indexes tend to be, although I've no first hand experience of this. So, although this post only really mentions nfs & mysql (the two technologies that I'm most familiar with) I think this is a much more general problem so I'm not advocating the use of either technology apart from them being most people's first choices for ease of use. What I'm really proposing is a way to separate the two different types of data that dovecot uses. Indexes&caches contain small frequent transactions; and whilst these are relatively important, dropping the past few seconds of these transactions doesn't seriously matter. On the other hand emails are larger, infrequently changed & it's important they are kept fully in sync - if we accept a message it should be guaranteed that we don't loose it. At the end of the day it seems to me that a filesystem is the ideal place to store emails, whereas a database server would be the ideal place to store indexes/caches. Obviously for speed of setup, simply storing everything on a filesystem is easy so I'm not suggesting that we abandon this route, but for truly large infrastructures I think being able to use a database system would have significant advantages in each of these four areas. Any thoughts? Mark -- Mark Zealey -- Platform Architect Product Development * Webfusion 123-reg.co.uk, webfusion.co.uk, donhost.co.uk, supanames.co.uk This mail is subject to http://www.gxn.net/disclaimer

2 1

[Dovecot] Dovecot-1.1.15 panics
by Mike Abbott 10 Aug '09

10 Aug '09

Dovecot-1.1.15 assert-fails frequently. Attached are some errors from the logs, and a stack trace from the common panic. Hope you can fix these soon. Thanks. 0 libSystem.B.dylib 0x00007fff8825e606 __kill + 10 1 libSystem.B.dylib 0x00007fff882e1c92 abort + 83 2 imap 0x0000000100069e1b default_fatal_finish + 70 3 imap 0x0000000100069e69 i_syslog_fatal_handler + 0 4 imap 0x00000001000695c8 i_info + 0 5 imap 0x000000010001913f maildir_uidlist_iter_next_rec + 210 6 imap 0x0000000100019177 maildir_uidlist_iter_next + 38 7 imap 0x0000000100018abb maildir_sync_index + 2019 8 imap 0x0000000100017788 maildir_sync_context + 662 9 imap 0x000000010001797c maildir_storage_sync_init + 104 10 imap 0x000000010000bbe3 imap_sync_init + 132 11 imap 0x000000010000be35 cmd_sync_delayed + 477 12 imap 0x0000000100006692 client_handle_input + 419 13 imap 0x000000010000676c client_input + 148 14 imap 0x0000000100070e60 io_loop_handler_run + 272 15 imap 0x0000000100070225 io_loop_run + 55 16 imap 0x000000010000d746 main + 1640 17 imap 0x0000000100000b84 start + 52

3 8

Re: [Dovecot] Mail archive
by fernando＠dfcom.com.br 10 Aug '09

10 Aug '09

I would like 'some process' to store old mails at a cheap storage. I know how to do it with symlinks, but I don´t know if it is the best option. So, I´m asking if dovecot improves it somehow. Fernando fernando at dfcom.com.br schrieb: > Hi, > > I´m using dovecot at our storages, accounts is distributed among many > storages (not entire domain), all of them with compression (when message > > 30Kb), nightly crontab script. > > Even though compression and many storages, we always have problems with > disk space and need to migrate accounts. > > Have you ever implemented any archive solution working with dovecot ? > > Regards, > Fernando > you might give more info what kind of "archive" you exactly mean meanwhile study http://wiki.dovecot.org/HowTo/ReadOnlyArchive http://wiki.dovecot.org/Plugins/Zlib http://wiki.dovecot.org/Plugins/Expire Alternative dbox directory expiration -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 1

[Dovecot] Mail archive
by fernando＠dfcom.com.br 10 Aug '09

10 Aug '09

Hi, I´m using dovecot at our storages, accounts is distributed among many storages (not entire domain), all of them with compression (when message > 30Kb), nightly crontab script. Even though compression and many storages, we always have problems with disk space and need to migrate accounts. Have you ever implemented any archive solution working with dovecot ? Regards, Fernando

2 1

[Dovecot] inconsistency with expire-tool and expire dict
by LEVAI Daniel 10 Aug '09

10 Aug '09

Hi! Here is the problem: passdb: daniell:*::::::user=daniell2 userdb: daniell2::uid:gid:gecos:home:: dovecot.conf: plugin { expire = SA.* 1 # (There are SA.HAM and SA.SPAM directories) } When copying a message to eg. the SA.HAM directory, then dovecot inserts this into my expires table: dovecot=# select * from expires ; username | mailbox | expire_stamp ---------------------+---------+-------------- daniell | SA.HAM | 1249976454 ^^^^^^^ wrong username This causes an error when running expire-tool (after changing expire_stamp): # /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire- tool --test Info: User lookup failed: daniell Info: daniell/SA.HAM: no messages left If I change the username field in the expires table... : # UPDATE expires SET username = 'daniell2'; UPDATE 1 ... expire-tool is fine: # /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire- tool --test Info: daniell2/SA.HAM: timestamp 1249880093 (Mon Aug 10 06:54:53 2009) -> 1249976454 (Tue Aug 11 09:40:54 2009) Daniel -- LÉVAI Dániel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1

1 1

[Dovecot] Mail not begin proccessed
by Andre Labuschagne 10 Aug '09

10 Aug '09

Good day all, [Dovecot version 1.2.1] I've set up postfix and dovecot on Centos. I have a problem with the mail, it is begin received but not "processed" by dovecot. I've looked in the maillog file and found two problems; the first is that private/dovecot directory (I think it should be a directory) did not exist and the second problem is "mail transport unavailable". I've create a directory called /var/spool/postfix/private/dovecot but I get the following error in the log file: Connection refused (Is this an ownership issue? I've made the owner postfix) As for the second problem, I've spend the most of the past 3 days googling the error and found very little "useful" information. Do I need to supply more info? Best regards, Andre

3 4

[Dovecot] Released Sieve v0.1.11 and ManageSieve v0.11.8 for Dovecot v1.2.3
by Stephan Bosch 10 Aug '09

10 Aug '09

Hello Dovecot users, Apart from unfinished development of the date extension, this is a set of bug-fix releases. A few portability issues were found, a few stupidities were fixed and the ManageSieve proxy now also works with TLS. Most notably, the include extension had an issue regarding the expansion of $HOME in the personal include path. I've built a project site at: http://pigeonhole.dovecot.org Changelog Sieve v0.1.11: + Built skeleton implementation for the date extension (RFC5260). It compiles, but it does not do anything useful yet. Therefore, it is not part of the default compilation. - Fixed ARM portability issues caused by char type not being signed on that platform. Reading optional operands from a binary would fail for action side effects. Also, an accidental mixup of an int return type with bool caused the interpreter to continue on ARM even though an error occured. - Removed direct stdint.h includes to prevent portability issues. - Fixed segfault bug in the handling of script open failures. - Include: improved user error messages and system log messages. - Fixed copy-paste mixup between sieve_after and sieve_before settings in the LDA Sieve plugin. If only a sieve_after script was active, nothing would have been executed. Patch by Mike Abbott. - Include: fixed a bug in HOME substitution in the sieve_dir path. Surfaced in ManageSieve. Changelog ManageSieve v0.11.8: - Fixed TLS support for proxying ManageSieve. The protocol state machine was incorrect. Also added a check that disables ssl when 'starttls' is not enabled for the user. This produces a proper warning in the log file. There is no such thing as a managesieveS protocol which has SSL from the start. The releases are available as follows: Sieve: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.11.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.11.tar.gz.sig ManageSieve (package + patch): http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.8.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.8.tar.gz.s… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.3-managesieve-0.11.8.diff.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.3-managesieve-0.11.8.diff.g… Have fun testing the new releases and don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 3

[Dovecot] virtual plugin and ACL
by Nikita Koshikov 10 Aug '09

10 Aug '09

Hello list, We are using virtual plugin for to provide users two additional folders: Company/all - it contains all messages in user's mailbox Company/favorites - here is flagged messages. Here is namespace part of config file: namespace private { prefix = Company/ separator = / location = virtual:/var/mail/virtual:INDEX=MEMORY:LAYOUT=maildir++ subscriptions = no } Everything works fine, but problem arises when someone rename or delete virtual mailbox. With above config, 1 user make changes to his mailbox, but changes distribute for entire domain. First, I have tried to add :CONTROL=/data/mail/%d/%n/data/virtual to location part of virtual namespace, but I have no luck with such settings. Directory /data/mail/%d/%n/data/virtual not even been created. Then I tried to setup ACL for virtual mailbox. Adding "acl" to mail_plugins in imap and lda section and acl=vfile to plugins config. Under /var/mail/virtual in each mailbox I create dovecot-acl file contaning: user=koshikov.n lrwstiekxa authenticated lrwstipe But this didn't work. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN] Server ready. a login test qwe a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA] Logged in a list "" * * LIST (\HasNoChildren) "/" "Sent" * LIST (\HasNoChildren) "/" "Drafts" * LIST (\HasNoChildren) "/" "Spam" * LIST (\HasNoChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\Noselect \HasChildren) "/" "Company" * LIST (\HasNoChildren) "/" "Company/all" * LIST (\HasNoChildren) "/" "Company/favorites" a OK List completed. a select Company/all * FLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk \*)] Flags permitted. * 13 EXISTS * 0 RECENT * OK [UIDVALIDITY 1249459221] UIDs valid * OK [UIDNEXT 14] Predicted next UID * OK [NOMODSEQ] No permanent modsequences a OK [READ-WRITE] Select completed. a getacl a BAD Error in IMAP command GETACL: Unknown command. a rename Company/all Company/test a OK Rename completed. After "rename completed" in /var/mail/virtual new file dovecot-acl-list is appear with content: 1249457074 test How can I get workaround for this situation ? I just need to restrict my users renaming and deleting virtualboxes.

2 2

[Dovecot] how secure is Dovecot when exposed to the Internet?
by Florin Andrei 10 Aug '09

10 Aug '09

$ dovecot -n # 1.1.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.28-11-server x86_64 Ubuntu 9.04 protocols: imap imaps managesieve I need to make an IMAP (actually imaps) server available over the Internet. Unfortunately, VPN is not available (not all clients support VPN), so I will have to expose the imaps port to the Internet. My question is: how reliable is Dovecot in such a setup? I am not talking about encryption (protecting the traffic between server and client). I am talking about having the daemon exposed to anything coming in from the Internet, buffer overflows and stuff like that. What's the security history of this software in situations like this? -- Florin Andrei http://florin.myip.org/

2 2

[Dovecot] http://wiki.dovecot.org/LDA typo
by LEVAI Daniel 09 Aug '09

09 Aug '09

-Note that dovecot.conf file must be world readable to enable deliver process read it, while running with user priviledges. +Note that dovecot.conf file must be world readable to enable deliver process read it, while running with user privileges. -- LÉVAI Dániel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1

2 2

[Dovecot] Wiki entry for expire plugin, PostgreSQL trigger needs update
by Stefan Förster 09 Aug '09

09 Aug '09

The wiki entry at http://wiki.dovecot.org/Plugins/Expire needs an update for Dovecot 1.2 and PostgreSQL: -- v1.2+: CREATE OR REPLACE FUNCTION merge_expires() RETURNS TRIGGER AS $$ BEGIN IF exists(SELECT 1 FROM expires WHERE username = NEW.username AND mailbox = NEW.mailbox) THEN UPDATE expires SET expire_stamp = NEW.expire_stamp WHERE username = NEW.username AND mailbox = NEW.mailbox; RETURN NULL; ELSE RETURN NEW; END IF; END; $$ LANGUAGE plpgsql; CREATE TRIGGER mergeexpires BEFORE INSERT ON expires FOR EACH ROW EXECUTE PROCEDURE merge_expires(); At least that's what I think after looking at the code: iter = dict_iterate_init(dict, DICT_EXPIRE_PREFIX, DICT_ITERATE_FLAG_RECURSE | DICT_ITERATE_FLAG_SORT_BY_VALUE); /* We'll get the oldest values (timestamps) first */ while (dict_iterate(iter, &key, &value) > 0) { /* key = DICT_EXPIRE_PREFIX<user>/<mailbox> */ userp = key + strlen(DICT_EXPIRE_PREFIX); [...] T_BEGIN { username = t_strdup_until(userp, p); If this code does somehow iterate usernames which are not present in the dict, I apologize. Cheers Stefan

1 1

[Dovecot] User Auth
by Richard Harwood 09 Aug '09

09 Aug '09

Hello all, I am new to the mailing list and I'm in the process of setting up a LAMP + mail server. I have configured my MTA (Postfix) to deliver messages to: /var/spool/mail/vhosts/domain.tld/name I have configured Dovecot as follows: -- # 1.2.2: /usr/local/etc/dovecot.conf protocols: imap imaps pop3 ssl: no disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login mail_privileged_group: mail mail_location: mbox:/var/spool/mail/vhosts/%d:INBOX=/var/spool/mail/vhosts/%d/%n mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 lda: postmaster_address: postmaster(a)example.com auth default: debug: yes passdb: driver: passwd-file args: /etc/passwd.dovecot userdb: driver: passwd -- Password excepted, my passwd.dovecot file containing a single virtual user looks like: richard:{plain}password:504:505::/home/vmail The uid/gid is the same as used by Postfix (a dedicated vmail user/group). That user/group owns the mbox I am trying to manipulate in this example. When I attempt to login via telnet on port 110 I get the error: +OK Dovecot ready. user richard(a)richardaharwood.com +OK pass password -ERR Authentication failed. It seems to dislike the fact I specify the domain as part of the login username. If I repeat and login as: user richard - I am authenticated, however I get the error: -ERR [IN-USE] Couldn't open INBOX: Internal error occurred. Refer to server log for more information. Tailing the maillog, I see the following: Aug 8 17:19:01 richardaharwood dovecot: auth(default): client in: AUTH 1 PLAIN service=pop3 secured lip=83.170.110.193 rip=83.170.110.193 lport=110 rport=58115 resp=<hidden> Aug 8 17:19:01 richardaharwood dovecot: auth(default): passwd-file(richard,83.170.110.193): lookup: user=richard file=/etc/passwd.dovecot Aug 8 17:19:01 richardaharwood dovecot: auth(default): client out: OK 1 user=richard Aug 8 17:19:01 richardaharwood dovecot: auth(default): master in: REQUEST 4 3603 1 Aug 8 17:19:01 richardaharwood dovecot: auth(default): passwd(richard,83.170.110.193): lookup Aug 8 17:19:01 richardaharwood dovecot: auth(default): master out: USER 4 richard system_groups_user=richard uid=500 gid=500 home=/home/richard Aug 8 17:19:01 richardaharwood dovecot: POP3(richard): Effective uid=500, gid=500, home=/home/richard Aug 8 17:19:01 richardaharwood dovecot: POP3(richard): mbox: data=/var/spool/mail/vhosts/:INBOX=/var/spool/mail/vhosts//richard Aug 8 17:19:01 richardaharwood dovecot: POP3(richard): fs: root=/var/spool/mail/vhosts, index=, control=, inbox=/var/spool/mail/vhosts//richard Aug 8 17:19:01 richardaharwood dovecot: POP3(richard): open(/var/spool/mail/vhosts//richard) failed: Permission denied (euid=500(richard) egid=500(richard) missing +x perm: /var/spool/mail/vhosts/) Aug 8 17:19:01 richardaharwood dovecot: POP3(richard): Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2009-08-08 17:19:01] Aug 8 17:19:01 richardaharwood dovecot: POP3(richard): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 Aug 8 17:19:01 richardaharwood dovecot: pop3-login: Login: user=<richard>, method=PLAIN, rip=83.170.110.193, lip=83.170.110.193, secured Assuming I could login with richard(a)richardaharwood.com, I should imagine Dovecot will successfully find the inbox, which is located at /var/spool/mail/vhosts/richardaharwood.com/richard in this example. I also notice the effective uid/gid is not that specified in the passwd file? The uid/gid appears to be that of my own ssh account which is not connected to the mail account that I wish to simply access as a virtual user. Would anyone be kind enough to point me in the right direction? In a nutshell, where am I going wrong with my authentication? This is a basic setup for the time being, until I get my head around it, but any pointers would be really appreciated. Have spent quite a few hours but I don't feel much closer to getting to the bottom of it! :) Many thanks, Richard

2 1

[Dovecot] multiple auth-client sockets
by LEVAI Daniel 09 Aug '09

09 Aug '09

Hi! I'm gonna need to use dovecot's auth-client socket in an authentication program. Now the auth-client socket is only used by my MTA, which is postfix. Because postfix's smtpd process (which uses the auth-client socket) runs chrooted under postfix's spool directory, I must create the auth-client socket under that spool directory. However, to reach that socket from another chrooted program is impossible. Can I create multiple instances of auth-client sockets? I tried to define another client {} stanza in socket listen {} in dovecot.conf, but only the last client socket got created. I need only a true or false response from dovecot regarding the authentication, and I thought that this is exactly what auth-client socket will do. However, if I can not reach it, is there any alternative to this? What's up with the auth-master or auth-worker sockets? Are they capable of respond to an auth request too? btw, I'm running dovecot-1.2.3 Thanks! Daniel -- LÉVAI Dániel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1

3 3

[Dovecot] autocreate plugin fails to subscribe mailbox in public namespace
by Stefan Förster 09 Aug '09

09 Aug '09

Hi, I'm one step away from replacing a 7 years old qmail/uw-imapd setup with some state of the art soft- and hardware. We got migration scripts and test almost done - just one thing that keeps failing: The autocreate plugin is supposed to subscribe new users to different mailboxes, one of them being in namespace "Public." - this subscription to "Public.announcements" fails. Below is a dovecot -n - and no, there are no error messages in the logs. # 1.2.2: /etc/dovecot/dovecot.conf # OS: Linux 2.6.30-bpo.1-amd64 x86_64 Debian 5.0.2 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps managesieve listen(default): *:143 listen(imap): *:143 listen(managesieve): * ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(managesieve): ssl_cert_file: /etc/ssl/owncerts/snakeoil.crt ssl_key_file: /etc/ssl/private/snakeoil.key login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login verbose_proctitle: yes mail_privileged_group: vmail mail_location: maildir:~/Maildir mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_process_size: 384 mail_plugins(default): quota imap_quota fts fts_squat acl autocreate expire trash mail_plugins(imap): quota imap_quota fts fts_squat acl autocreate expire trash mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve namespace: type: private separator: . inbox: yes list: yes subscriptions: yes namespace: type: public separator: . prefix: Public. location: maildir:/export/vmailboxes/public:INDEX=~/Maildir/public list: yes lda: postmaster_address: postmaster(a)test.cite.lan hostname: testvm06.test.cite.lan mail_plugins: quota sieve expire trash auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login cram-md5 passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: sasl master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: maildir:User quota quota_warning: storage=90%% /usr/local/bin/quota-warning.sh 90 quota_warning2: storage=95%% /usr/local/bin/quota-warning.sh 95 sieve: ~/.dovecot.sieve sieve_storage: ~/sieve sieve_extensions: +imapflags fts: squat fts_squat: partial=4 full=10 acl: vfile autocreate: Trash autocreate2: Drafts autocreate3: Sent autocreate4: learn-spam autosubscribe: Trash autosubscribe2: Drafts autosubscribe3: Sent autosubscribe4: learn-spam autosubscribe5: Public.announcements autosubscribe6: INBOX expire: Trash 60 Trash/* 60 expire_dict: proxy::expire trash: /etc/dovecot/dovecot-trash.conf dict: expire: pgsql:/etc/dovecot/dovecot-dict-expire.conf Any hints are really appreciated. Cheers Stefan BTW: If anybody is interested, I could provide load and usage statistics of our old and new software once step 1 of our migration (new hardware is step 2) is done. Only ~1000 users, but still...

2 1

[Dovecot] fatal: no SASL authentication mechanisms
by Ebbe Hjorth 09 Aug '09

09 Aug '09

Hi, I have setup freebsd, postfix, dovecot and maia, but all the time i get the following error in /var/log/maillog - and i cant google me to the solution, please advice. Aug 9 12:18:49 mail02 dovecot: auth(default): Authentication client trying to connect to master socket Aug 9 12:18:49 mail02 postfix/smtpd[1356]: fatal: no SASL authentication mechanisms Aug 9 12:18:50 mail02 postfix/master[777]: warning: process /usr/local/libexec/postfix/smtpd pid 1355 exit status 1 Aug 9 12:18:50 mail02 postfix/master[777]: warning: /usr/local/libexec/postfix/smtpd: bad command startup -- throttling Aug 9 12:18:50 mail02 amavis[834]: (00834-04) mail_via_smtp: 450 4.4.1 Can't connect to 127.0.0.1 port 10025, Bad file descriptor at /usr/local/sbin/amavisd-maia line 6599, <GEN12> line 229., id=00834-04 mail02# dovecot -n # 1.1.16: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-RELEASE-p2 i386 ufs protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/dovecot/cert.pem ssl_key_file: /etc/ssl/dovecot/key.pem disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: Apz.dk mail server ready. login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no verbose_proctitle: yes first_valid_uid: 125 last_valid_uid: 125 first_valid_gid: 125 last_valid_gid: 125 mail_privileged_group: mail mail_location: maildir:/usr/local/virtual/%d/%n mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login username_format: %Lu passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix

2 2

[Dovecot] Creating a "default" domain
by Charles Sprickman 09 Aug '09

09 Aug '09

Hello, I'm setting up a test server to work through the issues involved in bringing a bunch of vpopmail/qmail/courier users into a postfix/dovecot server. So far I'm seeing lots of info to aid in the transition. One thing I'm lost on is that since Dovecot is providing all the auth mechanisms rather than vpopmail, I'm not sure how to emulate a particular vpopmail behavior we rely on. Vpopmail allows for the concept of a "default" domain for authentication. So if I have a bunch of domains, and one is "example.com", users in that domain can login with only the username part of their id (ie: "john") rather than supplying the domain (ie: "john(a)example.com"). I need to continue to offer this unless I want to walk a few hundred users through reconfiguring their mail clients. :) Any pointers? Thanks, Charles ___ Charles Sprickman NetEng/SysAdmin Bway.net - New York's Best Internet - www.bway.net spork(a)bway.net - 212.655.9344

2 2

[Dovecot] convert config from 1.1.2_1 to 1.1.16
by Ebbe Hjorth 09 Aug '09

09 Aug '09

Hi, Im tryin to follow a guide, telling me howto setup freebsd with postfix and dovecot. The text in bold (first section), is what the guide says, and the text that follows is what the /usr/local/etc/dovecot.conf files says. Can you please help me on how to convert from the 1.1.2_1 setup to the correct configuration for the 1.1.16? / Thank you very much. *socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } * socket listen { master { # Master socket provides access to userdb information. It's typically # used to give Dovecot's local delivery agent access to userdb so it # can find mailbox locations. path = /var/spool/postfix/private/auth mode = 0600 # Default user/group is the one who started dovecot-auth (root) #user = #group = } client { # The client socket is generally safe to export to everyone. Typical use # is to export it to your SMTP server so it can do SMTP AUTH lookups # using it. path = /var/run/dovecot/auth-client mode = 0660 }

3 5

[Dovecot] v1.2.3 released
by Timo Sirainen 08 Aug '09

08 Aug '09

http://dovecot.org/releases/1.2/dovecot-1.2.3.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.3.tar.gz.sig A few days later than I wanted, but here it is. * Mailbox names with control characters can't be created anymore. Existing mailboxes can still be accessed though. + Allow namespace prefix to be opened as mailbox, if a mailbox already exists in the root dir. - Maildir: dovecot-uidlist was being recreated every time a mailbox was accessed, even if nothing changed. - listescape plugin was somewhat broken - Compiling fixes for non-Linux/BSDs - imap: tb-extra-mailbox-sep workaround was broken. - ldap: Fixed hang when >128 requests were sent at once. - fts_squat: Fixed crashing when searching virtual mailbox. - imap: Fixed THREAD .. INTHREAD crashing.

2 1

[Dovecot] All mail in mbox disappears when using Outlook
by Frank Leonhardt 08 Aug '09

08 Aug '09

I thought I was imaging it but... I have a friend (honestly) that likes to clear his inbox every month by copying older into a folder (e.g. June-2009). Every month he complains that all the mail in the new folder has disappeared. This has happened three times now, and he's sort-of-right. I now believe it's a bug rather than him. The setup is Dovecot 1.1.3 on FreeBSD 7.0 and the client is Outlook 2003 SP3 (using IMAP). What you end up with is a folder called June-2009 with no messages visible. Outlook reckons it's completely empty - size 0. I don't know how he gets to this point, but it can't be anything that bizarre - just copying messages. It's happened three months in a row. However, he can't see the contents and I can't see the contents using Outlook. Strangely, Eudora and Squirrel have no problem. Corrupt mbox file? Probably not. If you copy the problem one, the copy works fine. The really weird thing is that if you rename the problem file (using mv) it STILL DOESN'T work. I've considered the possibility that it's got a bad lock on it, but if so, how come Squirrel and Eudora have no problem? I've searched as far as I can for any known problems using Outlook. What next? Thanks, Frank. ====================================================== # 1.1.3: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/mail/certs/dovecot-cert.pem ssl_key_file: /etc/mail/certs/dovecot-private.pem disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: mbox:~/mail/:INBOX=/var/mail/%u maildir_copy_preserve_filename: yes 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_process_size: 512 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_enable_last(default): no pop3_enable_last(imap): no pop3_enable_last(pop3): yes pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login username_format: %Ln process_size: 512 passdb: driver: pam args: session=yes dovecot userdb: driver: passwd args: blocking=yes socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384

4 10