Cyradm Stops Working after upgrade

Stephen Conway sconway at wlnet.com
Tue Mar 14 16:44:35 EST 2006


I am using saslauthd and upgraded this also.  I am using a service script to
start both the saslauthd and the master process:

Saslauthd (from /etc/sysconfig/saslauthd):
# Directory in which to place saslauthd's listening socket, pid file, and so
# on.  This directory must already exist.
SOCKETDIR=/var/run/saslauthd

# Mechanism to use when checking passwords.  Run "saslauthd -v" to get a
list
# of which mechanism your installation was compiled to use.
MECH=shadow

# Additional flags to pass to saslauthd on the command line.  See
saslauthd(8)
# for the list of accepted flags.
FLAGS=


Master Process:
# Options to cyrus-master
CYRUSOPTIONS=""

# Mailbox list dumps are rotated n times via cron.daily
#ROTATE=6

When I run both via these.  I can see that POP3 logins work fine, but any
IMAP connections do not.

Regards,

Stephen Conway

-----Original Message-----
From: Stephen Conway [mailto:sconway at wlnet.com] 
Sent: Monday, March 13, 2006 4:39 PM
To: 'info-cyrus at lists.andrew.cmu.edu'
Subject: RE: Cyradm Stops Working after upgrade

Hello:

Actually further to this, POP logins are working, but IMAP are not.  I think
this is why Cyradm can't login.  Any idea why?  Here is my imapd.conf:

configdirectory: /var/imap
partition-default: /var/spool/imap
admins: dima cyrus
sasl_pwcheck_method: saslauthd
sendmail: /usr/sbin/sendmail
unixhierarchysep: 1
quotawarn: 10
lmtp_overquota_perm_failure: yes
defaultacl: cyrus c

Here is cyrus.conf:
START {
  # do not delete this entry!
  recover       cmd="ctl_cyrusdb -r"

  # this is only necessary if using idled for IMAP IDLE
#  idled                cmd="idled"
}

# UNIX sockets start with a slash and are put into /var/imap/socket SERVICES
{
  # add or remove based on preferences
  imap          cmd="imapd" listen="imap" prefork=0
  imaps         cmd="imapd -s" listen="imaps" prefork=0
  pop3          cmd="pop3d" listen="pop3" prefork=0
  pop3s         cmd="pop3d -s" listen="pop3s" prefork=0
  sieve         cmd="timsieved" listen="sieve" prefork=0

  # at least one LMTP is required for delivery
#  lmtp         cmd="lmtpd" listen="lmtp" prefork=0
  lmtpunix      cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0

  # this is only necessary if using notifications
#  notify       cmd="notifyd" listen="/var/imap/socket/notify" proto="udp"
prefork=1
}

EVENTS {
  # this is required
  checkpoint    cmd="ctl_cyrusdb -c" period=30

  # this is only necessary if using duplicate delivery suppression
  delprune      cmd="ctl_deliver -E 3" at=0400

  # this is only necessary if caching TLS sessions
  tlsprune      cmd="tls_prune" at=0400
}


Thanks,
 
Stephen Conway

-----Original Message-----
From: info-cyrus-bounces at lists.andrew.cmu.edu
[mailto:info-cyrus-bounces at lists.andrew.cmu.edu] On Behalf Of Stephen Conway
Sent: Monday, March 13, 2006 1:28 PM
To: info-cyrus at lists.andrew.cmu.edu
Subject: Cyradm Stops Working after upgrade

Hello:
 
I have recently upgraded from version cyrus-imapd-2.1.12  to
cyrus-imapd-2.2.12 , and as part of the requirement also upgraded my sasl
lib to cyrus-sasl-2.1.21.  I converted my db files to skiplist and sieve
scripts, etc.  All works fine after starting.  Authentication of users /
mailboxes works fine.  The sieve scripts are working as well.  The only
problem I am facing, is everytime I try to login using cyradm (with command
line, or from Perl scripts) i get get the following:
 
# cyradm --auth login --user cyrus --pass ANYTHING localhost Login failed:
can't request info until later in exchange at
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Cyrus/IMAP/Admin.pm
line 114
cyradm: cannot authenticate to server with login as cyrus

Any idea why standard authentication would work but cyradm would not?

Regards,

Stephen Conway


--
ShipMail Now 30% Faster

----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ:
http://cyruswiki.andrew.cmu.edu List Archives/Info:
http://asg.web.cmu.edu/cyrus/mailing-list.html


-- 
ShipMail Now 30% Faster



More information about the Info-cyrus mailing list