policy plugin, deprecated the policy_ttl attribute. File:
proto/TLSRPT_README.html.
+20250207
+
+ Performance: when a mysql: or pgsql: configuration specifies
+ a single host, assume that it is a load balancer and reconnect
+ immediately after a single failure, instead of failing all
+ requests for 60s. Files: global/dict_pgsql.c, global/dict_mysql.c,
+ proto/pgsql_table, proto/mysql_table.
+
Postfix 3.10 code freeze.
server_host = ldap.example.com:1444
- NOTE: if "server_host" specifies one load balancer and no alter-
- native servers, specify the load balancer multiple times in the
- "server_host" line. Without the duplicate info, the Postfix LDAP
- client would not reconnect immediately to the same load balancer
- after an LDAP server failure.
+ NOTE: this client will reconnect immediately after a single
+ failure, and will fail a lookup request after a second attempt
+ also fails.
With OpenLDAP, a (list of) LDAP URLs can be used to specify both
the hostname(s) and the port(s):
TCP you have to specify
hosts = 127.0.0.1
- NOTE: if the <b>hosts</b> setting specifies one load balancer and no
- alternative servers, specify the load balancer multiple times.
- Without the duplicate info, the Postfix MySQL client would not
- reconnect immediately to the same load balancer after a request
- failure.
+ NOTE: if the <b>hosts</b> setting specifies one server, this client
+ assumes that the target is a load balancer and will reconnect
+ immediately after a single failure, instead of failing all
+ requests temporarily. With older versions of this client, spec-
+ ify the same server twice.
<b>user</b>
The number of seconds that a database connection will be skipped
after an error.
- NOTE: if the <b>hosts</b> setting specifies one load balancer and no
- alternative servers, specify the load balancer multiple times.
- Without the duplicate info, the Postfix MySQL client would not
- reconnect immediately to the same load balancer after a request
- failure.
+ NOTE: if the <b>hosts</b> setting specifies one server, this client
+ assumes that the target is a load balancer and will reconnect
+ immediately after a single failure, instead of failing all
+ requests temporarily. With older versions of this client, spec-
+ ify the same server twice.
This feature is available in Postfix 3.9 and later.
URI, the Postfix PostgreSQL client will ignore the <b>dbname</b>, <b>user</b>,
and <b>password</b> settings for that connection.
- NOTE: if the <b>hosts</b> setting specifies one load balancer and no
- alternative servers, specify the load balancer multiple times.
- Without the duplicate info, the Postfix PostgreSQL client would
- not reconnect immediately to the same load balancer after a
- request failure.
+ NOTE: if the <b>hosts</b> setting specifies one server, this client
+ assumes that the target is a load balancer and will reconnect
+ immediately after a single failure, instead of failing all
+ requests temporarily. With older versions of this client, spec-
+ ify the same server twice.
<b>user</b>
The number of seconds that a database connection will be skipped
after an error.
- NOTE: if the <b>hosts</b> setting specifies one load balancer and no
- alternative servers, specify the load balancer multiple times.
- Without the duplicate info, the Postfix PostgreSQL client would
- not reconnect immediately to the same load balancer after a
- request failure.
+ NOTE: if the <b>hosts</b> setting specifies one server, this client
+ assumes that the target is a load balancer and will reconnect
+ immediately after a single failure, instead of failing all
+ requests temporarily. With older versions of this client, spec-
+ ify the same server twice.
This feature is available in Postfix 3.9 and later.
server_host = ldap.example.com:1444
.fi
-NOTE: if "server_host" specifies one load balancer and no
-alternative servers, specify the load balancer multiple
-times in the "server_host" line. Without the duplicate info,
-the Postfix LDAP client would not reconnect immediately to
-the same load balancer after an LDAP server failure.
+NOTE: this client will reconnect immediately after a single
+failure, and will fail a lookup request after a second attempt
+also fails.
With OpenLDAP, a (list of) LDAP URLs can be used to specify both
the hostname(s) and the port(s):
hosts = 127.0.0.1
.fi
-NOTE: if the \fBhosts\fR setting specifies one load balancer
-and no alternative servers, specify the load balancer multiple
-times. Without the duplicate info, the Postfix MySQL client
-would not reconnect immediately to the same load balancer after
-a request failure.
+NOTE: if the \fBhosts\fR setting specifies one server, this client
+assumes that the target is a load balancer and will reconnect
+immediately after a single failure, instead of failing all
+requests temporarily. With older versions of this client,
+specify the same server twice.
.IP "\fBuser\fR"
.IP "\fBpassword\fR"
The user name and password to log into the mysql server.
The number of seconds that a database connection will be
skipped after an error.
-NOTE: if the \fBhosts\fR setting specifies one load balancer
-and no alternative servers, specify the load balancer multiple
-times. Without the duplicate info, the Postfix MySQL client
-would not reconnect immediately to the same load balancer after
-a request failure.
+NOTE: if the \fBhosts\fR setting specifies one server, this client
+assumes that the target is a load balancer and will reconnect
+immediately after a single failure, instead of failing all
+requests temporarily. With older versions of this client,
+specify the same server twice.
This feature is available in Postfix 3.9 and later.
.IP "\fBquery\fR"
URI, the Postfix PostgreSQL client will ignore the \fBdbname\fR,
\fBuser\fR, and \fBpassword\fR settings for that connection.
-NOTE: if the \fBhosts\fR setting specifies one load balancer
-and no alternative servers, specify the load balancer multiple
-times. Without the duplicate info, the Postfix PostgreSQL client
-would not reconnect immediately to the same load balancer after
-a request failure.
+NOTE: if the \fBhosts\fR setting specifies one server, this client
+assumes that the target is a load balancer and will reconnect
+immediately after a single failure, instead of failing all
+requests temporarily. With older versions of this client,
+specify the same server twice.
.IP "\fBuser\fR"
.IP "\fBpassword\fR"
The user name and password to log into the pgsql server.
The number of seconds that a database connection will be
skipped after an error.
-NOTE: if the \fBhosts\fR setting specifies one load balancer
-and no alternative servers, specify the load balancer multiple
-times. Without the duplicate info, the Postfix PostgreSQL client
-would not reconnect immediately to the same load balancer after
-a request failure.
+NOTE: if the \fBhosts\fR setting specifies one server, this client
+assumes that the target is a load balancer and will reconnect
+immediately after a single failure, instead of failing all
+requests temporarily. With older versions of this client,
+specify the same server twice.
This feature is available in Postfix 3.9 and later.
.IP "\fBquery\fR"
# server_host = ldap.example.com:1444
# .fi
#
-# NOTE: if "server_host" specifies one load balancer and no
-# alternative servers, specify the load balancer multiple
-# times in the "server_host" line. Without the duplicate info,
-# the Postfix LDAP client would not reconnect immediately to
-# the same load balancer after an LDAP server failure.
+# NOTE: this client will reconnect immediately after a single
+# failure, and will fail a lookup request after a second attempt
+# also fails.
#
# With OpenLDAP, a (list of) LDAP URLs can be used to specify both
# the hostname(s) and the port(s):
# hosts = 127.0.0.1
# .fi
#
-# NOTE: if the \fBhosts\fR setting specifies one load balancer
-# and no alternative servers, specify the load balancer multiple
-# times. Without the duplicate info, the Postfix MySQL client
-# would not reconnect immediately to the same load balancer after
-# a request failure.
+# NOTE: if the \fBhosts\fR setting specifies one server, this client
+# assumes that the target is a load balancer and will reconnect
+# immediately after a single failure, instead of failing all
+# requests temporarily. With older versions of this client,
+# specify the same server twice.
# .IP "\fBuser\fR"
# .IP "\fBpassword\fR"
# The user name and password to log into the mysql server.
# The number of seconds that a database connection will be
# skipped after an error.
#
-# NOTE: if the \fBhosts\fR setting specifies one load balancer
-# and no alternative servers, specify the load balancer multiple
-# times. Without the duplicate info, the Postfix MySQL client
-# would not reconnect immediately to the same load balancer after
-# a request failure.
+# NOTE: if the \fBhosts\fR setting specifies one server, this client
+# assumes that the target is a load balancer and will reconnect
+# immediately after a single failure, instead of failing all
+# requests temporarily. With older versions of this client,
+# specify the same server twice.
#
# This feature is available in Postfix 3.9 and later.
# .IP "\fBquery\fR"
# URI, the Postfix PostgreSQL client will ignore the \fBdbname\fR,
# \fBuser\fR, and \fBpassword\fR settings for that connection.
#
-# NOTE: if the \fBhosts\fR setting specifies one load balancer
-# and no alternative servers, specify the load balancer multiple
-# times. Without the duplicate info, the Postfix PostgreSQL client
-# would not reconnect immediately to the same load balancer after
-# a request failure.
+# NOTE: if the \fBhosts\fR setting specifies one server, this client
+# assumes that the target is a load balancer and will reconnect
+# immediately after a single failure, instead of failing all
+# requests temporarily. With older versions of this client,
+# specify the same server twice.
# .IP "\fBuser\fR"
# .IP "\fBpassword\fR"
# The user name and password to log into the pgsql server.
# The number of seconds that a database connection will be
# skipped after an error.
#
-# NOTE: if the \fBhosts\fR setting specifies one load balancer
-# and no alternative servers, specify the load balancer multiple
-# times. Without the duplicate info, the Postfix PostgreSQL client
-# would not reconnect immediately to the same load balancer after
-# a request failure.
+# NOTE: if the \fBhosts\fR setting specifies one server, this client
+# assumes that the target is a load balancer and will reconnect
+# immediately after a single failure, instead of failing all
+# requests temporarily. With older versions of this client,
+# specify the same server twice.
#
# This feature is available in Postfix 3.9 and later.
# .IP "\fBquery\fR"
msg_info("%s: %s: no hostnames specified, defaulting to '%s'",
myname, mysqlcf, dict_mysql->hosts->argv[0]);
}
+ /* Don't blacklist the load balancer! */
+ if (dict_mysql->hosts->argc == 1)
+ argv_add(dict_mysql->hosts, dict_mysql->hosts->argv[0], (char *) 0);
myfree(hosts);
}
msg_info("%s: %s: no hostnames specified, defaulting to '%s'",
myname, pgsqlcf, dict_pgsql->hosts->argv[0]);
}
+ /* Don't blacklist the load balancer! */
+ if (dict_pgsql->hosts->argc == 1)
+ argv_add(dict_pgsql->hosts, dict_pgsql->hosts->argv[0], (char *) 0);
myfree(hosts);
}
* Patches change both the patchlevel and the release date. Snapshots have no
* patchlevel; they change the release date only.
*/
-#define MAIL_RELEASE_DATE "20250206"
+#define MAIL_RELEASE_DATE "20250207"
#define MAIL_VERSION_NUMBER "3.10"
#ifdef SNAPSHOT