similar to: dsync / doveadm sync problem

Hi Martin, Thanks for the reply. I got the error below, but when I changed the prefix in 4archives to Archive/ I am getting indeed something that is looking ok, I still have to test with a few clients. Why did you call the namespace 4archives? Because it would load before inbox? Or does this not matter at all. Error: namespace configuration error: Duplicate namespace prefix: ""

Hi everyone, I'm hoping I am just missing something obvious - but I cannot seem to get a one-way migration dsync working between two Dovecot servers because the Prefix configuration is different. I am doing a migration from our old Dovecot servers to some new cPanel based ones. Source: 2.2.15 Dest: 2.2.21 Here is the debug output for the sync: doveadm(root): Debug: Loading modules from

Here's a few tips: 1. I assume that's a 2U format -24 bays.?You only have 1 raid card for all 24 disks ? Granted you only have 16, but usually you should assign 1 card per 8 drives. In our standard 2U chassis we have 3 hba's per 8 drives. Your backplane should support that. 2. Add more drives 3. Get a pci nvme ssd card and move the indexes/control/sieve files there.? On Monday,

Hi, this setting might work. The default namespace "inbox" is managing INBOX and defines Special-Use folders on the same hierarchic level as INBOX. There is an extra namespace "4archives" which defines Archive as a mailbox on the same level as INBOX but stored on a different location. Set mailbox attribute auto to your liking. namespace inbox { type = private disabled = no hid

unfortunately after re-installing 2.3.11.3, those broken-pipe errors appear again. (on different, new files) so for sure there is something broken with zlib. I will go back to2.3.10.1 now. attached is the configuration file, though it did not change between 2.3.10.1 and 2.3.11.3 Robert Am 26.08.2020 um 09:42 schrieb Robert Nowotny: > I had 4 broken mdbox files for 4 different users. >

> On 31 December 2018 at 15:47 Marc Roos <M.Roos at f1-outsourcing.eu> wrote: > > > > > >> > >> I can only move messages to a root namespace folder when specifying > >> inbox=yes. That is strange because it is not even the inbox. I don't > > >> even get why it is not by default possible, maybe bug there? > >>

> >> >> I can only move messages to a root namespace folder when specifying >> inbox=yes. That is strange because it is not even the inbox. I don't >> even get why it is not by default possible, maybe bug there? >> > >This makes no sense. inbox=yes namespace means the namespace which has >'INBOX' folder as per RFC. With this

Dne 07.09.2020 v 12:43 Sami Ketola napsal(a): >> On 7. Sep 2020, at 12.38, Miloslav H?la <miloslav.hula at gmail.com> wrote: >> >> Hello, >> >> I sent this into the Linux Kernel Btrfs mailing list and I got reply: "RAID-1 would be preferable" (https://lore.kernel.org/linux-btrfs/7b364356-7041-7d18-bd77-f60e0e2e2112 at lechevalier.se/T/). May I ask you

Hi all! I have two dovecot servers with dsync replication over tcp. Replication works fine except for one user. # doveadm replicator status username priority fast sync full sync success sync failed customer at example.com none 00:00:33 07:03:23 03:22:31 y If i run dsync manually, i get the following error message: dsync-local(customer at example.com): Debug: brain M: -- Mailbox

Hi experts. in the output of imapsync I found: Host2: found quota, presented in raw IMAP Sending: 7 GETQUOTAROOT INBOX Sent 22 bytes Read: * QUOTAROOT INBOX "User quota" * QUOTA "User quota" (STORAGE 420325 1953125) 7 OK Getquotaroot completed (0.001 + 0.000 secs). Host2: Quota current storage is 430412800 bytes. Limit is 2000000000 bytes. So

This is a followup to my thread "Recommended Protocols?". The error message is as follows: dovecot: imap-login: Disconnected: TLS: SSL_read() failed: SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42 I have selected both SSL/TLS and STARTTLS on the Thunderbird side, with identical results. The first question that I have is this. Is there any way to know

Hi, I have a fedora28 system with dovecot-2.3.5 and I'm trying to figure out why I'm increasingly receiving duplicate emails. The message IDs are exactly the same. It's always two of the same messages. I don't think it's ever occurred in the inbox. It doesn't happen with every message or seemingly in every folder. I've read about dovecot deduplicate, but of course I

Hello! I'm using 2 namespaces, "inbox" for INBOX and it's subfolders and "special" containing folders like Sent, Junk or Drafts.??Though both use mdbox I decided to represent those namespaces in different locations "mdbox:~/mail" and "mdbox:~/mail_special_folders". The main reason to use 2 namespaces was to keep special_use folders out of INBOX by

Hi all, I hope it's okay to bump this once after four months. In the meantime we updated to 2.2.26.0 and our problem still persists: After unsubscribing from a shared mailbox, the subscription instantly re-appears. A pcap was attached to my original mail, in case it has something to do with dsync: http://dovecot.org/pipermail/dovecot/2016-September/105419.html Is anyone on this mailing list

DM> Interesting. DM> While I don't use mbox (dbox or maildir) I wouldn't think that would DM> matter. Your namespace layout looks nearly the same as my own. But to DM> verify what's going on - post the output of "doveconf namespace". DM> Possibly just reviewing that output may tell you enough - otherwise DM> share it (fully) here. DM> -- DM>

And I should have seen that from your first post but output from "doveconf" is definitive. -- Daniel On 1/23/2020 6:57 PM, Daniel Miller wrote: > Keeping in mind I'm 0% Dovecot certified and 100% certifiable... > > I'm guessing you have your namespace definition separate from your > special-use mailbox declarations. Possibly in 10-mail.conf and >

Hi, Here is a crash that's happening using the latest Dovecot version (v2.2.27 on CentOS7 x86_64): We are using replication. Judging by the second server's logs, I believe this has something to do with the fact that we're using the lazy_expunge plugin. Every night after midnight, we purge the lazy_expunge namespace by running a command similar to following one on the main server

Hi I understand the crash below is caused by filesystem quota. I just report it because perhaps it could have a more graceful failure. Apr 29 09:39:17 danceny dovecot: dsync-local(jdoe): Error: Mailbox Sent: Saving failed: Not enough disk space Apr 29 09:39:17 danceny syslogd[165]: last message repeated 4 times Apr 29 09:39:17 danceny dovecot: doveadm: Error: dsync-remote(jdoe): Error: Cached

doveadm already supports some nice things, such as being able to remotely launch a doveadm command via TCP socket. It also supports executing a command for all users or to some specific users using a wildcard. dsync could use these features, so I merged dsync and doveadm into same binary for v2.1. I'll still install "dsync" symlink pointing to "doveadm", and running that

Hi -- I'm used to dsync my two mailservers running 2.0.16. Today, I did upgrade one server to 2.1, and doveadm sync is throwing to following error: mail> doveadm sync -f -u test ssh vmail at remote-host.tld dsync -v -f -u test doveadm(test): Fatal: All your namespaces have a location setting. It should be empty (default mail_location) in the namespace to be converted. Same error with