[POLL] Cyrus ACLs and group names

For those of you using Cyrus with group ACLs, how are your groups named? I know with the auth_unix backend, they are 'group:'. What I've seen from CMU's groups is that they are of the form ':'. What I want to know is - do group names always contain a colon? If so it will make implementing

Re: cyrus-imapd-2.4 branch, segfault in lmtpd

Are you able to get a backtrace on the segfaulting processes? Thanks, Bron. On Wed, Dec 16, 2015, at 04:00, Sergey via Info-cyrus wrote: > Hello. > > I attempted to use last cyrus-imapd-2.4 branch and got error: > > kernel: [8211701.360899] lmtpd[20104]: segfault at 1 ip b717f3fc sp bfd1d8e0

Re: Ongoing inaccessible mailbox woes

It smells like maybe you have improved_mboxlist_sort set to the wrong value (off), and hence it's unable to see the mailbox at all! This is really bogus of the way that mailboxes are stored, and I have master plans of fixing it better... *sigh* Bron. On Sat, Dec 26, 2015, at 02:47, Patrick

Re: Archiving old email?

On Sun, Dec 27, 2015, at 04:22, Patrick Goetz via Info-cyrus wrote: > I have some users whose mail folders are approaching 2GB in size. > Unfortunately they can't delete any of this mail, but that doesn't mean > that it needs to be lugged around, indexed, and copied to local mail > caches as

Re: Ongoing inaccessible mailbox woes

On Sun, Dec 27, 2015, at 01:14, Patrick Goetz via Info-cyrus wrote: > Hi Bron - > >[root@www cyrus]# pwd >/etc/cyrus >[root@www cyrus]# grep improved_mboxlist_sort imapd.conf >improved_mboxlist_sort: yes > > But in any case, it is seeing the mailbox. The "Archives Staff" mailbox

Re: Weird Characters in unexpunge

It's dumping the raw literal data from the file. I have no idea why we're storing a literal in there, given that it's already a length-delimited record. We've seen the same bug at FastMail in our search system for a while until I patched it to parse a literal out of the cache. It would be

Re: determine whan the mailbox was last accessed

You'd be looking for the "recenttime" field in the mailbox. Interestingly, it appears you can get it via the 'fud' daemon, but it's not exposed via an annotation. If you create a bug in bugzilla (or phabricator) to remind us... it's probably not too hard to create an annotation that you can read

Re: Archiving old email?

On Mon, Dec 28, 2015, at 02:28, Patrick Goetz via Info-cyrus wrote: > On 12/26/2015 04:44 PM, Bron Gondwana via Info-cyrus wrote: > > > > Each mailbox can have its storage split between two drives - one that's > > high speed with recent mail, and slower speed dr

Retrospective on this year in the Cyrus Project

For those of you not following FastMail's Advent calendar (shame on you, surely you don't have anything better to do), I posted this today: https://blog.fastmail.com/2015/12/22/the-year-of-the-cyrus-foundation/ For all that we haven't done another beta release for ages (mainly because putting

Re: [cyrus 3.0] 20 delayed mailbox deleted limit?

On Thu, Jun 9, 2016, at 03:02, Andre Felipe Machado via Info-cyrus wrote: > Hello, > At future release notes I read > "Under delete_mode: delayed, only the 20 most recently deleted mailboxes are > kept for any given name." > https://cyrusimap.org/imap/release-notes/3.0/x/3.0.0-beta2.html > Is

Re: Cyrus and scale-out

Funny you should ask :) http://asg.andrew.cmu.edu/archive/message.php?mailbox=archive.cyrus-devel=4939 I definitely have plans of allowing everything to be written back in a reliable way so that losing an IMAP server is guaranteed(within the bounds of software reliability and all the parts

Re: [cyrus 3.0] 20 delayed mailbox deleted limit?

On Fri, Jun 10, 2016, at 04:38, Jason L Tibbitts III wrote: > >>>>> "BG" == Bron Gondwana via Info-cyrus <info-cyrus@lists.andrew.cmu.edu> > >>>>> writes: > > BG> How would you suggest we protect against exploiting delayed delete &g

Re: [cyrus 3.0] 20 delayed mailbox deleted limit?

On Fri, Jun 10, 2016, at 09:41, Jason L Tibbitts III wrote: > > "BG" == Bron Gondwana writes: > > BG> Just to be really clear what this is. It's per mailbox name - if > BG> you create and delete the SAME mailbox more 20 times, it only keeps > BG> the most recent 20 of

git.cyrus.foundation deprecated

Hi all, Phabricator is being deprecated. The project is moving to github at: https://github.com/cyrusimap/ I'm working on migrating all the bugs from bugzilla and phabricator to be github issues. For now the website is still hosted at CMU. One thing I'm doing is applying a "kill commit" to

cyrusimap.org website updated

Hi Everyone, Thanks to the awesome work by Nic, Nicola and others, the cyrusimap.org website is now entirely generated from Sphinx (not the same sphinx as the search engine - yay for namespaces) from the git repository which is currently at: https://git.cyrus.foundation/diffusion/D/ Feel free

Re: Sieve for shared mailboxes

We don't use shared mailboxes or non-user sieve at all at FastMail, so it gets less testing than most things. I'd love to have contributions of good test cases to Cassandane from someone who knows exactly how this should work so we can make sieve good for the shared case too. It's somewhat

Re: Replication CRC error

Master has: commit 6ef874319ecd98700e682ef30fcad5245ddfdb32 Author: Bron Gondwana Date:   Wed Oct 22 14:51:24 2014 -0400 sync_client: do ALL mailboxes, not just all users, for -A flag It should be pretty cherry-pickable back to 2.5 I would imagine. Bron. On Thu, Mar 3,

Re: IPv6

Ellie, can you please fix the listen statement to accept correctly bracketed ipv6 and backport to at least 2.5 and 2.4, shouldn't be many changes in that code. Nicola, can you check that we document how it's working now, and of course the fixed version :) Bron (on phone in bush somewhere) On

Re: ACL inheritance in Shared Namespace

Ack. It still works like this On Thu, Apr 14, 2016, at 03:51, Ken Murchison via Info-cyrus wrote: > Unless someone other than me changed the code, ACL inheritance only > applies to mailbox creation. Once a mailbox exists, its ACL is > independent of all others. > > > On 04/13/2016 12:27 PM,

Re: Shared folder, COPY, OK, message nowhere to be seen

Version? On Fri, Apr 22, 2016, at 21:47, Janne Peltonen via Info-cyrus wrote: > Hi! > > I've always thought that IMAP COPY should only say OK once the message file is > safely on the disk. So that it should block, should another imapd process be > holding a write lock to the folder. > > Now

Re: Shared folder, COPY, OK, message nowhere to be seen

2016 at 05:43:11PM +0300, Janne Peltonen via Info-cyrus > > > wrote: > > > > Hi! > > > > > > > > Oh. Sorry. I thought I'd forgot something important, must be the fact > > > > it's > > > > Friday night. > > > > > > > > 2.4

Re: Shared folder, COPY, OK, message nowhere to be seen

--Janne > > > > On Fri, Apr 22, 2016 at 11:27:40PM +1000, Bron Gondwana via Info-cyrus > > wrote: > > > Version? > > > > > > On Fri, Apr 22, 2016, at 21:47, Janne Peltonen via Info-cyrus wrote: > > > > Hi! > > > > > > >

Re: altnamespace doesn't seem to be working in 2.4.17

Is your user listed in admins in imapd.conf? Admin users never get alt namespace. On Sat, Apr 30, 2016, at 23:23, Brian J. Murrell via Info-cyrus wrote: > In 2.4.17 of Cyrus IMAPD I have the following /etc/imapd.conf: > > configdirectory: /var/lib/imap > partition-default: /var/spool/imap >

Re: altnamespace doesn't seem to be working in 2.4.17

