search for: xsasl

...org/dovecot-2.0/rev/fe8e82b5bff9 Thanks for that. is it save to use smtpd_sasl_path = inet:localhost:1434 in postfix's main.cf? there are some warnings in log: "when SASL type is "dovecot", SASL path "inet:localhost:1434" should be a socket pathname" ( Datei src/xsasl/xsasl_dovecot_server.c ) Thanks, Hajo

...ility and compatibility would you consider > accepting a patch? Yes. No promise, though, that it will be adopted. One consideration is that Postfix does not talk directly to Dovecot, but instead talks to an abstraction layer that is used for both Cyrus SASL and for Dovecot. Obviously, that XSASL abstraction layer must not be made specific to the underlying Cyrus SASL or Dovecot implementation. The solution therefore is not to extend XSASL functions with one extra argument for each Dovecot feature. Apart from being Dovecot-specific, functions with many parameters are difficult to update co...

Hi, does anyone have at working Perl example of how to use the auth protocol with Perl (I'm planing on making a dovecot auth plugin for qpsmtpd but it would a lot easier to reuse somebody elses code :)) tia, -- Allan Joergensen - http://nowhere.dk/ "All right, so it's impossible. How long will it take?" -------------- next part -------------- A non-text attachment was

Hello dovecot, I want to have all authorization in one place and don't use Cyrus-SASL. I cobfigure postfix 2.3.3 to use dovecot-SASL. I have next lines in main.cf: smtpd_sasl_security_options = noplaintext,noanonymous smtpd_sasl_tls_security_options = noanonymous But PLAIN and LOGIN are advertised by postfix :( Is it bug of postfix or dovecot-auth? I don't want to disable