similar to: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes

How problematic is it to have default_vsz_limit = 0 in dovecot.conf? macOS+MacPorts had this as a requirement even. Gerben > On 6 Jan 2023, at 16:49, Paul Kudla <paul at scom.ca> wrote: > > > i ran into this as well > > here is the full config for mine with replication > > # cat dovecot.conf > # 2.3.14 (cee3cbc0d): /usr/local/etc/dovecot/dovecot.conf > #

ok a little bit more info .... My servers all run under FreeBSD 12.xx which was also the base for the apple operating system origionally. setting default_vsz_limit = 0 i seem to remember trying with no so great results setting to zero can cause memory over runs (espically with replication) etc i found that when i used the config i sent eariler (vsz_limit is defaulted (not set )) everything

On January 6, 2023 3:56:39 AM GMT+02:00, Gerben Wierda <gerben.wierda at rna.nl> wrote: >One step further in my quest to create a replacement mail server. > >I now have my old mail server (2.3.19.1, macOS + MacPorts) and my new (2.3.20, Alpine Linux, Docker, apk package). When I turn on replication it works, but, after a while I see: > >Jan 06 00:50:31 replicator: Panic: data

I am aware that there are provising for redundant database connections Basically i was working on my main db server (which is also a mail sever) I current have this in the dovecot-pgsql.conf ______________________________________________________________________ driver = pgsql connect = host=localhost port=5433 dbname=scom_billing user=pgsql password=xxxxxxxxx default_pass_scheme = PLAIN

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

On Mac OS X 10.5.2 I run rsync to keep a couple of instances of my / usr/local tree in sync. With Apple's rsync I run (e.g.): sudo /usr/bin/rsync --rsync-path=/usr/bin/rsync -E --progress -avu -- delete --dry-run --exclude=TeXLive-working-copy/ --exclude=context- update/ --exclude=.Spotlight-V100/ --exclude=.fseventsd/ \ -e "ssh -i /Users/gerben/.ssh/id_rsync -l root" \

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

I am new to dovecot administration. I?ve read the Wiki but that hasn?t given me the understanding I need. When I query my LDAP (on macOS) on a value for user ?gerben?, I can get that: dumbledore:~ gerben$ dscl /LDAPv3/127.0.0.1 -read /users/gerben GeneratedUID GeneratedUID: 780D870E-6B00-478E-AB70-3D3307215A82 I would like to use that value in dovecot settings, e.g. something like user_attrs =

I am in the habit of syncing my /usr/local tree over several computers (all Mac OS X). Recently my /usr/local tree has doubled in size, from 300,000 files to 600,000 files because I have added a large subversion checkout (TeX Live). As a result, rsync has become a time hog. Instead of a minute or two or so to calculate what needs to be sent over, suddenly this process takes 18-20 minutes,

> On 22 Oct 2016, at 19:04, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > >> On October 22, 2016 at 7:51 PM Gerben Wierda <gerben.wierda at rna.nl> wrote: >> >> >> Hello folks, >> >> I have an older dovecot 2.0 (which I will migrate to a 2.2 asap, but at this point in time I need a fix). This is a dovecot 2.0 that came with Mac OS X

I am migrating a server. The old one uses dovecot 2.2.30.2 and the new one 2.3.7.1. I don?t want to use any tool that might influence flags on messages. I am using Maildir format on both ends and I have a way to let one server access the data on the other (either using an rsync or a direct access). Could I set up a sync between both to create a smooth migration? Gerben Wierda Chess and the Art

Hello folks, I have an older dovecot 2.0 (which I will migrate to a 2.2 asap, but at this point in time I need a fix). This is a dovecot 2.0 that came with Mac OS X 10.8.5 Server 2.2.5. Today, my spam/virus filtering (clamav) on the Server broke down. As a result, all my meesages got the ***UNCHECKED*** tag added to each subject. That was clearly unacceptable. SO, for the tim ebeing I have set

Suppose my mail_location is: mail_location = maildir:/private/var/mail/nl.rna.mail/%u But I would like to use a simple lookup table to replace %u with another value, say '8DB4E345-9144-4F92-8C9F-9D47BB61CBF8? instead of ?username?. Is there a (simple) way to do this? Gerben Wierda Chess and the Art of Enterprise Architecture <http://enterprisechess.com/> Mastering ArchiMate

A simple question: I?ve installed roundcube on macOS Sierra with Server 5.2 and created a set of sieve rules in my dovecot setup. How can I check their functioning (other than send test mails) e.g. is there some logging I can set / look at? G

I am migrating an old dovecot 2.2.30 (macOS High SIerra, macO S Server) to a new server with dovecot 2.3.7 (macOS Mojave, macports). To get the data over, I?m trying to do a reverse backup with doveadm between an old and a new mail server, but failing to do so. I?m trying (from the new server, the old server is 192.168.2.67): doveadm -Dv \ -o imapc_host=192.168.2.67 \ -o imapc_user=gerben \

I just found out that Ubuntu Linux 22.04 LTS has a dovecot apt package that is 2.3.16. Debian 11 (stable) is at dovecot 2.3.13 with apt. if I looked correctly. Dovecot itself is at 2.3.20. That surprised me (I am new to the Linux distro and package management world) as Ubuntu 22.04 is a Long-Time Support version, and I was expecting packages to be updated as well (as many users will want updated

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

I?m running version 2.1.7 under Raspbian Wheezy (and have been for a number of years). I want to allow one of my other computers to remotely issue doveadm commands to my server but can?t seem to find the right way to add an inet listener to permit this. Using ?doveconf -a? I?ve found the default service definition for doveadm-server. So I copied that and added it to the dovecot configuration with

Paul Kudla skrev den 2023-02-19 16:01: > May I please get some guidance on what to add to talk to another > postgresql server (i have 6 replicated servers so would probably want > a couple worst case issue) change host=localhost to host=some-other-hostname-with-multiple-ips :) then dovecot with timeout and test next server ip there might be more to it, but i think this is how to do it

> Le 13 sept. 2019 ? 09:29, Gerben Wierda via dovecot <dovecot at dovecot.org> a ?crit : > > Nobody? > >> On 10 Sep 2019, at 11:58, Gerben Wierda via dovecot <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> wrote: >> >> I am new to dovecot administration. I?ve read the Wiki but that hasn?t given me the understanding I need. >>