similar to: Dovecot Director behaviour when two or more fail

Hi, I am curious if Dovecot can add an empty file into a Maildir folder as soon as a mailbox has exceeded 100% capacity, and later when it detects the quota has fallen below 100% unlink the file. The idea is the Dovecot LDA would deliver the message and if this caused the mailbox to reach 100%+, add a file into the maibox say "username/Maildir/overquota". Interactions via Dovecot

Hi all, I have observed with my Dovecot setup that unique failed logins cause legitimate correct logins to be slowed. I am running two servers, each with two Dovecot instances, a Proxy with Director, and a backend Dovecot. I suspect that the backend instance is throttling connections from the same IP, and because I am running a Proxy, the backend will only see either of the two server IPs. I

Hello, I have some Data, that I analyse using a regression tree (by using rpart). Now I would like to save this tree to a file for later use, and load it (not necessarily in the same workspace). It would be most preferrable, if I could just save some parameters (later probably to a database) and load them again to reform the tree. Is this possible? And if yes, how? Thanks in advance

Hi there, I am working on a project which needs the value of the interaction area under two distributions( eatimated by kernel density estimators). For example: x<-rnorm(100,0,1) y<-rnorm(100,0.2,1) density(x) # This produces the summary of dependent variable and independent variable. How can I get the individual values of variables and reform a curve to calculate the area under

Hi, I have a director farm running in front of dovecot pop/imap servers. For a reason, one of my backend servers have been down, so poolmon disables it in director servers and users corresponding to it has been sent to other servers. Until this, no problem. Now my failed backend server is up again, and I want to redirect all of its users to it, without waiting for it director sessions to

Something I noticed on a 2.1.7 director test cluster (two directors, three backends): 'doveadm proxy kick user' will kick all connections for that user on that director only. Any additional connections on other directors will remain active unless the command is run on all directors. Are the proxy and director sub-commands intended to be separate and distinct in their operation? If so,

I have data in a file named hands.dat, which is given at the end of this question. (It's from a stats textbook example on anova). I'd like to do an aov on this, which I guess would be d <- read.table("~/hands.dat", header=TRUE) aov(Bacterial.Counts ~ Water + Soap + Antibacterial.Soap + Alcohol.Spray, data=d) but this fails. Do I need to break d$Method up into columns for

In playing with dovecot director, a couple of things came up, one related to the other: 1) Is there an effective maximum of directors that shouldn't be exceeded? That is, even if technically possible, that I shouldn't go over? Since we're 100% NFS, we've scaled servers horizontally quite a bit. At this point, we've got servers operating as MTAs, servers doing IMAP/POP

On 12/1/2012 10:02 AM, James Molloy wrote: > > I'm proposing a new function attribute, "noclone", with the semantics that "calls to functions marked "noclone" cannot be cloned or duplicated into the same function.". That is, it is illegal to call J = I->clone() then attach J to the same basic block as I if I is marked "noclone". The class Loop

On 15 May 2018, at 12.06, Timo Sirainen <tss at iki.fi> wrote: > > If you look at .176's error log, do you see an error about "director_consistent_hashing settings differ between directors"? Have you set director_consistent_hashing=yes in the old directors? That is needed now, because the old non-consistent-hashing method is obsoleted. Unfortunately there's no easy

Hi all, anyone having any problems with restarting the director? Every time I bring down 1 of the director servers, reboot it, or just restart it for whatever reason, im seeing all kinds of problems. Dovecot generally always gives me this error: Jan 20 22:49:55 imapdirector3 dovecot: director: Error: Director 194.109.26.173:444/right disconnected before handshake finished It seems the directors

On Thu, Feb 23, 2017 at 3:15 PM, Timo Sirainen <tss at iki.fi> wrote: > On 24 Feb 2017, at 0.08, Mark Moseley <moseleymark at gmail.com> wrote: > > > > As someone who is about to begin the process of moving from maildir to > > mdbox on NFS (and therefore just about to start the 'director-ization' of > > everything) for ~6.5m mailboxes, I'm

I noticed 2 minor things with the director. 1) if I start 2 directors, but in 1 of them I dont add the other as a director_servers, they both start spamming the logfiles really really fast. It seems there is no backoff mechanism in the protocol between directors. 2) user mail server ip expire time cor 194.109.26.171 2010-09-02 14:32:13

Hi all, simple Q: how do I extract the upper and lower CI for predicted probabilities directly for a glm - I'm sure there's a one line to do it but I can't find it. the predicted values I get with the predict (.. "response") Thanks Gerard ********************************************************************************** The information transmitted is intended only for

Hello dovecot! I administer a dovecot installation with 30k users. I've got 4 dovecot directors as frontend and 10 backends. The mailbox are now in maildir format, with maildir++ quota, on a shared netapp filer. Indexes are local on each backend. I'm reconfiguring the quota plugin: as a first step, I want to use the clone plugin to keep a copy of the quota on a redis database. Next,

I'm working the kinks of a new director based setup for the eventual migration away from courier. At this point, with everything basically working I'm trying to ensure that things are properly monitored and I've run into an issue. There doesn't appear to be a way to get dovecot to tell if it is (or is not) connected and properly synced with the other director servers in the ring

I'm trying to configure a doveadm service that will proxy trough our directors, following the recipie at: http://wiki2.dovecot.org/Director#Doveadm_server So on the backends I have: service doveadm { inet_listener { port = 24245 address = * } } doveadm_proxy_port = 24245 local 192.168.42.0/24 { doveadm_password = suPerSeecret } I assume the "local"

I have Samba 3.0.33-3.28.el5 running on a CentOS 5.5 server. The samba server is added as a Member server of our Windows 2003 AD, and winbind is working OK. I have a question about the assigning of permissions via the Windows XP file/folder properties dialog. My background is mainly in Windows, but I do grasp the concept of UNIX file permissions. When I attempt to modify the permissions on

In our experience. A ring with more of 4 servers is bad, we have sync problems everyone. Using 4 or less works perfect. Em 24 de fev de 2017 4:30 PM, "Mark Moseley" <moseleymark at gmail.com> escreveu: > > > > On Thu, Feb 23, 2017 at 3:15 PM, Timo Sirainen <tss at iki.fi> wrote: > > > >> On 24 Feb 2017, at 0.08, Mark Moseley <moseleymark at

Hello, using Dovecot 2.2.9 and a setup with directors and backends. The communication between directors and backends needs to be TLS secured. The director config contains a list of hostnames for the backends. (implicit list because of multiple A/AAAA records for a single hostname or explicit list of several host names) On connection setup from a client the director connects to the selected