Indeed, never use a user listed in admins as your actual email account. It has weird behavior around inbox itself too. On Sun, May 1, 2016, at 16:23, Bron Gondwana wrote: > Is your user listed in admins in imapd.conf? Admin users never get alt > namespace. > > On Sat, Apr 30, 2016, at 23:23,

Re: mailboxes.db invalid entries

The tool is safe to use with Cyrus running Of course if you delete a mailboxes db entry without deleting the underlying files and then recreate the folder, things can get confused because there are already files on disk... Bron On Sat, Apr 23, 2016, at 06:58, Jan Kowalsky via Info-cyrus

Re: mailboxes.db invalid entries

Ouch, yeah - spaces in group names? That's gotta be bogus. I'm surprised we accept those in the first place. I guess the code should probably check that keys are valid identifiers though :( So that is a legitimate bug. Bron. On Fri, Apr 22, 2016, at 09:28, Jan Kowalsky via Info-cyrus

Re: sieve runtime error Fileinto: Permission denied

On Tue, May 24, 2016, at 10:44, OBATA Akio via Info-cyrus wrote: > On Tue, 24 May 2016 07:25:42 +0900, Bron Gondwana via Info-cyrus > <info-cyrus@lists.andrew.cmu.edu> wrote: > > > On Mon, May 23, 2016, at 22:47, Sundeep Singh Nanuwa via Info-cyrus wrote: > >> On

Re: sieve runtime error Fileinto: Permission denied

On Mon, May 23, 2016, at 22:47, Sundeep Singh Nanuwa via Info-cyrus wrote: > On 23/05/16 13:35, Bron Gondwana via Info-cyrus wrote: > > You need to have "anyone p" acl to fileinto anything other than inbox. > That didn't work unfortunately. Deliver into INBOX works, filein

Re: sieve runtime error Fileinto: Permission denied

You need to have "anyone p" acl to fileinto anything other than inbox. Bron. On Mon, May 23, 2016, at 21:52, Sunny via Info-cyrus wrote: > Hi, > > I'm seeing the following error logs with some users sieve filtering > May 23 11:41:31 imap02 lmtpunix[26005]: sieve runtime error for test2 id

Re: sieve runtime error Fileinto: Permission denied

On Tue, May 24, 2016, at 20:16, Patrick Boutilier via Info-cyrus wrote: > On 05/24/2016 01:56 AM, OBATA Akio via Info-cyrus wrote: > > On Tue, 24 May 2016 12:32:07 +0900, Bron Gondwana via Info-cyrus > > <info-cyrus@lists.andrew.cmu.edu> wrote: > > > >> On Tue

Re: lmtpd triggering a delivery.db checkpointing (Cyrus 2.3.16)

On Tue, May 17, 2016, at 22:51, Eric Luyten via Info-cyrus wrote: > On Tue, May 17, 2016 11:45 am, Simon Matter wrote: > >> Hi, > >> > >> > >> > >> Several times a month our server freezes up on deliveries and the system > >> load average shoots up into the hundreds. Things quickly return to

Re: lmtpd triggering a delivery.db checkpointing (Cyrus 2.3.16)

> What we do at FastMail to make deliver.db not suck is store it on tmpfs. The > repack is tons faster. Sure you lose it over a full server restart, but all > you lose is the duplicate suppression. If you wanted to be really clever > about it, you could copy the file during the shutdown

Re: Problem moving between folders during 2.3.16 -> 2.5.9 upgrade

* OK [URLMECH INTERNAL] Ok > * OK [ANNOTATIONS 65536] Ok > a0084 OK [READ-WRITE] Completed > <1469384392 >1469384392>a0085 OK Completed > <1469384412 >1469384412>a0086 OK Completed > > Is this a known issue with the upgrade process? Messages can be delive

Re: version of cyrus.index

On Fri, Jul 29, 2016, at 18:51, Deniss via Info-cyrus wrote: > Hello, > > Is there any simple way to check version of cyrus.index format in 2.5 > installation ? # perl -e 'sysread(\*STDIN, $buf, 12); (undef, undef, $v) = unpack('NNN', $buf); print "$v\n"' < ./data/user/foo/cyrus.index 13

Re: sync_client errors out after 2.3.16 -> 2.5.9 upgrade

You can't sync a mailbox without GUID for messages. You need to upgrade the mailboxes before you can use them for replication. The GUID is used for replication - if we allowed zero GUIDs, then every message would deduplicate to the same message! On Tue, Aug 2, 2016, at 07:56, Kenneth

Re: Huge performance problems after updating from 2.4 to 2.5.8

On Fri, Jul 15, 2016, at 23:46, Andy Dorman via Info-cyrus wrote: > So if the issue apparently lies with twoskip, can we keep our dbs using > skiplist and do the 2.4 -> 2.5 upgrade? Is it possible -h could revert > back to skiplist? You can convert a db back just by changing the setting in

Re: Huge performance problems after updating from 2.4 to 2.5.8

Squatter indexes will be broken without the latest patches on the 2.5 branch. The data gets indexed differently, and I had to patch the squatter code to search both styles. Bron. On Fri, Jul 15, 2016, at 22:17, Andre Felipe Machado via Info-cyrus wrote: > Hello, > Maybe, after such upgrade,

Re: Huge performance problems after updating from 2.4 to 2.5.8

So we've discussed this at length in #cyrus on freenode, and concluded that the issue is that twoskip is doing far too many munmap / mmap calls during an unlocked foreach (which is what the LIST command uses). I've filed a bug: https://github.com/cyrusimap/cyrus-imapd/issues/5 And I'm looking

Re: Huge performance problems after updating from 2.4 to 2.5.8

On Fri, Jul 15, 2016, at 23:52, Bron Gondwana via Info-cyrus wrote: > On Fri, Jul 15, 2016, at 23:46, Andy Dorman via Info-cyrus wrote: > > So if the issue apparently lies with twoskip, can we keep our dbs using > > skiplist and do the 2.4 -> 2.5 upgrade? Is it possible -h coul

Re: sync_client errors out after 2.3.16 -> 2.5.9 upgrade

field in the > index for the guid, but that it wasn't necessarily populated? That > might complicate things? I don't know the history here. > > On Tue, Aug 2, 2016, at 10:01 AM, Bron Gondwana via Info-cyrus wrote: > > You can't sync a mailbox without GUID for messages. You need t

Re: sync_client errors out after 2.3.16 -> 2.5.9 upgrade

ed within the > patch series, they will all be 10. > > Regards, > Ken > > On Tue, Aug 02, 2016 at 11:39:01AM +1000, Bron Gondwana via Info-cyrus wrote: > > Yeah, could be. In that case then the mailbox needs a reconstruct -G first > > :( > > Version 10 mail

Re: Quick advise regarding Cyrus migration

Skiplist should be clean for a 32 bit to 64 bit architecture change. It's all very type-careful internally. It's also endian-change safe, because it uses network-byte-order for everything internally. We definitely did a 32 bit to 64 bit conversion (probably slightly earlier - Debian 6 to 7)

Re: squat broken after upgrade from 2.4 to 2.5?

This could very well be a bug in the upgrade :( It would be great to have a test case to check this. I can't do that today, but maybe ellie can do something. Sadly our bug tracking situtation for Cyrus is a mess at the moment, but I'm hoping to have that cleaned up soon. Bron. On Mon, Jun

Re: bugzilla.cyrusimap.org is down

Instructions need updating, please use https:://github.com/cyrusimap/cyrus- imapd/ Regards, Bron. On Thu, 9 Feb 2017, at 04:59, Mikhail T. via Info-cyrus wrote: > The Cyrus Bugzilla is not responding. Firefox claims: >> The server at bugzilla.cyrusimap.org is taking too long to

Re: Is guid_mode: sha1 really gone from imapd.conf?

Yep, it's gone away - sha1 is the only mode right now. We're going to want to look at blake2 soon though I reckon. Bron. On Tue, 17 Jan 2017, at 03:48, Andy Dorman via Info-cyrus wrote: > So the subject is the question... > > Running cyr_info conf-lint against our imapd.conf indicates

Re: Cyrus IMAP 3.0.0-rc1 Config Lint Surprise

Thanks Nic, yeah - that page was back to front. Good find Andy. Bron. On Tue, 17 Jan 2017, at 04:01, Nic Bernstein via Info-cyrus wrote: > Thanks for the heads-up. We'll get this fixed, it is the man page which > is correct. > -nic > > On 01/16/2017 10:19 AM, Andy Dorman via Info-cyrus

Re: What happened to normalizeuid?

On Fri, 20 Jan 2017, at 03:31, Sebastian Hagedorn via Info-cyrus wrote: > --On 19. Januar 2017 um 17:18:06 +0100 Simon Matter > wrote: > > > We and others had this as a patch in our RPMs but I think it has never > > been part of vanilla cyrus-imapd. > > Oops. Should I

Re: What happened to normalizeuid?

We force it to lowercase in Nginx. Bron. On Fri, 20 Jan 2017, at 21:24, Sebastian Hagedorn wrote: > > --On 20. Januar 2017 um 08:04:25 +1100 Bron Gondwana via Info-cyrus > <info-cyrus@lists.andrew.cmu.edu> wrote: > > > On Fri, 20 Jan 2017, at 03:31, Sebastian Haged

Re: Replication failing - IMAP_SYNC_CHECKSUM Checksum Failure

Sounds like you have been fiddling mailboxes.db entries and/or didn't clean it up properly? I would recommend sync_reset on the user on the replica for a better cleanup than delete. Oh yeah, don't create the mailbox on the replica before replicating it in, that's crazy talk - you'll get a new

Re: Replication failing - IMAP_SYNC_CHECKSUM Checksum Failure

What do you see in syslog? (both for the reconstruct and later when the sync_client runs) On Tue, 23 Aug 2016, at 03:49, Tod A. Sandman via Info-cyrus wrote: > I'm using rolling replication with cyrus-imapd-2.5.9. sync_client died and I > am not able to get replication working again. I've

Re: How to handle special use folders in Sieve?

On Tue, 13 Sep 2016, at 17:25, OBATA Akio via Info-cyrus wrote: > Hi, > > Since 3.0.0-beta2 release note's "Major changes since the 2.5.x series": > > * Sieve now supports special use folders. See Cyrus Sieve > > http://cyrusimap.org/imap/admin/sieve.html#cyrus-sieve-specialuse > > But I

Re: Cyrus 2.5.9 imapd children and tcp_timeout questions

On Tue, 13 Sep 2016, at 10:44, ellie timoney via Info-cyrus wrote: > Note that it talks about the process being used for new connections. > Each imapd process serves one connection at a time (so if you have 50 > client connections, you will have 50 imapd processes to serve them, plus > whatever

Re: Twoskip DB files broken

A couple of things. 1. Why are you doing this? What do you hope to achieve? 2. Possibly kolab's Cyrus configuration stores files in other paths (tmpfs, data dirs) which are Berkeley dbs and don't expect their environment to be trashed under them. On Thu, 29 Sep 2016, at 23:47, Tobias Brunner

Re: command line deletion of files

Ahh, and reading on I see that this exists already :) On Fri, 30 Sep 2016, at 08:02, Bron Gondwana wrote: > You're the reason we can't have nice things :( rm + reconstruct will bite you > one upgrade for sure. > > A dry run option to ipurge sounds like a great idea. We just always use IMAP >

Re: command line deletion of files

You're the reason we can't have nice things :( rm + reconstruct will bite you one upgrade for sure. A dry run option to ipurge sounds like a great idea. We just always use IMAP to do admin on Cyrus, but I can see a case for improving ipurge. On Fri, 30 Sep 2016, at 01:04, Vladislav Kurz via

Re: Invalid mailbox name

On Fri, 23 Sep 2016, at 02:37, Paul van der Vlis via Info-cyrus wrote: > Op 22-09-16 om 09:46 schreef Michael Menge via Info-cyrus: > > > > Quoting Paul van der Vlis via Info-cyrus : > > > >> Op 21-09-16 om 14:11 schreef Michael Menge via Info-cyrus: > >>> Hi, >

Re: Invalid mailbox name

If anyone is interested in looking in the code on master to see how this works: https://github.com/cyrusimap/cyrus-imapd/ You're looking for mbname_t, and in particular mbname_from_*. EXPORTED mbname_t *mbname_from_extname(const char *extname, const struct namespace *ns, const char *userid)

Re: Invalid mailbox name

On Thu, 22 Sep 2016, at 22:11, Eric Luyten via Info-cyrus wrote: > On Thu, September 22, 2016 9:46 am, Michael Menge via Info-cyrus wrote: > > > > > Quoting Paul van der Vlis via Info-cyrus : > > > > >> I am wondering about the dot. So far I know I cannot use it

Re: how to deal with mail retention/archival.

On Sat, 27 Aug 2016, at 02:13, Shawn Bakhtiar via Info-cyrus wrote: > >> On Aug 26, 2016, at 8:35 AM, Giuseppe Ravasio (LU) via Info-cyrus > cy...@lists.andrew.cmu.edu> wrote: >> >> I saw that someone proposed to make a sort of abuse of delayed >> expunge, >> but I think that in order to

Re: cannot unlink .... mboxkey: No such file or directory

If you're running rolling replication, it SHOULD have logged both the old mailbox name and the DELETED mailbox name, and calculate the move when syncing. If you're running sync_client -m on just the mailbox, sure - it will get deleted, because sync_client can't tell what name it was renamed to

Re: cyrus master fails with status 71

On Tue, 8 Nov 2016, at 05:01, Eric Cunningham via Info-cyrus wrote: > Are such numbers of imapd processes to be expected? Depends on your usage patterns of course. > Why is lmptunix complaining about options passed to imapd? Because the names of the config files are bogus for historical

Re: Xapian search databases

On Mon, 7 Nov 2016, at 23:23, Adam Tauno Williams via Info-cyrus wrote: > On Thu, 2016-11-03 at 10:47 +1100, Bron Gondwana via Info-cyrus wrote: > > Just out of interest - is anyone other than Fastmail currently using > > the Cyrus Xapian-based search system? > > No

Re: cyrus master fails with status 71

On Tue, 25 Oct 2016, at 02:45, Eric Cunningham via Info-cyrus wrote: > Hi list, we're running cyrus imap 2.5.9 built from the FreeBSD 10-2 > (release-p7) ports tree. > > The cyrus master process is failing periodically (every 1-2 weeks) as > follows: > > Oct 22 07:38:48 imap1 master[7767]:

Re: mailboxes.db locking problem after updating from 2.4 to 2.5.9

On Fri, 18 Nov 2016, at 10:51, Wolfgang Breyha via Info-cyrus wrote: > On 17/11/16 14:00, Deniss via Info-cyrus wrote: > > Any ideas or suggestion for investigation ? > > I already filed a bug > https://github.com/cyrusimap/cyrus-imapd/issues/43 > but no response so far. I directly asked Bron,

Re: limit max child per user or IP

No idea with perdition either. There is support directly in Cyrus though, at least new cyrus: { "maxlogins_per_host", 0, INT } /* Maximum number of logged in sessions allowed per host, zero means no limit */ { "maxlogins_per_user", 0, INT } /* Maximum number of logged in sessions allowed per

Xapian search databases

Just out of interest - is anyone other than Fastmail currently using the Cyrus Xapian-based search system? We're making a bunch of changes: * transition to Glass backend in Xapian 1.4 * move cyrus.indexed information into Xapian metadata * index by GUID rather than folder/uid pair These changes

Re: Did calculating the quota change from 2.3 to 2.5?

On Wed, 30 Nov 2016, at 08:37, Jason L Tibbitts III via Info-cyrus wrote: > >>>>> "BG" == Bron Gondwana via Info-cyrus <info-cyrus@lists.andrew.cmu.edu> > >>>>> writes: > > BG> If you use imapsync, it doesn't know about that, a

Re: Did calculating the quota change from 2.3 to 2.5?

. Bron. On Wed, 30 Nov 2016, at 01:24, Marc Patermann via Info-cyrus wrote: > Bron, > > Am 29.11.2016 um 13:26 Uhr schrieb Bron Gondwana via Info-cyrus: > > No, the quota calculations are identical. It's possible that your > > quota was incorrectly calculated on the source server

Cyrus Project bug tracking moved to Github

Effective immediately, we are no longer using bugzilla.cyrusimap.org for bug tracking, and anything filed there since last Friday (December 9th) will be lost. I have asked CMU to shut the old bugzilla down. All the bugs have been migrated to Issues section of the github repositories for the

Re: IOERROR: mapping /srv/imap/config/annotations.db.NEW file: Cannot allocate memory

How big is your annotations.db ? What architecture are you running on? On Sat, 17 Dec 2016, at 04:34, Jan Kowalsky via Info-cyrus wrote: > Hi all, > > for a few days all time creating or deleting folders we get an error in > mail.log: > > Dec 16 18:28:17 mail imap[10078]: IOERROR: mapping >

Re: Did calculating the quota change from 2.3 to 2.5?

No, the quota calculations are identical. It's possible that your quota was incorrectly calculated on the source server though. A quota -f there should correct the calculations. Regards, Bron. On Tue, 29 Nov 2016, at 01:36, Marc Patermann via Info-cyrus wrote: > Hi, > > while migrating

Re: 2.5.10 autocreate on login not working?

Is there anything in syslog? Bron On Tue, 6 Dec 2016, at 05:40, Nels Lindquist via Info-cyrus wrote: > I'm experimenting with a build of 2.5.10 on CentOS 7 in preparation for > upgrading from our installed 2.3.16 (built from Simon Mattar's RPMs). > > We rely on mailbox auto-creation

Re: Did calculating the quota change from 2.3 to 2.5?

On Sat, 31 Dec 2016, at 10:57, Wolfgang Breyha via Info-cyrus wrote: > On 29/11/16 22:37, Jason L Tibbitts III via Info-cyrus wrote: > > Fun random question: Does anything blow up if you run hardlink on your > > mail spool? (The hardlink program finds identical files and hardlinks > > them.) > >

Re: DBERROR: critical database situation

2.4 was releasted in 2010, it's 2017. We advise not to run Berkeley DB (even on 2.3.19), because it doesn't upgrade very nicely. I would advise that you get some version 10 binaries and use cvt_cyrusdb to convert all your berkeley databases to skiplist. Skiplist in 2.3.19 is rock solid.

Re: R: Re: DBERROR: critical database situation

Indeed, with all the right libraries. You can't upgrade libdb without everything going to shit, which is why we have ditched BDB - the upgrade path is bogus. Bron. On Wed, 4 Jan 2017, at 21:20, absolutely_free--- via Info-cyrus wrote: > > Hi Bron, > thank you for you reply. > What do

Re: R: Re: DBERROR: critical database situation

Oh good, you can just delete those two BDB files with Cyrus shut down (and change them to skiplist while you're at it!) Once you've done that you can delete everything in the $confdir/db folder too. (delete might mean take a copy somewhere else until you're happy everything is working of

Re: R: Re: R: Re: DBERROR: critical database situation

Just removing the config options that say berkeley for those two databases in imapd.conf should do the trick (followed by nuking them again, and while Cyrus is shut down) Bron. On Wed, 4 Jan 2017, at 22:08, absolutely_free--- via Info-cyrus wrote: > After deleting /var/imap/db/*,

Release plan blog post

I posted on the FastMail advent about our plans for releasing Cyrus 3.0 - it's a bit roundabout doing it this way rather than here first, but hey - we talked about it on Monday night's regular meeting. Here's the blog post: