Re: Dovecot's default password storage scheme is not GDPR compliant

2025-02-10 Thread Kent Borg via dovecot
On 2/10/25 5:07 AM, Robert Nowotny via dovecot wrote: A default dovecot (el9 rpm) install is compliant as it does not work and does not do anything, it is just a bunch of binaries on a disk. and how exactly this answer is useful ? oh my, I am feeding the troll again I see it as a useful

Re: Different Replicator Crash??

2025-02-09 Thread Kent Borg via dovecot
On 2/3/25 8:19 PM, Dmitry Melekhov via dovecot wrote: Are you sure you patched both sides? No, did not patch the far side, just the side where I configured the replicator to run. (Can the replicator run on both sides? Do they play nicely if both replicating to the other?) Yes, it can run

Re: Replicator Crash

2025-02-05 Thread Kent Borg via dovecot
On 1/28/25 11:53 AM, Aki Tuomi wrote: It's maybe https://github.com/dovecot/core/commit/d3a097075afb7b5d8955978ed4a2ae99add11f88.patch That was still giving me occasional crashes. This seems to not crash, but I don't know that it is sensible: --- a/src/replication/replicator/replicator-queu

Re: Different Replicator Crash??

2025-02-03 Thread Kent Borg via dovecot
On 2/2/25 8:00 PM, Dmitry Melekhov via dovecot wrote: After adding patch you mentioned I no longer have replicatior out of memory.  The syncing now appears to work correct and I *mostly* don't get the error. I used to get the error I think with ever sync. This new error? I didn't know it was

Different Replicator Crash??

2025-01-31 Thread Kent Borg via dovecot
I added the suggested "count--" and recompiled, and it now appears to work, the replication goes both ways, eyeballing the e-mail on the two servers they look the same. Good. But part of the time I am still getting what looks very much like the same crash, is there another "count--" I need to

Different Replicator Crash??

2025-01-31 Thread Kent Borg via dovecot
I added the suggested "count--" and recompiled, and it now appears to work, the replication goes both ways, eyeballing the e-mail on the two servers they look the same. Good. But part of the time I am still getting what looks very much like the same crash, is there another "count--" I need to

Replication Question: Who Initiates?

2025-01-30 Thread Kent Borg via dovecot
As I understand it, if I am doing replication between a pair of servers, I run the replicator on just one and it makes all the two way changes necessary to make the two machines match. But this only happens when some change happens on that machine that runs the replicator. First, is this corre

"Modseq 34839 no longer in transaction log"

2025-01-29 Thread Kent Borg via dovecot
My new custom-built .deb packages seem to work, or at least work better! When new e-mails come in, it quickly attempts a sync, but says it fails: Jan 29 10:31:49 la dovecot[1199]: doveadm: Error: doveadm(kentborg)<2465>: Warning: Failed to do incremental sync for mai\ lbox INBOX, retry with a

Re: Replicator Crash

2025-01-28 Thread Kent Borg via dovecot
On 1/28/25 11:53 AM, Aki Tuomi wrote: It's maybe https://github.com/dovecot/core/commit/d3a097075afb7b5d8955978ed4a2ae99add11f88.patch Oh, fun. Time to figure out how to build a .deb! And…it's not that bad. The correct way to clear the cruft to build subsequent times wasn't immediately obviou

Replicator Crash

2025-01-28 Thread Kent Borg via dovecot
I have replicator working well enough…to crash: Jan 28 11:26:12 la dovecot[1187]: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes Jan 28 11:26:12 la dovecot[1187]: replicator: Error: Raw backtrace: #0 t_askpass[0x7fa59db0c0] -> #1 backtrace_append[0x7fa59db374] -> #

Re: newbie dsync problems

2025-01-25 Thread Kent Borg via dovecot
So trying to debug replication via getting manual "doveadmin sync" hasn't gotten me there, Any suggests on how to debug the replication approach? Would it be helpful to post the "/etc/dovecot/conf.d/backup.conf.ext" I created? Thanks, -kb On 1/23/25 10:50 AM, Kent Borg wrote: I have a ver

Re: newbie dsync problems

2025-01-23 Thread Kent Borg via dovecot
On 1/23/25 2:44 PM, Doug via dovecot wrote: I don't have a working example because I do my dsync backups on the local machine with output to shared NFS storage that is accessible to both my primary and backup systems. No ssh required or remote connection required. That is provided by NFS. A

Re: newbie dsync problems

2025-01-23 Thread Kent Borg via dovecot
On 1/23/25 1:41 PM, cdm...@yahoo.com wrote: In your working example you are connecting as root but in your dsync example your user is remoteprefix:root. Try removing the "remoteprefix:" which is being treated as part of the user name. If I take off the "remoteprefix" it logs in, but it does

Re: newbie dsync problems

2025-01-23 Thread Kent Borg via dovecot
On 1/23/25 12:26 PM, cdm...@yahoo.com wrote: Kent, You are being prompted for a password, so it isn't using private key authentication. I recommend you get ssh working first, prove you are indeed connecting to your secondary server, and only then introduce doveadm. Yes, I checked that: I t

Re: newbie dsync problems

2025-01-23 Thread Kent Borg via dovecot
I had a typo (I said I'm a newbie). On 1/23/25 10:50 AM, Kent Borg via dovecot wrote: But when I try to make the command more complete and send a username to the remote end, and now I am no longer talking to the remote end: root@la:/etc/dovecot# doveadm sync  -u kentborg -1 ssh -i /root

newbie dsync problems

2025-01-23 Thread Kent Borg via dovecot
I have a very basic postfix/dovecot server, with just a few users, and it works. But in the past I have had hardware failures…so I would like use dsync to a nearly matching server for some extra safety, and I have not yet been successful. I am trying to do this as root over ssh, with a private