- dovecot - dovecot.org

Multiple user attributes in LDAP
by CARDENAS Eduardo SIDOR 25 Oct '14

25 Oct '14

Hello, I have an issue with dovecot and Ldap… Any help will be grateful… I have dovecot 1.2.15 and i want to know if in that version can i use two values returned from LDAP in the user_attrs template? Thanking you in anticipation… -- " Notificación Automática: Este mensaje y cualquier archivo que se adjunte contiene información privilegiada y confidencial. Es para uso exclusivo del destinatario. Si usted ha recibido esta comunicación por error, por favor avísenos inmediatamente. Automatic notification: This e-mail and any file transmitted with it are confidential and may be legally privileged. It is intended solely for the addressee and may not be disclosed to or used by anyone other than the addressee. If you have received this e-mail by mistake , please advise the sender immediately"

3 3

Where can I find change logs/release notes for Dovecot EE releases?
by deoren 25 Oct '14

25 Oct '14

I searched for them and haven't come across them yet. Could any point me in the right direction? Specifically the Ubuntu 12.04 package notes if they're split out. Thanks!

4 4

2.2.14 Panic in sync_expunge_range()
by Hans Morten Kind 25 Oct '14

25 Oct '14

I am getting some panics after upgrading from 2.2.13 to 2.2.14 This panic happens for one user only, he is subscribed to 86 folders, on two of them this panic happens quite often - several times a day. The mbox folders seems OK, less than 30M with 30 and 200 messages. Panic: file mail-index-sync-update.c: line 250 (sync_expunge_range): assertion failed: (count > 0) hmk GNU gdb 6.8 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 "i386-pc-solaris2.10"... Reading symbols from /datapool/local/dovecot-2.2.14/lib/dovecot/libdovecot-storage.so.0...done. Loaded symbols for /local/dovecot-2.2.14/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /datapool/local/dovecot-2.2.14/lib/dovecot/libdovecot.so.0...done. Loaded symbols for /local/dovecot-2.2.14/lib/dovecot/libdovecot.so.0 Reading symbols from /datapool/local/program/lib/libssl.so.1.0.0...done. Loaded symbols for /local/program/lib/libssl.so.1.0.0 Reading symbols from /datapool/local/program/lib/libcrypto.so.1.0.0...done. Loaded symbols for /local/program/lib/libcrypto.so.1.0.0 Reading symbols from /datapool/local/program/lib/libz.so...done. Loaded symbols for /local/program/lib/libz.so Reading symbols from /lib/libm.so.2...done. Loaded symbols for /lib/libm.so.2 Reading symbols from /datapool/local/program/lib/libiconv.so.2...done. Loaded symbols for /local/program/lib/libiconv.so.2 Reading symbols from /lib/librt.so.1...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /lib/libnsl.so.1...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/libsocket.so.1...done. Loaded symbols for /lib/libsocket.so.1 Reading symbols from /lib/libsendfile.so.1...done. Loaded symbols for /lib/libsendfile.so.1 Reading symbols from /lib/libc.so.1...done. Loaded symbols for /lib/libc.so.1 Reading symbols from /lib/libdl.so.1...done. Loaded symbols for /lib/libdl.so.1 Reading symbols from /usr/lib/libz.so...done. Loaded symbols for /usr/lib/libz.so Reading symbols from /lib/libaio.so.1...done. Loaded symbols for /lib/libaio.so.1 Reading symbols from /lib/libmd.so.1...done. Loaded symbols for /lib/libmd.so.1 Reading symbols from /lib/ld.so.1...done. Loaded symbols for /lib/ld.so.1 Core was generated by `dovecot/imap imap-postlogin'. Program terminated with signal 6, Aborted. [New process 76621 ] #0 0xfe7fc8e5 in _lwp_kill () from /lib/libc.so.1 #0 0xfe7fc8e5 in _lwp_kill () from /lib/libc.so.1 No symbol table info available. #1 0xfe7f7765 in thr_kill () from /lib/libc.so.1 No symbol table info available. #2 0xfe7a376f in raise () from /lib/libc.so.1 No symbol table info available. #3 0xfe7829e1 in abort () from /lib/libc.so.1 No symbol table info available. #4 0xfeda13ba in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:152 backtrace = 0x8093660 "0xfeda22d7 -> 0xfeda15d3 -> 0xfef31e5f -> 0xfef32d65 -> 0xfef3349e -> 0xfef33b77 -> 0xfef1dcbd -> 0xfef170e4 -> 0xfef173a4 -> 0xfef1767d -> 0xfef03e09 -> 0xfeea5540 -> 0xfeea5714 -> 0xfeea5857 -> 0xfe"... #5 0xfeda22d7 in i_internal_fatal_handler (ctx=0x8047400, format=0xfef5ebc8 "file %s: line %d (%s): assertion failed: (%s)", args=0x8047424 ".ìõþú") at failures.c:152 status = 0 #6 0xfeda15d3 in i_panic (format=0xfef5ebc8 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:152 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0, timestamp_usecs = 0} args = 0x8047424 ".ìõþú" #7 0xfef31e5f in sync_expunge_range (ctx=0x8047600, seqs=0x80474d8) at ../../src/lib/array.h:197 map = (struct mail_index_map *) 0x80c5d90 range = (const struct seq_range *) 0x8093430 i = 134509780 count = 0 dest_seq1 = 562 prev_seq2 = 562 orig_rec_count = 4277606968 __FUNCTION__ = "sync_expunge_range" #8 0xfef32d65 in mail_index_sync_record_real (ctx=0x8047600, hdr=0x80b5d28, data=0x80b5df8) at ../../src/lib/array.h:197 rec = (const struct mail_transaction_expunge_guid *) 0x80b8968 end = (const struct mail_transaction_expunge_guid *) 0x80b8968 seqs = {arr = {buffer = 0x8093410, element_size = 8}, v = 0x8093410, v_modifiable = 0x8093410} seq = 0 modseq = 32612 ret = 0 __FUNCTION__ = "mail_index_sync_record_real" #9 0xfef3349e in mail_index_sync_record (ctx=0x8047600, hdr=0x80b5d28, data=0x80b5df8) at ../../src/lib/array.h:197 _data_stack_cur_id = 5 ret = 1 #10 0xfef33b77 in mail_index_sync_map (_map=0x80b5400, type=MAIL_INDEX_SYNC_HANDLER_HEAD, force=true) at ../../src/lib/array.h:197 map = (struct mail_index_map *) 0x0 index = (struct mail_index *) 0x80b53b0 view = (struct mail_index_view *) 0x80ab8b0 sync_map_ctx = {view = 0x80ab8b0, modseq_ctx = 0x809ca50, cur_ext_map_idx = 0, ext_intro_seq = 5, ext_intro_offset = 52, ext_intro_end_offset = 84, expunge_handlers = {arr = { buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}, extra_contexts = {arr = { buffer = 0x809c348, element_size = 4}, v = 0x809c348, v_modifiable = 0x809c348}, unknown_extensions = 0x0, type = MAIL_INDEX_SYNC_HANDLER_HEAD, sync_handlers_initialized = 0, expunge_handlers_set = 0, expunge_handlers_used = 0, cur_ext_ignore = 0, internal_update = 0, errors = 0} thdr = (const struct mail_transaction_header *) 0x80b5d28 tdata = (const void *) 0x80b5df8 prev_seq = 5 start_offset = 0 prev_offset = 144 ret = 1 had_dirty = false reset = true __FUNCTION__ = "mail_index_sync_map" #11 0xfef1dcbd in mail_index_map (index=0x80b53b0, type=MAIL_INDEX_SYNC_HANDLER_HEAD) at mail-index-map-read.c:35 ret = 1 __FUNCTION__ = "mail_index_map" #12 0xfef170e4 in mail_index_try_open (index=0x80b53b0) at ../../src/lib/array.h:197 ret = 134919688 __FUNCTION__ = "mail_index_try_open" #13 0xfef173a4 in mail_index_open_files (index=0x80b53b0, flags=21) at ../../src/lib/array.h:197 ret = 1 #14 0xfef1767d in mail_index_open (index=0x80b53b0, flags=21) at ../../src/lib/array.h:197 ret = 134960048 __FUNCTION__ = "mail_index_open" #15 0xfef03e09 in index_storage_mailbox_open (box=0x80b47c8, move_to_memory=false) at index-storage.c:39 ibox = (struct index_mailbox_context *) 0x80b4a80 index_flags = 21 ret = 0 __FUNCTION__ = "index_storage_mailbox_open" #16 0xfeea5540 in mbox_mailbox_open_finish (mbox=0x80b47c8, move_to_memory=false) at mbox-storage.c:77 No locals. #17 0xfeea5714 in mbox_mailbox_open_existing (mbox=0x80b47c8) at mbox-storage.c:77 box = (struct mailbox *) 0x80b47c8 rootdir = 0xfeea581f "\215\225`ÿÿÿ\211T$\004\211\004$è\023¨ûÿ\211Eð\203}ð" box_path = 0x80b4b78 "/Home/USER/mail/pro/triad" move_to_memory = false #18 0xfeea5857 in mbox_mailbox_open (box=0x80b47c8) at mbox-storage.c:77 mbox = (struct mbox_mailbox *) 0x80b47c8 st = {st_dev = 82051096, st_pad1 = {0, 0, 0}, st_ino = 4141941, st_mode = 33152, st_nlink = 1, st_uid = 32440, st_gid = 4601, st_rdev = 0, st_pad2 = {0, 0}, st_size = 16826589, st_atim = { tv_sec = 1411034237, tv_nsec = 0}, st_mtim = {tv_sec = 1413152136, tv_nsec = 0}, st_ctim = { tv_sec = 1413659956, tv_nsec = 975959000}, st_blksize = 8192, st_blocks = 33016, st_fstype = "nfs", '\0' <repeats 12 times>, st_pad4 = {0, 0, 0, 0, 0, 0, 0, 0}} ret = 0 #19 0xfeec94cc in mailbox_open_full (box=0x80b47c8, input=0x0) at ../../src/lib/array.h:197 _data_stack_cur_id = 4 ret = 143 #20 0xfeec9807 in mailbox_open (box=0x80b47c8) at ../../src/lib/array.h:197 No locals. #21 0xfef024ec in index_storage_get_status (box=0x80b47c8, items=23, status_r=0x8047a04) at index-status.c:23 No locals. #22 0xfeeca8ac in mailbox_get_status (box=0x80b47c8, items=23, status_r=0x8047a04) at ../../src/lib/array.h:197 __FUNCTION__ = "mailbox_get_status" #23 0x08073ddb in imap_status_get (cmd=0x80b1fb8, ns=0x80ab1b0, mailbox=0x8093318 "pro/triad", items=0x8047a70, result_r=0x8047a04) at imap-status.c:23 client = (struct client *) 0x80b17b0 box = (struct mailbox *) 0x80b47c8 errstr = 0x8064d84 "\205Àu\034\213\205hÿÿÿÇD$\004\005" ret = 0 #24 0x08064e65 in cmd_status (cmd=0x80b1fb8) at cmd-status.c:23 client = (struct client *) 0x80b17b0 args = (const struct imap_arg *) 0x80ab240 list_args = (const struct imap_arg *) 0x80ab328 items = {status = 23, metadata = 0} result = {status = {messages = 0, recent = 0, unseen = 0, uidvalidity = 0, uidnext = 0, first_unseen_seq = 0, first_recent_uid = 0, last_cached_seq = 0, highest_modseq = 0, highest_pvt_modseq = 0, keywords = 0x0, permanent_flags = 0, permanent_keywords = 0, allow_new_keywords = 0, nonpermanent_modseqs = 0, no_modseq_tracking = 0, have_guids = 1, have_save_guids = 0, have_only_guid128 = 0}, metadata = { guid = "\000\000\000\000\001\000\000\000\r\000\000\000\033\000\000", virtual_size = 2199023255593, cache_fields = 0xfe7a67f2, precache_fields = 134861792, backend_ns_prefix = 0x80921a8 "0(\t\b\030", backend_ns_type = 134511236}, error = 134654712, errstr = 0x80b2038 "STATUS"} ns = (struct mail_namespace *) 0x80ab1b0 mailbox = 0x8093318 "pro/triad" orig_mailbox = 0x80ab2f8 "pro/triad" selected_mailbox = false #25 0x0806aa61 in command_exec (cmd=0x80b1fb8) at imap-commands.c:101 hook = (const struct command_hook *) 0x809bfd8 ret = 8 #26 0x080699d2 in client_command_input (cmd=0x80b1fb8) at imap-client.c:130 client = (struct client *) 0x80b17b0 command = (struct command *) 0x3 __FUNCTION__ = "client_command_input" #27 0x08069cb7 in client_command_input (cmd=0x80b1fb8) at imap-client.c:130 client = (struct client *) 0x80b17b0 command = (struct command *) 0x809d3d4 __FUNCTION__ = "client_command_input" #28 0x08069dba in client_handle_next_command (client=0x80b17b0, remove_io_r=0x8047b9d) at imap-client.c:130 No locals. #29 0x08069e57 in client_handle_input (client=0x80b17b0) at imap-client.c:130 _data_stack_cur_id = 3 ret = 10 remove_io = false handled_commands = false __FUNCTION__ = "client_handle_input" #30 0x08069fe0 in client_input (client=0x80b17b0) at imap-client.c:130 cmd = (struct client_command_context *) 0x80aa9a4 output = (struct ostream *) 0x80abe08 bytes = 55 __FUNCTION__ = "client_input" #31 0xfedba96d in io_loop_call_io (io=0x80abe70) at ioloop.c:28 ioloop = (struct ioloop *) 0x809bf20 t_id = 2 __FUNCTION__ = "io_loop_call_io" #32 0xfedbc0cc in io_loop_handler_run_internal (ioloop=0x809bf20) at ioloop-poll.c:96 ctx = (struct ioloop_handler_context *) 0x809ca10 pollfd = (struct pollfd *) 0x809e0a8 tv = {tv_sec = 1799, tv_usec = 999672} io = (struct io_file *) 0x80abe70 msecs = 1800000 ret = 0 call = true #33 0xfedbab06 in io_loop_handler_run (ioloop=0x809bf20) at ioloop.c:28 No locals. #34 0xfedbaa5d in io_loop_run (ioloop=0x809bf20) at ioloop.c:28 __FUNCTION__ = "io_loop_run" #35 0xfed41db1 in master_service_run (service=0x809be68, callback=0x80771da <client_connected>) at master-service.c:75 No locals. #36 0x08077577 in main (argc=2, argv=0x809bc78) at main.c:72 set_roots = {0x8092fe0, 0x0} login_set = {auth_socket_path = 0x80930e8 "", postlogin_socket_path = 0x8093120 "", postlogin_timeout_secs = 60, callback = 0x8076f4e <login_client_connected>, failure_callback = 0x807715d <login_client_failed>, request_auth_token = 1} service_flags = MASTER_SERVICE_FLAG_KEEP_CONFIG_OPEN storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT username = 0x0 c = -1

2 1

Properly "locking" a useraccount (on a proxy)
by Ralf Hildebrandt 25 Oct '14

25 Oct '14

I'm preparing a migration of several mailboxes to another machine. The different useraccounts are distributed to different backend machines by means of a dovecot LMTP/IMAP/POP proxy. Proxying is working really well (now that the kernel does as it should). But how can I "lock" a user during migration? The plan is: ============ * lock the user * kick the user (doveadm kick) * migrate mailbox (some rsync magic) * unlock the user again But how would I lock the user? What locking needs to achieve: 1) Disallow IMAP/POP login (that's easy!) 2) defer LMTP delivery somehow (Postfix is talking to dovecot's LMTP server) Because currently, we're seeing dovecot trying local delivery on the proxy machine once an account is locked (probably because LMTP proxying uses passdb lookups, and since that one is failing it's using the userdb lookup?): Oct 21 20:15:27 lmtp(87892): Error: user sys4(a)test.invalid: Initialization failed: Namespace '': mkdir(/var/mail/test.invalid/sys4/mdbox/mailboxes) failed: Permission denied (euid=10000(vmail) egid=10000(vmail) missing +w perm: /var/mail, we're not in group 8(mail), dir owned by 0:8 mode=0775) Admittedly, this is somehow working. But it's not very elegant to use a side-effect. Is the a reserved userdb/passwd return value which will let dovecot "tempfail" in a n elegant fashion? -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

5 7

Dovecot Master/Master Replication Problem
by Felix Amler 25 Oct '14

25 Oct '14

Hi, I've set up 2 servers with dovecot 2.2.9 using maildir using structure: /var/maildir/domain/localpart Server A: mx1.xxx.de Server B: mx2.xxx.de Mails are delivered to dovecot only on server A by exim4/dovecot deliver replication to Server B works immediatelly: mark mail as read on server A, mail is marked as read on server B. BUT: when i mark a mail as read on Server B, noting happens. On Server A I get messages like this in dovecot-error.log: 2014-10-22 22:35:05 dsync-server(localpart(a)domain.de): Error: stat(/var/maildir/domain.de/localpart/.dovecot-sync.lock/tmp) failed: Not a directory 2014-10-22 22:35:05 dsync-server(localpart(a)domain.de): Error: Failed to access mailbox dovecot-sync.lock: Internal error occurred. Refer to server log for more information. [2014-10-22 22:35:05] I googled a bit, this could habben if there is a file ".dovecot-sync.lock" in the maildir, but I've double checked that, there is no such file... Why does it work in one direction, but not in the other? Please help best regards Felix

2 1

Replication .dovecot-sync.lock
by Hans-Werner Paulsen 25 Oct '14

25 Oct '14

Hello all, I have set up two servers with dovecot and replication. The mail location is mail_location = sdbox:/var/spool/mail/%u Everything works fine when I override the homedirectories userdb { driver = passwd override_fields = home=/var/spool/mail/%u } But, when I do not override the homedirectories, replication does not work, and the following error is logged: Oct 24 14:40:45 dsync-local(hans): Error: Couldn't create lock /afs/mpa/home/hans/.dovecot-sync.lock: Permission denied With a self-written module an IMAP user can get access to his homedirectory: protocol imap { mail_plugins = afsToken } The user has to type in his password. Obviously this does not work for replication. Is there a way to specify a different location for the lockfile? Isn't better to use the maildirectory but the homedirectory? Is there a way to set the homedirectory differently for replication? Thank you for any help. HW -- Hans-Werner Paulsen hans(a)MPA-Garching.MPG.DE MPI für Astrophysik Tel 089-30000-2602 Karl-Schwarzschild-Str. 1 Fax 089-30000-2235 D-85741 Garching

2 1

2.2.14 and "Panic: file virtual-sync.c"
by Michael Köhler 25 Oct '14

25 Oct '14

Hi, after upgrading to 2.2.14 (debian wheezy with apt source from rename-it.nl) I´ve got from time to time a panic in virtual plugin. Here are an excerpt from the log file: ---------------------------------- Oct 21 20:44:15 mailserver dovecot: imap(michael@DOMAIN): flag_change: box=Virtual.Ungelesen, uid=1, msgid=<54466F71.3050702(a)makomi.de>, size=1661, flags=(\Seen \Draft \Recent) Oct 21 20:44:15 mailserver dovecot: imap(michael@DOMAIN): Panic: file virtual-sync.c: line 1115 (virtual_sync_backend_box): assertion failed: (array_count(&bbox->sync_pending_removes) == 0) Oct 21 20:44:15 mailserver dovecot: imap(michael@DOMAIN): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x752af) [0x7f5f2630e2af] -> /usr/lib/dovecot/libdovecot .so.0(+0x7530e) [0x7f5f2630e30e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f5f262c05de] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0x266c ) [0x7f5f24abb9cc] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x35) [0x7f5f26601195] -> dovecot/imap(imap_sync_init+0x7a) [0x41faaa] -> dovecot/imap(cmd_sync_dela yed+0x190) [0x420710] -> dovecot/imap(client_handle_input+0x1d5) [0x417a35] -> dovecot/imap(client_input+0x72) [0x417d22] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [ 0x7f5f263200fb] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xbb) [0x7f5f2632117b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7f5f26320189] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f5f26320208] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f5f262c5ab3] -> dovecot/imap(main+0x2a1) [0x 40c311] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f5f25f2bead] -> dovecot/imap() [0x40c475] Oct 21 20:44:15 mailserver dovecot: imap(michael@DOMAIN): Fatal: master: service(imap): child 31075 killed with signal 6 (core dumps disabled) ————————————————— Are the problem well-known? And what could I do? Thanks, Michael

2 1

dovecot-lda from postfix on remote dovecot server
by nik600 25 Oct '14

25 Oct '14

Dear all i've got many SMTP front-end that filter the mail and do some custom stuff... then when i've decided the final destination i'd like to call /usr/lib/dovecot/dovecot-lda to deliver the mail. Actually i have in master.cf: #####################à dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail null_sender= argv=/usr/lib/dovecot/dovecot-lda -f ${sender} -d ${recipient} #####################à I'd like to know if is possible to use some other command or some additional parameter to deliver the mail to a remote dovecot server. Thanks -- /*************/ nik600 http://www.kumbe.it

3 3

Replication only sporadic
by Lucas Rothamel - Eye Catching Webdesign 24 Oct '14

24 Oct '14

Hello dear Dovecot Gurus, I am setting up two servers with Dovecot replication as hot-standby servers for a small high availability cluster, switch-over through DNS-redirect. For testing purposes, both servers are generating a small test mail every few minutes and delivering to the local dovecot each. In my mail client, I added both servers through IMAP to watch how the replication is working. However, I noted that replication is very sporadic: sometimes a new email is received "instantaneous" by both servers, then no replication updates are visible for hours, and suddenly all missing mail appear in the other server. Why is this? Can this be changed to be more realtime? Thank you! Lucas doveconf -n: # 2.2.14: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.7 ext4 auth_mechanisms = plain login cram-md5 disable_plaintext_auth = no info_log_path = /var/log/dovecot-info.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_location = maildir:/home/%d/%n/Maildir mail_plugins = " notify replication" mail_privileged_group = mail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { mail_replica = remote:vmail@... quota = maildir:User quota quota_rule = *:storage=1GB replication_full_sync_interval = 1 hours } protocols = imap pop3 service aggregator { fifo_listener replication-notify-fifo { mode = 0600 user = vmail } unix_listener replication-notify { mode = 0600 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service config { unix_listener config { user = vmail } } service doveadm { user = vmail } service replicator { process_min_avail = 1 } ssl_cert = ... ssl_key = ... userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { info_log_path = /var/log/dovecot-lda.log mail_plugins = quota postmaster_address = ... } -- Lucas Rothamel Eye Catching Webdesign info(a)eye-catching-webdesign.de - www.eye-catching-webdesign.de You know, we go to the gym to keep the body fit. Similarly the mind needs some rest. The mind is bombarded with so many impressions. Our mind has been bombarded by impressions the whole time. It needs a different kind of rest other than sleep. And meditation is such a rest. It calms the mind. energizes the spirit and makes the body more strong and vibrant. improves the immune system. The immune cells, the T-cell count go higher through Sudarshan Kriya and meditation. And you feel so nice inside. - Sri Sri Ravi Shankar I love deadlines. I like the whooshing sound they make as they fly by. -- Douglas Adams

