February 2014 - dovecot

[Dovecot] (no subject)
by Axel Reinhold 12 Feb '14

12 Feb '14

Subject: dovecot-2.2.11 crash on quit after update to dovecot-2.2.11 pop3 crashes at QUIT after successful deliver: [axel@bongo axel]$ gdb opt/dovecot-2.2.11-1/sbin/dovecot core.13590 warning: core file may not match specified executable file. Core was generated by `dovecot/pop3 p3postlogin'. Program terminated with signal 11, Segmentation fault. #0 0x0804e601 in main () (gdb) bt #0 0x0804e601 in main () #1 0xbfec7ff0 in ?? () #2 0x0804e7dc in main () #3 0x08050038 in service_anvil_global_deinit () #4 0x0804da9d in get_gid () #5 0x0804dc6c in main () #6 0xb7e2de37 in ?? () #7 0xb7e2f477 in ?? () #8 0xb7e2df24 in ?? () #9 0xb7dc2fbd in ?? () #10 0x0804bf13 in __register_frame_info_bases () #11 0xb7c55ebc in ?? () (gdb) q last part of conversation: pop* [20053] 140212130153 debug8: SMTP< 250 2.1.5 axel... Recipient ok pop* [20053] 140212130153 debug8: SMTP> DATA pop* [20053] 140212130153 debug8: SMTP< 354 Enter mail, end with "." on a line by itself pop* [20053] 140212130153 debug8: SMTP> . pop* [20053] 140212130153 debug8: SMTP< 250 2.0.0 s1CC1rGZ020100 Message accepted for delivery pop* [20053] 140212130153 debug8: SMTP> QUIT pop* [20053] 140212130153 debug8: SMTP< 221 2.0.0 bongo.freakout.de closing connection pop* [20053] 140212130153 debug6: SMTP sent to axel Id:2.0.0 s1CC1rGZ020100 pop* [20053] 140212130153 debug8: POP3> DELE 8 pop* [20053] 140212130153 debug8: POP3< +OK Marked to be deleted. pop* [20053] 140212130153 debug6: POP3 delete 8 pop* [20053] 140212130153 debug8: POP3> QUIT pop* [20053] 140212130153 debug8: POP3< #CRASH pop* [20053] 140212130153 error : POP3 no quit pop* [20053] 140212130153 debug5: POP3 logout Regards Axel

1 0

[Dovecot] Fatal: master: service(pop3): child 20972 killed with signal 11
by Jim Knuth 12 Feb '14

12 Feb '14

Hello, since V 2.2.11 I get that error with pop3. With imap everything is fine. Feb 12 13:06:40 server2 dovecot: pop3-login: Login: user=<user>, method=PLAIN, rip=84.183.42.55, lip=195.137.213.14, mpid=20972, TLS, TLSv1 with cipher AES128-SHA (128/128 bits) Feb 12 13:06:41 server2 dovecot: pop3(user): Fatal: master: service(pop3): child 20972 killed with signal 11 (core dumps disabled) Upgrade/Bugfix is coming? -- Mit freundlichen Grüßen, with kind regards, Jim Knuth --------- Lebenskünstler leben von der Zeit, die andere nicht haben.(Michael Douglas)

1 0

[Dovecot] Order of istream and ostream chains
by Philipp Brüll 12 Feb '14

12 Feb '14

Hi, I'm creating a scrambler plugin, that adds an istream and an ostream to the stream-chain for the mail input/output. It works well until the zlib plugin is added to the configuration. The scrambler should run before the zlib and encrypt the mail before it's compressed. Since, the plugin is named lib18_scrambler_... (and the other lib20_zlib....), that works well when a mail is received. When a mail is read via IMAP, the plugins should handle the mail in the reverse order. So first, the zlib should decompress it and afterwards the scrambler should decrypt it. But it seems, that they work the other way around. The scrambler istream gets compressed data as input. It's hooked in the chain of istream as the following... static int scrambler_istream_opened(struct mail *_mail, struct istream **stream) { struct mail_private *mail = (struct mail_private *)_mail; union mail_module_context *mmail = SCRAMBLER_MAIL_CONTEXT(mail); struct istream *input, *inputs[2]; input = *stream; *stream = scrambler_istream_create(input); i_stream_unref(&input); return mmail->super.istream_opened(_mail, stream); } static void scrambler_mail_allocated(struct mail *_mail) { struct mail_private *mail = (struct mail_private *)_mail; struct mail_vfuncs *v = mail->vlast; union mail_module_context *mmail; mmail = p_new(mail->pool, union mail_module_context, 1); mmail->super = *v; mail->vlast = &mmail->super; v->istream_opened = scrambler_istream_opened; MODULE_CONTEXT_SET_SELF(mail, scrambler_mail_module, mmail); } How can I reverse the order of istreams? Should I use another hook or vfuns? I'm stuck in the problem for a while now, so any help would be very welcome. Best regards, Philipp

2 3

[Dovecot] Crash in recent dovecot, different line (with Backtrace:dovecot/pop3)
by Ralf Hildebrandt 12 Feb '14

12 Feb '14

Reading symbols from /usr/local/dovecot-2.2/libexec/dovecot/pop3...done. [New LWP 17294] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1". Core was generated by `dovecot/pop3'. Program terminated with signal 11, Segmentation fault. #0 0x0804eb6a in client_update_mails (client=client@entry=0x82017a0) at pop3-commands.c:256 256 ret = FALSE; #0 0x0804eb6a in client_update_mails (client=client@entry=0x82017a0) at pop3-commands.c:256 search_args = <optimized out> ctx = <optimized out> mail = 0xb759a797 deleted_msgs = {arr = {buffer = 0x81e2098, element_size = 8}, v = 0x81e2098, v_modifiable = 0x81e2098} seen_msgs = {arr = {buffer = 0xb75de224, element_size = 3076002107}, v = 0xb75de224, v_modifiable = 0xb75de224} msgnum = <optimized out> bit = 1 #1 0x0804ee80 in cmd_quit (client=0x82017a0, args=<optimized out>) at pop3-commands.c:289 No locals. #2 client_command_execute (client=client@entry=0x82017a0, name=<optimized out>, name@entry=0x823e08c "QUIT", args=args@entry=0x804f839 "") at pop3-commands.c:920 No locals. #3 0x0804d5f1 in client_handle_input (client=0x82017a0) at pop3-client.c:739 _data_stack_cur_id = 3 line = 0x823e08c "QUIT" args = <optimized out> ret = <optimized out> #4 0xb7585d44 in io_loop_call_io (io=0x8200a80) at ioloop.c:388 ioloop = 0x81ea490 t_id = 2 #5 0xb7586e0e in io_loop_handler_run (ioloop=ioloop@entry=0x81ea490) at ioloop-epoll.c:220 ctx = 0x81eb178 events = 0x0 event = 0x81eb1b8 list = 0x81ebaa0 io = <optimized out> tv = {tv_sec = 9, tv_usec = 999652} events_count = 0 msecs = <optimized out> ret = 1 i = <optimized out> j = <optimized out> call = <optimized out> __FUNCTION__ = "io_loop_handler_run" #6 0xb75857d8 in io_loop_run (ioloop=0x81ea490) at ioloop.c:412 __FUNCTION__ = "io_loop_run" #7 0xb752ad7e in master_service_run (service=0x81ea3b8, callback=callback@entry=0x804b940 <client_connected>) at master-service.c:566 No locals. #8 0x0804bd05 in main (argc=1, argv=0x81ea1e0) at main.c:277 set_roots = {0x80504c0, 0x0} login_set = { auth_socket_path = 0x81e2048 "/usr/local/dovecot-2.2/var/run/dovecot/auth-master", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x804b800 <login_client_connected>, failure_callback = 0x804b7c0 <login_client_failed>, request_auth_token = 0} service_flags = <optimized out> storage_service_flags = <optimized out> username = 0x0 c = <optimized out> -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 1

