similar to: Dovecot HA

Hello folks, Any plans on implementing the PROXY protocol to allow Dovecot being behind a TCP proxy, and still logging the real IP address of the users ? See : http://blog.haproxy.com/haproxy/proxy-protocol/ Thanks ! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature

On 12/1/2015 10:29 ??, Francisco Wagner C. Freire wrote: > +1 > > On Fri, Jan 9, 2015 at 3:49 PM, Hoggins! <fuckspam at wheres5.com> wrote: > >> Hello folks, >> >> Any plans on implementing the PROXY protocol to allow Dovecot being >> behind a TCP proxy, and still logging the real IP address of the users ? >> See :

Hello, The subject says it all. I have a replica 3 cluster : gluster> volume info thedude ? Volume Name: thedude Type: Replicate Volume ID: bc68dfd3-94e2-4126-b04d-77b51ec6f27e Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: ngluster-1.network.hoggins.fr:/export/brick/thedude Brick2:

Hello list, I'm not sure what to look for here, not sure if what I'm seeing is the actual "backlog" (that we need to make sure is empty while performing a rolling upgrade before going to the next node), how can I tell, while reading this, if it's okay to reboot / upgrade my next node in the pool ? Here is what I do for checking : for i in `gluster volume list`; do

Hello list, I have an issue on my Gluster cluster. It is composed of two data nodes and an arbiter for all my volumes. After having upgraded my bricks to gluster 3.12.9 (Fedora 27), this is what I get : ??? - on node 1, volumes won't start, and glusterd.log shows a lot of : ??? ??? [2018-05-02 09:46:06.267817] W [glusterd-locks.c:843:glusterd_mgmt_v3_unlock]

* Edgar Pettijohn <edgar at pettijohn-web.com>: > Is your goal to have "1" config file? No, that would eliminate the ability to change distro settings via the regular package management. My goal is to add/remove what my service requires via the additional local.conf. p at rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schlei?heimer Stra?e 26/MG,80333 M?nchen

I updated dovecot today and all over a sudden I'm getting: Mar 6 14:40:46 mail postfix/lmtp[3150]: 3kz95y3nX3zCtTS: to=<recipient at backup.invalid>, relay=127.0.0.1[private/dovecot-lmtp], delay=88, delays=87/0.94/0.01/0.01, dsn=4.3.0, status=deferred (host 127.0.0.1[private/dovecot-lmtp] said: 451 4.3.0 <recipient at backup.invalid> Too many concurrent deliveries for user (in

* Edgar Pettijohn <edgar at pettijohn-web.com>: > What distro settings? These files should remain unchanged: ~$ tree /etc/dovecot/ /etc/dovecot/ ??? conf.d ??? ??? 10-auth.conf ??? ??? 10-director.conf ??? ??? 10-logging.conf ??? ??? 10-mail.conf ??? ??? 10-master.conf ??? ??? 10-ssl.conf ??? ??? 10-tcpwrapper.conf ??? ??? 15-lda.conf ??? ??? 15-mailboxes.conf ??? ??? 20-imap.conf ???

Greetings, I'm trying to create a configuration that leaves every config file deployed by an install process or paket management software untouched. The goal is to put every configuration required into /etc/dovecot/local.conf. I've come quite far, but I fail to disable pam as passdb service in local.conf. What I get if I run doveconf -n is this section: passdb { driver = pam } It is

Am 04.09.2018 um 18:27 schrieb Sami Ketola: > > >> On 4 Sep 2018, at 18.38, Robert Schetterer <rs at sys4.de> wrote: >> >> Sorry i migrated terrabytes of mail with imapsync and never had a >> problem, it works as designed, also with maildir rsync did a good job, >> what never worked as it should was dsync ,cause of bugs ,that may >> changed now

Hi, I did some experiments with dovecot on a glusterfs on the active nodes without a director. So I had concurrent access to the files. With the help of the available documentation about NFS and fcntl locks I managed to find out the following: With the plain mbox format dovecot seems to apply and to honor the fcntl locks. But since this format is not used any more in real setups, it is

* Thore B?decker <me at foxxx0.de>: > You might need to quote that last argument, otherwise it can get > interpreted by the shell as globbing, which obviously is not what you > want. > > I've been using wildcard arguments enclosed within '' and "" for > various doveadm commands without issues so far. Right. I had thought so too (and forgot to mention

Hi Timo, using http://wiki2.dovecot.org/Migration/Dsync for migration i am getting this in periods dsync(sys4-test-2 at example.de): Info: INBOX: Couldn't keep all uids dsync(sys4-test-2 at example.de): Warning: Mailbox changes caused a desync. You may want to run dsync again. dsync(sys4-test-2 at example.de): Warning: I/O leak: 0x756547164490 (line 1229, fd 15) dsync(sys4-test-2 at

* Edgar Pettijohn <edgar at pettijohn-web.com>: > > Only /etc/dovecot/local.conf should be changed. > > > So you want the standard files to remain unchanged from default settings and override them with your settings in local.conf? Exactly (he said that in his initial mail). -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schlei?heimer Stra?e 26/MG, 80333 M?nchen

Hi, I have finally managed to implement the Sieve "foreverypart" and "mime" extensions (RFC 5703). These are now included in the main Mercurial repository and will be included in the next release. I will be fixing a few minor details in the coming week; e.g., interaction with "include" and "editheader" extensions needs more work. Still, in the mean time,

Hi, I want to build a system where 6 months old mail to be moved to archive server to keep my mailbox clean and fast. Is there any way to achieve the same using any pre-built binary shipped with dovecot ? Thanks and Regards Joy

Mine also has a list of files that seemingly never heal. They are usually isolated on my arbiter bricks, but not always. I would also like to find an answer for this behavior. -----Original Message----- From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Hoggins! Sent: Tuesday, December 19, 2017 12:26 PM To: gluster-users <gluster-users at

I'm using "/usr/bin/doveadm purge -A" to purge the mdboxes of my users. Unfortunately this command terminates prematurely once it reaches a defective mdbox! Is there a workaround for this? Like using doveadm to get a list of valid users and then run "doveadm purge -u" on each of those? -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669

> On 26 Jan 2016, at 15:56, Marc Schiffbauer <m at sys4.de> wrote: > > * Sami Ketola schrieb am 23.01.16 um 23:27 Uhr: >> >> >> On 23/01/16 15:33, Robert Schetterer wrote: >>> for multiple advanced imap settings at migration you might use >>> imapsync not dsync Best Regards MfG Robert Schetterer >> Sure but imapsync does not preserve

On 24 Apr 2015, at 13:54, Ralf Hildebrandt <r at sys4.de> wrote: > > * Ralf Hildebrandt <r at sys4.de>: >> I don't find "fts_languages" in the documentation... What should I add >> there anbd where? > > fts_languages = de,en > seems to do the trick. But I wonder if there's something like "all" > and what exactly this setting