1 0

Sieve Advice Needed, Please
by Casey Bralla 24 Oct '14

24 Oct '14

Anybody here familiar with the Sieve language? I'm rebuilding my mail server, and I am working with the sieve language to automatically filter spam into a separate account. However, I've hit a snag that I can't get around. BTW, I'm using a clean install of dovecot, postfix, spamassassin on Debian 7.5. I want to do server-side spam filtering, so I've got spamasassin identifying spam, and then have sieve sorting the mail to a special spam folder. I can easily send spam to special folder in the inbox for each mail user, but I wanted to have a single mail account for spam. I can use the "redirect" sieve command to send anything with the X-spam-flag set, but this triggers an error and bounces the offending mail. The bounce message is: From: MAILER-DAEMON(a)NerdWorld.org (Mail Delivery System) To: casey(a)vmailservertest.nerdworld.org Subject: Undelivered Mail Returned to Sender Date: Sun, 19 Oct 2014 16:41:49 -0400 (EDT) This is the mail system at host VMailServerTest.NerdWorld.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <spam(a)vmailservertest.nerdworld.org>: mail forwarding loop for spam(a)vmailservertest.nerdworld.org From: casey(a)vmailservertest.nerdworld.org Date: Sun, 19 Oct 2014 16:41:20 -0400 (EDT) viagra!!!! www.viagra.com I think this is a recursion problem, since the redirected mail has to go through the spamassassin check and sieve again. I tried to get clever and prevent the recursion, but I'm not clever enough. Here is my sieve rule file. # # # A rule to move spam to the spam user # based on spamassassin setting the spam flag # # # require ["redirect"]; (Not needed, since it is part of the basis sieve spec) # # rule:[SPAM] if header :contains "X-Spam-Flag" ["YES"] { if address :is "to" "Spam(a)VMailServerTest.NerdWorld.org" { keep; } else { redirect "spam(a)VMailServerTest.NerdWorld.org"; } } # # # Anybody able to give me any advice? TIA -- Casey Bralla Chief Nerd in Residence The NerdWorld Organisation www.NerdWorld.org