[Dovecot] personal sieve script not included
by Thomas Krause 12 Feb '14

12 Feb '14

Hello, I'm using dovecot 2.2.10 and roundcube (with managesieve enabled). Sieve filtering works well, as long the rule is written into ~/.dovecot.sieve (which is a link to ~/sieve/managesieve.sieve) When adding a new filter set (in roundcube) the script is written to ~/sieve/newfilterset.sieve. This script will not be executed. How can I solve this? I set sieve_dir = ~/sieve This should work, except I misunderstand the doc. # ls -l ./sieve total 6 -rw------- 1 vmail mail 105 Feb 5 09:24 managesieve.sieve -rw------- 1 vmail mail 113 Feb 4 16:30 test.sieve drwx------ 2 vmail mail 512 Feb 5 09:24 tmp Regards, Thomas.

3 5

[Dovecot] Problem rebuilding Centos 5/6 pigeonhole RPM from mercurial version
by Juan C. Blanco 12 Feb '14

12 Feb '14

Hi Stephan, I'm traying to rebuild the RH (Centos) EL5 and EL6 RPM with the last mercurial pigeonhole 0.4.2 version, but I'm having problems with the build. I think that I've isolated the problem outside rpmbuild context. I've downloaded dovecot and pigeonhole mercurial versions and built dovecot with the commands: dovecot-2.2.10$ ./autogen.sh dovecot-2.2.10$ ./configure INSTALL_DATA="install -c -p -m644" --enable-header-install --disable-static --with-nss --with-shadow --with-pam --with-gssapi=plugin --with-ldap=plugin --with-sql=plugin --with-mysql --with-zlib --with-sql-drivers --with-libcap --with-db --with-ssl=openssl --with-ssldir=/etc/pki/dovecot --with-notify=inotify --with-solr --with-docs dovecot-2.2.10$ make dovecot-2.2.10$ make install DESTDIR=/var/tmp/dovecot after that, building pigeonhole with the commands pigeonhole-0.4.2$ ./autogen.sh pigeonhole-0.4.2$ ./configure INSTALL_DATA="install -c -p -m644" --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --with-dovecot=/var/tmp/dovecot --with-managesieve=yes pigeonhole-0.4.2$ make pigeonhole-0.4.2$ make install DESTDIR=/var/tmp/dovecot works fine, but if I install pigeonhole in a different path, i.e. pigeonhole-0.4.2$ make install DESTDIR=/var/tmp/pigeonhole I get the following error make[4]: Entering directory `/home/jc/pigeonhole-0.4.2/src/lib-sieve' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib64/dovecot" || mkdir -p -- "/var/tmp/pigeonhole/usr/lib64/dovecot" /bin/sh ../../libtool --mode=install /usr/bin/install -c 'libdovecot-sieve.la' '/var/tmp/pigeonhole/usr/lib64/dovecot/libdovecot-sieve.la' libtool: install: warning: relinking `libdovecot-sieve.la' (cd /home/jc/pigeonhole-0.4.2/src/lib-sieve; /bin/sh ../../libtool --tag=CC --mode=relink gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/usr/kerberos/include -o libdovecot-sieve.la -rpath /usr/lib64/dovecot sieve-settings.lo sieve-message.lo sieve-smtp.lo sieve-lexer.lo sieve-script.lo sieve-script-file.lo sieve-script-dict.lo sieve-ast.lo sieve-binary.lo sieve-binary-file.lo sieve-binary-code.lo sieve-binary-debug.lo sieve-parser.lo sieve-address.lo sieve-validator.lo sieve-generator.lo sieve-interpreter.lo sieve-runtime-trace.lo sieve-code-dumper.lo sieve-binary-dumper.lo sieve-result.lo sieve-error.lo sieve-objects.lo sieve-stringlist.lo sieve-comparators.lo sieve-match-types.lo sieve-address-parts.lo sieve-match.lo sieve-commands.lo sieve-code.lo sieve-actions.lo sieve-extensions.lo sieve-plugins.lo cmp-i-octet.lo cmp-i-ascii-casemap.lo mcht-is.lo mcht-contains.lo mcht-matches.lo tst-truefalse.lo tst-not.lo tst-anyof.lo tst-allof.lo tst-address.lo tst-header.lo tst-exists.lo tst-size.lo cmd-require.lo cmd-stop.lo cmd-if.lo cmd-keep.lo cmd-redirect.lo cmd-discard.lo ext-fileinto.lo ext-reject.lo ext-envelope.lo ext-encoded-character.lo sieve.lo ../../src/lib-sieve/plugins/vacation/libsieve_ext_vacation.la ../../src/lib-sieve/plugins/subaddress/libsieve_ext_subaddress.la ../../src/lib-sieve/plugins/comparator-i-ascii-numeric/libsieve_ext_comparator-i-ascii-numeric.la ../../src/lib-sieve/plugins/relational/libsieve_ext_relational.la ../../src/lib-sieve/plugins/regex/libsieve_ext_regex.la ../../src/lib-sieve/plugins/copy/libsieve_ext_copy.la ../../src/lib-sieve/plugins/imap4flags/libsieve_ext_imap4flags.la ../../src/lib-sieve/plugins/include/libsieve_ext_include.la ../../src/lib-sieve/plugins/body/libsieve_ext_body.la ../../src/lib-sieve/plugins/variables/libsieve_ext_variables.la ../../src/lib-sieve/plugins/enotify/libsieve_ext_enotify.la ../../src/lib-sieve/plugins/notify/libsieve_ext_notify.la ../../src/lib-sieve/plugins/environment/libsieve_ext_environment.la ../../src/lib-sieve/plugins/mailbox/libsieve_ext_mailbox.la ../../src/lib-sieve/plugins/date/libsieve_ext_date.la ../../src/lib-sieve/plugins/spamvirustest/libsieve_ext_spamvirustest.la ../../src/lib-sieve/plugins/ihave/libsieve_ext_ihave.la ../../src/lib-sieve/plugins/editheader/libsieve_ext_editheader.la ../../src/lib-sieve/plugins/vnd.dovecot/debug/libsieve_ext_debug.la ../../src/lib-sieve/plugins/vnd.dovecot/duplicate/libsieve_ext_duplicate.la ../../src/lib-sieve/util/libsieve_util.la /home/jc/dovecot-2.2.10/src/lib-lda/libdovecot-lda.la /home/jc/dovecot-2.2.10/src/lib-storage/libdovecot-storage.la /home/jc/dovecot-2.2.10/src/lib-imap-storage/libimap-storage.la /home/jc/dovecot-2.2.10/src/lib-dovecot/libdovecot.la -export-dynamic -ldl -lrt -inst-prefix-dir /var/tmp/pigeonhole) gcc -shared .libs/sieve-settings.o .libs/sieve-message.o .libs/sieve-smtp.o .libs/sieve-lexer.o .libs/sieve-script.o .libs/sieve-script-file.o .libs/sieve-script-dict.o .libs/sieve-ast.o .libs/sieve-binary.o .libs/sieve-binary-file.o .libs/sieve-binary-code.o .libs/sieve-binary-debug.o .libs/sieve-parser.o .libs/sieve-address.o .libs/sieve-validator.o .libs/sieve-generator.o .libs/sieve-interpreter.o .libs/sieve-runtime-trace.o .libs/sieve-code-dumper.o .libs/sieve-binary-dumper.o .libs/sieve-result.o .libs/sieve-error.o .libs/sieve-objects.o .libs/sieve-stringlist.o .libs/sieve-comparators.o .libs/sieve-match-types.o .libs/sieve-address-parts.o .libs/sieve-match.o .libs/sieve-commands.o .libs/sieve-code.o .libs/sieve-actions.o .libs/sieve-extensions.o .libs/sieve-plugins.o .libs/cmp-i-octet.o .libs/cmp-i-ascii-casemap.o .libs/mcht-is.o .libs/mcht-contains.o .libs/mcht-matches.o .libs/tst-truefalse.o .libs/tst-not.o .libs/tst-anyof.o .libs/tst-allof.o .libs/tst-address.o .libs/tst-header.o .libs/tst-exists.o .libs/tst-size.o .libs/cmd-require.o .libs/cmd-stop.o .libs/cmd-if.o .libs/cmd-keep.o .libs/cmd-redirect.o .libs/cmd-discard.o .libs/ext-fileinto.o .libs/ext-reject.o .libs/ext-envelope.o .libs/ext-encoded-character.o .libs/sieve.o -Wl,--whole-archive ../../src/lib-sieve/plugins/vacation/.libs/libsieve_ext_vacation.a ../../src/lib-sieve/plugins/subaddress/.libs/libsieve_ext_subaddress.a ../../src/lib-sieve/plugins/comparator-i-ascii-numeric/.libs/libsieve_ext_comparator-i-ascii-numeric.a ../../src/lib-sieve/plugins/relational/.libs/libsieve_ext_relational.a ../../src/lib-sieve/plugins/regex/.libs/libsieve_ext_regex.a ../../src/lib-sieve/plugins/copy/.libs/libsieve_ext_copy.a ../../src/lib-sieve/plugins/imap4flags/.libs/libsieve_ext_imap4flags.a ../../src/lib-sieve/plugins/include/.libs/libsieve_ext_include.a ../../src/lib-sieve/plugins/body/.libs/libsieve_ext_body.a ../../src/lib-sieve/plugins/variables/.libs/libsieve_ext_variables.a ../../src/lib-sieve/plugins/enotify/.libs/libsieve_ext_enotify.a ../../src/lib-sieve/plugins/notify/.libs/libsieve_ext_notify.a ../../src/lib-sieve/plugins/environment/.libs/libsieve_ext_environment.a ../../src/lib-sieve/plugins/mailbox/.libs/libsieve_ext_mailbox.a ../../src/lib-sieve/plugins/date/.libs/libsieve_ext_date.a ../../src/lib-sieve/plugins/spamvirustest/.libs/libsieve_ext_spamvirustest.a ../../src/lib-sieve/plugins/ihave/.libs/libsieve_ext_ihave.a ../../src/lib-sieve/plugins/editheader/.libs/libsieve_ext_editheader.a ../../src/lib-sieve/plugins/vnd.dovecot/debug/.libs/libsieve_ext_debug.a ../../src/lib-sieve/plugins/vnd.dovecot/duplicate/.libs/libsieve_ext_duplicate.a ../../src/lib-sieve/util/.libs/libsieve_util.a /home/jc/dovecot-2.2.10/src/lib-imap-storage/.libs/libimap-storage.a -Wl,--no-whole-archive -Wl,--rpath -Wl,/usr/lib64/dovecot -L/home/jc/dovecot-2.2.10/src/lib-storage/.libs -L/home/jc/dovecot-2.2.10/src/lib-dovecot/.libs -L/var/tmp/pigeonhole/usr/lib64/dovecot -L/usr/lib64/dovecot -ldovecot-lda -ldovecot-storage -ldovecot -ldl -lrt -Wl,-soname -Wl,libdovecot-sieve.so.0 -o .libs/libdovecot-sieve.so.0.0.0 /usr/bin/ld: cannot find -ldovecot-lda collect2: ld returned 1 exit status libtool: install: error: relink `libdovecot-sieve.la' with the above command before installing it make[4]: *** [install-dovecot_pkglibLTLIBRARIES] Error 1 make[4]: Leaving directory `/home/jc/pigeonhole-0.4.2/src/lib-sieve' make[3]: *** [install-am] Error 2 make[3]: Leaving directory `/home/jc/pigeonhole-0.4.2/src/lib-sieve' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/home/jc/pigeonhole-0.4.2/src/lib-sieve' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/home/jc/pigeonhole-0.4.2/src' Note that in the link command there are library paths for -L/home/jc/dovecot-2.2.10/src/lib-storage/.libs -L/home/jc/dovecot-2.2.10/src/lib-dovecot/.libs while there is not an equivalent one for the libdovecot-lda -Lhome/jc/dovecot-2.2.10/src/lib-lda/.libs Perhaps some problem with libtool is not generating the right library paths? In the first case, since dovecot and pigeonhole where installed in the same path, the library was found in the installation path -L/var/tmp/pigeonhole/usr/lib64/dovecot but in the second case (the normal if building two separate rpm) the pigeonhole installation path does not contains the dovecot libaries. I'm not a developper and am not familiar enough with libtool, so I'm not able to determine the reason of the error since the DEPENDENCIES and LIBADD definitions in src/lib-sieve/Makefile.am seems to be correct ibdovecot_sieve_la_DEPENDENCIES = \ $(plugins) \ $(top_builddir)/src/lib-sieve/util/libsieve_util.la \ $(LIBDOVECOT_LDA_DEPS) \ $(LIBDOVECOT_STORAGE_DEPS) \ $(LIBDOVECOT_DEPS) libdovecot_sieve_la_LIBADD = \ $(plugins) \ $(top_builddir)/src/lib-sieve/util/libsieve_util.la \ $(LIBDOVECOT_LDA) \ $(LIBDOVECOT_STORAGE) \ $(LIBDOVECOT) I apologize for the long message, hope you can help on this. Regards Juan C. Blanco-- +----------------------------------------------------------------+ | Juan C. Blanco | | | | Centro de Calculo | | | Facultad de Informatica U.P.M. | E-mail: jcblanco(a)fi.upm.es | | Campus de Montegancedo | | | Boadilla del Monte | Tel.: (+34) 91 336 7466 | | 28660 MADRID (Spain) | Fax : (+34) 91 336 6913 | +----------------------------------------------------------------+

