On Fri, Mar 18, 2005 at 04:15:59PM +0100, Marc Haber wrote:
> Without having too much clue about SASL, I understand the reporter
> that a SASL client is able to specify which mechanisms to use, and
> exim doesn't specify that list, meaning that it uses "all", which can
> clutter up the logs of the SASL server.
The cyrus_sasl authenticator acts as a SASL server only. It has no way
to specify where it gets the passwords from. On startup, it queries the
SASL server to find all available mechanisms, as it won't advertise a
mechanism that it doesn't know how to deal with.
> The issue report for #299743 has a patch. Please consider this patch.
Oops, I thought you were referring to a patch for this problem. As far
as I recall, I got my original code out of the Cyrus examples.
I'm not sure what the solution is - I think the check is valuable, though
it's probably possible to change it to backend onto a different database.
Unfortunately, I'm not an expert in Cyrus' SASL implementation.
Hope this explains what's going on at least.
Cheers
Matthew
--
Matthew Byng-Maddick <mbm@???> http://colondot.net/
(Please use this address to reply)
