Revert previous SASL fix (wrong approach)
authorPeter Maydell <pmaydell@chiark.greenend.org.uk>
Tue, 29 Apr 2008 20:53:33 +0000 (20:53 +0000)
committerPeter Maydell <pmaydell@chiark.greenend.org.uk>
Tue, 29 Apr 2008 20:53:33 +0000 (20:53 +0000)
ChangeLog
mts/smtp/smtp.c

index 046a118..9a7b310 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,10 @@
 2008-04-29  Peter Maydell  <pmaydell@chiark.greenend.org.uk>
 
+       * Revert previous attempt at fix for SASL issue as it
+       is the wrong approach.
+
+2008-04-29  Peter Maydell  <pmaydell@chiark.greenend.org.uk>
+
        * Cope with sasl_decode64() returning SASL_CONTINUE, as
        happens with newer sasl libraries and LOGIN auth.
 
index 9527a5e..1ab027f 100644 (file)
@@ -1246,7 +1246,7 @@ sm_auth_sasl(char *user, char *mechlist, char *host)
            result = sasl_decode64(sm_reply.text, sm_reply.length,
                                   outbuf, sizeof(outbuf), &outlen);
        
-           if (result != SASL_OK && result != SASL_CONTINUE) {
+           if (result != SASL_OK) {
                smtalk(SM_AUTH, "*");
                sm_ierror("SASL base64 decode failed: %s",
                          sasl_errstring(result, NULL, NULL));