2 2

[Dovecot] Crash in pop3 with recent dovecot, backtrace
by Ralf Hildebrandt 12 Feb '14

12 Feb '14

Core was generated by `dovecot/pop3'. Program terminated with signal 11, Segmentation fault. #0 0x0804eb6a in client_update_mails (client=client@entry=0x8afd7a8) at pop3-commands.c:256 256 seq_range_array_add(&deleted_msgs, client->msgnum_to_seq_map[msgnum]); #0 0x0804eb6a in client_update_mails (client=client@entry=0x8afd7a8) at pop3-commands.c:256 search_args = <optimized out> ctx = <optimized out> mail = 0xb762d797 deleted_msgs = {arr = {buffer = 0x8ade098, element_size = 8}, v = 0x8ade098, v_modifiable = 0x8ade098} seen_msgs = {arr = {buffer = 0xb7671224, element_size = 3076604219}, v = 0xb7671224, v_modifiable = 0xb7671224} msgnum = <optimized out> bit = 1 #1 0x0804ee80 in cmd_quit (client=0x8afd7a8, args=<optimized out>) at pop3-commands.c:289 No locals. #2 client_command_execute (client=client@entry=0x8afd7a8, name=<optimized out>, name@entry=0x8b3e194 "QUIT", args=args@entry=0x804f839 "") at pop3-commands.c:920 No locals. #3 0x0804d5f1 in client_handle_input (client=0x8afd7a8) at pop3-client.c:739 _data_stack_cur_id = 3 line = 0x8b3e194 "QUIT" args = <optimized out> ret = <optimized out> #4 0xb7618d44 in io_loop_call_io (io=0x8afca88) at ioloop.c:388 ioloop = 0x8ae6498 t_id = 2 #5 0xb7619e0e in io_loop_handler_run (ioloop=ioloop@entry=0x8ae6498) at ioloop-epoll.c:220 ctx = 0x8ae7180 events = 0x0 event = 0x8ae71c0 list = 0x8ae7aa8 io = <optimized out> tv = {tv_sec = 9, tv_usec = 999871} events_count = 0 msecs = <optimized out> ret = 1 i = <optimized out> j = <optimized out> call = <optimized out> __FUNCTION__ = "io_loop_handler_run" #6 0xb76187d8 in io_loop_run (ioloop=0x8ae6498) at ioloop.c:412 __FUNCTION__ = "io_loop_run" #7 0xb75bdd7e in master_service_run (service=0x8ae63c0, callback=callback@entry=0x804b940 <client_connected>) at master-service.c:566 No locals. #8 0x0804bd05 in main (argc=1, argv=0x8ae61e0) at main.c:277 set_roots = {0x80504c0, 0x0} login_set = { auth_socket_path = 0x8ade048 "/usr/local/dovecot-2.2/var/run/dovecot/auth-master", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x804b800 <login_client_connected>, failure_callback = 0x804b7c0 <login_client_failed>, request_auth_token = 0} service_flags = <optimized out> storage_service_flags = <optimized out> username = 0x0 c = <optimized out> -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

1 0

[Dovecot] Fatal: All your namespaces have a location setting.
by Zbyszek Żółkiewski 12 Feb '14

12 Feb '14

Hello, I am trying to setup dovecot sync between 2 servers and come up with this error: Fatal: All your namespaces have a location setting. It should be empty (default mail_location) in the namespace to be converted. i am stuck with this as i cannot find any resolution on the web, here are my config details: doveconf -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 disable_plaintext_auth = no dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u mail_plugins = " notify replication" mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { autocreate = Trash autocreate2 = Sent autosubscribe = Trash autosubscribe2 = Sent mail_replica = remote:vmail@some-mx2.com } protocols = imap lmtp sieve service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl = required ssl_cert = </etc/ssl/certs/some-mx.pem ssl_key = </etc/ssl/private/some-mx.key userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = " autocreate" } protocol lmtp { hostname = some-mx.com mail_plugins = sieve postmaster_address = postmaster(a)some-mx.com } cat dovecot-sql.conf driver = pgsql connect = host=/var/run/postgresql/ dbname=mail user=mailreader default_pass_scheme = SHA512 password_query = SELECT email as user, password, '/home/mailboxes/maildir/'||maildir as userdb_home, 500 as userdb_uid, 500 as userdb_gid FROM users WHERE email = '%u' user_query = SELECT '/home/mailboxes/maildir/'||maildir as home, 500 as uid, 500 as gid FROM users WHERE email = '%u'; Any help will be appreciated! thanks, __ Zbyszek

1 2

[Dovecot] RFC 5267 Contexts for IMAP4 PARTIAL results
by Anders Thøgersen 11 Feb '14

11 Feb '14

Hello, I am looking at PARTIAL responses using a dovecot version 2.2.5 and am running into an inconsistency with the RFC which I would like to ask about. The following section http://tools.ietf.org/html/rfc5267#section-4.4 lists client requests and server responses which I have tried running against a folder, specifying the ranges that fit the contents of the folder I have selected. The Last of the listed client requests returns a response that is not as I would expect: C: A04 UID SEARCH RETURN (PARTIAL 24000:24500) UNDELETED UNKEYWORD $Junk should return S: * ESEARCH (TAG "A04") UID PARTIAL (24000:24500 NIL) // No results are present, this is beyond the end of the results. S: A04 OK Completed. according to the RFC, but instead of NIL in the PARTIAL result I see the full range of UIDs that are in the folder, as in: C: A02 UID SEARCH RETURN (PARTIAL 23500:24000) UNDELETED S: * ESEARCH (TAG "A02") UID PARTIAL (23500:24000 1:9) S: A02 OK Search completed (0.000 secs). The folder that is selected contains 9 emails with the UIDs 1-9. Should the server return NIL Instead of returning 1:9? Thanks! Anders

2 2

[Dovecot] Undertanding what the lmtp_save_to_detail_mailbox actually does
by Alan Chandler 11 Feb '14

11 Feb '14

Hi I am just learning to setup dovecot as part of a project to move my home mail serving from a large and complex linux computer which is acting as internet router/nat gateway to the internet (this leaving me exposed without internet connection when it goes down) to a raspberry pi - which will be port-forwarded to, when I turn my internet cable modem back into a router/modem. I have chosen to try and do this with a Postfix/Dovecot combination with some key user information coming from an sqlite database. Postfix will use Dovecot for authentication (where needed) and use its lmtp service for local delivery. I have so far got Dovecot working fine for the basic stuff, including using rsync to copy each of my users entire maildir from the old machine to the new to prove that it can be accessed. but I have one last specific piece of functionality I want to achieve that the old system does (and has been doing) for at least 5 years (that is what is still online - I think I have "archived" some older stuff). The existing environment uses a Exim4/Cyrus IMAP combination and with Exim I have managed to develop the rules so that all outgoing mail from my internal clients is copied into a subdirectory of their sent mail folder. The format of the folder is Sent.yyyy.mm where yyyy and mm are computed on the fly from todays date. (the .separator defining a subfolder in the hierarchy) I now have several years of saved messages in my existing system. Postfix has nowhere near the flexibility of Exim to develop rules like that, but I think I could potentially use an sql query on my user database to set up a sender_bcc_map that addressed the result to <sender local part>+Sent.<yyyy>.<mm> (or maybe<senderlocalpart>+Sent/<yyyy>/<mm> and then send that to dovecot. I have then to decide how to handle it. The problem I am facing is I can find no documentation about what lmtp_save_to_detail_mailbox actually causes lmtp to actually do. Searching the wiki refers to it only in the LMTP page. How should the detail of the address be formatted to specify a subdirectory - can it be specified even? Should I be using it? I have seen comments in the past about people recommending using sieve for this sort of thing. and indeed it might be better if I could figure it out, in that 1) I could then send to something more simple like <senderlocalpart>+saveoutgoing and use the "date" extension of sieve to generate the split. 2) Users could ultimately decide what to do them selves with this tag (and I could define a global "after_sieve" to throw it away. Unfortunately my reading of the fileinto extension is that the destination can only be a literal string and not a "computed" value based on the date. UNLESS anyone knows different? I would welcome any advice anyone could give me Thanks Alan Chandler

2 2