Cyrus hmh branch

[Henrique de Moraes Holschuh]

On Thu, 14 Oct 2010, Patrick Goetz wrote:
> So why is anything from cyrus being written to syslog at all?  This

Make sure =debug does not end up in /var/log/syslog.

> message should be going to /var/log/mail.err, as far as I can tell.
> This seems like it might be a bug.

The bug is that Cyrus logs too much debug crap with scary prefixes.

> I have not been able to get an answer on how the set of database
> names cyrus uses is determined; i.e. why are /var/lib/cyrus
>   annotations.db, deliver.db, mailboxes.db, and tls_sessions.db
> created automatically, but not user_deny.db?  Maybe this db is only
> set up if you actually have some deny user entries?

I have no idea about this one.

> While on the subject, I also can't determine what /var/lib/cyrus/db
> is for, or why /var/lib/cyrus/user/[a-z]/{user_name.seen,

Berkeley DB environment.

> user_name.sub} are placed in /var/lib/cyrus rather than in the
> appropriate user directory under /var/spool/cyrus.

They're supposed to be in diferent filesystems for performance or something
like that.  New cyrus can place them anywhere you want, but we go with the
defaults.

> >Apparently, this can be quite problematic in some cases as mentioned
> >here:
> >http://www.mail-archive.com/info-cyrus@lists.andrew.cmu.edu/msg39304.html.
> 
> At least the logging seems like a bug.  Also, shouldn't this be
> checked just once per IMAP session?

Ask upstream :-(

> but it is probably better to maintain continuity with the upstream
> source for these, particularly since they live in sbin rather than
> bin.

upstream is messy and polutes namespace.  We can't really follow whatever
they do blindly, it causes problems.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh