postfix-3.10.2

postfix/HISTORY

@@ -28966,9 +28966,9 @@ Apologies for any names omitted.
 	tls/tls_misc.c.
 
 	Bugfix (defect introduced: Postfix 3.4, date 20181113): a
-	server with multiple TLS certificates could report for a
+	server with multiple TLS certificates could report, for a
-	resumed TLS session, in logging and Received: message
+	resumed TLS session, the wrong server-signature and
-	headers, the wrong server-signature and server-digest names.
+	server-digest names in logging and Received: message headers.
 	Viktor Dukhovni. File: tls/tls_misc.c.
 
 20250213
@@ -28982,4 +28982,50 @@ Apologies for any names omitted.
 	tls_config_file description. File: proto/postconf.proto.
 	The unused parameters will be deleted in Postfix 3.11.
 
-	Postfix 3.10 code freeze.
+20250215
+
+	Safety: added a TLSRPT library version check. Log a warning
+	when the run-time TLSRPT library API version is not compatible
+	with the build-time TLSRPT API version, where 'compatible'
+	is defined according to the rules of semantic versioning.
+	This completes the Postfix 3.10 stable release.
+
+20250216
+
+	Bugfix (defect introduced: Postfix 3.10): Postfix SMTP
+	client segfault while reporting a 'certificate expired'
+	event. Problem reported by Oemer Gueven. File: tls/tls_verify.c.
+
+20250221
+
+	Bugfix (defect introduced: 20250210): a recent 'fix' for the
+	default smtp_tls_dane_insecure_mx_policy setting resulted in
+	unnecessary 'dnssec_probe' warnings, on systems that disable
+	DNSSEC lookups (the default). File: smtp/smtp_addr.c.
+
+20250223
+
+	Documentation: updated link to Dovecot documentation. File:
+	proto/SASL_README.
+
+20250227
+
+	Improved and corrected error messages when converting (host
+	or service) information to (symbolic text, numerical text,
+	or binary) form. File: util/myaddrinfo.c.
+
+20250304
+
+	Bugfix (defect introduced: Postfix 2.3, date 20051222): the
+	Dovecot auth client did not attempt to create a new connection
+	after an I/O error on an existing connection. Reported by
+	Oleksandr Kozmenko. File: xsasl/xsasl_dovecot_server.c.
+
+20250316
+
+	Bugfix (defect introduced: date 19991116): when appending
+	a setting to a main.cf or master.cf file that did not end
+	in a newline character, the "postconf -e" command did not
+	add an extra newline character before appending the new
+	setting, causing information to become garbled. Fix by
+	Michael Tokarev. File: postconf/postconf_edit.c.

postfix/RELEASE_NOTES

@@ -1,12 +1,12 @@
-This is the Postfix 3.10 experimental release.
+This is the Postfix 3.10 stable release.
 
-The stable Postfix release is called postfix-3.9.x where 3=major
+The stable Postfix release is called postfix-3.10.x where 3=major
-release number, 9=minor release number, x=patchlevel. The stable
+release number, 10=minor release number, x=patchlevel. The stable
 release never changes except for patches that address bugs or
 emergencies. Patches change the patchlevel and the release date.
 
 New features are developed in snapshot releases. These are called
-postfix-3.10-yyyymmdd where yyyymmdd is the release date (yyyy=year,
+postfix-3.11-yyyymmdd where yyyymmdd is the release date (yyyy=year,
 mm=month, dd=day). Patches are never issued for snapshot releases;
 instead, a new snapshot is released.
 
@@ -25,63 +25,74 @@ now also distributed with the more recent Eclipse Public License
 (EPL) 2.0. Recipients can choose to take the software under the
 license of their choice. Those who are more comfortable with the
 IPL can continue with that license.
- 
-[Feature 20250117]
 
-Support for the RFC 8689 "TLS-Required: no" message header to request
+Major changes - tls
-delivery of messages such as TLSRPT summaries even if the preferred
+-------------------
-TLS security policy cannot be enforced. This limits the Postfix
+
-SMTP client to "smtp_tls_security_level = may" which does not
+[Forward compatibility 20250212] Support for OpenSSL 3.5 post-quantum
-authenticate server certificates and which allows falling back to
+cryptography. To manage algorithm selection, OpenSSL introduces new
-plaintext.
+TLS group syntax that Postfix will not attempt to imitate. Instead,
+Postfix now allows the tls_eecdh_auto_curves and tls_ffdhe_auto_groups
+parameter values to have an empty value. When both are set empty,
+the algorithm selection can be managed through OpenSSL configuration.
+For more, look for "Post-quantum" in the postconf(5) manpage.
+
+[Feature 20250117] Support for the RFC 8689 "TLS-Required: no"
+message header to request delivery of messages such as TLSRPT
+summaries even if the preferred TLS security policy cannot be
+enforced. This limits the Postfix SMTP client to "smtp_tls_security_level
+= may" which does not authenticate server certificates and which
+allows falling back to plaintext.
 
 Support for the REQUIRETLS SMTP service extension remains future work.
 
-[Incompat 20250116]
+[Feature 20240926] Support for the TLSRPT protocol (defined in RFC
+8460). With this, a domain can publish a policy in DNS, and request
+daily summary reports for successful and failed SMTP-over-TLS
+connections to that domain's MX hosts.
 
-Postfix needs "postfix reload" after upgrade, because of a change in
+Postfix supports TLSRPT summaries for DANE (built-in) and MTA-STS
-the delivery agent protocol. If this step is skipped, Postfix delivery
+(via an smtp_tls_policy_maps plugin). For details, see TLSRPT_README.
-agents will log a warning:
 
-    unexpected attribute smtputf8 from xxx socket (expecting: sendopts)
+Major changes - privacy
+-----------------------
 
-where xxx is the delivery agent service name.
+[Feature 20250205] With "smtpd_hide_client_session = yes", the
+Postfix SMTP server generates a Received: header without client
+session info This setting may be used with the MUA submission
+services (port 465 and 587), but it must not be used with the MTA
+service (port 25).
 
-[Incompat 20250106]
+Depending on the number of recipients, a redacted Received: header
+has one of the following forms:
 
-The logging of the Milter 'quarantine' action has changed. Instead
+Received: by mail.example.com (Postfix) id postfix-queue-id
-of logging "milter triggers HOLD action", it logs the reason given
+        for <user@example.com>; Day, dd Mon yyyy hh:mm:ss tz-offset (zone)
-by a Milter application, or "default_action" if a Milter application
-was unavailable and the milter_default_action parameter or Milter
-"default_action" property specifies "quarantine".
 
-[Feature 20250106]
+Received: by mail.example.com (Postfix) id postfix-queue-id
+        Day, dd Mon yyyy hh:mm:ss tz-offset (zone)
 
-The Postfix Milter implementation now logs the reason for a 
+The redacted form hides that a message was received with SMTP, and
-'quarantine' action, instead of "milter triggers HOLD action".
+therefore it does not need to provide the information required by
+RFC 5321. It only has to satisfy RFC 5322.
 
-- If the quarantine action was requested by a Milter application,
+Major changes - rfc2047
-  Postfix will log the reason given by the application.
+-----------------------
 
-- If the quarantine action was requested with the "milter_default_action"
+[Feature 20250105] Support for automatic RFC 2047 encoding of
-  parameter setting or with a Milter "default_action" property,
+non-ASCII "full name" information in Postfix-generated From: message
-  Postfix will log "default_action".
+headers.  Encoding non-ASCII full names can avoid the need to use
-
+SMTPUTF8, and therefore can avoid incompatibility with sites that
-[Feature 20250105]
+do not support SMTPUTF8.
-
-Support for automatic RFC 2047 encoding of non-ASCII "full name"
-information in Postfix-generated From: message headers. Encoding
-non-ASCII full names can avoid the need to use SMTPUTF8, and therefore
-can avoid incompatibility with sites that do not support SMTPUTF8.
 
 The encoded result looks like "=?charset?Q?gibberish?=: for
 quoted-printable encoding, or "=?charset?B?gibberish?=" for base64
 encoding. Postfix uses quoted-printable for a full name that is
 short or mostly ASCII, and uses base64 otherwise.
 
-Background: when a message without a From: header is submitted with the
+Background: when a message without a From: header is submitted with
-Postfix sendmail(1) command, Postfix will add a From: header and will
+the Postfix sendmail(1) command, Postfix may add a From: header and
-try to use the sender's full name specified with the Postfix sendmail(1)
+use the sender's full name specified with the Postfix sendmail(1)
 "-F" option, with the sendmail(1) "NAME" environment variable, or
 with the GECOS field in the UNIX password database.
 
@@ -89,31 +100,101 @@ This introduces a new configuration parameter "full_name_encoding_charset"
 (default: utf8) which specifies the character set of the full name
 information in the Postfix sendmail(1) "-F" option or "NAME"
 environment variable, or in the GECOS field in the UNIX password
-database. The parameter value is also part of the encoded full name,
+database. The parameter value becomes part of the encoded full name,
 and informs a Mail User Agent how to display the decoded gibberish.
 
-[Incompat 20250105]
+Major changes - bugfix
+----------------------
 
-The SMTP server now logs the queue ID (or "NOQUEUE") when a connection
+[Incompat 20241130] The spawn(8) daemon failed to enforce the command
-ends abnormally (timeout, lost connection, or too many errors).
+time limit. It was sending the SIGKILL signal using the wrong
+effective UID and GID. The pipe(8) daemon has always done this
+right.
 
-[Feature 20250105]
+Major changes - database
+------------------------
 
-The SMTP server now logs the queue ID (or "NOQUEUE") when a connection
+[Feature 20250207] When mysql: or pgsql: configuration specifies
-ends abnormally (timeout, lost connection, or too many errors).
+a single host, assume that it is a load balancer and reconnect
+immediately after a single failure, instead of failing all requests
+for 60s.
 
-[Feature 20241104]
+[Feature 20250114] first/next iterator support for cdb: tables, and
+other cdb: table code cleanups by Michael Tokarev.
 
-The cleanup server now logs "queueid: canceled" when a message
+[Feature 20241024] In a pgsql: client configuration, the setting
-transaction is started but not completed. This provides a clear
+"dbname" is required, but ignored when the setting "hosts" contains
-signal to logfile collation tools.
+an URI with a database name.
 
-[Feature 20240926]
+[Feature 20241025] The Postfix pgsql: client configuration now
+allows any well-formed URI prefix as a pgsql: client connection
+target (the PostgreSQL URI parser decides what is allowed). The
+dbname setting is now optional if the hosts setting specifies only
+URIs.
 
-Support for the TLSRPT protocol (defined in RFC 8460). With this,
+Major changes - internal protocol
-an email receiving domain can publish a policy in DNS, and request
+---------------------------------
-daily summary reports for successful and failed SMTP-over-TLS
-connections to that domain's MX hosts.
 
-Postfix supports TLSRPT summaries for DANE (built-in) and MTA-STS
+[Incompat 20250116] Postfix needs "postfix reload" after upgrade,
-(via an smtp_tls_policy_maps plugin). For details, see TLSRPT_README.
+because of a change in the delivery agent protocol. If this step
+is skipped, Postfix delivery agents will log a warning:
+
+    unexpected attribute smtputf8 from xxx socket (expecting: sendopts)
+
+where xxx is the delivery agent service name.
+
+Major changes - milter
+----------------------
+
+[Incompat 20250106] The logging of the Milter 'quarantine' action
+has changed.  Instead of logging "milter triggers HOLD action", it
+logs the reason given by a Milter application, or "default_action"
+if a Milter application was unavailable and the milter_default_action
+parameter or per-Milter "default_action" property specifies
+"quarantine".
+
+[Feature 20250106] The Postfix Milter implementation now logs the
+reason for a 'quarantine' action, instead of "milter triggers HOLD
+action".
+
+- If the quarantine action was requested by a Milter application,
+  Postfix will log the reason given by the application.
+
+- If the quarantine action was requested with the "milter_default_action"
+  parameter setting or with a per-Milter "default_action" property,
+  Postfix will log "default_action".
+
+Major changes - logging
+-----------------------
+
+[Feature 20250106] The Postfix Milter implementation now logs the
+reason for a 'quarantine' action, instead of "milter triggers HOLD
+action".
+
+- If the quarantine action was requested by a Milter application,
+  Postfix will log the reason given by the application.
+
+- If the quarantine action was requested with the "milter_default_action"
+  parameter setting or with a per-Milter "default_action" property,
+  Postfix will log "default_action".
+
+[Incompat 20250105] The SMTP server now logs the queue ID (or
+"NOQUEUE") when a connection ends abnormally (timeout, lost connection,
+or too many errors).
+
+[Feature 20250105] The SMTP server now logs the queue ID (or
+"NOQUEUE") when a connection ends abnormally (timeout, lost connection,
+or too many errors).
+
+[Incompat 20241104] The cleanup server now logs "queueid: canceled"
+when a message transaction is started but not completed.
+
+[Feature 20241104] The cleanup server now logs "queueid: canceled"
+when a message transaction is started but not completed. This
+provides a clear signal to logfile collation tools.
+
+[Incompat 20241031] the Dovecot SASL client logging for "Invalid
+authentication mechanism" now includes the name of that mechanism.
+
+[Incompat 20241023] Postfix SMTP server 'reject' logging now shows
+the sasl_method, sasl_username, and sasl_sender if available.

postfix/html/SASL_README.html

@@ -178,7 +178,7 @@ later. </p>
 <p> Dovecot is a POP/IMAP server that has its own configuration to
 authenticate POP/IMAP clients. When the Postfix SMTP server uses
 Dovecot SASL, it reuses parts of this configuration.  Consult the
-<a href="https://wiki.dovecot.org">Dovecot documentation</a> for how
+<a href="https://doc.dovecot.org">Dovecot documentation</a> for how
 to configure and operate the Dovecot authentication server.  </p>
 
 <h4><a name="server_dovecot_comm">Postfix to Dovecot SASL communication</a></h4>

postfix/html/postconf.5.html

@@ -20119,13 +20119,11 @@ openssl.cnf:
     Groups = *X25519MLKEM768 / *X25519:X448 / P-256:P-384
 </pre>
 
-<p> Caution: It is typically best to just use the default group
+<p> Caution: It is typically best to just use the default OpenSSL
-settings, for which no $<a href="postconf.5.html#tls_config_file">tls_config_file</a> is required (you can set
+group settings, by setting "<a href="postconf.5.html#tls_config_file">tls_config_file</a> = none". Overly strict
-"<a href="postconf.5.html#tls_config_file">tls_config_file</a> = none", to avoid unwanted leakage of system-wide
+system-wide TLS settings will conflict with Postfix's opportunistic
-settings that strive to harden HTTPS against mostly browser-specific
+TLS, where being less restrictive is better than downgrading to
-security and privacy issues into Postfix use of opportunistic TLS,
+cleartext SMTP. </p>
-where they're they can be counterproductive, leading to downgrades
-to cleartext, rather than more "secure" TLS). </p>
 
 <p> This feature is available in Postfix &ge; 3.9, 3.8.1, 3.7.6,
 3.6.10, and 3.5.20. </p>

postfix/makedefs

@@ -975,7 +975,7 @@ case "$CC" in
 esac
 
 # Snapshot only.
-CCARGS="$CCARGS -DSNAPSHOT"
+#CCARGS="$CCARGS -DSNAPSHOT"
 
 # Non-production: needs thorough testing, or major changes are still
 # needed before the code stabilizes.

postfix/man/man5/postconf.5

@@ -13988,13 +13988,11 @@ openssl.cnf:
 .fi
 .ad
 .PP
-Caution: It is typically best to just use the default group
+Caution: It is typically best to just use the default OpenSSL
-settings, for which no $tls_config_file is required (you can set
+group settings, by setting "tls_config_file = none". Overly strict
-"tls_config_file = none", to avoid unwanted leakage of system\-wide
+system\-wide TLS settings will conflict with Postfix's opportunistic
-settings that strive to harden HTTPS against mostly browser\-specific
+TLS, where being less restrictive is better than downgrading to
-security and privacy issues into Postfix use of opportunistic TLS,
+cleartext SMTP.
-where they're they can be counterproductive, leading to downgrades
-to cleartext, rather than more "secure" TLS).
 .PP
 This feature is available in Postfix >= 3.9, 3.8.1, 3.7.6,
 3.6.10, and 3.5.20.

postfix/proto/SASL_README.html

@@ -178,7 +178,7 @@ later. </p>
 <p> Dovecot is a POP/IMAP server that has its own configuration to
 authenticate POP/IMAP clients. When the Postfix SMTP server uses
 Dovecot SASL, it reuses parts of this configuration.  Consult the
-<a href="https://wiki.dovecot.org">Dovecot documentation</a> for how
+<a href="https://doc.dovecot.org">Dovecot documentation</a> for how
 to configure and operate the Dovecot authentication server.  </p>
 
 <h4><a name="server_dovecot_comm">Postfix to Dovecot SASL communication</a></h4>

postfix/proto/postconf.proto

@@ -19245,13 +19245,11 @@ openssl.cnf:
     Groups = *X25519MLKEM768 / *X25519:X448 / P-256:P-384
 </pre>
 
-<p> Caution: It is typically best to just use the default group
+<p> Caution: It is typically best to just use the default OpenSSL
-settings, for which no $tls_config_file is required (you can set
+group settings, by setting "tls_config_file = none". Overly strict
-"tls_config_file = none", to avoid unwanted leakage of system-wide
+system-wide TLS settings will conflict with Postfix's opportunistic
-settings that strive to harden HTTPS against mostly browser-specific
+TLS, where being less restrictive is better than downgrading to
-security and privacy issues into Postfix use of opportunistic TLS,
+cleartext SMTP. </p>
-where they're they can be counterproductive, leading to downgrades
-to cleartext, rather than more "secure" TLS). </p>
 
 <p> This feature is available in Postfix &ge; 3.9, 3.8.1, 3.7.6,
 3.6.10, and 3.5.20. </p>

postfix/proto/stop.spell-history

@@ -100,3 +100,5 @@ Roessner
 bitflags
 Schulze
 tlspol
+Gueven
+Oemer

postfix/src/global/mail_version.h

@@ -20,8 +20,8 @@
   * Patches change both the patchlevel and the release date. Snapshots have no
   * patchlevel; they change the release date only.
   */
-#define MAIL_RELEASE_DATE	"20250215"
+#define MAIL_RELEASE_DATE	"20250422"
-#define MAIL_VERSION_NUMBER	"3.10"
+#define MAIL_VERSION_NUMBER	"3.10.2"
 
 #ifdef SNAPSHOT
 #define MAIL_VERSION_DATE	"-" MAIL_RELEASE_DATE

postfix/src/postconf/postconf_edit.c

@@ -113,8 +113,13 @@ static char *pcf_find_cf_info(VSTRING *buf, VSTREAM *dst)
 static char *pcf_next_cf_line(VSTRING *buf, VSTREAM *src, VSTREAM *dst, int *lineno)
 {
     char   *cp;
+    int     last_char;
 
-    while (vstring_get(buf, src) != VSTREAM_EOF) {
+    while ((last_char = vstring_get(buf, src)) != VSTREAM_EOF) {
+	if (last_char != '\n') {
+	    VSTRING_ADDCH(buf, '\n');
+	    VSTRING_TERMINATE(buf);
+	}
 	if (lineno)
 	    *lineno += 1;
 	if ((cp = pcf_find_cf_info(buf, dst)) != 0)

postfix/src/smtp/smtp_addr.c

@@ -299,7 +299,8 @@ static DNS_RR *smtp_addr_list(DNS_RR *mx_names, DSN_BUF *why)
     if (mx_names->dnssec_valid)
 	res_opt = RES_USE_DNSSEC;
 #ifdef USE_TLS
-    else if (smtp_tls_insecure_mx_policy > TLS_LEV_MAY)
+    else if (smtp_tls_insecure_mx_policy > TLS_LEV_MAY
+	     && smtp_dns_support == SMTP_DNS_DNSSEC)
 	res_opt = RES_USE_DNSSEC;
 #endif
 

postfix/src/smtpd/smtpd_peer.c

@@ -217,8 +217,13 @@ static int smtpd_peer_sockaddr_to_hostaddr(SMTPD_STATE *state)
 	 */
 	if ((aierr = sockaddr_to_hostaddr(sa, sa_length, &client_addr,
 					  &client_port, 0)) != 0)
-	    msg_fatal("%s: cannot convert client address/port to string: %s",
+	    msg_fatal("%s: cannot convert client sockaddr type %s length %ld "
-		      myname, MAI_STRERROR(aierr));
+		      "to string: %s", myname,
+#ifdef AF_INET6
+		      sa->sa_family == AF_INET6 ? "AF_INET6" :
+#endif
+		      sa->sa_family == AF_INET ? "AF_INET" : "other",
+		      (long) sa_length, MAI_STRERROR(aierr));
 	state->port = mystrdup(client_port.buf);
 
 	/*
@@ -299,9 +304,15 @@ static int smtpd_peer_sockaddr_to_hostaddr(SMTPD_STATE *state)
 					  state->dest_sockaddr_len,
 					  &server_addr,
 					  &server_port, 0)) != 0)
-	    msg_fatal("%s: cannot convert server address/port to string: %s",
+	    /* TODO: convert IPv4-in-IPv6 to IPv4 form. */
-		      myname, MAI_STRERROR(aierr));
+	    msg_fatal("%s: cannot convert server sockaddr type %s length %ld "
-	/* TODO: convert IPv4-in-IPv6 to IPv4 form. */
+		    "to string: %s", myname,
+#ifdef AF_INET6
+		   state->dest_sockaddr.ss_family == AF_INET6 ? "AF_INET6" :
+#endif
+		      state->dest_sockaddr.ss_family == AF_INET ? "AF_INET" :
+		      "other", (long) state->dest_sockaddr_len,
+		      MAI_STRERROR(aierr));
 	state->dest_addr = mystrdup(server_addr.buf);
 	state->dest_port = mystrdup(server_port.buf);
 
@@ -409,8 +420,8 @@ static void smtpd_peer_hostaddr_to_sockaddr(SMTPD_STATE *state)
 
     if ((aierr = hostaddr_to_sockaddr(state->addr, state->port,
 				      SOCK_STREAM, &res)) != 0)
-	msg_fatal("%s: cannot convert client address/port to string: %s",
+	msg_fatal("%s: cannot convert client address '%s' port '%s' to binary: %s",
-		  myname, MAI_STRERROR(aierr));
+		  myname, state->addr, state->port, MAI_STRERROR(aierr));
     if (res->ai_addrlen > sizeof(state->sockaddr))
 	msg_panic("%s: address length > struct sockaddr_storage", myname);
     memcpy((void *) &(state->sockaddr), res->ai_addr, res->ai_addrlen);

postfix/src/tls/tls_verify.c

@@ -315,7 +315,7 @@ void    tls_log_verify_error(TLS_SESS_STATE *TLScontext,
 	if (tlsrpt)
 	    trw_report_failure(tlsrpt, TLSRPT_CERTIFICATE_EXPIRED,
 			        /* additional_info= */ (char *) 0,
-			        /* failure_code= */ (char *) 8);
+			        /* failure_code= */ (char *) 0);
 #endif
 	break;
     case X509_V_ERR_INVALID_PURPOSE:

postfix/src/tls/tlsrpt_wrapper.c

@@ -252,6 +252,13 @@
 #include <tlsrpt.h>
 #endif
 
+#if !defined(TLSRPT_PREREQ)
+#define TLSRPT_PREREQ(maj, min) \
+    (defined(TLSRPT_VERSION_MAJOR) && \
+	((TLSRPT_VERSION_MAJOR << 16) + TLSRPT_VERSION_MINOR >= \
+	    ((maj) << 16) + (min)))
+#endif
+
  /*
   * Utility library.
   */
@@ -321,6 +328,15 @@ TLSRPT_WRAPPER *trw_create(const char *rpt_socket_name,
 		 myname, rpt_socket_name, rpt_policy_domain,
 		 rpt_policy_string, skip_reused_hs);
 
+#if TLSRPT_PREREQ(0, 6)
+    if (tlsrpt_version_check(TLSRPT_VERSION_MAJOR, TLSRPT_VERSION_MINOR,
+			     TLSRPT_VERSION_PATCH) == 0)
+	msg_warn("run-time library vs. compile-time header version mismatch: "
+		 "libtlsrpt API version '%s' is not compatible with "
+		 "libtlsrpt API version '%s' ", tlsrpt_version(),
+		 TLSRPT_VERSION_STRING);
+#endif
+
     /*
      * memset() is not portable for pointer etc. types.
      */

postfix/src/xsasl/xsasl_dovecot_server.c

@@ -617,6 +617,7 @@ static int xsasl_dovecot_handle_reply(XSASL_DOVECOT_SERVER *server,
     }
 
     vstring_strcpy(reply, "Connection lost to authentication server");
+    xsasl_dovecot_server_disconnect(server->impl);
     return XSASL_AUTH_TEMP;
 }
 
@@ -707,6 +708,7 @@ int     xsasl_dovecot_server_first(XSASL_SERVER *xp, const char *sasl_method,
 
 	if (i == 1) {
 	    vstring_strcpy(reply, "Can't connect to authentication server");
+	    xsasl_dovecot_server_disconnect(server->impl);
 	    return XSASL_AUTH_TEMP;
 	}
 
@@ -735,6 +737,7 @@ static int xsasl_dovecot_server_next(XSASL_SERVER *xp, const char *request,
 		    "CONT\t%u\t%s\n", server->last_request_id, request);
     if (vstream_fflush(server->impl->sasl_stream) == VSTREAM_EOF) {
 	vstring_strcpy(reply, "Connection lost to authentication server");
+	xsasl_dovecot_server_disconnect(server->impl);
 	return XSASL_AUTH_TEMP;
     }
     return xsasl_dovecot_handle_reply(server, reply);