similar to: Dovecot Replication Errors (only) when using tcps: as the mail_replica Protocol

Displaying 20 results from an estimated 1000 matches similar to: "Dovecot Replication Errors (only) when using tcps: as the mail_replica Protocol"

2020 Nov 18
0
Dovecot Replication Errors (only) when using tcps: as the mail_replica Protocol
Hello, I have two mail servers and am also experiencing sporadic replication errors over tcps, similar to Reuben. Each server is running Dovecot 2.3.11.3 (502c39af9) on Debian 10.6. *Log entries from MX1* Nov 18 00:39:26 mx1 dovecot: dsync-local(user at example.com)<Ow3zAjWxtF+TDgAAPHKnuQ>: Error: dsync(mx2.example.com): I/O has stalled, no activity for 600 seconds (last sent=mailbox,
2023 Jan 15
1
dovecot replication - new and cur folders on mx1 and mx2
Hello, I have a question in regards to specific dovecot replication behaviour and I'm just wondering if this is actually an expected/normal behaviour, or just a version issue. I'm using dovecot 2.3.16 which is packed by default with latest Ubuntu 22.04.1 LTS server release. I setup dovecot replication pair (mx1 - mx2) which is working ok. MX1 has priority 10, MX2 has priority 20. I
2023 Jan 17
1
dovecot replication - new and cur folders on mx1 and mx2
I can confirm this in a slightly different setting, but still using two-way sync between two dovecots. On e is 2.3.19.1 running on macOS Monterey, the other is 2.3.20 running in an alpine container on Ubuntu. Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>) R&A IT Strategy <https://ea.rna.nl/> (main site) Book: Chess and the Art of Enterprise?Architecture
2023 Jan 17
1
dovecot replication - new and cur folders on mx1 and mx2
It might have a noticeable effect on clients. I encountered (probably triggered by this in some way?) that I was unable to het the 'read' bit set in macOS Mail.app. Maybe (as I am doing HA with round robin) the Mail.app client got to one dovecot repository on one tcp connection and then on the other. Is there a reason why syncing tis move from new to cur is a bad idea? Gerben Wierda
2018 May 06
3
2.3.1 Replication is throwing scary errors
Ah yes. The hash I put below is wrong but the commit message I quoted was right. This is the last known working good commit, which was on Mar 6: https://github.com/dovecot/core/commit/ff5d02182573b1d4306c2a8c36605c98f217ef3b "doveadm: Unref header search context after use Fixes memory leak, found by valgrind" I've subsequently been able to determine that the bad commit was one of
2018 May 06
2
2.3.1 Replication is throwing scary errors
Hi Andy, Funny you say that - I've been testing this very problem for some time today to narrow down the commits where I think the problem started occurring. So far I have been able to roll forward to commit from git: 74ef8506dcb946acc42722683e49fdcb964eed19 >> "doveadm: Unref header search context after use" . So far I have been running on that code for a few hours
2018 May 08
2
replicator: User listing returned failure
> I don't know if it makes a difference, I don't have quotes on my > mail_plugins: I don't have quotes too (It's difference between config file and dovecot -n output) > Did you check permissons on the replication fifos? For what? I think that problems on slave. How it should work in automatic mode? I repeat that from slave manually all works fine: >> As I
2005 Oct 25
8
Load balancing email?
Currently, we have two mail relays for inbound messages, and a third for POP. The inbound messages go thru all the CPU-intensive anti-spam stuff, and then they relay it to the POP server for pickup. Currently, one of these is the "primary", and the other is "secondary", and I'd like them to be considered more or less as equals, since the "primary" system is
2018 May 08
2
replicator: User listing returned failure
Hello Gerald, > Besides you have configured mysql userdb twice: > >> userdb { >> args = /etc/dovecot/dovecot-sql-master.conf.ext >> driver = sql >> } >> userdb { >> args = /etc/dovecot/dovecot-sql.conf.ext >> driver = sql >> } Great!!! This was the root cause. Second userdb with dovecot-sql-master.conf rewrite the first one, but
2018 May 06
1
2.3.1 Replication is throwing scary errors
Hi all, New to the mailing lists but have joined up because of above */2.3.1 Replication is throwing scary errors /*Brief system configuration ??? MX1 - Main ??? ??? Freebsd 11.1-Release-p9 ??? ??? Hosted on a Vultr VM in Sydney AU ??? ??? MTA = Postfix 3.4-20180401 ??? ??? Dovecot = 2.3.1 ??? ??? File system = ufs ??? MX2 - Backup ??? ??? Freebsd 11.1-Release-p9 ??? ???? Running on
2012 Mar 20
2
Dsync Dovecot
Hi guys, I am using dovecot-2.1.0 in centos 5.7, I configured dovecot with postfix in 2 system both system is having same configuration and os. I want to use dsync in mirror mode via ssh but I am not able to do it. When I followed the dsync wiki then I an unable to find the username : *dsync -u username mirror ssh -i id_dsa.dovecot mailuser at example.com dsync -u username* In the above
2012 Mar 13
2
problems with SSH-based clustering dovecot 2.1.1
Hello, I'm using dovecot 2.1.1 with vpopmail 5.4.30 with multiples domains and I have problems setting up synchronization in between multiple computers. All act like master (my clients can connect to any of the them and read their emails either via POP3 either via IMAP, inbound email gets on any of the machines). Each machine is on a different continent, there is no shared drive in between
2018 May 07
2
replicator: User listing returned failure
Hello. I've tried to configure TCP replication to slave server. But I got some errors... mx1:~# dovecot --version 2.2.27 (c0f36b0) From dovecot.log: May 07 19:27:41 auth-worker(34348): Warning: mysql: Query failed, retrying: Unknown column 'username' in 'field list' May 07 19:27:41 auth-worker(34348): Debug: sql(*): SELECT username, domain FROM users May 07 19:27:41
2012 Mar 04
4
dsync replication available for testing
In dovecot-2.1 hg you can now test dsync-based replication. Everything isn't finished yet, but it appears to work and I've enabled it for my @dovecot.fi mails. Some issues: - public namespace isn't replicated at all - shared namespace is replicated, but not private mail flags - I've only tested SSH replication setup now, not director replication setup (and director setup
2005 Mar 24
1
Robust multivariate regression with rlm
Dear Group, I am having trouble with using rlm on multivariate data sets. When I call rlm I get Error in lm.wfit(x, y, w, method = "qr") : incompatible dimensions lm on the same data sets seem to work well (see code example). Am I doing something wrong? I have already browsed through the forums and google but could not find any related discussions. I use Windows XP and R
2009 Nov 05
3
Bhattacharyya distance metric
I need to use the Bhattacharyya distance metric to determine population separation. Has anyone written a Bhattacharyya distance metric function in R? -- View this message in context: http://old.nabble.com/Bhattacharyya-distance-metric-tp26221259p26221259.html Sent from the R help mailing list archive at Nabble.com.
2018 May 06
0
2.3.1 Replication is throwing scary errors
Hi Reuben, thank you for digging into this issue reported by some users, now. I wonder if there are users out there using master/master replication with 2.3.1 dovecot that do *NOT* observe the errors mentioned in this thread? Please report, please. And, pleas have a closer look for It would be interesting to know if these failures are seen by a subset of users, only. And please have a look
2004 Apr 06
4
SYN attacks
Heya, FREEBSD 4.9-STABLE Is there anyway to block SYN attacks and prevent it from bring down my server? Its been attacking for sometime.
2017 Oct 12
2
SSL overview...
Can someone help me understand the overall picture of SSL certificates in this scenario? I have a working dovecot/postfix/mysql server. It has a certificate. I now want to create a second, essentially duplicate configured server for use with replication. What is the relationship between the certificate and the hostname, or the DNS entry since the certs are created using the server?s domain
2018 May 06
0
2.3.1 Replication is throwing scary errors
Seems you got the hash wrong... You probably mean 4a1e2e8e85ad5d4ab43496a5f3cd6b7ff6ac5955, which fixes a memory leak, but does not release sync lock. Interesting if this commit fixes the issue. Looking at the sync code, where the lock is made / released, there is only one commit recently, which is 8077d714e11388a294f1583e706152396972acce and that one creates home directory if missing. Would