3 2

Re: special "what's my ip" pop account
by Joseph Tam 24 Oct '14

24 Oct '14

Steffen Kaiser writes: > let's put aside the question, if this way is sensible or not. [... continuing in nonsensible mode ...] > And if you are at it, maybe a dummy server with a self-made script that > returns "+OK POP3 your IP is ....", then return +FAIL for any further > command. Been there, done that (for a different problem). Not all mail readers will show you banners; to make this really work, you have to implement USER and PASS (accepts anything), STAT and LIST (one message available), RETR (dump your informational message payload), QUIT (disconnect), maybe TOP, and everything else is an +OK no-op. I patched Qualcomm's qpopper to do this. As to whether the OP *should* do this, definitely not. Find a better solution. Joseph Tam <jtam.home(a)gmail.com>

1 0

Public root folder is \Noselect
by G H 23 Oct '14

23 Oct '14

I am utilizing a public namespace via http://wiki2.dovecot.org/SharedMailboxes/Public and using sdbox storage format. How can I get rid of the \Noselect flag that is set by default for this folder? IMAP output: b LIST "" "*" * LIST (\HasNoChildren \Sent) "/" Sent * LIST (\HasNoChildren \Trash) "/" Trash * LIST (\Noselect \HasNoChildren) "/" Public * LIST (\HasNoChildren) "/" INBOX If this is not possible, what is the best way to create a sub-folder in here upon system setup (one w/o a \Noselect flag)? Thanks, G H

1 0

special "what's my ip" pop account
by A. Schulze 23 Oct '14

23 Oct '14

Hello, I like to enable the allow_nets Feature (http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets) for my customers. To help them knowing there own IP I imagine a special mailbox/loginuser at the pop3 server. That user could give a valid pop3 answer from a dummy pop3 server or simply throw a login error with customised answer containing the IP information. Has anybody done something similar or ideas to build such a system? Thanks for ideas Andreas

4 6

What is the correct way to configure the mail_location option for Mailidr format?
by deoren 23 Oct '14

23 Oct '14

Short version: What is the correct way to configure the mail_location option for Mailidr format? I've long had it setup this way: mail_location = maildir:/var/vmail/%d/%n based on this guide: https://www.linode.com/docs/email/postfix/email-with-postfix-dovecot-and-my… Is that correct? Longer version: After upgrading from Dovecot v2.0.x to v2.2.x yesterday I'm coming to the conclusion that I've got it configured wrong. This is probably compounded by my bright idea of explicitly setting the path separator prior to the upgrade like so: separator = . Because we're using Maildir I thought it would be useful to explicitly set the separator value to what the default is for Maildir. I figured this would be a good way to remind myself what the separator is by default. I also figured while I was merging the conf changes between v2.0 and v2.2 I could roll that additional change in also. Looks like that was a bad idea to include unnecessary changes until things had stabilized. I should know better; I was too optimistic for my own good. Here is an example error message I ran into: stat(/var/vmail/example.com/username/.dovecot.lda-dupes/tmp) failed: Not a directory which is nearly identical (other than leading path) to what is shown here: http://www.dovecot.org/list/dovecot/2010-April/048227.html Steffen Kaiser responded with, "You should not (must not) have home == maildir root." That is when I double-checked the guide that I mentioned above and found that I had followed their directions exactly for that conf setting. Looking at some other guides/tutorials shows something more like: mail_location = maildir:/var/vmail/%d/%n/Maildir I assume the latter is how it's supposed to be done? If so, that would explain the problems I've had with Sieve scripts in the past until I explicitly set 'sieve_dir' like so: sieve_dir = /var/vmail/sieve/%d/%n/sieve_dir I did review the official docs here: http://wiki2.dovecot.org/MailLocation/Maildir but I didn't find where it explicitly warns against setting home == maildir root. It should probably be apparent, but it wasn't to me when I first configured that setting. Thanks in advance for your help. If it turns out that the linode.com guide is wrong I'll create a Pull request to have that guide updated.

3 6

Re: dictionary attack defense
by Joseph Tam 23 Oct '14

23 Oct '14

Cliff Hayes writes: > a) I read about auth_failure_delay even before I posted my question and > I could not figure out the one-line explanation in the dovecot wiki: > "Number of seconds to delay before replying to failed authentications." > It's delaying a reply. Does that mean the hacker can keep asking as > fast as he wants? As Reindl states, authentication is a synchronous operation so the BFD attacker must wait for a reply before continuing. An attacker can get around this by running a botnet against you or opening up many concurrent connections (I think the latter can be capped), but I've rarely seen this. A botnet attack will defeat IP based blocking anyways. > Is it per user or per IP? Irrelevant -- there is no tracking. It's simply pauses the reply to bad auth attempts and tarpits the session. auth_failure_delay does not block BFD attacks, but makes it infeasable for reasonable strength passwords. It's simpler to implement, robust, and fault tolerant (e.g. a user cannot accidentally lock themselves out requiring administrative intervention to restore immediate access, or repeated failures from a NAT'd network does not DoS everything within the NAT'd network). Joseph Tam <jtam.home(a)gmail.com>

1 0

How to configure read-only access during a migration?
by Jeffrey Tunison 22 Oct '14

22 Oct '14

