- dovecot - dovecot.org

[Dovecot] raw backtrace in masses
by John Adams 06 Jun '10

06 Jun '10

Hi I've got huge amounts of May 3 15:47:37 host dovecot: [ID 583609 mail.error] IMAP(user): close(/home/user/Mail/R-Help.lock) failed: Disc quota exceeded May 3 15:47:37 host dovecot: [ID 583609 mail.error] IMAP(user): Raw backtrace: 0xb0e58 -> 0xb0894 -> 0x552b4 -> 0x55508 -> 0x55774 -> 0x55d9c -> 0x5759c -> 0x57ad0 -> 0x713cc -> 0x64284 -> 0x57be0 -> 0x71178 -> 0x6841c -> 0x76a38 -> 0x76a6c -> 0x25a08 -> 0x2afd4 -> 0x2bee4 -> 0x2bea0 -> 0x2c1f8 -> 0x2cb4c -> 0xb9450 -> 0xb8d00 -> 0x35294 -> 0x246e8 May 3 15:47:37 host dovecot: [ID 583609 mail.error] dovecot: child 3892 (imap) killed with signal 6 (core dumps disabled) May 3 15:47:49 host dovecot: [ID 583609 mail.error] IMAP(user): Raw backtrace: 0xb0e58 -> 0xb0894 -> 0x552b4 -> 0x55508 -> 0x55774 -> 0x55d9c -> 0x5759c -> 0x57ad0 -> 0x713cc -> 0x64284 -> 0x57be0 -> 0x71178 -> 0x6841c -> 0x76a38 -> 0x76a6c -> 0x25a08 -> 0x2afd4 -> 0x2bee4 -> 0x2bea0 -> 0x2c1f8 -> 0x2cb4c -> 0xb9450 -> 0xb8d00 -> 0x35294 -> 0x246e8 May 3 15:47:49 host dovecot: [ID 583609 mail.error] dovecot: child 4277 (imap) killed with signal 6 (core dumps disabled) The backtrace is always the same content. is this a disc quota problem? Dovecot is 1.2.11, managesieve patched. Thanks

3 9

[Dovecot] DOES NOT PERTAIN TO DOVECOT: Does anyone use postfix for some help?
by Jerrale Gayle 05 Jun '10

05 Jun '10

When mail is sent from the mail server, it shows up as originating from the MAIN ip address of the server, 173.50.101.11, when the mail server is bound to 173.50.101.12. I have already set smtp_bind_address: 173.50.101.12 in main.cf and 173.50.101.12:smtp inet - - smtpd in master.cf. This prevents smtp connects TO any other ip but 173.50.101.12 BUT mail STILL shows up originating from eth1, where 173.50.101.12 is eth1:2 I think this is *nix related and most here, on dovecot mailing list, could provide help.

3 2

[Dovecot] mdbox error with 2.0.beta5
by Mike Abbott 05 Jun '10

05 Jun '10

Running 2.0.beta5 on Mac OS X with HFS+J, I often see this error in the log: Fri May 14 12:25:59 gromit dovecot[5466]: imap(pid 8101 user joe): Error: mdbox /var/spool/imap/dovecot/mail/mailboxes/INBOX/Foobar/dbox-Mails: map uidvalidity mismatch (1273852899 vs 1273853949) Fri May 14 12:25:59 gromit dovecot[5466]: imap(pid 8101 user joe): Disconnected: Internal error occurred. Refer to server log for more information. [2010-05-14 12:25:59] bytes=1337/4443 Fri May 14 12:25:59 gromit dovecot[5466]: imap(pid 8101 user joe): Warning: mdbox /var/spool/imap/dovecot/mail/storage: rebuilding indexes The logs also reveal that this user was logged in twice at the time. There appear to be two issues here: the uidvalidity mismatch, and the path in the "rebuilding indexes" message does not match the path in the "uidvalidity mismatch" error.

2 6

[Dovecot] Managesieve connection hangs with TLS
by Joel James Adamson 04 Jun '10

04 Jun '10

Hello, I've got dovecot 1.2.11 running on Fedora 12 (x86_64) with the managesieve protocol and sieve plugins enabled, with deliver handling local delivery. I've set disable_plaintext_auth = yes ssl = yes ssl_cert_file = /etc/pki/dovecot/certs/dovecot.pem ssl_key_file = /etc/pki/dovecot/private/dovecot.pem mail_debug = yes protocol managesieve { listen = *:2000 login_executable = /usr/libexec/dovecot/managesieve-login mail_executable = /usr/libexec/dovecot/managesieve } and generated local SSL certificates; everything is going fine on the IMAP end of things (clients ask if I trust the certificate the first time, etc). I've open the appropriate ports, etc. No problems with mail delivery. However, I can't connect to the managesieve daemon. I've tried the Emacs client[1], and it just hangs. I tried manual login to port 2000 and here's what happened: joel@chondestes: /etc/mail > gnutls-cli --starttls -p 2000 localhost Resolving 'localhost'... Connecting to '127.0.0.1:2000'... - Simple Client Mode: "IMPLEMENTATION" "dovecot" "SIEVE" "comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date" "SASL" "PLAIN" "STARTTLS" "NOTIFY" "mailto" "VERSION" "1.0" OK "Dovecot ready." *** Starting TLS handshake C-c C-c That last line is me hanging up in Emacs' shell buffer because nothing was happening. Sorry to sound like such a newbie, but what do I need on the client end to complete the TLS transaction? What else do I need to set up to get managesieve to connect? Thanks, Joel Footnotes: [1] http://josefsson.org/sieve/ -- Joel J. Adamson Servedio Lab University of North Carolina at Chapel Hill FSF Member #8164 http://www.unc.edu/~adamsonj

2 2

[Dovecot] dovecot 2.0: * BAD Internal quota calculation error
by e-frog 04 Jun '10

04 Jun '10

Hello, I'm seeing * BAD Internal quota calculation error's with dovecot 2.0. It doesn't happen always but quite frequently. Here is an example imap traffic: 24 select "Drafts" 25 getquotaroot "Drafts" * OK [CLOSED] Previous mailbox closed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 0 RECENT * OK [UIDVALIDITY 1239455951] UIDs valid * OK [UIDNEXT 5] Predicted next UID * OK [HIGHESTMODSEQ 11] Highest 24 OK [READ-WRITE] Select completed. * QUOTAROOT "Drafts" "user" * QUOTA "user" () * BAD Internal quota calculation error 25 OK Getquotaroot completed. Reverting the following change fixes the issue http://hg.dovecot.org/dovecot-2.0/rev/50a0c05fb4e7 Thanks, e-frog

2 4

[Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)
by Thomas Leuxner 04 Jun '10

04 Jun '10

Hi, captured a crash on mdbox with latest mercurial: Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): msg header has bad magic value Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): uid=4831 points to broken data at offset=1438073 Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): msg header has bad magic value Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): uid=4831 points to broken data at offset=1438073 Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): Disconnected: Internal error occurred. Refer to server log for more information. [2010-03-09 13:56:28] bytes=74358/28147042 Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): dbox /var/vmail/leuxner.net/tlx/mdbox/storage: rebuilding indexes Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=2075210): msg header has bad magic value Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): dbox: Copy of the broken file saved to /var/vmail/leuxner.net/tlx/mdbox/storage/m.59.broken Mar 9 13:56:29 spectre dovecot: imap(tlx(a)leuxner.net): Panic: file index-sync.c: line 40 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) Mar 9 13:56:29 spectre dovecot: imap(tlx(a)leuxner.net): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x7f184c7d92b2] -> /usr/lib/dovecot/libdovecot.so.0 [0x7f184c7d931a] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f184c7d96c3] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mailbox_set_recent_seq+0) [0x7f184ca84010] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mailbox_set_recent_seq+0x3c) [0x7f184ca8404c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync_begin+0x37b) [0x7f184caafddb] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync+0x12) [0x7f184cab00c2] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_storage_sync_init+0x43) [0x7f184cab0133] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x7f184ca414e1] -> dovecot/imap [tlx(a)leuxner.net 80.187.100.24 IDLE](imap_sync_init+0x68) [0x417db8] -> dovecot/imap [tlx(a)leuxner.net 80.187.100.24 IDLE] [0x40ab5e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x9b) [0x7f184c7e342b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x6f) [0x7f184c7e3f8f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x18) [0x7f184c7e3168] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f184c7d3143] -> dovecot/imap [tlx(a)leuxner.net 80.187.100.24 IDLE](main+0x191) [0x418681] -> /lib/libc.so.6(__libc_start_main+0xe6) [0x7f184c0601a6] -> dovecot/imap [tlx(a)leuxner.net 80.187.100.24 IDLE] [0x4084e9] Mar 9 13:56:29 spectre dovecot: master: service(imap): child 32643 killed with signal 6 (core dumped) [14:02] root spectre:/# gdb /usr/lib/dovecot/imap /var/vmail/leuxner.net/tlx/core GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu"... warning: Can't read pathname for load map: Input/output error. Reading symbols from /usr/lib/dovecot/libdovecot-storage.so.0...Reading symbols from /usr/lib/debug/usr/lib/dovecot/libdovecot-storage.so.0.0.0...done. done. Loaded symbols for /usr/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/lib/dovecot/libdovecot.so.0...Reading symbols from /usr/lib/debug/usr/lib/dovecot/libdovecot.so.0.0.0...done. done. Loaded symbols for /usr/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/librt.so.1...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux-x86-64.so.2...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib/libpthread.so.0...done. Loaded symbols for /lib/libpthread.so.0 Reading symbols from /usr/lib/dovecot/modules/lib01_acl_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib01_acl_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib01_acl_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib02_imap_acl_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib10_quota_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib10_quota_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib10_quota_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib11_imap_quota_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Core was generated by `dovecot/imap'. Program terminated with signal 6, Aborted. [New process 32643] #0 0x00007f184c073ed5 in raise () from /lib/libc.so.6 (gdb) bt full #0 0x00007f184c073ed5 in raise () from /lib/libc.so.6 No symbol table info available. #1 0x00007f184c0753f3 in abort () from /lib/libc.so.6 No symbol table info available. #2 0x00007f184c7d92c5 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:164 backtrace = 0x61f0e8 "/usr/lib/dovecot/libdovecot.so.0 [0x7f184c7d92b2] -> /usr/lib/dovecot/libdovecot.so.0 [0x7f184c7d931a] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f184c7d96c3] -> /usr/lib/dovecot/libdovecot-st"... #3 0x00007f184c7d931a in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=<value optimized out>, args=<value optimized out>) at failures.c:592 No locals. #4 0x00007f184c7d96c3 in i_panic (format=<value optimized out>) at failures.c:230 args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7fffffffcd00, reg_save_area = 0x7fffffffcc40}} #5 0x00007f184ca84010 in index_mailbox_set_recent_uid (box=<value optimized out>, uid=4722) at index-sync.c:40 ibox = (struct index_mailbox_context *) 0x654890 __PRETTY_FUNCTION__ = "index_mailbox_set_recent_uid" #6 0x00007f184ca8404c in index_mailbox_set_recent_seq (box=0x654508, view=0x665040, seq1=2, seq2=44) at index-sync.c:57 uid = 4722 #7 0x00007f184caafddb in mdbox_sync_begin (mbox=0x654508, flags=<value optimized out>, ctx_r=0x7fffffffcea8) at mdbox-sync.c:141 storage = (struct mail_storage *) 0x648c78 ctx = (struct mdbox_sync_context *) 0x657260 sync_flags = <value optimized out> ret = 1 storage_rebuilt = false #8 0x00007f184cab00c2 in mdbox_sync (mbox=0x7f83, flags=32643) at mdbox-sync.c:286 sync_ctx = (struct mdbox_sync_context *) 0x654508 #9 0x00007f184cab0133 in mdbox_storage_sync_init (box=0x654508, flags=0) at mdbox-sync.c:310 mdbox_sync_flags = 32643 #10 0x00007f184ca414e1 in mailbox_sync_init (box=0x654508, flags=0) at mail-storage.c:848 _data_stack_cur_id = 0 ctx = <value optimized out> #11 0x0000000000417db8 in imap_sync_init (client=0x64f9d8, box=<value optimized out>, imap_flags=0, flags=0) at imap-sync.c:142 ctx = <value optimized out> __PRETTY_FUNCTION__ = "imap_sync_init" #12 0x000000000040ab5e in idle_sync_now (box=<value optimized out>, ctx=0x650228) at cmd-idle.c:122 __PRETTY_FUNCTION__ = "idle_sync_now" #13 0x00007f184c7e342b in io_loop_handle_timeouts (ioloop=0x6275c0) at ioloop.c:328 _data_stack_cur_id = 2 #14 0x00007f184c7e3f8f in io_loop_handler_run (ioloop=0x6275c0) at ioloop-epoll.c:180 ctx = (struct ioloop_handler_context *) 0x6277d0 event = <value optimized out> list = <value optimized out> io = <value optimized out> tv = {tv_sec = 0, tv_usec = 499327} t_id = <value optimized out> msecs = 500 ret = 0 call = <value optimized out> #15 0x00007f184c7e3168 in io_loop_run (ioloop=0x6275c0) at ioloop.c:350 No locals. #16 0x00007f184c7d3143 in master_service_run (service=0x627490, callback=0x7f83) at master-service.c:478 No locals. #17 0x0000000000418681 in main (argc=1, argv=0x627370) at main.c:313 service_flags = <value optimized out> storage_service_flags = <value optimized out> postlogin_socket_path = 0x0 set_roots = {0x41b980, 0x0} (gdb) Regards Thomas

2 11

[Dovecot] dsync panic in dsync-worker-local.c - 2.0.beta4
by Frode Nordahl 04 Jun '10

04 Jun '10

Hello, While testing mailbox conversion I encountered a Panic in dsync on a few users mailboxes. Running dovecot 2.0.beta4 on RedHat Enterprise Linux 5 (x86_64). I tried to compile the code with -ggdb and debug some more before posting this, but I was unsuccessful. Running dsync from a source tree is hard because of all the dependencies on shares libraries. Is it possbile to build static binaries? Panic message and backtrace included below (anonymized): dsync(user): Error: o_stream_send_istream(/home/user/mdbox/storage/temp.1271871137.P25074Q1M330350.localhost.localdomain) failed: Bad file descriptor dsync(user): Panic: file dsync-worker-local.c: line 1460 (local_worker_save_msg_continue): assertion failed: (ret == -1) dsync(user): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x3da92343a0] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x37) [0x3da9234487] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3da92338c8] -> /usr/bin/dsync [0x40db83] -> /usr/bin/dsync [0x40dc5e] -> /usr/bin/dsync(dsync_worker_msg_save+0x79) [0x40d429] -> /usr/bin/dsync [0x408b4c] -> /usr/bin/dsync [0x40d88d] -> /usr/bin/dsync(dsync_worker_msg_get+0x81) [0x40d061] -> /usr/bin/dsync [0x4085fe] -> /usr/bin/dsync [0x40868d] -> /usr/bin/dsync [0x4087d5] -> /usr/bin/dsync(dsync_brain_msg_sync_more+0x3f5) [0x408395] -> /usr/bin/dsync(dsync_brain_sync+0x93f) [0x40720f] -> /usr/bin/dsync [0x4078e0] -> /usr/bin/dsync(dsync_brain_sync+0x42e) [0x406cfe] -> /usr/bin/dsync [0x4079e1] -> /usr/bin/dsync(dsync_brain_sync+0x3f0) [0x406cc0] -> /usr/bin/dsync(dsync_brain_sync_all+0x18) [0x407728] -> /usr/bin/dsync(main+0x436) [0x406156] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3d18a1d994] -> /usr/bin/dsync [0x405c29] -- Frode Nordahl

2 1

[Dovecot] 2.0.beta4, Panic: stream doesn't support seeking backwards
by Juergen Daubert 04 Jun '10

04 Jun '10

Hi, got the following with beta4 while uploading messages from a local mbox to the dovecot server in my LAN, tested with mutt and sylpheed, the same action works with 1.2.11: Mar 29 13:42:46 [dovecot] imap(juergen): Panic: stream doesn't support seeking backwards Mar 29 13:42:46 [dovecot] imap(juergen): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xb76b7ec4] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76b7f2c] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0xb76b8193] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76c02cd] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_seek+0xbb) [0xb76be1db] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76c08a9] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x6e) [0xb76be27e] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x40) [0xb76be570] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x6d) [0xb76a7b6d] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a4302] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a498f] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x6e) [0xb76be27e] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a3f61] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a4072] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_seek+0xbb) [0xb76be1db] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x52) [0xb76be262] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76c246d] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x6e) [0xb76be27e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mbox_save_continue+0x4c) [0xb776ca6c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_continue+0x14) [0xb7708964] -> dovecot/imap [0x804e32f] -> dovecot/imap [0x804ed31] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd1) [0xb76c38f1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x29) [0xb76c29f9] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x25) [0xb76b1c45] -> dovecot/imap(main+0x1b3) [0x805da13] -> /lib/libc.so.6(__libc_start_main+0xdb) [0xb7559a3b] -> dovecot/imap [0x804e161] Mar 29 13:42:46 [dovecot] master: service(imap): child 21107 killed with signal 6 (core dumps disabled) # dovecot -n # 2.0.beta4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32.10 i686 listen = * login_access_sockets = tcpwrap passdb { driver = shadow } service tcpwrap { unix_listener login/tcpwrap { mode = 0666 } } ssl_cert = </etc/ssl/certs/dovecot.crt ssl_key = </etc/ssl/keys/dovecot.key userdb { driver = passwd } Greetings Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux

3 16

[Dovecot] userdb prefetch not compatible with ssl_require_client_cert
by zhong ming wu 04 Jun '10

04 Jun '10

Dear List I looked into docs but couldn't see any where that says of this incompatibility. Anywhere this is confirmed in the doc? Thanks mr.wu

2 3

[Dovecot] 'doveadm who' enhancement request
by Brad Davidson 04 Jun '10

04 Jun '10

When Dovecot is in proxy mode, the client sends along the original connection endpoints in an ID command. Is there any chance 'doveadm who' could use this to display the original connection source? As it currently stands, all I see is a bunch of connections from the proxy. Thanks! --- Brandon 'Brad' Davidson Virtualization Systems Administrator University of Oregon Information Services (541) 346-8098 brandond(a)uoregon.edu

3 7

[Dovecot] v2.0.beta4: conversion of v1.2 configuration
by Pascal Volk 04 Jun '10

04 Jun '10

Hi Timo, I've just tried to convert my v1.2 configuration to a v2.0 configuration. Below a few obsolete warnings, among others "mail_executable has been replaced by service { executable }", was an interesting error: "doveconf: Error: duplicate listener: 198:" The broken parts of the converted configuration: # 2.0.beta4 (84ffb38839b9): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-trunk-amd64 x86_64 Debian squeeze/sid listen = 192.168.111.222 [2a01 service imap-login { inet_listener imap { port = 198 } } service managesieve-login { inet_listener managesieve { port = 198 } } service managesieve { executable = /usr/lib/dovecot/rawlog /usr/lib/dovecot/managesieve } service pop3-login { inet_listener pop3 { port = 198 } } # missing section: #protocol lda { # … #} # missing setting #postmaster_address The corresponding parts from v1.2 configuration: protocols = imap imaps managesieve pop3 pop3s listen = 192.168.111.222 [2a01:198:37a:1::1] protocol managesieve { mail_executable = /usr/lib/dovecot/rawlog /usr/lib/dovecot/managesieve } protocol lda { postmaster_address = f007ba11.1008605(a)localdomain.org mail_plugins = sieve } Why is the lda section missing? Because it is not listed in v1.2's protocols setting? (only an idea/wild guess) Regards, Pascal -- The trapper recommends today: deadbeef.1008606(a)localdomain.org

3 3

[Dovecot] Panic with mail_log activated
by Xavier Pons 04 Jun '10

04 Jun '10

Hi, We get intermitend deliver-errors when we have activated the mail_log plugin. The installed version is dovecot-2.0-beta5. Below, the error we get: Jun 02 21:58:11 lda(xxx(a)uib.es): Panic: file mail-log-plugin.c: line 364 (mail_log_mail_transaction_commit): assertion failed: (ret) Jun 02 21:58:11 lda(xxx(a)uib.es): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x31c4a35dd0] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x37) [0x31c4a35eb7] -> /usr/lib/dovecot/libdovecot.so.0 [0x31c4a352f8] -> /usr/lib/dovecot/lib20_mail_log_plugin.so [0x2ba85f9a6369] -> /usr/lib/dovecot/lib15_notify_plugin.so(notify_contexts_mail_transaction_commit+0x76) [0x2ba85f7a3716] -> /usr/lib/dovecot/lib15_notify_plugin.so [0x2ba85f7a3b49] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x3d) [0x31c4e2d5bd] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x255) [0x31c5205585] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0xd3) [0x31c5205903] -> /usr/libexec/dovecot/deliver(main+0x63a) [0x402c0a] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x324d01d994] -> /usr/libexec/dovecot/deliver [0x402509] it's a bug or a misconfiguration? thanks Xavier

3 5

[Dovecot] SORT with unknown charset bug?
by A.L.E.C 04 Jun '10

04 Jun '10

I'm not sure this is a known bug. I'm using dovecot 1.1.19. C: s SORT (DATE) blah ALL UNDELETED OR HEADER SUBJECT {4} S: + OK C: asdf HEADER FROM {4} S: + OK C: asdf S: * SORT 1 2 4 5 3 6 7 (... all messages in folder) S: s NO [BADCHARSET] Unknown charset I think there shouldn't be "* SORT... " response. -- Aleksander 'A.L.E.C' Machniak http://alec.pl gg:2275252 LAN Management System Developer http://lms.org.pl Roundcube Webmail Developer http://roundcube.net

2 3

[Dovecot] Auto forward virtual users mail using Sieve
by Julian Baker 04 Jun '10

04 Jun '10

Hi All I'm trying to configure Dovecot to automatically forward mail to another account without the virtual user having to log-in first to Roundcube web mail. These are virtual users with no log-in to the server only Roundcube's web interface The situation is that I have two domains only who want to receive email at their domains, get a forwarded copy at their hotmail account, then log-in to Roundcube to reply. A Sieve script running in Dovecot seems the way to go, but the finer points of configuration have failed me. I got as far as 1) /etc/dovecot/dovecot.conf Adding: protocol lda { mail_plugins = cmusieve mail_plugin_dir = /usr/lib/dovecot/modules/lda } 2) /var/vmail/___domain___/___user___/.dovecot.sieve Created the .dovecot.sieve file in the domain/user directory and added: require ["fileinto ","reject","vacation","imapflags","relational","regex","notify"]; # Resend a copy of the message to another address # if true { redirect "julian(a)flatearth.co.uk"; } Which doesn't seem to have broken anything. Or worked. I'm assuming that as /var/vmail/___domain___/___user___/ is their virtual user home/mail spool the '.dovecot.sieve' file will get picked up. It seems that Dovecot isn't configured to use send via Deliver ? My conf is pasted before (Exim handles regular domain email forwarding mail for a bunch of virtual domains to pop accounts.) TIA Julian dovecot --version 1.0.rc15 ovecot -n # /etc/dovecot/dovecot.conf protocols: imap imaps pop3 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 login_process_size: 64 verbose_proctitle: yes first_valid_uid: 102 first_valid_gid: 104 mail_privileged_group: Debian-exim mail_location: maildir:/var/vmail/%d/%n/ mbox_write_locks: fcntl mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 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 tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle namespace: type: private separator: . prefix: INBOX. inbox: yes namespace: type: private separator: . inbox: yes hidden: yes auth default: verbose: yes debug: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: prefetch args: /etc/dovecot/dovecot-sql.conf Roundcube v0.3.0 _______________________________________________ F L A T E A R T H I N D U S T R I E S L T D Julian Baker - Email: julian(a)flatearth.co.uk - AIM: juliobesq Phone: +44 (0)20 7916 4801 - Mobile: +44 (0)7961 307879 124 Agar Grove, London NW1 9TY, UK - www.flatearth.co.uk · DESIGN FOR PIXELS · PRINTING BY HAND · Privileged/Confidential information may be contained in this message. If you are not the intended addressee you should destroy this message & kindly notify the sender by reply email. Opinions, conclusions & other information in this message that do not relate to the official business of Flat Earth shall be understood as neither given nor endorsed by it.

3 4

Re: [Dovecot] auth socket goes away on reload
by David Jonas 03 Jun '10

03 Jun '10

On 6/3/10 , Jun 3, 9:45 AM, Jerrale Gayle wrote: > On 6/3/2010 12:35 PM, David Jonas wrote: >> We're using the SQLite backend for authentication of Postfix SASL. When >> the db is replaced we HUP dovecot to close and reopen its connection. >> During this time it appears the socket file is removed and Postfix >> rejects the authentication attempt. From the logs: >> >> Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading >> configuration >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: SASL: Connect to >> private/auth failed: Connection refused >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: unknown[dd.dd.dd.dd]: >> SASL LOGIN authentication failed: >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: NOQUEUE: reject: RCPT from >> unknown[dd.dd.dd.dd]: 554 5.7.1<user(a)example.com>: Relay access denied; >> from=<user2(a)example.com> to=<user(a)example.com> proto=ESMTP >> helo=<localhost.localdomain> >> >> Jun 3 00:23:02 xxx postfix/smtpd[14930]: warning: unknown[dd.dd.dd.dd]: >> SASL LOGIN authentication failed: Connection lost to authentication >> server >> Jun 3 00:23:02 xxx postfix/smtpd[14930]: lost connection after AUTH >> from unknown[dd.dd.dd.dd] >> >> Is there an obvious way around this? I know I could somehow merge the >> changes into the running sqlite db but that undermines the simplicity of >> the design I have. Maybe a patch to reopen the db if it's replaced? Or >> perhaps I should just switch to a different db format -- that's probably >> the quickest/easiest solution. Any other ideas? There are about 20k >> entries to deal with. >> >> Thanks, >> >> David >> >> > the HUP reload method is only available on dovecot 2.0. Make sure > you're using that version to do that; otherwise, killall dovecot and > then dovecot. I should have specified that this is dovecot 1.2.7. The sighup seems to work just fine except for the effect I've outlined.

2 1

[Dovecot] Sieve GUI
by Gerhard Waldemair 03 Jun '10

03 Jun '10

> Is there à GUI for sieve. > > I don't have installed Squrielmail, but won't like to manage the > Rules per ssh

13 19

[Dovecot] auth socket goes away on reload
by David Jonas 03 Jun '10

03 Jun '10

We're using the SQLite backend for authentication of Postfix SASL. When the db is replaced we HUP dovecot to close and reopen its connection. During this time it appears the socket file is removed and Postfix rejects the authentication attempt. From the logs: Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading configuration Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: SASL: Connect to private/auth failed: Connection refused Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: unknown[dd.dd.dd.dd]: SASL LOGIN authentication failed: Jun 3 00:23:02 xxx postfix/smtpd[14746]: NOQUEUE: reject: RCPT from unknown[dd.dd.dd.dd]: 554 5.7.1 <user(a)example.com>: Relay access denied; from=<user2(a)example.com> to=<user(a)example.com> proto=ESMTP helo=<localhost.localdomain> Jun 3 00:23:02 xxx postfix/smtpd[14930]: warning: unknown[dd.dd.dd.dd]: SASL LOGIN authentication failed: Connection lost to authentication server Jun 3 00:23:02 xxx postfix/smtpd[14930]: lost connection after AUTH from unknown[dd.dd.dd.dd] Is there an obvious way around this? I know I could somehow merge the changes into the running sqlite db but that undermines the simplicity of the design I have. Maybe a patch to reopen the db if it's replaced? Or perhaps I should just switch to a different db format -- that's probably the quickest/easiest solution. Any other ideas? There are about 20k entries to deal with. Thanks, David

2 1

Re: [Dovecot] auth socket goes away on reload
by William Blunn 03 Jun '10

03 Jun '10

On 03/06/2010 19:08, David Jonas wrote: > On 6/3/10 , Jun 3, 10:16 AM, William Blunn wrote: > >> On 03/06/2010 17:35, David Jonas wrote: >> >>> We're using the SQLite backend for authentication of Postfix SASL. When >>> the db is replaced we HUP dovecot to close and reopen its connection. >>> During this time it appears the socket file is removed and Postfix >>> rejects the authentication attempt. From the logs: >>> >>> Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading >>> configuration >>> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: SASL: Connect to >>> private/auth failed: Connection refused >>> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: unknown[dd.dd.dd.dd]: >>> SASL LOGIN authentication failed: >>> Jun 3 00:23:02 xxx postfix/smtpd[14746]: NOQUEUE: reject: RCPT from >>> unknown[dd.dd.dd.dd]: 554 5.7.1<user(a)example.com>: Relay access denied; >>> from=<user2(a)example.com> to=<user(a)example.com> proto=ESMTP >>> helo=<localhost.localdomain> >>> >>> Jun 3 00:23:02 xxx postfix/smtpd[14930]: warning: unknown[dd.dd.dd.dd]: >>> SASL LOGIN authentication failed: Connection lost to authentication >>> server >>> Jun 3 00:23:02 xxx postfix/smtpd[14930]: lost connection after AUTH >>> from unknown[dd.dd.dd.dd] >>> >>> Is there an obvious way around this? I know I could somehow merge the >>> changes into the running sqlite db but that undermines the simplicity of >>> the design I have. Maybe a patch to reopen the db if it's replaced? Or >>> perhaps I should just switch to a different db format -- that's probably >>> the quickest/easiest solution. Any other ideas? There are about 20k >>> entries to deal with. >>> >> It sounds like your updates arrive in the shape of entire-table updates. >> >> That is no problem. You can easily apply entire-table updates to the >> database without having to re-create the SQLite database file, and >> without having to tell Dovecot. >> >> Just create a new table (with a different name) inside the SQLite >> database file, with the new content, then snap it into place using a >> pair of table renames inside a transaction; then delete the old table. >> >> That way you don't need to re-create the database file or HUP Dovecot, >> and Dovecot will only ever see the old data or the new data. >> > That sounds reasonable, not sure why I didn't think of it! Thanks. > If you are going to keep the SQLite database around, you might want to look at vacuuming it periodically using either VACUUM or the auto_vacuum PRAGMA depending on what fits your context best. http://sqlite.org/lang_vacuum.html http://sqlite.org/pragma.html#pragma_auto_vacuum Bill

2 2

Re: [Dovecot] auth socket goes away on reload
by David Jonas 03 Jun '10

03 Jun '10

On 6/3/10 , Jun 3, 10:16 AM, William Blunn wrote: > On 03/06/2010 17:35, David Jonas wrote: >> We're using the SQLite backend for authentication of Postfix SASL. When >> the db is replaced we HUP dovecot to close and reopen its connection. >> During this time it appears the socket file is removed and Postfix >> rejects the authentication attempt. From the logs: >> >> Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading >> configuration >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: SASL: Connect to >> private/auth failed: Connection refused >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: unknown[dd.dd.dd.dd]: >> SASL LOGIN authentication failed: >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: NOQUEUE: reject: RCPT from >> unknown[dd.dd.dd.dd]: 554 5.7.1<user(a)example.com>: Relay access denied; >> from=<user2(a)example.com> to=<user(a)example.com> proto=ESMTP >> helo=<localhost.localdomain> >> >> Jun 3 00:23:02 xxx postfix/smtpd[14930]: warning: unknown[dd.dd.dd.dd]: >> SASL LOGIN authentication failed: Connection lost to authentication >> server >> Jun 3 00:23:02 xxx postfix/smtpd[14930]: lost connection after AUTH >> from unknown[dd.dd.dd.dd] >> >> Is there an obvious way around this? I know I could somehow merge the >> changes into the running sqlite db but that undermines the simplicity of >> the design I have. Maybe a patch to reopen the db if it's replaced? Or >> perhaps I should just switch to a different db format -- that's probably >> the quickest/easiest solution. Any other ideas? There are about 20k >> entries to deal with. > > It sounds like your updates arrive in the shape of entire-table updates. > > That is no problem. You can easily apply entire-table updates to the > database without having to re-create the SQLite database file, and > without having to tell Dovecot. > > Just create a new table (with a different name) inside the SQLite > database file, with the new content, then snap it into place using a > pair of table renames inside a transaction; then delete the old table. > > That way you don't need to re-create the database file or HUP Dovecot, > and Dovecot will only ever see the old data or the new data. That sounds reasonable, not sure why I didn't think of it! Thanks.

1 0

[Dovecot] Configure unsuccessful login attempts
by Greg Pearson 03 Jun '10

03 Jun '10

Hi, using PAM, how can I configure how many attempts a user can make to connect, and if exceeding a certain number, block him for a specified amount of time? Any idea what the defaults are?

4 6

[Dovecot] master users with dovecot2 braek down to allowed domain
by Robert Schetterer 03 Jun '10

03 Jun '10

Hi, i think ive asked it before perhaps this feature can be included in dovecot2 couldnt get it run with dovecot 1.2.x if i use the postfixadmin superuser,domainadmin,domainuser layout so there are domainadmins defined in a sql table it would be a nice feature to break it down to be master only at there related domains via sql lookup at recent i think there is only the chance to give master rights to all adresses for users defined as masters -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 2

[Dovecot] Dovecot aspects of fighting spam
by Phil Howard 02 Jun '10

02 Jun '10

