next stable release (expected by the end of January). Experimental releases
are now labeled 2.6-* but we'll track the 2.5.0 release candidates for now and
switch to 2.6 snapshots later.
Lots of changes, see HISTORY/RELEASES_NOTES for details.
Ok with martti.
default (this doesn't actually depend on Dovecot for building, the code is
shipped with Postfix).
Set the default value for smtpd_sasl_type to "dovecot" unless cyrus SASL is
enabled, too. This ensures backwards compatibility for most cases.
Ok with martti, joerg.
20061017
Cleanup: removed spurious warning when the cleanup server
attempts to bounce mail with soft_bounce=yes. Problem
reported by Ralf Hildebrandt. File: cleanup/cleanup_bounce.c.
Bugfix: null pointer bug when receiving a non-protocol
response on a cached SMTP/LMTP connection. Report by Brian
Kantor. Fix by Victor Duchovni. File: smtp/smtp_reuse.c.
in post-extract.
I exchanges few mails with Wietse and he refused to fix the "==" lines and
instructed me to simply remove the offending file. Instead of having a patch
for a file which is not used by pkgsrc I think it makes sense to remove it.
20060217
Bugfix: don't terminate with a non-standard exit status
when the pipe-to-command feature has a problem before it
executes the command. File: global/pipe_command.c.
20060223
Bugfix: detect integer overflow when multiplying time values
with non-trivial time units. File: global/conv_time.c.
20060307
Bugfix: reset the msg_cleanup() fatal error handler in child
processes. See also change 20060217. Files: postlock/postlock.c,
master/multi_server.c, global/mail_run.c, util/vstream_popen.c.
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
Postfix now preserves uppercase information while mapping addresses
with canonical, virtual, relocated or generic maps; this happens
even with $number substitutions in regular expression maps. However,
the local(8) and virtual(8) delivery agents still fold addresses
to lower case.
By default, Postfix now folds the search string to lowercase only
with tables that have fixed-case lookup fields such as btree:,
hash:, dbm:, ldap:, or *sql:. The search string is no longer case
folded with tables whose lookup fields can match both upper or lower
case, such as regexp:, pcre:, or cidr:.
For safety reasons, Postfix no longer allows $number substitution
in regexp: or pcre: transport tables or per-sender relayhost tables.
Postfix snapshot 20051220 provides a plug-in architecture for SASL
authentication. With this, Postfix can support multiple SASL
implementations without source code patches.
Incompatibility with snapshot 20051220
======================================
The Postfix-with-Cyrus-SASL build procedure has changed. You now
need to specify -DUSE_CYRUS_SASL in addition to -DUSE_SASL_AUTH or
else you end up without any Cyrus SASL support. The error messages
are:
unsupported SASL server implementation: cyrus
unsupported SASL client implementation: cyrus
Major changes with snapshot 20051220
====================================
Plug-in support for SASL authentication in the SMTP server and in
the SMTP+LMTP client. With this, Postfix can support multiple SASL
implementations without source code patches. Some distributors may
even make SASL support a run-time linking option, just like they
do with Postfix lookup tables.
Hints and tips for plug-in developers are in the xsasl/README file.
For backwards compatibility the default plug-in type is Cyrus SASL,
so everything should behave like it did before. Some error messages
are slightly different, but these are generally improvements.
The "postconf -a" command shows what plug-in implementations are
available for the SMTP server, and "postconf -A" does the same for
the SMTP+LMTP client. Plug-in implementations are selected with
the smtpd_sasl_type, smtp_sasl_type and lmtp_sasl_type configuration
parameters.
Other new configuration parameters are smtpd_sasl_path, smtp_sasl_path
and lmtp_sasl_path. These are better left alone; they are introduced
for the convenience of other SASL implementations.
