Bug#379881: cyrus-imapd-2.2: several oddities about imapd.conf parameters

[Sven Mueller]

Package: cyrus-imapd-2.2
Tags 379881 + pending upstream
Thanks

Ross Boylan wrote on 26/07/2006 05:34:
> Package: cyrus-imapd-2.2
> Version: 2.2.13-3
> Severity: normal
> 
> I've left severity at normal since some of these might affect
> someone's ability to get the system working.
> 
> 1.lmtp_admins
> The distributed imapd.conf has this
> # Space-separated list of users that have lmtp "admin" status (i.e. that
> # can deliver email through TCP/IP lmtp) in addition to those in the
> # admins: entry above
> #lmtp_admins: postman
> 
> The imapd.conf man page doesn't mention the parameter.

Right, because there is no lmtp_admins parameter unless you defined an
"lmtp" service in cyrus.conf. I updated lib/imapoptions to at least
mention this type of parameters.

> And the upstream upgrade instructions (from 2.1 to 2.2) says "the
> admins and lmtp_admins configuration options no longer union.  Per
> service options completely override the default value when they are
> specified."  This contradicts the comment in the config file, which
> says they do union.  It is also a bit ambiguous whether the upgrade
> instructions mean that if you do not specify lmtp_admins, you will get
> them equal to the admins list.

Right, if you specify "lmtp_admins" (and have an "lmtp" service in
cyrus.conf), that service will use the value from "ltmp_admins" instead
of the one from "admins". This is now also corrected in both
lib/imapoptions (which is used to generate the imapd.conf manpage) and
in the imapd.conf file we ship with the package.

> 2. lmtp_allowplaintext is no longer defined say the upgrade
> instructions "and must be specified using the service name of your
> lmtp process if you require a specific value".  The parameter is
> absent from imapd.conf and its man page, which is good (or at least
> consistent).  I can't tell what the alternate syntax is, however, or
> how this relates to the sasl options.

Every configuration parameter mentioned in imapd.conf can also be
specified as <service>_<parameter to override <parameter> just for
<service>.

> 3. Both of the preceding suggest there may be some new syntax for
> specifying options in imapd.conf (something like the sasl_foo for sasl
> options), but I don't see it spelled out anywhere.

> These are likely all upstream issues.

Yes, somewhat, they certainly are upstream (except for the imapd.conf we
ship). Would have forwarded the bug upstream, but for some unknown
reason, I can't create a BugZilla account in their bugtracker. So if
anyone else has such an account, please report this bug to upstream.

Regards,
Sven