similar to: PROXY protocol

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 :

Op 19-8-2015 om 16:36 schreef Nikolaos Milas: > 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

Hello everyone, Following my previous message about replication (I'm still stuck), I was wondering in a more general way how to achieve high availability with Dovecot, and how to store the mail data. Do you have some thoughts about this ? Maybe one or two links leading to people who already have ideas or experience ? I don't host a big e-mail service, nor have a lot of clients

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:

+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 : http://blog.haproxy.com/haproxy/proxy-protocol/ > > Thanks ! > >

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]

Op 8/21/2015 om 1:31 PM schreef Nikolaos Milas: > On 20/8/2015 11:09 ??, Nikolaos Milas wrote: > >> As soon as I manage to re-build Dovecot with the latest snapshot, >> I'll test it! > > Hello, > > I've built dovecot with a today snapshot from hg > (dovecot-2-2-9f815e781beb) and I am trying to enable haproxy. > > I configured as follows (lines added

On 20/8/2015 10:35 ??, Tim Groeneveld wrote: > # This is a list of trusted networks... ips are seperated by ", " > # default, empty > haproxy_trusted_networks = 10.1.2.0/24, 10.2.1.0/24 > > # This is the timeout... in seconds. > # default, 3 > # haproxy_timeout = 3 > > # modify your inet listener's to include haproxy=yes > inet_listener { >

https://bugzilla.samba.org/show_bug.cgi?id=14160 Bug ID: 14160 Summary: rsynd in daemon mode should support haproxy proxy protocol Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: core Assignee:

Hey Nikolaos, ---- On Sat, 22 Aug 2015 21:56:17 +1000 Nikolaos Milas<nmilas at noa.gr> wrote ---- > ...and everything seems to be working fine. Obviously, the proxy sends > requests to different ports. For example, requests received by the proxy > at port 993 are sent to dovecot's port 23003 etc. Have you come across any issues after enabling the haproxy on the

On 20/8/2015 11:09 ??, Nikolaos Milas wrote: > As soon as I manage to re-build Dovecot with the latest snapshot, I'll > test it! Hello, I've built dovecot with a today snapshot from hg (dovecot-2-2-9f815e781beb) and I am trying to enable haproxy. I configured as follows (lines added compared to initial config are marked with +): + haproxy_trusted_networks =

On 22/8/2015 10:38 ??, Stephan Bosch wrote: > Why are you putting this in the auth service? That makes no sense. Sorry for my ignorance. > This needs to be put in the services that you want to enable the haproxy > protocol for. For pop and imap those are the login sevices pop3-login > and imap-login. > > ... > > Note that this will prevent normal clients from connecting

On 19/8/2015 5:43 ??, Stephan Bosch wrote: > Well... > > http://hg.dovecot.org/dovecot-2.2/rev/4d7a83ddb644 > > Regards, > > Stephan. That was impressive! Thank you Timo and Stephan. You are superb! I hope you will be able to provide some basic guidelines on how to enable/use the new functionality. (I am not very code-literate.) Looking forward to it! Thanks again!

Hi all, I'm load balancing 4 mysql databases using HAProxy. The setup seems to be working pretty well. Except I keep seeing these messages turning up in syslog: Mar 12 22:11:31 db1 kernel: [6058125.959624] type=1400 audit(1457820691.824:3029129): avc: denied { name_connect } for pid=801 comm="haproxy" dest=7778 scontext=system_u:system_r:haproxy_t:s0

I''ve been having a mess of a time using this module, which stinks because its behavior is EXACTLY what I am looking for... whenever I bootstrap new rabbitMQ nodes I want to add them to our HAProxy instance. Here''s my relevant site.pp entries: node /^rabbit.*/ inherits basenode { @@haproxy::balancermember { $fqdn: listening_service => ''messaging00'',

> btw, what is the reasong for NGINX proxy anyway? Since dovecot proxy can do this for you too. I want to do authentication using the IP that the IMAP client used to connect to the IMAP server. That is, I have 50 IPs, one for each state my users live in, so the users can only connect to the IMAP server using the domain name where their account is hosted (e.g., va.example.com

Even though it seems dovecot (using 2.2.33.1) supports haproxy's send-proxy-v2, it seems to lack send-proxy-v2-ssl (which also sends client's ssl state). It would be a nice feature for the backend server to identify clients so one wouldn't have to use disable_plaintext_auth on a production environment. --- haproxy.cfg frontend pop3 bind [::]:110 v4v6 bind

for more information : https://www.mankier.com/8/haproxy_selinux On Sun, Mar 13, 2016 at 2:05 AM, Alexander Dalloz <ad+lists at uni-x.org> wrote: > Am 12.03.2016 um 23:18 schrieb Tim Dunphy: > >> Hi all, >> >> I'm load balancing 4 mysql databases using HAProxy. The setup seems to be >> working pretty well. Except I keep seeing these messages turning up in

guys, i am trying to install HAproxy infront of my webserver. usually my webserver listens on port 80 and since we have 5 ip address serving 5 different sites on the same physical server the webserver listens to all these ips and proxy the traffic to the relavent app servers. now the problem is if want to loadbalance i should install HAproxy on port 80 and there lies the problem.