Postfix snapshot 20041023 available
[email protected] (Wietse Venema) Sat, 23 Oct 2004 21:35:37 -0400 (EDT)
| Newsgroups | gmane.mail.postfix.announce |
|---|---|
| Message-ID | <20041024013537.DCF5DBC16F__48054.9791166142$1098581913$gmane$org@spike.porcupine.org> |
Postfix snapshot 20041023 is expected to be the last one before
STARTTLS support is merged into the main source tree. The current
TLS patch for snapshot 20040829 has a problem and should not be
used.
New features are released first as Postfix snapshots. The stable
Postfix 2.1 release does not change except for bugfixes. Once the
new code stops changing the snapshots evolve into the official
Postfix 2.2 release.
- The NIS+ client by Geoff Gibbs is now part of the Postfix source
tree. Details are given in the nisplus_table(5) manual page.
- By default, Postfix no longer appends its own domain to
addresses in message headers from remote clients. Thus, spam from
poorly written software no longer looks like it came from a local
user.
Postfix either does not rewrite remote message headers at all,
or it rewrites headers and appends the domain name that is
specified with the remote_header_rewrite_domain parameter (like
"domain.invalid").
Full details are given in ADDRESS_REWRITING_README, and in the
postconf(5) manual. For best results, point your browser at the
ADDRESS_REWRITING_README.html file and navigate to the section
titled "To rewrite or not to rewrite, or to label as invalid".
You can also find a bit more information in the HISTORY and
RELEASE_NOTES sections at the end of this announcement.
Available soon from the download mirrors listed at http://www.postfix.org:
340820 Oct 23 21:04 postfix-2.2-20041023.HISTORY
11259 Oct 23 21:14 postfix-2.2-20041023.RELEASE_NOTES
2108383 Oct 23 21:14 postfix-2.2-20041023.tar.gz
152 Oct 23 21:14 postfix-2.2-20041023.tar.gz.sig
Happy Postfixing.
Wietse
HISTORY file:
=============
20041014-23
Postfix no longer appends the local domain to header
addresses from remote clients. Instead, Postfix either
does not rewrite those headers at all, or it appends the
domain specified with the new remote_header_rewrite_domain
parameter.
Postfix still appends $@myorigin or .$mydomain to headers
from the Postfix sendmail command, or from clients listed
with the new local_header_rewrite_clients parameter (default:
permit_mynetworks, permit_sasl_authenticated).
These changes affect the SMTP server (including XFORWARD
support), the cleanup server (do or don't rewrite headers),
the trivial-rewrite server (append local domain or surrogate
remote domain to incomplete addresses), the queue manager
(send additional attributes to delivery agents), the LMTP
and SMTP clients (XFORWARD support), and the local delivery
agent (preserve XFORWARD attributes when forwarding mail).
20041016
Bugfix: attr_clnt_request() did not properly skip hash
table arguments. Luc Pardon, Skopos Consulting. File:
util/attr_clnt.c.
20041018
The NIS+ module by Geoff Gibbs is now part of Postfix.
Files: util/dict_nisplus.c, proto/nisplus_table.
20041019
Support for Errors-To: is permanently removed.
20041022
Bugfix: "smtp_connection_cache_on_demand=no" could crash
the SMTP client. File: smtp/smtp_connect.c.
Robustness: extra sanity checks. Files: util/dict_db.c,
util/dict_dbm.c.
RELEASE_NOTES:
==============
Incompatible changes with snapshot Postfix-2.2-20041023
=======================================================
You must reload or stop/start Postfix, because the queue manager
to delivery agent protocol has changed. If you forget this, mail
will remain queued until the queue manager is restarted.
Support for the non-standard Errors-To: return addresses is removed.
It was already disabled by default with Postfix version 2.1. Since
Errors-To: is non-standard, there was no guarantee that it would
have effect with other MTAs.
Major changes with snapshot Postfix-2.2-20041023
================================================
The NIS+ client by Geoff Gibbs is now part of the Postfix source
tree. Details are given in the nisplus_table(5) manual page.
By default, Postfix no longer appends its own domain to addresses
in message headers from remote clients. Thus, spam from poorly
written software no longer looks like it came from a local user.
Postfix either does not rewrite remote message headers at all, or
it rewrites headers and appends the domain name that is specified
with the remote_header_rewrite_domain parameter (like "domain.invalid").
To get the behavior of earlier Postfix versions (always append
Postfix's own domain to incomplete addresses in message headers)
specify:
/etc/postfix/main.cf:
local_header_rewrite_clients = static:all
Postfix always appends its own domain information to addresses in
message headers from Postfix sendmail and from local SMTP clients.
By default, Postfix considers an SMTP client local (and thus updates
message header addresses with the Postfix's own domain) when the
client IP address matches mynetworks, or when the client is SASL
or TLS authenticated.
If you want to include other clients via a pop-before-smtp table,
then you have to specify that via the new local_header_rewrite_clients
parameter:
/etc/postfix/main.cf:
local_header_rewrite_clients = permit_mynetworks,
permit_sasl_authenticated, permit_tls_clientcerts,
check_address_map hash:/etc/postfix/pop-before-smtp
As before, Postfix appends local domain information to envelope
addresses (as opposed to header addresses), because an unqualified
envelope address is effectively local for the purpose of delivery,
and for the purpose of replying to it.
Full details are given in ADDRESS_REWRITING_README, and in the
postconf(5) manual. For best results, point your browser at the
ADDRESS_REWRITING_README.html file and navigate to the section
titled "To rewrite or not to rewrite, or to label as invalid".