similar to: how to enable debugging in imapc

we have setup a two level proxy configuration for our zimbra server: [ dovecot 2.2.12 (imap proxy mode) ] V [ nginx (imap proxy mode) ] V [ zimbra imap server] and it does not work ... after tying a login, the connection just hangs and ends after 30 seconds with a timeout. - if I try again rightaway in the same dovecot connection, the login goes though without trouble.

Hi List, I have updated my rsync fadvise patch which stops rsync from ousting all your other data from cache when running large jobs. I have also written an article about the whole issue. http://insights.oetiker.ch/linux/fadvise.html cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten http://it.oetiker.ch tobi@oetiker.ch ++41 62 213 9902

Hi List, I am using rsync for hard-link backup. I found that there is a major problem with frequent backup filling up the file system cache with all the data from the files being backed up. The effect is that all the other 'sensible' data in the cache gets thrown out in the process. This is rather unfortunate as the performance of the system becomes very bad after running rsync. Some

Teemu, If just need the http request, I will need something like the following configuration, right? So no meta data plugin, but with notify and push_notification? protocol lmtp { mail_plugins = $mail_plugins notify push_notification } plugin { push_notification_driver = ox:url=http://myurl/ <http://login:pass at node1.domain.tld:8009/preliminary/http-notify/v1/notify> }

On Monday 01 December 2014 03:41 PM, Teemu Huovila wrote: > On 11/30/2014 05:53 AM, AMM wrote: >> __strspn_sse42 (in /lib64/libc-2.14.90.so) > Is it possible that you are encountering this issue? https://bugs.kde.org/show_bug.cgi?id=270925 > Either way, the error seems to stem from your libc implementation (if it is not the valgrind bug). > > If possible, upgrade your

On 04/25/2015 11:55 AM, James wrote: > On 24/04/2015 22:17, Hanno B?ck wrote: > > Hello, > >> I tracked down a tricky bug in dovecot that can cause the imap-login >> and pop3-login processes to crash on handshake failures. >> This can be tested by disabling SSLv3 in the dovecot config >> (ssl_protocols = !SSLv2 !SSLv3) and trying to connect with openssl and

On 04/26/2015 04:07 PM, Florian Pritz wrote: > Since there are three people involved I kindly ask you to be more > specific as to who should provide which (exact) information. > > Given you ask for it right after quoting my link all I can tell you is > that I provide all the information you ask for (openssl version, crash > message) in the link you quoted. Sorry if I was not

Ah fantastic. Now I guess I can use notify plugin without push_notification metadata plugins, right? On 26-10-15 08:36, Teemu Huovila wrote: > > On 26.10.2015 08:59, Frederik Bosch | Genkgo wrote: >> Thanks again. Final question: how do I configure this plugin? > As the only existing driver at the moment is the OX one, the plugin is documented in OX wiki at >

On 7/05/2015 7:49 AM, Timo Sirainen wrote: > On 06 May 2015, at 13:52, Reuben Farrelly <reuben-dovecot at reub.net> wrote: >> >> On 4/05/2015 11:06 PM, Teemu Huovila wrote: >>>> Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs? >>> You can set the userdb to return an empty mail_replica variable for

On 4/05/2015 11:06 PM, Teemu Huovila wrote: >> Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs? > You can set the userdb to return an empty mail_replica variable for users you want to exclude from replication. > http://hg.dovecot.org/dovecot-2.2/rev/c1c67bdc8752 > > br, > Teemu Huovila One last question. Is it

On 18.05.2017 10:55, Tom Sommer wrote: > On 2017-05-18 09:36, Teemu Huovila wrote: >> Hello Tom >> >> On 02.05.2017 11:19, Timo Sirainen wrote: >>> On 2 May 2017, at 10.41, Tom Sommer <mail at tomsommer.dk> wrote: >>>> >>>> (gdb) bt full >>>> #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 >>>>

On 8/05/2015 6:10 PM, Teemu Huovila wrote: > On 05/07/2015 02:32 PM, Reuben Farrelly wrote: >> On 7/05/2015 7:49 AM, Timo Sirainen wrote: >>> On 06 May 2015, at 13:52, Reuben Farrelly >>> <reuben-dovecot at reub.net> wrote: >>>> >>>> On 4/05/2015 11:06 PM, Teemu Huovila wrote: >>>>>> Also is there a way to restrict

I have postfix/dovecot setup on a virtual gentoo server. It's been in service for almost two years without any issues. Now I want to set up a spare server to replicate mails from the one running. I copied the vm files to the second host server, changed the ip, hostname and hosts file for the copy and followed the dovecot replication doc. The last point in the doc tells to rundovecot

* Teemu Huovila <teemu.huovila at dovecot.fi> 2015.08.27 13:58: > Did you specify a value other than zero for 'imap_hibernate_timeout'? Yes I did: $ doveconf imap_hibernate_timeout imap_hibernate_timeout = 1 mins I sometimes see one imap-hibernate process (only one), but several imap processes active which should be idling... -------------- next part -------------- A non-text

On 16/06/15 14:27, lejeczek wrote: > On 16/06/15 14:16, lejeczek wrote: >> On 16/06/15 13:14, B wrote: >>> P, >>> >>> On Tue, Jun 16, 2015 at 01:07:52PM +0100, lejeczek wrote: >>> >>>> I've barely started reading on dsync and I wonder.. >>>> would you know if it is possible to sync/replicate only >>>> specific

Hello, I am currently using Dovecot 2.2.10 on Fedora 16 - 64 bit system I had made v2.2.10 Fedora 16 rpm file using spec file from ATrpms. http://dl.atrpms.net/all/dovecot.spec It has been working well from 6 months or so. Today I tried to make v2.2.15 rpm using same spec file. But "make check" is giving following error: fatal_printf_format_fix

Il 26.10.2015 12:04 Teemu Huovila ha scritto: > On 26.10.2015 12:44, Frederik Bosch | Genkgo wrote: >> Teemu, >> >> If just need the http request, I will need something like the >> following configuration, right? So no meta data plugin, but with >> notify and push_notification? >> >> protocol lmtp { >> mail_plugins = $mail_plugins notify

Is there explicit documentation available for the (probably trivial) configuration needed for Dovecot and Wforce? I'm probably missing something that should be perfectly obvious... Wforce appears to start without errors. I added a file to dovecot's conf.d: 95-policy.conf: auth_policy_server_url = http://localhost:8084/ auth_policy_hash_nonce = this_is_my_super_secret_something

Does Dovecot presently support the MULTISEARCH command, or are there plans to do so? --- Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20200506/eb271fc2/attachment.html>

> On Dec 10, 2014, at 1:42 AM, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 9 Dec 2014, Stephen Lidie wrote: >>> On Dec 9, 2014, at 11:00 AM, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> wrote: >>> On Tue, 9 Dec 2014, Stephen Lidie wrote: >>>>> On Dec 9,