Bug 29881 – Exim have problems with using saslauthd as auth solution.

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Marcin Jurczuk 2003-09-29 03:54:37 UTC]

When I try to run exim with sasl authorization support there were information 
like:  
2003-09-29 11:36:17 login authenticator failed for (IP) [IP]: 435 Unable to 
authenticate at present (set_id=spock): unknown condition "saslauthd" 
Problem is with path to mux file. 
 
 

Reproducible: Always
Steps to Reproduce:
1.emerge exim  
2. setup sasl auth 
3. try to use auth mech i.e LOGIN 
Actual Results:  
There were error described above in details 

Expected Results:  
 

I have solve problem - here is patch for exim-4.22.ebuild: 
shapieron exim # diff exim-4.22.ebuild exim-4.22-r1.ebuild 
70a71 
> 		-e "s:# 
CYRUS_SASLAUTHD_SOCKET=/var/state/saslauthd/mux:CYRUS_SASLAUTHD_SOCKET=/var/lib/sasl2/mux:" 
\ 
shapieron exim # 
exim-4.22-r1.ebuild 0 is ebuild with solution.

[Comment 1 Pawel Sikora 2003-10-05 03:34:51 UTC]

http://www.ds14.agh.edu.pl/~pluto/gentoo/patches/exim-4.22-ebuild-sasl.patch

[Comment 2 Pawel Sikora 2003-10-05 03:35:20 UTC]

http://www.ds14.agh.edu.pl/~pluto/gentoo/patches/exim-4.22-ebuild-sasl.patch

[Comment 3 Kurt Lieber (RETIRED) 2003-11-05 06:24:31 UTC]

fixed and in portage (~masked).  Thanks for the patch.

[Comment 4 Kurt Lieber (RETIRED) 2003-12-06 13:10:53 UTC]

closing old bug.

[Comment 5 Arturas lajus 2004-02-13 06:46:52 UTC]

Created attachment 25534 [details]
ebuild i used to build cyrus-sasl