Wolfgang Breyha wrote, on 24.05.2012 16:11:
> I tried to activate RC5 and fail badly with
>> May 24 15:58:00 moorhuhn exim[31647]: [1\2] 2012-05-24 15:58:00 
>> sasl_cram_md5 authenticator (CRAM-MD5):
>> May 24 15:58:00 moorhuhn exim[31647]: [2/2]   Cyrus SASL SSF 141300024 not 
>> supported by Exim
> if I try to use SASL_PLAIN auth? The exactly same config works with 4.77.

Sorry, not SASL_PLAIN. It's CRAM-MD5 actually, or cyrus-sasl at all if TLS/SSL
is in use. Source of src/auth/cyrus_sasl.c changed and Changelog mentions
that, but not that it may break existing configurations? Bug or feature? ;-)

Only a wild guess reading the source:
src/auths/cyrus_sasl.c:259ff
sets EXTERNAL_SFF to the value of tls_bits if TLS/SSL is in use.

And in
:410ff
   if (negotiated_ssf > 0)
is checked... does cyrus-sasl return tls_bits here and exim fails selflarting
itself?

Greetings, Wolfgang
-- 
Wolfgang Breyha <[email protected]> | http://www.blafasel.at/
Vienna University Computer Center | Austria


-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

Reply via email to