imapd, sasl, imtest connection refused

[Kimberly Triplett]

The /usr/local/bin was a mistake - it was /usr/bin - sorry :)
I had done a manual install first and when I saw that the rpm's were
available, I did the make distclean and  installed the rpm's.

When I do the ps -ef, I do see the /var/run/saslauthd/mux and I have set the
password for the cyrus account.

Kim


> -----Original Message-----
> From: Simon Matter [mailto:simix at datacomm.ch]
> Sent: Monday, September 16, 2002 10:12 AM
> To: ktriplett at riteaid.com; Mr. Simix
> Cc: pauls at utdallas.edu; pstreibig at bcj.com;
> info-cyrus at lists.andrew.cmu.edu
> Subject: Re: imapd, sasl, imtest connection refused
>
>
> On Monday 16 September 2002 15:41, Kimberly Triplett wrote:
> > The chkconfig saslauthd on  command came back with nothing
> > The service was started but I stopped it and issued the
> > service saslauthd start again.  It came back with OK and when I
> look there
> > are 5 daemons running.  I still get the same error message.
> Someone else
> > suggested that I put the host in host.allow, which I did.  But
> it made no
> > difference.
>
> chkconfig saslauthd on installs the links to let saslauthd start
> on boot. It
> doesn't come back with anything.
> If saslauthd is running, do you see the communication socket
> /var/run/saslauthd/mux? And, did you set the password for the cyrus user?
> Another question, why do you call "/usr/local/bin/imtest -m login
> newpopmail"? If you installed from my RPMs, no files were placed into
> /usr/local. So you installed 'by hand' before? Well, it means you
> system is a
> mess now :) You have to distclean any files installed by manual installs
> before the RPM install will work correctly.
>
> Simon
>
> >
> > Kim
> >
> > > -----Original Message-----
> > > From: Mr. Simix [mailto:simix at datacomm.ch]
> > > Sent: Friday, September 13, 2002 5:05 PM
> > > To: ktriplett at riteaid.com
> > > Cc: simix at datacomm.ch; pauls at utdallas.edu; pstreibig at bcj.com;
> > > info-cyrus at lists.andrew.cmu.edu
> > > Subject: RE: imapd, sasl, imtest connection refused
> > >
> > > > I have gotten past a lot of the issues I was facing.  I am
> now running
> > > > the imtest and getting the following error message:
> > > >
> > > > /usr/local/bin/imtest -m login newpopmail
> > > >
> > > > S: * OK newpopmail Cyrus IMAP4 v2.1.9-Invoca-RPM-2.1.9-1
> server ready
> > > > C: C01 CAPABILITY
> > > > S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS
> > > > NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND
> > > > SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE STARTTLS LISTEXT
> > > > LIST-SUBSCRIBED ANNOTATEMORE X-NETSCAPE
> > > > S: C01 OK Completed
> > > > Please enter your password:
> > > > C: L01 LOGIN cyrus {10}
> > > > S: + go ahead
> > > > C: <omitted>
> > > > S: L01 NO Login failed: generic failure
> > > > Authentication failed. generic failure
> > > > Security strength factor: 0
> > > >
> > > > The syslog shows the following error:
> > > > Sep 13 14:33:38 newpopmail imapd[11490]: cannot connect to saslauthd
> > > > server: No such file or directory
> > >
> > > Seems like saslauthd is not running or the socket for saslauthd
> > > communication is not there (not likely if you installed via RPM)
> > >
> > > try:
> > >
> > > chkconfig saslauthd on
> > > service saslauthd start
> > >
> > > BTW, when I find some time I'll write a small quick start
> howto for the
> > > cyrus rpm install.
> > >
> > > HTH
> > > Simon
> > >
> > > > Sep 13 14:33:38 newpopmail imapd[11490]: badlogin:
> > > > newpopmail[10.47.10.35] plaintext cyrus SASL(-1): generic failure:
> > > > checkpass failed
> > > >
> > > > Anyone have any suggestions or something to check?
> > > > Kim
> > > >
> > > >> -----Original Message-----
> > > >> From: simix at xxl.bi.corp.invoca.ch
> > > >> [mailto:simix at xxl.bi.corp.invoca.ch]On Behalf Of Mr. Simix
> > > >> Sent: Thursday, September 12, 2002 2:58 AM
> > > >> To: Schmehl, Paul L
> > > >> Cc: ktriplett at riteaid.com; ps; info-cyrus at lists.andrew.cmu.edu
> > > >> Subject: Re: imapd, sasl, imtest connection refused
> > > >>
> > > >> "Schmehl, Paul L" wrote:
> > > >> > Is Cyrus running?  Is saslauthd running?
> > > >> >
> > > >> > You start Cyrus with /usr/cyrus/bin/master &
> > > >> > You start saslauthd with /usr/local/sbin/saslauthd -a plain
> > > >> > (substitute paths accordingly)
> > > >>
> > > >> With the RPM install, it's:
> > > >> service saslauthd start
> > > >> service cyrus-imapd start
> > > >>
> > > >> You may also want to give the cyrus account a password with:
> > > >> passwd cyrus
> > > >>
> > > >> Then login with something like this:
> > > >> cyradm --user cyrus --auth PLAIN localhost
> > > >>
> > > >> Simon
> > > >>
> > > >> > If you haven't specified the location of the saslauthd socket in
> > > >>
> > > >> imapd.conf, then you can do so when you start it:
> > > >> > /usr/local/sbin/saslauthd -a plain -m /var/run/saslauthd/mux
> > > >> > (again, substitute paths as appropriate)
> > > >> >
> > > >> > # man 8 master
> > > >>
> > > >> master may conflict with postfix's master, so it "man
> cyrus-master" in
> > > >> the RPM.
> > > >>
> > > >> > # man 8 saslauthd
> > > >> >
> > > >> > Paul Schmehl (pauls at utdallas.edu)
> > > >> > Department Coordinator
> > > >> > The University of Texas at Dallas
> > > >> > AVIEN Founding Member
> > > >> > http://www.utdallas.edu/~pauls/
> > > >> >
> > > >> > > -----Original Message-----
> > > >> > > From: Kimberly Triplett [mailto:ktriplett at riteaid.com]
> > > >> > > Sent: Wednesday, September 11, 2002 4:04 PM
> > > >> > > To: ps
> > > >> > > Cc: info-cyrus at lists.andrew.cmu.edu
> > > >> > > Subject: RE: imapd, sasl, imtest connection refused
> > > >> > >
> > > >> > >
> > > >> > > I downloaded all the rpm's from the web site you listed, did a
> > > >>
> > > >> make distclean on both packages and installed the rpm's.
> > > >>
> > > >> > > I installed cyrus-imapd-2.1.9-1.i386.rpm
> > > >> > >             cyrus-imapd-utils-2.1.9-1.i386.rpm
> > > >> > >             perl-cyrus-2.1.9-1.i386.rpm
> > > >> > >
> > > >> > >             cyrus-sasl-2.1.5-1.i386.rpm
> > > >> > >             cyrus-sasl-devel-2.1.5-1.i386.rpm
> > > >> > >             cyrus-sasl-md5-2.1.5-1.i386.rpm
> > > >> > >             cyrus-sasl-plain-2.1.5-1.i386.rpm
> > > >> > > Everything seemed to go ok - I logged into the cyrus
> account and
> > > >>
> > > >> issued the following commands and got the following error
> > > >>
> > > >> messages:
> > > >> > > imtest -m login -p imap localhost
> > > >> > >        connect: connection refused
> > > >> > >        failure: network initialization
> > > >> > >
> > > >> > > cryadm localhost
> > > >> > >        cryadm: cannot connect to server
> > > >> > >
> > > >> > > Are there any more suggestions on what else I can do
> or where else
> > > >>
> > > >> to look.
> > > >>
> > > >> > > Thanks
> > > >> > > Kim
> > > >> > >
> > > >> > > > -----Original Message-----
> > > >> > > > From: ps [mailto:pstreibig at bcj.com]
> > > >> > > > Sent: Tuesday, September 10, 2002 5:06 PM
> > > >> > > > To: ktriplett at riteaid.com
> > > >> > > > Cc: info-cyrus at lists.andrew.cmu.edu
> > > >> > > > Subject: Re: imapd, sasl, imtest connection refused
> > > >> > > >
> > > >> > > >
> > > >> > > > Kim,
> > > >> > > >
> > > >> > > > I had similar issues with an almost identical installation.
> > > >> > >
> > > >> > >  Someone
> > > >> > >
> > > >> > > > on the list (forgive me I forget who) mentioned that the
> > > >> > >
> > > >> > > perl issues
> > > >> > >
> > > >> > > > were due to RedHat's implementation and location of Perl.  I
> > > >>
> > > >> highly recommend (as many other list readers pointed out) that
> > > >> you
> > > >>
> > > >> > > use Simon
> > > >> > >
> > > >> > > > Matter's RPMs located  (and maintained wonderfully
> up to date)
> > > >>
> > > >> at http://home.teleport.ch/simix/ grab all the pieces...
> > > >>
> > > >> > > > before using the RPMs  make sure to  "make distclean"  both
> > > >> > >
> > > >> > > cyrus-sasl
> > > >> > >
> > > >> > > > and cyrus-imapd in the directory that you compiled from.
> > > >> > > >
> > > >> > > > i would also suggest using the GNOME  GNORPM tool if you
> > > >> > >
> > > >> > > can, since it
> > > >> > >
> > > >> > > > is a bit easier to see when something conflicts, for
> instance my
> > > >>
> > > >> RedHat 7.2 had a 1.5.x version of SASL included that i chose to
> > > >> upgrade via rpm  from Simon's packages.
> > > >>
> > > >> > > > i am currently having issues with the setup of the
> OpenSSL and
> > > >>
> > > >> OpenLDAP portions of my server, but that's another matter.
> > > >>
> > > >> > > > hth
> > > >> > > > peter
>