> Did you select your canonuser Plugin?
>
> (sasl_)canon_user_plugin: the_name
Yes! And it even does its work, i.e. it does successfully canonicalize
usernames! At least with a very simple test szenario. Not yet really
what I am looking at implementing.
> And if and where you see something depends on the Context, where
> cyrus-sasl is used. Som Applications implement their own Log-Callback.
I am using it with Cyrus IMAPd. Might I have to change logging options
there as well? What I mean is: Are you saying that IMAPd (or another app
using libsasl2 might intercept logs from the SASL layer and decide not
to pass them on?
Regards,
Torsten
Andreas Winkelmann schrieb:
Am Sunday 01 October 2006 15:18 schrieb Torsten Schlabach:
> Remove the "sasl_ldapdb_uri" Option from your imapd.conf. If the
> ldapdb Plugin is installed, you should see an Error in your Log:
>
> imap[]: auxpropfunc error invalid parameter supplied
> imap[]: _sasl_plugin_load failed on sasl_auxprop_plug_init for plugin:
> ldapdb
Ok, that worked, thank you.
> (lib)ldapdb itself has no Output.
I see.
Maybe you could help with one more hint?
I am currently writing a canon_user plugin, and I would like it to have
some debugging output. I tried adding something like:
sparams->utils->log(NULL, SASL_LOG_ERR, "PaTTern ");
Looks ok.
Did you select your canonuser Plugin?
(sasl_)canon_user_plugin: the_name
And if and where you see something depends on the Context, where cyrus-sasl is
used. Som Applications implement their own Log-Callback.
but that output does not seem to show up anywhere.
