Re: [PATCH] Re: cyrus saslauthd error handling

2016-04-07 Thread Wietse Venema
Benning, Markus: > vstring_strcpy(reply, xsasl_cyrus_strerror(sasl_status)); > switch (sasl_status) { > + case SASL_FAIL: > + case SASL_NOMEM: > case SASL_TRYAGAIN: > case SASL_UNAVAIL: > return XSASL_AUTH_TEMP; Fixed in Postfix 3.2.

[PATCH] Re: cyrus saslauthd error handling

2016-04-07 Thread Benning, Markus
On 2016-04-06 16:19, Benning, Markus wrote: In sasl.h: #define SASL_FAIL -1 /* generic failure */ Could this one be added to the AUTH_TEMP case? I took a look at the cyrus-sasl code in lib/checkpw.c and most error cases there return SASL_FAIL. Wrong credentails return

Re: cyrus saslauthd error handling

2016-04-06 Thread Benning, Markus
On 2016-04-06 16:19, Benning, Markus wrote: In sasl.h: #define SASL_FAIL -1 /* generic failure */ Could this one be added to the AUTH_TEMP case? Could it be that the libsasl uses SASL_FAIL also in case of a wrong password? In this case i think it would be an error in libsasl. It

cyrus saslauthd error handling

2016-04-06 Thread Benning, Markus
Hi, when i use a cyrus saslauthd: pwcheck_method: saslauthd mech_list: plain login saslauthd_path: /var/run/kokolores/mux And the saslauthd is not running. Then the socket /var/run/kokolores/mux does not exist and postfix returns 535 5.7.8 Error: authentication failed: generic failure