Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 34272 - saslauthd[25300] :set_auth_mech : failed to initilize mechanism rimap
Summary: saslauthd[25300] :set_auth_mech : failed to initilize mechanism rimap
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Nick Hadaway
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-24 11:04 UTC by Martin
Modified: 2004-01-28 07:38 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin 2003-11-24 11:04:52 UTC 
This is the same as bug 23037, however upgrading cyrus-sasl did not provide a 
resolution. 
 
Starting saslauthd manually to use rimap authentication mechanism - 
saslauthd -a rimap -O 127.0.0.1 
I receive  
saslauthd[25300] :set_auth_mech   : failed to initilize mechanism rimap 
 
I have tried this using cyrus-sasl-2.1.13, 2.1.14 and 2.1.15. 
 
I have tried this on 4 different x86 machines and each gives the same error. 
 
This has nothing to do with /etc/conf.d/saslauthd, which is up to date. 
 

Reproducible: Always
Steps to Reproduce:
1.saslauthd -a rimap -O 127.0.0.1 
 
2. 
3. 
Actual Results:  
saslauthd[19557] :set_auth_mech   : failed to initilize mechanism rimap 

Expected Results:  
Started SASL 

hermes etc # emerge info 
Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 
2.4.22-hardened) 
================================================================= 
System uname: 2.4.22-hardened i686 Pentium III (Coppermine) 
Gentoo Base System version 1.4.3.10 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-O2 -mcpu=i686 -pipe" 
CHOST="i686-pc-linux-gnu" 
COMPILER="gcc3" 
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config 
/usr/kde/2/share/config /usr/kde/3/share/config" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" 
CXXFLAGS="-O2 -mcpu=i686 -pipe" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="sandbox ccache autoaddcvs" 
GENTOO_MIRRORS="http://gentoo.chem.wisc.edu/gentoo/ http://adelie.polymtl.ca/ 
http://gentoo.mirrors.pair.com/ http://gentoo.noved.org/" 
MAKEOPTS="-j2" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="" 
SYNC="rsync://rsync.gentoo.org/gentoo-portage" 
USE="perl x86 -oss apm -arts -avi berkdb crypt -cups -encode -foomaticdb gdbm 
gif gpm -gtk imlib java jpeg -kde -gnome -libg++ libwww -mad -mikmod mmx 
-motif -mpeg ncurses nls -oggvorbis -opengl pam pdflib png python -qt 
-quicktime readline -sdl slang spell ssl -svga tcpd -truetype -X xml2 -xmms 
-xv zlib ethereal -ldap mysql sasl usb apache2"
Comment 1 Max Kalika (RETIRED) gentoo-dev 2004-01-28 07:38:24 UTC 
This will be fixed the hard way in 2.1.17 momentarily. In the mean time, you can fix this the easy way by setting the host to "127.0.0.1/imap2"  <-- notice the protocol is imap2 (by default it uses imap which is not defined in /etc/services on Gentoo.)  I added a quick sed fix to change the default.  But if you don't want to rebuild the whole thing, then just stick the proper port as part of the hostname in /etc/conf.d/saslauthd.