- dovecot - dovecot.org

Maybe error in login-common/login-proxy.c/proxy_client_input
by Potapov Sergey 01 Aug '14

01 Aug '14

Hi! It seems that o_stream_cork should be done on proxy->server_output but not on proxy->client_output. o_stream_cork(proxy->client_output); ret2 = o_stream_send(proxy->server_output, buf, ret); o_stream_uncork(proxy->server_output);

2 1

solr_add_definite_query quotes queries
by G H 01 Aug '14

01 Aug '14

So Solr 4.0 and higher supports regular expressions in searching. However, Dovecot is quoting search queries in solr_add_definite_query (via solr_add_str_arg). This breaks regex searching. I do a sample search for emails with "merged" in their body via the query /merg.*/. If you look at the Solr logs, it is sending: q=body:"/merg.*/" which is converted to body:\"/merg.*/\" inside Solr. but if it had sent only: q=body:/merg.*/ then regex would have worked. Is regular expression searching on the dashboard? I'm considering patching fts-backend-solr.c to not quote-enclose the search, but am looking for any better suggestions. Or perhaps not quote-enclose if the search is prefixed with RX: (ie: "RX:/merg.*/")... Thanks, G H

2 1

using flat file for dictionary quota backend
by www-1223 01 Aug '14

01 Aug '14

Hi! I want use flat file for dictionary quota backend, but I didn't find the description of that he has to contain. Somebody can give an example of such file? PS: sorry for my English. Regards, Oleg Ivanov.

1 0

vacation rule addresses
by Héctor Moreno Blanco 01 Aug '14

01 Aug '14

Hello everyone, We have Dovecot 2.1.6 and Pigeonhole 0.3.0. We would like Pigeonhole not to send the vacation response to noreply(a)whatever.com<mailto:noreply@whatever.com>. In this wiki http://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Vacation_auto-reply are showed the different exceptions, but the noreply is not in there. How can I add this address, or another one, to this exception list? Thank you very much in advanced. Kind regards. Héctor Moreno. P Please consider the environment before printing this e-mail. ______________________ This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it. ______________________ Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informacion clasificada por su emisor como confidencial en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion. ______________________

2 1

Re: [PATCH] Fix typo in src/imap-urlauth/imap-urlauth-worker.c
by Jelmer Vernooij 01 Aug '14

01 Aug '14

On Sun, Jul 20, 2014 at 12:50:43AM +0200, Jelmer Vernooij wrote: > The attached trivial patch fixes a typo in src/imap-urlauth/imap-urlauth-worker.c. Ping? > diff -r fd0616d553b0 -r 6fabd9046558 src/imap-urlauth/imap-urlauth-worker.c > --- a/src/imap-urlauth/imap-urlauth-worker.c Fri Jul 11 16:49:35 2014 +0300 > +++ b/src/imap-urlauth/imap-urlauth-worker.c Sun Jul 20 00:29:35 2014 +0200 > @@ -478,7 +478,7 @@ > } > if (client_run_url(client) < 0) { > client_abort(client, > - "Session aborted: Fatal failure while transfering URL"); > + "Session aborted: Fatal failure while transferring URL"); > return 0; > } > }

1 0

Solr 4+ schema.xml?
by G H 31 Jul '14

31 Jul '14

Does anyone have a Solr 4+ compatible schema.xml for dovecot indexing? I am trying to test to see if regex-based FTS searching works through IMAP, but Solr 4.9.0 is throwing an error, "SolrException: undefined field text", on startup with the schema.xml included with Dovecot 2.2.9. Thanks. G H

2 2

Issue with exim and auth protocol
by Mildred Ki'Lya 31 Jul '14

31 Jul '14

Hi, I'm trying to set up exim (4.83) as a submission server, and need to set up the dovecot authentication in exim. I'm having an issue with that (documented at <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756258>) The problem is that exim doesn't follow the handshake as described here: <http://wiki2.dovecot.org/Design/AuthProtocol>. The wiki page says that the client should start the handshake, but exim waits for the server to start and to receive the DONE command until it starts its own handshake. What I actually get is: exim connects to dovecot auth dovecot VERSION 1 1 dovecot SPID 48 And then, dovecot stops (I presume it waits for the client handshake, VERSION and CPID). Exim on its side waits for the DONE. This results in the SMTP connection by exim never replying to the AUTH PLAIN command. This is exim 4.80 (or 4.83) and dovecot 2.1.7. I have another server set up almost exactly the same (but with dovecot 2.1.17) where it does work. In that case, dovecot finishes the handshake before exim starts its handshake. It results in: exim connects to dovecot auth dovecot VERSION 1 1 dovecot MECH PLAIN plaintext dovecot SPID 10905 dovecot CUID 1 dovecot COOKIE d3861d29441f06d962490eab8549fd46 dovecot DONE exim VERSION 1 0 exim CPID 10619 exim AUTH 1 PLAIN service=smtp secured rip=82.247.184.53 lip=80.67.179.36 nologin resp=<base64 encoded string> I don't understand what could change the dovecot behaviour in that regard. Is there a solution that would only require modifying the configuration? Thank you, Mildred

3 6

Die Hütchen-Spiel Mafia wird das nicht gerne sehen. Diese Katze ist Profi!
by Michael Grimm 31 Jul '14

31 Jul '14

http://heftig.co/katze-mit-huetchen/

3 5

▶ Leopard Is Getting Relaxed big cat purrs - YouTube
by Michael Grimm 30 Jul '14

30 Jul '14

Whow! In einer Auffangstation für Wildtiere in den USA laut Spiegel.de http://www.youtube.com/watch?v=4BLoHyeevcU

1 0

dovecot-2-2-pigeonhole-92405f753f6a - 77e6a42bff9b
by Tamsy 30 Jul '14

30 Jul '14

Just a report to Stephan: I tried to compile two builds from the Mercurial: - dovecot-2-2-pigeonhole-92405f753f6a - dovecot-2-2-pigeonhole-77e6a42bff9b Both builds fail to compile with the same following error: ---------------- 8< ---------------- ../../src/lib-sieve-tool/.libs/libsieve-tool.a(sieve-tool.o): In function `sieve_tool_open_output_stream': /usr/local/src/dovecot-2-2-pigeonhole-77e6a42bff9b/src/lib-sieve-tool/sieve-tool.c:518: undefined reference to `o_stream_create_fd_autoclose' ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `i_stream_create_fd_autoclose' collect2: ld returned 1 exit status make[3]: *** [sievec] Error 1 make[3]: Leaving directory `/usr/local/src/dovecot-2-2-pigeonhole-77e6a42bff9b/src/sieve-tools' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot-2-2-pigeonhole-77e6a42bff9b/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot-2-2-pigeonhole-77e6a42bff9b' make: *** [all] Error 2 Server OS: 2 servers, both running on Ubuntu 10.04 32 Bit Rgds Tamsy

4 5