similar to: Migrating from Cyrus to Dovecot

> On 27 Mar 2015, at 10:19, Miloslav H?la <miloslav.hula at gmail.com> wrote: > > Hi, > > we are migrating from Cyrus 2.3.7 to Dovecot 2.2.13. We have ~7000 maildirs with ~500GB. Our goal is to do the migration without users have notice and with the shortest service downtime. The users use IMAP (with shared folders and ACL), POP3 and sieve filters. > > As a first

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 for the comments as from people around the Dovecot? We are using btrfs RAID-10 (/data, 4.7TB) on a physical Supermicro server with Intel(R) Xeon(R) CPU E5-2620 v4 @

I have a folder created in dovecot entered by the user as "??o??" On the file system it appears as "&APEA8Q-o&AOkA6Q-" (mUTF7) When creating a sieve rule, to file into the folder ??o??, I am converting the name from UTF8 into UTF7, the rule becomes require ["fileinto"]; if header :contains ["From"] "user at domain.com" { fileinto

Hi, thank you for your reply. I'll continue inline... Dne 09.09.2020 v 3:15 John Stoffel napsal(a): > Miloslav> Hello, > Miloslav> I sent this into the Linux Kernel Btrfs mailing list and I got reply: > Miloslav> "RAID-1 would be preferable" > Miloslav> (https://lore.kernel.org/linux-btrfs/7b364356-7041-7d18-bd77-f60e0e2e2112 at lechevalier.se/T/). >

Dne 09.09.2020 v 17:52 John Stoffel napsal(a): > Miloslav> There is a one PCIe RAID controller in a chasis. AVAGO > Miloslav> MegaRAID SAS 9361-8i. And 16x SAS 15k drives conneced to > Miloslav> it. Because the controller does not support pass-through for > Miloslav> the drives, we use 16x RAID-0 on controller. So, we get > Miloslav> /dev/sda ... /dev/sdp (roughly) in

Dne 10.09.2020 v 17:40 John Stoffel napsal(a): >>> So why not run the backend storage on the Netapp, and just keep the >>> indexes and such local to the system? I've run Netapps for many years >>> and they work really well. And then you'd get automatic backups using >>> schedule snapshots. >>> >>> Keep the index files local on

Hello, Using cyrus2dovecot (https://github.com/a-schild/cyrus2dovecot) I have migrated some test mailboxes from Cyrus (2.4.17) to Dovecot (2.2.9). The problem I'm having is that the seen status is in cyrus.index files, which cyrus2dovecot doesn't understand. Does anyone use cyrus2dovecot for migrations? If so, how do you deal with seen status when it is stored in the .index files?

I have been attempting to use the cyrus2dovecot script, to no avail. I have many years of content that I want to convert from Cyrus to Dovecot; with the above not working, what are other options out there? Another idea I had is simply set up another IMAP server (using Dovecot) and drag-and-drop and just wait, which I may end up doing. In the above, I copied over my entire /var/imap and

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

Thank you for the reply. I did find imapsync whilst perusing Google. I will give it a shot, it sounds more realistic/reliable. I have a hoard of emails going back to 1999, so I want as few errors as possible :) On 11/7/15 3:31 PM, Philon wrote: > Hi there, > > I was in the same position, but for mutliple accounts. Still you might want to look at imapsync

Hi, we are planning to change hardware for our standalone Dovecot instance handling ~5800 IMAP users with 1TB mailboxes on local RAID. Is there some recommendation about CPU? We can choose from: - Intel Xeon E5-2620v4 - 2,1GHz at 8,0GT 20MB cache, 8core, HT, 85W, LGA2011 - Intel Xeon E5-2623v4 - 2,6GHz at 8,0GT 10MB cache, 4core, HT, 85W, LGA2011 The difference is about more cores vs. hi

Hello, Because it did not work ? In a similar situation, we where forced to use isync/mbsync in imap to imap mode because dsync did not work. It was reported here more than a year ago (May 2014). Time to time, I see the same report from other trying to use dsync to do a migration to dovecot. Dsync is a very appealing and elegant solution to this usage, but it does not always work in real

Hi, No, I tried fetching over imapc too exactly as you suggested. In my case it was not from cyrus, but from CriticalPath. isync was finally able to do the job, preserving flags and doing UIDs mapping. The most boring part was generating proper config file for thousands of accounts. A working imapc/dsync would have been better. Emmanuel. Le 26/11/2015 15:24, Sami Ketola a ?crit : > Hi,

Hi, is there any way, based on userdb/passwdb attribute, how to postpone an email delivery? The purpose is, I need to freeze an account (Maildir++) for a few minutes and new email must not be delivered. But emails must be delivered when account is unfrozen. I found few things about Postfix filters, but I'm not sure it's a good way. Thank you, Milo

Hello, we are running Dovecot (2.2.13-12~deb8u1) on Debian stable. Configured with Mailbox++, IMAP, POP3, LMTPD, Managesieved, ACL. Mailboxes are on local 1.2TB RAID, it's about 5310 accounts. We are slowly getting out of space and we are considering to move Mailboxes onto Netapp disk array with two independent network connections. Are there some pitfalls? Not sure we should use NTP or

Hi. I've made a strange observation. When having Dovecot (at least) with maildir and moving (via IMAP) mail received by some client (Evolution 3.4) into it the following happens: Regardless of whether the mail was originally(!) set with CRLF or LF (i.e. when I use netcat to submit the plain SMTP to the relaying MTA). When the client (Evolution) had received the mail via POP3 before moving

kmail stopped working and when I check the dovecot log file I see: May 4 11:40:38 f12barry dovecot: IMAP(bscott): Corrupted index cache file /home/bscott/Maildir/._NewMail-com/dovecot.index.cache: Corrupted virtual size for uid=234: 633278 != 633251 May 4 11:40:38 f12barry dovecot: IMAP(bscott): Corrupted index cache file /home/bscott/Maildir/._NewMail-com/dovecot.index.cache: Corrupted virtual

Dne 28.8.2015 v 9:56 Steffen Kaiser napsal(a): >> we are using LDAP binding as a passdb, and static with >> allow_all_users=yes as an userdb. >> >> Works fine, but problem is, Maildirs are created for non-existent >> accounts too. We would like to prevent it. >> >> The LDAP binding does not supporta user lookups. Is the correct way to >> use

Hi When I mount CIFS share (mount -t cids) with vers=1.0 I can perform getcifsacl sucessfully. But when I mount with vers=2.0, or 2.1, or 3.0, ACL reading fails. getxattr error: 95 REVISION:0x0 CONTROL:0x0 Why getcifsacl depends on SMB protocol version? Can I read ACL via newer SMB protocol? A asked on Serverfault but without reply:

On Wed, 23 Jan 2019 09:47:11 +0100 Miloslav Hůla via samba <samba at lists.samba.org> wrote: > Dne 2019-01-15 v 13:22 Miloslav Hůla via samba napsal(a): > > When I mount CIFS share (mount -t cids) with vers=1.0 I can perform > > getcifsacl sucessfully. But when I mount with vers=2.0, or 2.1, or > > 3.0, ACL reading fails. > > > > getxattr error: 95 >