I see no documents in the Dovecot documents wiki on how Dovecot features can be used in the fight against spam. One hit came up in a search, and it was about how to fight spam in the MoinMoin Wiki itself (e.g. TextCHAs and such). I already asked in another thread about removing message files at the search from a designated "learn-spam" folder. My next question would be how to automatically place detected spam into a specific folder for the user to access or ignore as they deem fit. That would seem to me to be something for the deliver command and its -m option. But this might be more of a Dovecot and MTA coordination issue, too (e.g. how to get the spam detection done in the MTA ... Postfix in my case ... to become a label of some sort that ends deciding the folder. The -m option might be harder to get it dynamically set since it would be hard coded in master.cf for Postfix (so a variable has to be able to direct it to INBOX in this case). But maybe the "standard" way of doing this is to shim another program between the MTA (Postfix for me) and the LDA (Dovecot deliver) to dynamically add the -m option on the fly? Lacking any other clever solution, this seems to me to be the way I could make it work. Maybe there is a special header deliver could detect, such as "X-Spam: yes"? A wiki document on how Dovecot helps (or how to help Dovecot) in the fight against spam, I think, would be helpful.

10 28

[Dovecot] returned error 83 (Out of memory)
by J Contad 02 Jun '10

02 Jun '10

Hello! I've setup dovecot a few months ago, and it was working pretty swimmingly. Then, out of nowhere, we started getting this error: Apr 21 19:15:17 IMAP(xx(a)xxx.com): Fatal: block_alloc(1073741824): Out of memory Apr 21 19:15:17 IMAP(xx(a)xxx.com): Error: Raw backtrace: imap [0x49e5e0] -> imap [0x49e643] -> imap [0x49dba1] -> imap [0x4a7f6d] -> imap [0x4a7f98] -> imap [0x4a8028] -> imap [0x49bf6f] -> imap(buffer_write+0xe4) [0x49c334] -> imap(mail_cache_lookup_headers+0x146) [0x46dcf6] -> imap [0x458162] -> imap(index_mail_get_first_header+0x45) [0x458685] -> imap [0x45fe44] -> imap [0x460008] -> imap [0x4796d1] -> imap(hash2_lookup+0x64) [0x4a1c94] -> imap(mail_index_strmap_view_sync_add+0x85) [0x47ab05] -> imap(mail_thread_init+0x2a5) [0x4602f5] -> imap(cmd_thread+0x161) [0x41f931] -> imap(cmd_uid+0x78) [0x41fb38] -> imap [0x42079c] -> imap [0x420852] -> imap(client_handle_input+0x3f) [0x42098f] -> imap(client_input+0x5f) [0x4214df] -> imap(io_loop_handler_run+0xf8) [0x4a63a8] -> imap(io_loop_run+0x1d) [0x4a54ed] -> imap(main+0x620) [0x428db0] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3f75e1d8a4] -> imap [0x419969] Apr 21 19:15:17 dovecot: Error: child 25918 (imap) returned error 83 (Out of memory - see mail_process_size setting) The folder (which is shared) has about 8 thousand emails in it. I'm not sure if it's pertinent, but the dovecot.index.cache file is about 8MB. Help? Cheers, -- John

3 2

[Dovecot] Dovecot install problem
by David 02 Jun '10

02 Jun '10

I am trying to set up a new web and mail server i have postfix now working but dovecot will not allow me to login and retrieve the emails so below isa portion of the log file passwd-file /var/mail/vhosts/xxxx.net/shadow: stat() failed: Permission denied passwd-file(xxxxx@xxxx.net,::ffff:0.0.0.0): no passwd file: /var/mail/vhosts/xxxx.net/shadow Dovecot -n output # 1.0.7: /etc/dovecot.conf login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: Maildir:/var/mail/vhosts/%d/%n mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: mechanisms: plain login CRAM-MD5 verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /var/mail/vhosts/%d/shadow userdb: driver: passwd-file args: /var/mail/vhosts/%d/passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix The passwd shadow file -rw-r----- 1 root root 210 May 24 21:39 passwd -rw-r----- 1 root root 327 May 24 21:39 shadow So who whould own these files? What should the perrmissions be?

4 7

[Dovecot] configuring sendmail to work with dovecot+LDAP
by Douglas Maus 02 Jun '10

02 Jun '10

I would like to setup dovecot (1.1.20) with LDAP virtual users, but I don't seem to understand how to get my sendmail to accept mail for the virtual users. (I am rather new to this, so I may have some misunderstandings) I have followed - wiki.dovecot.org/HowTo/DovecotOpenLdap (OpenLDAP 2.3.43) and I think I have IMAP working for virtual users. I can connect to port 143, enter a username and password and it works. Now I surmise I need to configure my SMTP server to accept mail for these LDAP virtual users, and deliver it appropriately. (The above HowTo doesn't address this step, from what I can tell) I read - wiki.dovecot.org/LDA and wiki.dovecot.org/LDA/Sendmail (I'm using OpenBSD 4.7, which uses sendmail for MTA / SMTP server, sendmail version 8.14.3) For sendmail.cf, I made the changes in my sendmail.mc file to include the dovecot mailer (calling /usr/local/libexec/dovecot/deliver), and compiled with m4 and installed the new sendmail.cf For dovecot.conf, I edited the portions (abbreviated): protocol lda { auth_socket_path = /var/run/dovecot/auth-master } and auth default { socket listen { master {path = /var/run/dovecot/auth-master }}} When I try to test this, (telnet www.example.org 25) If I try: MAIL TO:jdoe@www.example.org I get "User unknown" I see that if I try: MAIL TO:jdoe@example.org I get "Relaying denied" Either way it doesn't get delivered. Thank you for any help. And if anyone knows a good basic tutorial for dovecot+LDAP+sendmail I would really appreciate it. dovecot -n (de-identified, and yes I know SSL is disabled, after it all works I'll fix it) ---------- # 1.1.20: /etc/dovecot.conf Warning: fd limit 128 is lower than what Dovecot can use under full load (more than 640). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: OpenBSD 4.7 i386 ffs base_dir: /var/dovecot/ protocols: imap listen: *:143 ssl_disable: yes ssl_cert_file: /etc/ssl/dovecotcert.pem disable_plaintext_auth: no login_dir: /var/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: _dovecot verbose_proctitle: yes first_valid_uid: 519 last_valid_uid: 519 first_valid_gid: 519 last_valid_gid: 519 mail_uid: 519 mail_gid: 519 mail_location: mbox:/var/mail/virtual/%u/mail mbox_write_locks: fcntl imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep lda: postmaster_address: postmaster(a)example.org sendmail_path: /usr/sbin/sendmail auth_socket_path: /var/run/dovecot/auth-master auth default: verbose: yes passdb: driver: bsdauth passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: passwd userdb: driver: ldap args: /etc/dovecot-ldap.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: _dovevirt

2 1

[Dovecot] Migration - Dovecot to Dovecot
by Greg Pearson 02 Jun '10

02 Jun '10

Hi, I am using Dovecot with mbox format, and I am interested to move to Maildir. I have run the modified script (mb2md) but it seems UIDs are not preserved. I don't know how to verify this, but my client seems to be downloading all messages again. Can someone help?

3 2

[Dovecot] recipient_delimiter
by Phil Howard 02 Jun '10

02 Jun '10

I have recipient_delimiter = + in main.cf (Postfix). But deliveries to dovecot/deliver are still being rejected. It appears that the full email is still in the envelope (e.g. phil+howard(a)example.com which I want to be delivered to phil(a)example.com) Is that how it's supposed to work and Dovecot just doesn't support this?

4 29

Re: [Dovecot] draft-ietf-morg-list-specialuse-01 - IMAP LIST extension for special-use mailboxes
by Nikolay Shopik 01 Jun '10

01 Jun '10

On 20.05.2010 14:40, Timo Sirainen wrote: > On 20.5.2010, at 12.11, Nikolay Shopik wrote: > >> I don't think this really need per-user option. This is basically "system folders" and MUA will decide on their local names. Combining with autocreate plugin seems reasonable. > > Autocreate plugin would be useful only if it was a per-user option. Then it could create some kind of a file into the created mailbox. > > If it was a global option .. could it be just something as simple as > > list_specialuse = \Trash:Trash "\Sent:Sent Messages" etc. > > or > > list_specialuse_trash = Trash > list_specialuse_sent = Sent > etc. > > I don't really like either of them.. > What's wrong with these examples for global option, second one looks good for me.

3 4

[Dovecot] Intermittent timeout issues
by Del Stoliker 01 Jun '10

01 Jun '10

Greetings list! We've been experiencing an intermittent issue in which none users are able to log into the mail server for about 10 to 20 minutes. This issue first appeared on our CentOS 4 box running dovecot 1.2.11 after upgrading from the stock version 0.99. The issue persists after migrating our users to a CentOS 5 server - also running version dovecot 1.2.11 but now in the 64-bit flavor. Our users authenticate against LDAP via PAM in case that might be relevant. I've yet to find anything "of interest" in the logs covering the outages. But here is what I've noticed: * Users on our internal network are still able to authenticate and login. * Users from the outside are "Disconnected for inactivity" * Immediately after the restart, external users were able to log in again. It almost sounds like the firewall is blocking external access except that: * The version of dovecot was the thing that changed * Everything starts working again after a dovecot restart If anyone could provide some insight, I'd sure appreciate it. Output of dovecot -n # 1.2.11: /etc/dovecot.conf # OS: Linux 2.6.18-164.15.1.el5 x86_64 CentOS release 5.4 (Final) listen: * shutdown_clients: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_process_per_connection: no login_trusted_networks: x.x.x.x/x login_max_processes_count: 164 max_mail_processes: 2048 mail_max_userip_connections: 50 mail_location: maildir:~/Maildir mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 pop3_no_flag_updates(default): no pop3_no_flag_updates(imap): no pop3_no_flag_updates(pop3): yes pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh lda: postmaster_address: postmaster(a)domain.com sendmail_path: /usr/sbin/sendmail auth default: passdb: driver: pam userdb: driver: passwd

2 1

[Dovecot] purge maildir folder after sa-learn
by Florian Effenberger 01 Jun '10

01 Jun '10

Hello, I am looking for a command-line utility to automatically purge one Maildir folder. I want to periodically run sa-learn from cron, and after the spam learning folder has been added to the Bayes database, its contents should be deleted. I've searched a bit, but only found a few old utilities or some telnet+expect scripts, which both didn't look too reliable. Is there any command-line utility to delete all contents of a Maildir folder, or is there any other solution? Thanks, Florian

6 16

Re: [Dovecot] cur folder e-mails are not shown...
by Gonzalo Aguilar Delgado 01 Jun '10

01 Jun '10

>Since you didn't claim you actually are missing mail, just seeing more Nope. As I suffer the same problem from Evolution and ThunderBird >They could be "deleted" (actually marked for deletion, physically >removed upon expunge). Those would have a T flag in the file name after >the comma. Your MUA Evolution shows them in the Trash (virtual) folder. I tried all this but nothing shown. It's like cur folder is not shown. >They could have been flagged Junk, and only be displayed in the Junk >(virtual) folder. Junk folder is almost empty since I have SpamAsassin in place >You could have a search active, hiding some mail. I checked this also. But's not. >You could have specifically hidden them. See the View menu. I checked show all. But only a few appears. The one deleted by spam filter in the client. What else can be?

2 2

[Dovecot] RTFM: Manual pages for Dovecot v2.0
by Pascal Volk 01 Jun '10

01 Jun '10

Hello Dovecot admins. I've started writing manual pages for Dovecot v2.0. I'm sure they are not perfect yet. I'd like to ask you all to read the manual pages. It would be nice to get some ideas/suggestions/improvements. So that that the Dovecot v2.0.0 release could be distributed with /fine manuals/. The manual pages are available at: http://wiki2.dovecot.org/ManPages This is also the intended place for 'discussions' about the man pages. Regards, Pascal -- The trapper recommends today: cafebabe.1007713(a)localdomain.org

2 3

Re: [Dovecot] quota and postfix virtual users
by gbotero＠emailforall.no-ip.org 01 Jun '10

01 Jun '10

hi, Simone Caruso, thanks for your answer but i have some questions i test the script in the console and he works he read the quota pased by mysql and then quota_rule ok but he update the maildirsize file??? and this script have to be called from postfix or dovecot?? thanks for all, sorry for my english ;) Guillermo Botero Leticia, Amazonas - Colombia gbospina(a)gmail.com

2 1

[Dovecot] Error: file_dotlock_open() failed with file $FILE ENOENT
by Pascal Volk 31 May '10

31 May '10

I've deleted some empty IMAP folders, using Thunderbird. But before deleting them, I had a look into Trash directory on the filesystem: /home/pvo/mdbox/mailboxes/Trash/ ├── dbox-Mails │ ├── dovecot.index │ ├── dovecot.index.backup │ ├── dovecot.index.cache │ └── dovecot.index.log ├── Dev │ └── dbox-Mails │ └── dovecot.index.log ├── S4 │ └── dbox-Mails │ └── dovecot.index.log └── Server4 └── dbox-Mails └── dovecot.index.log (Yeah, looks good, no dbox-GUID file.) After deleting all IMAP folders from Trash I found this lines in the log file: Apr 06 05:44:36 imap(pvo): Error: file_dotlock_open() failed with file /home/pvo/mdbox/mailboxes/Trash/S4/dbox-Mails/dovecot.index.log: No such file or directory Apr 06 05:44:36 imap(pvo): Error: file_dotlock_open() failed with file /home/pvo/mdbox/mailboxes/Trash/S4/dbox-Mails/dovecot.index.log: No such file or directory Regards, Pascal -- The trapper recommends today: fabaceae.1009606(a)localdomain.org

2 1

[Dovecot] dovecot-2.0-pigeonhole/ManageSieve: wrong service name
by Pascal Volk 31 May '10

31 May '10

Hi Stephan, ManageSieve uses the wrong™ service name for the authdb lookup. With dovecot-1.2-managesieve the service name was changed from 'managesieve' to 'sieve'. So I altered my table layout in order to make the query "SELECT userid AS "user", password FROM dovecotpassword('%Ln', '%Ld') WHERE %Ls" work again. When I try to login on the sieve port 4190/tcp, I find this in my dovecot.log: auth: Error: pgsql: Query failed, retrying: ERROR: column "managesieve" does not exist auth: Error: LINE 1: ...", password FROM dovecotpassword('user', 'example.org') WHERE managesiev... Regards, Pascal -- The trapper recommends today: defaced.1015004(a)localdomain.org

3 4

[Dovecot] Permanent flags not announced and public mailbox with per-user index
by Julien Danjou 31 May '10

31 May '10

Hi, I've a set of public mailboxes that all users can access. The index is stored per user, so each user can mark the message as read for themselves. This is with dovecot 1.2.10. However, when selecting the mailbox, system flags are not announced as permanent but only as session flags: 3619 SELECT "public.Admin" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 324 EXISTS * 0 RECENT * OK [UNSEEN 171] First unseen. * OK [UIDVALIDITY 1254326934] UIDs valid * OK [UIDNEXT 1102] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest 3445 OK [READ-ONLY] Select completed. I think (reading the RFC, but I bet you know it better than me) that FLAGS should also been set in PERMANENTFLAGS since they can be permanent. The relevant code seems to be in commands-util.c (dovecot 1.2.11): void client_send_mailbox_flags(struct client *client, bool selecting) { […] if (mailbox_is_readonly(client->mailbox)) { client_send_line(client, "* OK [PERMANENTFLAGS ()] " "Read-only mailbox."); } else { […] } } Even if it's true that the Maildir is read-only, it's still possible to store \Seen permanently. Am I getting things wrong, or is this a bug? If I'm correct, a simple fix MAY be not to send the PERMANENTFLAGS at all since the RFC says: OK [PERMANENTFLAGS (<list of flags>)] A list of message flags that the client can change permanently. If this is missing, the client should assume that all flags can be changed permanently. Thanks, -- Julien Danjou // ᐰ <julien(a)danjou.info> http://julien.danjou.info

2 6

[Dovecot] Dovecot 2.0beta4 HG 11189: dovecot-uidvalidity warning with mdbox mailboxes
by Thomas Leuxner 31 May '10

31 May '10

Hi, the latest HG of Dovecot 2.0 throws a warning when creating a new mailbox inside an INBOX with 'mdbox' format. It does however create the mailbox correctly. ==> /var/log/dovecot.log <== Apr 24 14:35:09 spectre dovecot: imap(tlx(a)leuxner.net): rename(/var/vmail/leuxner.net/tlx/mdbox/dovecot-uidvalidity, /var/vmail/leuxner.net/tlx/mdbox/dovecot-uidvalidity) failed: No such file or directory $ ls -al /var/vmail/leuxner.net/tlx/mdbox total 36 drwx--S--- 4 vmail vmail 4096 2010-04-24 14:37 . drwx--S--- 4 vmail vmail 4096 2010-04-19 10:23 .. -rw------- 1 vmail vmail 386 2010-03-25 19:58 dovecot-acl-list -rw------- 1 vmail vmail 2952 2010-04-24 14:35 dovecot.mailbox.log -rw------- 1 vmail vmail 53 2010-04-24 14:37 dovecot-quota -rw------- 1 vmail vmail 8 2010-04-24 14:35 dovecot-uidvalidity -r--r--r-- 1 vmail vmail 0 2010-04-24 14:35 dovecot-uidvalidity.4bd2e57d drwx--S--- 15 vmail vmail 4096 2010-03-17 19:57 mailboxes drwx--S--- 2 vmail vmail 4096 2010-04-24 14:37 storage -rw------- 1 vmail vmail 1639 2010-04-24 14:35 subscriptions # 2.0.beta4 (6a3eaad2bae6): /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.4 auth_verbose = yes mail_location = mdbox:~/mdbox mail_plugins = acl quota namespace { hidden = no inbox = yes location = prefix = separator = / type = private } namespace { list = yes location = maildir:/var/vmail/public:LAYOUT=fs:INDEX=~/public prefix = Public/ separator = / subscriptions = no type = public } passdb { args = username_format=%u /var/vmail/auth.d/%d/passwd driver = passwd-file } plugin { acl = vfile:/var/vmail/conf.d/%d/acls:cache_secs=300 mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename quota = dict:user::file:%h/mdbox/dovecot-quota quota_rule = *:storage=1GB quota_rule2 = Trash:storage=10%% sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /var/vmail/conf.d/%d/sieve } protocols = imap lmtp service auth-worker { user = doveauth } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = doveauth } service imap-login { inet_listener imap { address = 1.2.3.4 port = 143 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/host_domain.crt ssl_key = </etc/ssl/private/host_domain_2010.key syslog_facility = local1 userdb { args = username_format=%u /var/vmail/auth.d/%d/passwd driver = passwd-file } verbose_proctitle = yes protocol imap { mail_plugins = $mail_plugins imap_acl imap_quota mail_log notify } protocol lmtp { mail_plugins = $mail_plugins sieve } Regards Thomas

2 1

[Dovecot] Dovecot 2.0.beta5: dovecot-uidlist: Duplicate file entry at line X
by Chris Laif 31 May '10

31 May '10

Hi, I'm using dovecot 2.0.beta5 (IMAP and LMTP+sieve) and I'm getting lots of errors like this: Warning: /data/mail/4567/Maildir/dovecot-uidlist: Duplicate file entry at line 3: 1274182284.M635158P16414.mail,S=767,W=785:2,S (uid 5 -> 16) All data is stored on local disk (ext3, no NFS!). As this is a fresh installation of dovecot I do not know if older versions work better. One user complained about loosing email from inbox but I guess that's probably a user error :) I think that the error might be related to deliveries via LMTP as this (new) functionality has not been tested extensivly (?) Regards, Chris ./configure \ --with-pgsql \ --with-ioloop=best \ --without-shadow \ --without-pam \ --without-nss \ --with-storages=maildir \ --without-vpopmail # 2.0.beta5: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.4 auth_cache_negative_ttl = 60 s auth_cache_size = 10485760 auth_mechanisms = plain login cram-md5 disable_plaintext_auth = no first_valid_gid = 1234 first_valid_uid = 1234 info_log_path = /dev/stderr last_valid_gid = 1234 last_valid_uid = 1234 mail_location = maildir:~/Maildir passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts = squat sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = -reject -vacation -enotify -notify } protocols = imap lmtp managesieve service lmtp { inet_listener { port = 24 } } service managesieve-login { inet_listener sieve { address = 10.2.3.4 } } ssl_cert = </etc/dovecot/ssl.crt ssl_key = </etc/dovecot/ssl.key userdb { args = uid=1234 gid=1234 home=/data/mail/%u driver = static } verbose_proctitle = yes protocol lda { mail_plugins = sieve } protocol imap { mail_max_userip_connections = 10 mail_plugins = fts fts_squat } protocol lmtp { mail_plugins = sieve

2 2

[Dovecot] cur folder e-mails are not shown...
by Gonzalo Aguilar Delgado 31 May '10

31 May '10

Hi All! I realized that I have only e-mails from last 13 days. I see that I have lots more in the cur folder inside my Maildir folder. The problem is that I cannot see them. Permissions seems to be right: drwx------ 2 gaguilar gaguilar 1081344 2010-05-28 12:53 cur -rw------- 1 gaguilar gaguilar 4798145 2010-05-28 12:52 deliver.info -rw------- 1 gaguilar gaguilar 0 2010-04-17 21:17 deliver.log -rw------- 1 gaguilar gaguilar 191344 2010-05-28 12:51 dovecot.index -rw------- 1 gaguilar gaguilar 708608 2010-05-28 12:52 dovecot.index.cache -rw------- 1 gaguilar gaguilar 26356 2010-05-28 12:53 dovecot.index.log -rw------- 1 gaguilar gaguilar 35 2010-04-24 19:57 dovecot-keywords -rw------- 1 gaguilar gaguilar 746874 2010-05-28 12:52 dovecot-uidlist -rw------- 1 gaguilar gaguilar 8 2010-05-28 12:46 dovecot-uidvalidity -rw------- 1 gaguilar gaguilar 0 2010-04-17 00:45 dovecot-uidvalidity.4bc8e88d drwx------ 2 gaguilar gaguilar 32768 2010-05-28 12:52 new -rw------- 1 gaguilar gaguilar 2742243 2010-05-28 12:52 procmail.log -rw------- 1 gaguilar gaguilar 48 2010-05-28 12:46 subscriptions drwx------ 2 gaguilar gaguilar 4096 2010-05-28 12:52 tmp dovecot --version 1.1.11 What can be the problem? ____________________________________

3 5

[Dovecot] 1.2.11, mbox, new mail
by Stan Hoeppner 31 May '10

31 May '10

With 1.2.11 and mbox storage, the delay time in pulling new mail headers to the client from imap folders seems to be directly proportional to mailbox size, regardless of the number of new messages. At present, if the mailbox is large, pulling new headers is rather painfully slow. Is this expected behavior? Especially given that the client already has all the "old" mails in the folder cached, and thus wouldn't be asking for them? Is there a setting(s) I can change to optimize/fix this? -- Stan

4 8

[Dovecot] strange sieve situation
by Andy Dills 31 May '10

31 May '10

Hi there, I've been working on rolling out the "deliver" service so we can implement sieve. Dovecot 1.2.11, Postfix 2.6.6, FreeBSD 8, installed by ports. Clustered environment, NFS backend. Everything is working great for the most part, I'm using it to sort a copy of my personal email on a test server. However, I noticed two emails were not properly sorted. I had added a rule (using Ingo, nice little piece of software) to redirect the nightly FreeBSD security output emails into a folder "servers". However, nothing had triggered that rule, and the "Maildir/.servers" directory had not yet been created. Then, three of the "security outputs" came in at one time: May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070108.F2F0B7F5D4(a)mail-out04.xecu.net>: failed to store into mailbox 'servers': Mailbox already exists May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070109.D8F5E159913(a)mail-out01.xecu.net>: failed to store into mailbox 'servers': Mailbox already exists May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070109.D8F5E159913(a)mail-out01.xecu.net>: stored mail into mailbox 'INBOX' May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: execution of script /mail/var/mail2/xecunet/andytest.xecu.net//.dovecot.sieve failed, but implicit keep was successful May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070110.17A781B53B9(a)mail-out02.xecu.net>: stored mail into mailbox 'servers' May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070108.F2F0B7F5D4(a)mail-out04.xecu.net>: stored mail into mailbox 'INBOX' May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: execution of script /mail/var/mail2/xecunet/andytest.xecu.net//.dovecot.sieve failed, but implicit keep was successful That's the order they appeared in my logfile. I'm assuming they were all sent to deliver at the same time, they all thought they needed to make the directory, the one with msgid 20100529070110.17A781B53B9(a)mail-out02.xecu.net was able to make the directory and get delivered, whereas the other two freaked out because they couldn't make the directory they thought needed to be made, and just sent the mail to the inbox. That's a reasonable approach, although I wonder if deliver/sieve could be (or perhaps "has been in 2.0") adjusted to more intelligently handle that edge case. Also, I'm wondering about "dovecot_destination_recipient_limit = 1". I have that set in my main.cf, but I'm not 100% positive it's taking effect. # grep dovecot /usr/local/etc/postfix/main.cf dovecot_destination_recipient_limit = 1 virtual_transport = dovecot # grep dovecot /usr/local/etc/postfix/master.cf dovecot unix - n n - - pipe flags=DRhu user=mailman argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} # postconf | grep dovecot smtpd_sasl_type = dovecot virtual_transport = dovecot # postconf | grep destination_recipient_limit default_destination_recipient_limit = 50 lmtp_destination_recipient_limit = $default_destination_recipient_limit local_destination_recipient_limit = 1 relay_destination_recipient_limit = $default_destination_recipient_limit smtp_destination_recipient_limit = $default_destination_recipient_limit virtual_destination_recipient_limit = $default_destination_recipient_limit Is "dovecot_destination_recipient_limit" being converted into local_ ? Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 ---

2 1

[Dovecot] Unresolved client rejection
by Greg Pearson 31 May '10

31 May '10

Hi, would it be possible to prevent users who try to login from an unresolved IP from connecting to Dovecot IMAP? I have a suspicion that it should be done via the authentication module (ie PAM) but I am not sure (if this is the case could someone recommend a good resource or even a solution). For example sendmail has a relevant macro to achieve this, I was wondering if Dovecot can have similar behavior. Thanks

2 1

Re: [Dovecot] Dovecot and Apples Mail.app
by Gerhard Waldemair 31 May '10

31 May '10

thanks for your answer. There is only 1 Account in Mail.app I have imigratet from Courier and there I had no Problem with all the settings. Is it possible that the index file is damaged or something like that ? Gerhard Am 28.05.10 17:56, schrieb Timo Sirainen: > > On Thu, 2010-05-27 at 10:17 +0200, Gerhard Waldemair wrote: > > >> Now I have the problem, that I get mail under Mail.app double. (same >> header, Message-ID ,...) >> >> When I use Thudnerbird under MacOS there is all OK. >> > That doesn't make any sense. Only thing I can think of is that you > created two identical accounts to Mail.app.. > > >> Are there some Configs that I need to make for MacOS / Mail.app ? >> > No. > >

1 0

[Dovecot] imap folder aliases for different mail clients naming convention
by Robert Schetterer 31 May '10

31 May '10

Hi, sorry if this was asked before and/or if there is allready a solution different imap mail clients, have different imap folder naming conventions typical by sent , trash, spam i normally use thunderbird conventions, as its working on all major plattforms and configure hord/imp , squirrelmail to use it like thunderbird does, additional i use autocreate with this folders it would be nice to alias other mail clients naming conventions to TB folder naming conventions without poke around with i.e symlinks etc, i guess there might be some solution with namespaces but i hope i could be done more easy eventually with a alias plugin etc? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 0

Re: [Dovecot] Dovecot 1.2 - Quotas - Ignoring Trash folder
by e-frog 31 May '10

31 May '10

On 30.05.2010 15:28, wrote Shayne Jellesma: > Hello e-frog, > > Thanks for your reply. I have made the changes you suggested and it is still > not working. > > The new updated SQL query is as follows: > user_query = SELECT maildir, 5000 AS uid, 5000 AS gid, CONCAT('*:storage=', > quota, 'B') AS quota_rule, 'Trash:ignore' AS quota_rule2 FROM mailbox WHERE > username = '%u' AND active = '1' > Looks correct and works for me. You could try and set mail_debug=yes in dovecot.conf This should log the quota rules dovecot is using once you login. e.g. May 30 15:36:52 server dovecot: IMAP(xxx): Quota rule: root=user mailbox=* bytes=1073741824 messages=0 May 30 15:36:52 server dovecot: IMAP(xxx): Quota rule: root=user mailbox=Trash ignored > Regards, > > Shayne Jellesma > Network Administrator / ICT Support > St Martins Lutheran College > Web: http://www.stmartins.sa.edu.au > Skype: shayne.jellesma.smlc > > -----Original Message----- > From: dovecot-bounces+shayne=stmartins.sa.edu.au(a)dovecot.org > [mailto:dovecot-bounces+shayne=stmartins.sa.edu.au@dovecot.org] On Behalf Of > e-frog > Sent: Sunday, 30 May 2010 10:09 PM > To: dovecot(a)dovecot.org > Subject: Re: [Dovecot] Dovecot 1.2 - Quotas - Ignoring Trash folder > > Hello, > > On 30.05.2010 13:34, wrote Shayne Jellesma: >> Hello guys, >> >> Firstly I would like to state that I am fairly new to Dovecot. I have >> played around with it in the past here and there but mainly with debian > packages. >> I have compiled this version of Dovecot from source, so please go easy >> with me. >> >> Ok now down to my questions: >> I am having trouble getting Dovecot to 'ignore' the Trash folder when >> summing up the used quota for a user. > > [snip] > >> plugin: >> >> quota: maildir:ignore=Trash > > Change this to > > quota = maildir > > [snip] > >> >> charged:/usr/local/etc# grep -v '^ *$#.*$\?$' dovecot-sql.conf >> >> driver = mysql >> >> connect = host=localhost dbname=xxx user=mailuser password=xxx >> >> default_pass_scheme = MD5-CRYPT >> >> user_query = SELECT maildir, 5000 AS uid, 5000 AS gid, >> CONCAT('*:storage=', quota, 'B') AS quota_rule FROM mailbox WHERE >> username = '%u' AND active = '1' > > Insert a second quota_rule in your sql query > > 'Trash:ignore' AS quota_rule2 > > See also http://wiki.dovecot.org/Quota/1.1#Quota_rules > > Regards, > e-frog

2 2

[Dovecot] beta5 builds under RHEL
by Axel Thimm 31 May '10

31 May '10

Hi, beta4 built under RHEL4, RHEL5 and RHEL6 (the latter being the public beta). beta5 now builds only for RHEL5, the other two fail with: strnum.c: In function `str_to_llong': strnum.c:139: error: `LLONG_MIN' undeclared (first use in this function) strnum.c:139: error: (Each undeclared identifier is reported only once strnum.c:139: error: for each function it appears in.) Thanks! -- Axel.Thimm at ATrpms.net

4 16

[Dovecot] quota and postfix virtual users
by gbotero＠emailforall.no-ip.org 30 May '10

30 May '10

hi guys, anyone have a virtual server working with postfix + dovecot + roundcube + mysql + virtual domain + virtual users and quota working because the quota is not good, the calculation is wrong i need to delete the maildirsize file to force recalculate, how can i do? the email send and receive fine the virtual users and domain users is fine....... help postfix 2.3.3 dovecot 1.2.11 roundcube 0.3 mysql 5.0.7 i need to solve this please

2 1

[Dovecot] dovecot2beta5 lmtp
by Andreas Schulze 30 May '10

30 May '10

Hello, recently I inspected the sourcecode of the lmtp server. I searched for changes that would add return-path header. ( http://www.dovecot.org/list/dovecot/2010-February/046401.html ) But I found, that all mails are spooled via files in /tmp. ( dovecot2/srv/lmtp/commands.c ~line 695 ) has somebody experiences while delivering huge ammount of mail via dovecot2 lmtp service? - is it faster/slower/comaparable with deliver? - it's hard to believe, that nobody realy misses the return-path header Thanks, Andreas -- Andreas Schulze Internetdienste | P532 DATEV eG 90329 Nürnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196 E-Mail info @datev.de | Internet www.datev.de Sitz: 90429 Nürnberg, Paumgartnerstr. 6-14 | Registergericht Nürnberg, GenReg Nr.70 Vorstand Prof. Dieter Kempf (Vorsitzender) Dipl.-Kfm. Wolfgang Stegmann (stellvertretender Vorsitzender) Dipl.-Kfm. Michael Leistenschneider Jörg Rabe v. Pappenheim Dipl.-Vw. Eckhard Schwarzer Vorsitzender des Aufsichtsrates: Reinhard Verholen

4 3

[Dovecot] Dovecot 1.2 - Quotas - Ignoring Trash folder
by Shayne Jellesma 30 May '10

30 May '10

Hello guys, Firstly I would like to state that I am fairly new to Dovecot. I have played around with it in the past here and there but mainly with debian packages. I have compiled this version of Dovecot from source, so please go easy with me. Ok now down to my questions: I am having trouble getting Dovecot to 'ignore' the Trash folder when summing up the used quota for a user. I am running Dovecot 1.2.11 (with LDA), Postfix 2.5.5, and Postfixadmin 2.3. I am able to send and receive emails fine. Roundcube displays the quota used but this quota also counts what is in the users Trash can. Postfix is configured to hand over delivering of the mail to Dovecot. I have tried different methods from the documentation on ignoring the Trash folder, but have not come up with anything that has worked yet. If someone could point me in the right direction, that would be great. I apologise now if I have not included all required information, I did read the mailing list guidelines and believe I have follow all required steps. charged:/usr/local/etc# dovecot --version 1.2.11 charged:/usr/local/etc# charged:/usr/local/etc# dovecot -n # 1.2.11: /usr/local/etc/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian 5.0.4 ext3 base_dir: /var/run/dovecot/ log_path: /var/log/dovecot12.log info_log_path: /var/log/dovecot12.log protocols: imap imaps pop3 pop3s listen: 118.127.29.214 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 first_valid_uid: 5000 last_valid_uid: 5000 first_valid_gid: 5000 last_valid_gid: 5000 mail_privileged_group: vmail mail_uid: 5000 mail_gid: 5000 mail_location: maildir:/var/vmail/%d/%n/Maildir mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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 namespace: type: private separator: . inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmaster(a)ignitioncarclub.com mail_plugins: quota mail_plugin_dir: /usr/local/lib/dovecot/lda quota_full_tempfail: no auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login 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/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail plugin: quota: maildir:ignore=Trash trash: /usr/local/etc/dovecot-trash.conf charged:/usr/local/etc# charged:/usr/local/etc# grep -v '^ *$#.*$\?$' dovecot-sql.conf driver = mysql connect = host=localhost dbname=xxx user=mailuser password=xxx default_pass_scheme = MD5-CRYPT user_query = SELECT maildir, 5000 AS uid, 5000 AS gid, CONCAT('*:storage=', quota, 'B') AS quota_rule FROM mailbox WHERE username = '%u' AND active = '1' password_query = SELECT username as user, password, '/var/vmail/%d/%n' as userdb_home, 'maildir:/var/vmail/%d/%n' as userdb_mail, 5000 as userdb_uid, 5000 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' charged:/usr/local/etc# charged:/usr/local/etc# dpkg -l | grep postfix ii postfix 2.5.5-1.1 High-performance mail transport agent ii postfix-mysql 2.5.5-1.1 MySQL map support for Postfix charged:/usr/local/etc# Regards, Shayne Jellesma Network Administrator / ICT Support St Martins Lutheran College Web: <http://www.stmartins.sa.edu.au> http://www.stmartins.sa.edu.au Phone: (08) 87 251 430 Skype: shayne.jellesma.smlc

2 1

[Dovecot] doveadm: Error: dlopen(/path/2/lib10_doveadm_expire_plugin.so) failed
by Pascal Volk 30 May '10

30 May '10

Hi Timo, dunno why, but I've executed doveadm with the -D option. Debug output contains: doveadm(root): Error: dlopen(/path/2/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so) failed: /path/2/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_lookup dovecot --version 2.0.beta5 (4faaf5b037d5) Regards, Pascal -- The trapper recommends today: 5e1f1e55.1014901(a)localdomain.org

2 3