On 02/16/17 16:10 -0600, Kenneth Marshall wrote:
We are running version cyrus-imapd-2.5.10, and even though no databases
in imapd.conf default to berkeleydb, something is still using it. Here
are our database definitions from our imapd.conf:
duplicate_db_path: /dev/shm/cyrus-imapd/duplicate_db
On Fri, Feb 17, 2017, at 09:42 AM, Kenneth Marshall wrote:
> On Thu, Feb 16, 2017 at 04:14:38PM -0600, Dan White wrote:
> > On 02/16/17 16:10 -0600, Kenneth Marshall wrote:
> > >We are running version cyrus-imapd-2.5.10, and even though no databases
> > >in imapd.conf default to berkeleydb,
Hi Cyrus Developers,
We are running version cyrus-imapd-2.5.10, and even though no databases
in imapd.conf default to berkeleydb, something is still using it. Here
are our database definitions from our imapd.conf:
duplicate_db_path: /dev/shm/cyrus-imapd/duplicate_db
statuscache_db_path:
On Thu, Feb 16, 2017 at 04:14:38PM -0600, Dan White wrote:
> On 02/16/17 16:10 -0600, Kenneth Marshall wrote:
> >We are running version cyrus-imapd-2.5.10, and even though no databases
> >in imapd.conf default to berkeleydb, something is still using it. Here
> >are our database definitions from
The Cyrus team is proud to announce the immediate availability of the
third release candidate from the Cyrus IMAP 3.0 series: 3.0.0-rc3.
As a release candidate, it is considered near-stable for production
usage. Interfaces, APIs, features, etc are not likely to change
between now and the full
