heavily hacked RH 6.2 system -- 2.2.17 kernel + most libs
compiled locally.
attached is output from:
./configure --prefix=/opt/imapd 2>&1 | tee LOG;
make -wk 2>&1 | tee -a LOG;
configre doesn't seem unhappy, unless the:
checking for AgentX... configure: warning: Could
On Sat, 21 Oct 2000, Gary Mills wrote:
> I'm testing cyrus-imapd-2.0.7, and I notice that the userid hashing
> scheme in conf/deliverdb, conf/quota, and conf/user use the first
> letter of the userid for subdirectory names. Unfortunately, we have
> about 20,000 userids that begin with the strin
Various components of cyrus-imapd-2.0.7 create Unix-domain sockets,
and use the permissions of the enclosing directory to restrict access
to the sockets. I'm using /var/run for these directories because it's
on a temporary filesystem in Solaris-8. What should be the correct
directory permissions
I'm testing cyrus-imapd-2.0.7, and I notice that the userid hashing
scheme in conf/deliverdb, conf/quota, and conf/user use the first
letter of the userid for subdirectory names. Unfortunately, we have
about 20,000 userids that begin with the string `um', which will all
hash to the same directory
In cyrus-imapd-2.0.7, /etc/sasldb is used to contain shared secrets
for pop3d and imapd, as well as sendmail and any other servers that
use SASL. This is a local file. Has anyone thought of storing this
information in a database so that it could be used for authentication
on more than one host?