Hi. I would appreciate your advice about this PROBLEM: ======================================================= Find the simplest way to configure a Dovecot 2.2.10 IMAP server to access existing email users' (mbox-format) mail folders via a master_user ****in read-only mode.**** (I've got the master_user access working.) Simplest because while I'm proficient at UNIX systems administration, I'm under time pressure and dovecot has a lot of configuration flexibility. Identifying the right way to do this is proving time- consuming. Namespaces? ACL's? Passdb's? Mounting the mail-containing file systems in read-only mode did not work. (Would it have worked if I had disabled all file-locking rules (if so, how?)?) I thought it was time to bring in the dovecot wizards. You! GOAL: ======================================================= Without knowing or changing users' passwords, migrate several hundred users of dovecot IMAP to MS Exchange using the commercial product Transend. I'm manging the dovecot side, someone else is doing the Transend/Exchange piece. Migration would occur in batches due to slowness of the Transend side when dealing with users with email collections over a few gigabytes. I have a production IMAP server (dovecot 1.0.13 on 32-bit RHEL 4.9). Let's call it PROD for short. Users INBOXes are stored locally on PROD. Their other mail folders are stored on a second machine and accessed via NFS. Those other folders contain the great majority of the email to be migrated. Let's call the NFS server MIGR for short. On MIGR, I've set up a migration IMAP server (dovecot 2.2.10 on 64-bit RHEL 5.10). MIGR is a dedicated NFS server with newer hardware than PROD. It has an unused Ethernet NIC I can tell Transend to use. Both PROD and MIGR use NIS for authentication. Therefore PAM is consulted for passdb information, normally. No SQL db's used. I set up the second server (MIGR) for several reasons: 1) there are some users mail folders larger than the 32-bit file size limit found on the PROD server. 2) the bulk of the email is stored locally on the MIGR server. 3) the version of dovecot is much newer and therefore more likely to have fewer bugs and more configuration options. 4) I don't want to modify the production environment except where really necessary. Pointing Transend at MIGR instead of PROD seems like it will be faster and better. Telling end-users to use MIGR instead of PROD would allow them to verify that their email came across okay (into MS Exchange) without being able to modify the original copy of email (in Dovecot). In the days and weeks after migration. I'd like to disable access ***for a batch of users*** on the PROD server at the time the migration begins for that batch. I may need to re-enable access on PROD for certain users if the migration does not succeed. Transend has been dying on a number of test users despite tweaking its parameters in consultation with the vendor. "Corrupt" messages seem to be the issue. Users (or sysadmins) might be required to identify and delete the offending messages before we retry their migration. (Which folders and which messages are causing problems will hopefully be discernible in Transend logs.) Ha! If you've read this far, then I'd also say that I welcome any advice on changes to increase performance on MIGR, such as whether trying to minimize indexing as I've done is useful. Current configurations of the two servers follow. =========================================================================== PRODUCTION: =========================================================================== # 1.0.13: /etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log protocols: imaps imap listen: *:143 ssl_listen: *:993 ssl_cert_file: /etc/pki/dovecot/certs/dovecot.pem ssl_key_file: /etc/pki/dovecot/private/dovecot.key login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_processes_count: 20 login_max_processes_count: 500 max_mail_processes: 1524 first_valid_uid: 100 mail_location: mbox:~/Mail:INBOX=/var/mail/%u:INDEX=/var/spool/dovecot-indexes/%u/ mbox_read_locks: dotlock mbox_write_locks: dotlock mbox_dotlock_change_timeout: 60 mbox_min_index_size: 2048 namespace: type: private separator: / inbox: yes namespace: type: private separator: / prefix: Mail/ hidden: yes namespace: type: private separator: / prefix: ~/Mail/ hidden: yes namespace: type: private separator: / prefix: mail/ hidden: yes namespace: type: private separator: / prefix: ~/mail/ hidden: yes auth default: master_user_separator: * verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /etc/dovecot.deny deny: yes passdb: driver: passwd-file args: /etc/dovecot.transend master: yes passdb: driver: shadow passdb: driver: pam userdb: driver: passwd =========================================================================== MIGRATION: =========================================================================== # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-348.18.1.el5 x86_64 Scientific Linux release 5.10 (Boron) auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no first_valid_uid = 100 log_path = /var/log/dovecot.log mail_debug = yes mail_location = mbox:~/Mail:INBOX=/var/spool/concmail/%u:INDEX=MEMORY mbox_min_index_size = 50048 B mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } namespace one { hidden = yes location = prefix = Mail/ separator = / } namespace three { hidden = yes location = prefix = mail/ separator = / } passdb { args = /etc/dovecot/deny-users deny = yes driver = passwd-file } passdb { args = /etc/dovecot/dovecot.transend driver = passwd-file master = yes } passdb { driver = pam } protocols = imap service imap-login { process_min_avail = 15 service_count = 10 } service imap { executable = imap postlogin process_limit = 2048 } service postlogin { executable = script-login -d rawlog } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } deny = yes driver = passwd-file } passdb { args = /etc/dovecot/dovecot.transend driver = passwd-file master = yes } passdb { driver = pam } protocols = imap service imap-login { process_min_avail = 15 service_count = 10 } service imap { executable = imap postlogin process_limit = 2048 } service postlogin { executable = script-login -d rawlog } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } verbose_proctitle = yes protocol imap { mail_max_userip_connections = 1000 }

1 0

dictionary attack defense
by Cliff Hayes 22 Oct '14

22 Oct '14

Does dovecot have any dictionary attack defenses yet? In the past I have had to implement defense from outside dovecot, but since dovecot is at the front lines and therefore is the first to know I'm hoping by now there is something we can set. For example, a limit on access failures per minut/hour/day or some such. If not why not?

4 8

authenticate plain, and virtual users
by Eric Abrahamsen 22 Oct '14

22 Oct '14

I'm running dovecot 2.2.14 on Archlinux. I've been using it with the isync syncing utility for quite some time with no problems, using the LOGIN authentication mechanism. Recently Isync was updated to support PLAIN, and I'm having trouble moving to that. The authenticate string that isync is sending is not the one that dovecot is expecting. I suspect this is because of how I have virtual users set up on my machine. This is a personal laptop, no other users, and so I didn't want to go through the rigmarole of creating more system users just for mail accounts. I also wanted everything stored under my home directory. So my dovecot config looks like this: # 2.2.14: /etc/dovecot/dovecot.conf # OS: Linux 3.16.4-1-ARCH i686 auth_verbose = yes disable_plaintext_auth = no info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_plugins = " fts fts_lucene" passdb { args = username_format=%u /etc/dovecot/passwd driver = passwd-file } plugin { fts = lucene fts_autoindex = yes fts_lucene = whitespace_chars=@. } protocols = imap ssl = no userdb { args = uid=eric gid=users home=/home/eric/.mail/%d/%n username_format=%u default_fields = mail=maildir:/home/eric/.mail/%d/%n/mail driver = static } My /etc/dovecot/passwd looks like this: eric@ericabrahamsen.net:{PLAIN}password1 eric@paper-republic.org:{PLAIN}password2 When isync tries to log into the local dovecot using PLAIN, it sends the base64-encoded version of this string: eric(a)paper-republic.org\0eric\0password2 With my current dovecot config, telnet experimentation shows that dovecot will accept either of these two: \0eric(a)paper-republic.org\0password2 eric@paper-republic.org\0eric@paper-republic.org\0password2 Ie, either with or without the authorization ID, just like it says at http://wiki2.dovecot.org/Debugging/Authentication Given that I'm unlikely to be able to change how isync sends the string (and that it's really doing the right thing), are there alterations I can make to my dovecot config to get it to accept the authenticate string that isync is sending? Ideally, can I do that without having to set up system users? I've already tried using the other fields in the passwd file, putting "eric" and "eric(a)paper-republic.org" into the UID fields, just in case. No dice. Thanks in advance for any advice! Eric

1 0

Multiple user attributes in LDAP userdb query strings
by BINOTTO Luis SIDOR 21 Oct '14

21 Oct '14

Hello list, I have an issue with dovecot and Ldap... Any help will be grateful... I have my virtual users stored in an Active Directory database. I am using 2 attributes in AD to locate the user account: mail (their primary email address) and proxyAddresses (a multivalue attribute containing their mail aliases). I also control the mount point in which the mail is located with another attribute in AD, in this case I used "pager". I have dovecot 1.2.15 and there are no immediate plans to upgrade it. I configured Dovecot's deliver process in order to integrate sieve capability. I have configured userdb ldap and passdb ldap in Dovecot and have set up master and client sockets. I am using maildir format for directory layout. The problem is to set the variables home and mail that will define the mail location. The format must be like this: home: /Mailboxes/<mount point>/<user login>/ mail: /Mailboxes/<mount point>/<user login>/Maildir So, for a particular user (Login: user1, smtp: user1(a)domain1.com, alias smtp: user1_alias(a)domain1.com) the variables will be: home: /Mailboxes/AdmUsers/user1/ mail: /Mailboxes/AdmUsers/user1/Maildir Active Directory has the values in: mail:(user1@domain1.com), proxyAddresses:(user1_alias@domain1.com), sAMAaccountName(user1). I have defined home and mail in dovecot-ldap.conf. # User attributes are given in LDAP-name=dovecot-internal-name list. The # internal names are: # uid - System UID # gid - System GID # home - Home directory # mail - Mail location # # There are also other special fields which can be returned, see # http://wiki.dovecot.org/UserDatabase/ExtraFields user_attrs = pager=home=/mailboxes/%$/%u,mobile=quota_rule=*:storage=%$M If the mail is sent to the Principal SMTP (user1(a)domain1.com) in which the user part (%u) is the same as sAMAccountName, it works. The variable home is set correctly (home: /Mailboxes/AdmUsers/user1/). The problem is when the mail is sent to the smtp alias, in which the variable home is set incorrectly (home: /Mailboxes/AdmUsers/user1_alias/). There is a way to set two values to user_attrs?, in this case I would need to set pager and sAMAccountName (instead of %u), to it. Thanking you in anticipation... Attached is the out of dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.7 log_path: /var/log/dovecot.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 mail_uid: 16343 mail_gid: 16343 mail_location: maildir:~/Maildir mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): autocreate deleted_to_trash quota imap_quota expire mail_plugins(imap): autocreate deleted_to_trash quota imap_quota expire mail_plugins(pop3): quota expire 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): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh lda: postmaster_address: postmaster(a)domain1.com mail_plugins: quota expire log_path: /var/log/dovecot.log auth default: mechanisms: gssapi gss-spnego login ntlm plain username_format: %Ln use_winbind: yes passdb: driver: pam userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf 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 plugin: autocreate: Deleted Items autocreate: Sent Items autosubscribe: Deleted Items autosubscribe: Sent Items deleted_to_trash_folder: Sent Items quota: maildir:User quota quota_rule: *:storage=100M quota_rule2: Deleted Items:ignore quota_warning: storage=80%% /etc/dovecot/scripts/quota-warning.sh 80 quota_warning2: storage=90%% /etc/dovecot/scripts/quota-warning.sh 90 quota_warning3: storage=99%% /etc/dovecot/scripts/quota-exceeded.sh 100 expire: "Deleted Items" 1 "Deleted Items/*" 1 expire_dict: proxy::expire dict: expire: pgsql:/etc/dovecot/dovecot-dict-expire.conf " Notificacion Automatica: Este mensaje y cualquier archivo que se adjunte contiene informacion privilegiada y confidencial. Es para uso exclusivo del destinatario. Si usted ha recibido esta comunicacion por error, por favor avisenos inmediatamente. Automatic notification: This e-mail and any file transmitted with it are confidential and may be legally privileged. It is intended solely for the addressee and may not be disclosed to or used by anyone other than the addressee. If you have received this e-mail by mistake , please advise the sender immediately"

1 0

Proxy problem: "imap-login: Error: proxy(USERNAME): connect(10.x.x.178, 993) failed: Cannot assign requested address (after 0 secs, local=10.x.x.104)"
by Ralf Hildebrandt 21 Oct '14

21 Oct '14

After fixing the "duplicate compression" problem, we're now encountering "imap-login: Error: proxy(USERNAME): connect(10.x.x.178, 993) failed: Cannot assign requested address (after 0 secs, local=10.x.x.100)" in the logs. We already tried raising the ulimit, the max number of open files. Once we reach about 25k connections, we're getting the error above... for all local addresses. It seems as if the system cannot create any more outgoing connections. We already optimized: ---- snip ---- net.ipv4.tcp_fin_timeout=5 # down from 30s net.ipv4.tcp_tw_reuse=1 net.ipv4.tcp_tw_recycle=1 # http://redis4you.com/articles.php?id=012&name=Redis+high+traffic+connection… net.ipv4.ip_local_port_range=10000 65000 # http://www.fromdual.com/huge-amount-of-time-wait-connections net.ipv4.netfilter.ip_conntrack_max=524288 ---- snip ---- But still we get (once the load is rising beyond some point): # fgrep "Cannot assign requested address" /var/log/dovecot/dovecot.log |awk '{print $NF}' | sort | uniq -c | sort -n 142 local=10.x.x.100) 147 local=10.x.x.107) 148 local=10.x.x.106) 151 local=10.x.x.104) 151 local=10.x.x.109) 152 local=10.x.x.105) 156 local=10.x.x.110) 162 local=10.x.x.102) 165 local=10.x.x.101) 178 local=10.x.x.103) 189 local=10.x.x.108) We're using multiple local addresses when proxying to the backends -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

4 7

only inbox folder after courier-imap migration
by Luciano Gabriel Andino 21 Oct '14

21 Oct '14

Hello, after courier-dovecot-migrate.pl, the only folder appears in webmail menu is "Inbox". The others still are in Maildir "Maildir/.myfolder" and contains its "dovecot-uidlist" and "dovecot-keywords" files. May I need to edit some file? -- Saludos!! Luciano Andino GNU/Linux user #185103 Santa Fe - Argentina -----------------------------------------------

1 0

Dovecot Auth Issue
by Austin Einter 21 Oct '14

21 Oct '14

Dear All I have been able to setup postfix and dovecot. Through command line, I can send mail out. Now I have installed roundcube in mail server side, and I am able to access like https://mydomain/webmail.com Login was failing. Then I debugged and modified settings in dovecot and using PAM for authentication. Now I trying to login to email server. I am not sure if authentication by dovecot and pam is successful. I enabled logging for dovecot. The below logs I get when a user "try" logs in. Oct 21 07:44:55 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Oct 21 07:44:55 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Oct 21 07:44:55 auth: Debug: auth client connected (pid=15357) Oct 21 07:44:55 auth: Debug: client in: AUTH 1 PLAIN service=imap secured lip=128.199.214.27 rip=128.199.214.27 lport=993 rport=43323 resp=AHRyeUBsb2FkbXVsdGlwbGllci5jb20AdHJ5MTIz Oct 21 07:44:55 auth-worker: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Oct 21 07:44:55 auth-worker: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Oct 21 07:44:55 auth-worker: Debug: pam(try,128.199.214.27): lookup service=dovecot Oct 21 07:44:55 auth-worker: Debug: pam(try,128.199.214.27): #1/1 style=1 msg=Password: Oct 21 07:44:55 auth: Debug: client out: OK 1 user=try Oct 21 07:44:55 auth: Debug: master in: REQUEST 1571291137 15357 1 b3cc155dfd3bb2fd576bfeeceaf1ce3d Oct 21 07:44:55 auth: Debug: passwd(try,128.199.214.27): lookup *Oct 21 07:44:55 auth: Debug: master out: USER 1571291137 try home=/var/mail/ mail=maildir:/var/mail/try system_groups_user=try uid=5001 gid=5001*Oct 21 07:44:55 imap-login: Info: Login: user=<try>, method=PLAIN, rip=128.199.214.27, lip=128.199.214.27, mpid=15361, TLS *Oct 21 07:44:55 imap(try): Info: Disconnected: Logged out bytes=29/399* >From the logs above (in bold), I hope auth is successful, then in last line why it is logging out.., I am confused , not sure if auth is completely successful or not. Kindly experts please help. Best Regards, Austin

1 0

SMTP authentication setup
by Brian 21 Oct '14

21 Oct '14

At my company we've had a longstanding problem of not being able to send email from devices outside of our internal network and any specific IP address that we open the relay to. As it turns out, SASL has never been set up. I need to set up SASL ASAP but none of the guides I've found seem to work. This is the latest guide I tried: http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL I did everything on here minus the last part because it's on the same server. Also, instead of submission inet n - - - - smtpd I did: 127.0.0.1:1025 inet n - - - - smtpd After all is done, however, I'm unable to send any mail. Thunderbird just says sending message but doesn't send and I don't even get an error. I end up having to disable SASL again before I can send mail. Dovecot version 2.0.9 Postfix version 2.6.6 CentOS 6 I have Postfix, Dovecot, and ASSP on the same server. Thanks everyone. -- This email was Virus checked by Astaro Security Gateway. http://www.sophos.com

4 5

90-sieve.conf syntax - moving from v2.0.x to v2.2.x
by deoren 21 Oct '14

21 Oct '14

Hi, I'm currently running version v2.0.x in production (using Maildir storage) and it's been working well. I'm interested in moving to version 2.2.x and am preparing a test server to do so. As I have been merging the conf file changes between the two versions I noticed syntax changes for the 90-sieve.conf file. There are now 'locations' and presumably to keep referring to local content I'll need to use the 'file:' location type. On my production box (v2.0.x) I have 90-sieve.conf configured like so: sieve = /var/vmail/sieve/%d/%n/.dovecot.sieve sieve_default = /var/vmail/sieve/global.sieve sieve_dir = /var/vmail/sieve/%d/%n/sieve_dir Inside of the /var/vmail/sieve/%d/%n/ directory (i.e., /var/vmail/sieve/example.com/testuser/) I find: drwxr-xr-x 3 vmail vmail 64 Oct 19 12:07 . drwxr-xr-x 9 vmail vmail 101 Jun 21 10:47 .. lrwxrwxrwx 1 vmail vmail 25 Jun 21 11:10 .dovecot.sieve -> sieve_dir/roundcube.sieve -rw------- 1 vmail vmail 3694 Oct 19 12:07 .dovecot.svbin drwx------ 3 vmail vmail 38 Oct 19 11:58 sieve_dir and that works well. I look at the current wiki documentation: http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration and I find that the 'seive_dir' conf option is still listed, but the comments for it appear very similar to the comments that precede the 'sieve' conf option in the stock 90-sieve.conf file: # The location of the user's main Sieve script or script storage. The LDA # Sieve plugin uses this to find the active script for Sieve filtering at # delivery. The "include" extension uses this location for retrieving # :personal" scripts. This is also where the ManageSieve service will store # the user's scripts, if supported. Assuming that the 'sieve' and 'sieve_dir' conf settings have not been merged into just 'sieve' (and that I need to use the 'file:' location specifier), is this how I would configure the two settings for Dovecot 2.2.x? sieve = file:/var/vmail/sieve/%d/%n;active=~/.dovecot.sieve sieve_dir = file:/var/vmail/sieve/%d/%n/sieve_dir If the two have been merged, how would I go about configuring the 90-sieve.conf file to get the same results? Thanks for your help.

1 1

Re: last_login plugin with MySQL
by Joseph Tam 21 Oct '14

21 Oct '14

Michael Cramer <michael(a)bigmichi1.de> writes: > anybody knows how this can be achieved with postgresql, because 'ON > DUPLICATE KEY UPDATE' syntax is mysql specific A clear, concise explanation of consistency problems with SQL update-or-insert ("upsert") operation, including a PostgreSQL implementation: http://www.depesz.com/2012/06/10/why-is-upsert-so-complicated/ Joseph Tam <jtam.home(a)gmail.com>

1 0