similar to: Static Passdb

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

> On Dec 22, 2015, at 9:49 AM, Dominik Breu <dominik at dominikbreu.de> wrote: > the autoexpunge feature only removes mails wich have the \Delete Flag so no deletion of mails wich doesn't have this Flag(see https://tools.ietf.org/html/rfc4315#section-2.1 or http://wiki2.dovecot.org/Tools/Doveadm/Expunge) > > you could run a cron job with a doveadm move comando to move the

Am 30.10.15 um 11:49 schrieb Teemu Huovila: > > > On 30.10.2015 12:18, G?tz Reinicke - IT Koordinator wrote: >> Hi, >> >> winter is coming and so I start to clean up some left overs of the year. >> >> One thing is to use the yum.dovecot.fi repository. >> >> After installing the current availabel dovecot and dovecot-ee-pigeonhole >> package

Is it possible to run a bash script for authentication where a 0 exit code indicates success and a non-zero is failure? What I'm trying to do is create a shadow IMAP server that authenticates against a different server. That way my server will use the same passwords as an existing server. So what I would need is for dovecot to pass the username and password to my script, I attempt to log

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

On 02.03.2018 09:38, MRob wrote: > On 2018-03-01 22:59, John Woods wrote: >> Hey Everyone, >> >> ??? We are getting a compile error for Dovecot 2.2.34 on Solaris 11.3 >> x86, using Solaris Studio 12.6 compiler, and it doesn't occur with >> Dovecot 2.2.33. >> >>> Making all in charset-alias > > Can someone easily explain what the usage of

Am 30.10.15 um 15:44 schrieb Teemu Huovila: > > > On 30.10.2015 15:35, G?tz Reinicke - IT Koordinator wrote: >> Am 30.10.15 um 11:49 schrieb Teemu Huovila: >>> >>> >>> On 30.10.2015 12:18, G?tz Reinicke - IT Koordinator wrote: >>>> Hi, >>>> >>>> winter is coming and so I start to clean up some left overs of the year.

Hi all, I've had an interesting use case come up which - to cut the story short - one way to solve the problem I am looking at may be to replicate a small number of mailboxes to a third remote server. I've currently had replication running between my main dovecot machine and another remote VM for some time and working well (so I'm not new to replication and I've got a good

On 13.04.2017 15:33, @lbutlr wrote: > On 2017-04-13 (05:27 MDT), Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> >> 4) you can use autoexpunge here, i guess. > > Are messages marked in anyway once they?ve been fetched with pop3 (like marked read?). If so, I could auto-archive them. Yes, they are marked read. See "Flag changes" on

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

hi timo, I checked out the commit causing this. its this one: http://hg.dovecot.org/dovecot-2.2/diff/5e445c659f89/src/auth/auth-request.c#l1.32 if I move this block back as it was. everything is fine diff -r a46620d6e0ff -r 5e445c659f89 src/auth/auth-request.c --- a/src/auth/auth-request.c Tue May 05 13:35:52 2015 +0300 +++ b/src/auth/auth-request.c Tue May 05 14:16:31 2015 +0300 @@ -618,30

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 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

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

> 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,

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 >

Situation: one front-facing server running Dovecot as IMAP/POP3/ ManageSieve proxy, a mixture of IMAP servers (Dovecot, Exchange, ...) in the back-end. Dovecot's passdb does lookups against MySQL which contains a simple user/host mapping, the actual authentication happens on the back-end IMAP servers. The configuration is more or less as described here: