Changelog for
postfix-debuginfo-2.5.6-5.1.i586.rpm :
Wed Mar 17 13:00:00 2010 varkolyAATTsuse.de
- bnc#589077 - postfix config will not be written correctly with autoyast install
Fri Mar 12 13:00:00 2010 varkolyAATTsuse.de
- Since POSTFIX_SMTP_TLS_CLIENT is ternary the SuSEconfig.postfix
script had to been adapted too.
Tue Mar 9 13:00:00 2010 varkolyAATTsuse.de
- bnc#559145 - Changed Domain name not reflected when sending mail
First /var/run/dhcp-hostname will be evaluated
Thu Jan 28 13:00:00 2010 varkolyAATTsuse.de
- bnc#559145- Changed Domain name not reflected when sending mail
Now POSTFIX_SMTP_TLS_CLIENT is ternary : no yes must
Mon Jan 12 13:00:00 2009 varkolyAATTsuse.de
- bnc#465165 - postfix src package
Fri Jan 9 13:00:00 2009 varkolyAATTsuse.de
- bnc#464869 - SuSEconfig.postfix causes DNS lookup
- bnc#460442 - amavisd-new and Postfix need fqdn-hostname in \"uname -n\"
Mon Jan 5 13:00:00 2009 varkolyAATTsuse.de
- update to 2.5.6
- The SMTP server did not ask for a client certificate
with \"smtpd_tls_req_ccert = yes\". Reported by Rob Foehl.
- Avoid reduced TCP performance when reusing an SMTP connection
with a larger than 4096-byte TCP MSS value. In practice, this
could happen only with loopback (localhost) connections.
Sun Nov 16 13:00:00 2008 varkolyAATTsuse.de
- (bnc#442456) - chrooted postfix and saslauthd
Tue Nov 4 13:00:00 2008 roAATTsuse.de
- fix build
Tue Nov 4 13:00:00 2008 varkolyAATTsuse.de
- upgrade must not be executed during installation
Tue Oct 14 14:00:00 2008 varkolyAATTsuse.de
- (bnc#403976) - permissions on /var/lib/postfix changed
- (bnc#433916) - postfix should be splitted into postfix and postfix-doc
Thu Sep 11 14:00:00 2008 varkolyAATTsuse.de
- (bnc#415216) - Postfix RPM Install Displays Multiple Warnings
- clean up spec file
Tue Sep 9 14:00:00 2008 varkolyAATTsuse.de
- Update to Version 2.5 patchlevel 5
* Bugfix (introduced Postfix 2.4): epoll file descriptor leak.
With Postfix >= 2.4 on Linux >= 2.6, Postfix has an epoll
file descriptor leak when it executes non-Postfix commands
in, for example, user-controlled $HOME/.forward files.
* Security: some systems have changed their link() semantics,
and will hardlink a symlink, contrary to POSIX and XPG4.
Sebastian Krahmer, SuSE. File: util/safe_open.c.
The solution introduces the following incompatible change:
when the target of mail delivery is a symlink, the parent
directory of that symlink must now be writable by root only
(in addition to the already existing requirement that the
symlink itself is owned by root). This change will break
legitimate configurations that deliver mail to a symbolic
link in a directory with less restrictive permissions.
* Bugfix: dangling pointer in vstring_sprintf_prepend().
File: util/vstring.c.
Mon Aug 25 14:00:00 2008 mtAATTsuse.de
- init script: copy LSB
*-Start tags to
*-Stop
- spec file: removed obsolete rc.config update hooks
Wed Aug 6 14:00:00 2008 varkolyAATTsuse.de
- (bnc#414959) postfix doesn\'t have any \"Name: \" tag in firewall definition
- (bnc#405900) SuSEconfig.postfix changes owner and permissions of
/tmp if smtpd_tls_CApath is not set
- Update to Version 2.5 patchlevel 3
* Cleanup of code
* defer delivery when a mailbox file is not owned by the recipient.
Requested by Sebastian Krahmer, SuSE.
Specify \"strict_mailbox_ownership=no\" to ignore ownership discrepancies.
* Bugfix: null-terminate CN comment string after sanitization.
* Bugfix (introduced Postfix 2.0): after \"warn_if_reject
reject_unlisted_recipient/sender\", the SMTP server mistakenly
remembered that recipient/sender validation was already done.
Wed Jul 9 14:00:00 2008 varkolyAATTsuse.de
- (fate#305005) Enable SMTPS in postfix ootb
Tue Jun 17 14:00:00 2008 varkolyAATTsuse.de
- (bnc#396985) sending of NUL character disallowed by RFC2822
- (bnc#397127) without relay is silent about undeliverable mails
Tue May 13 14:00:00 2008 varkolyAATTsuse.de
- (bnc#389670) - postfix generates invalid config
Tue Apr 1 14:00:00 2008 mkoenigAATTsuse.de
- remove dir /usr/share/omc/svcinfo.d as it is provided now
by filesystem
Tue Feb 26 13:00:00 2008 varkolyAATTsuse.de
- Update to Version 2.5 patchlevel 1
Changes: The Postfix 2.5 \"postfix upgrade-configuration\" command
now works even with Postfix 2.4 or earlier versions of the
postfix command. When installing Postfix 2.5.0 without upgrading
from an existing master.cf file, the new master.cf file had an
incorrect process limit for the proxywrite service. This service
is used only by the obscure \"smtp_sasl_auth_cache_name\" and
\"lmtp_sasl_auth_cache_name\" configuration parameters. Someone
needed multi-line support for header/body Milter replies. The
LDAP client\'s TLS support was broken in several ways.
Wed Feb 13 13:00:00 2008 varkolyAATTsuse.de
- #360572 - postfix %post script leaves lots of backup files in /etc/postfix/
Wed Jan 30 13:00:00 2008 varkolyAATTsuse.de
- Update to Version 2.5 patchlevel 0
Major changes - critical
- -----------------------
[Incompat 20071224] The protocol to send Milter information from
smtpd(8) to cleanup(8) processes was cleaned up. If you use the
Milter feature, and upgrade a live Postfix system, you may see an
\"unexpected record type\" warning from a cleanup(8) server process.
To prevent this, execute the command \"postfix reload\". The
incompatibility affects only systems that use the Milter feature.
It does not cause loss of mail, just a minor delay until the remote
SMTP client retries.
[Incompat 20071212] The allow_min_user feature now applies to both
sender and recipient addresses in SMTP commands. With earlier Postfix
versions, only recipients were subject to the allow_min_user feature,
and the restriction took effect at mail delivery time, causing mail
to be bounced later instead of being rejected immediately.
[Incompat 20071206] The \"make install\" and \"make upgrade\" procedures
now create a Postfix-owned directory for Postfix-writable data files
such as caches and random numbers. The location is specified with
the \"data_directory\" parameter (default: \"/var/lib/postfix\"), and
the ownership is specified with the \"mail_owner\" parameter.
[Incompat 20071206] The tlsmgr(8) and verify(8) servers no longer
use root privileges when opening the address_verify_map,
* _tls_session_cache_database, and tls_random_exchange_name cache
files. This avoids a potential security loophole where the ownership
of a file (or directory) does not match the trust level of the
content of that file (or directory).
[Incompat 20071206] The tlsmgr(8) and verify(8) cache files should
now be stored as Postfix-owned files under the Postfix-owned
data_directory. As a migration aid, attempts to open these files
under a non-Postfix directory are redirected to the Postfix-owned
data_directory, and a warning is logged.
This is an example of the warning messages:
Dec 6 12:56:22 bristle postfix/tlsmgr[7899]: warning: request
to update file /etc/postfix/prng_exch in non-postfix directory
/etc/postfix
Dec 6 12:56:22 bristle postfix/tlsmgr[7899]: warning: redirecting
the request to postfix-owned data_directory /var/lib/postfix
If you wish to continue using a pre-existing tls_random_exchange_name
or address_verify_map file, move it to the Postfix-owned data_directory
and change ownership from root to Postfix (that is, change ownership
to the account specified with the mail_owner configuration parameter).
[Feature 20071205] The \"make install\" and \"make upgrade\" procedures
now create a Postfix-owned directory for Postfix-writable data files
such as caches and random numbers. The location is specified with
the \"data_directory\" parameter (default: \"/var/lib/postfix\"), and
the ownership is specified with the \"mail_owner\" parameter.
[Incompat 20071203] The \"make upgrade\" procedure adds a new service
\"proxywrite\" to the master.cf file, for read/write lookup table
access. If you copy your old configuration file over the updated
one, you may see warnings in the maillog file like this:
connect #xx to subsystem private/proxywrite: No such file or directory
To recover, run \"postfix upgrade-configuration\" again.
[Incompat 20070613] The pipe(8) delivery agent no longer allows
delivery with the same group ID as the main.cf postdrop group.
Major changes - malware defense
- ------------------------------
[Feature 20080107] New \"pass\" service type in master.cf. Written
years ago, this allows future front-end daemons to accept all
connections from the network, and to hand over connections from
well-behaved clients to Postfix. Since this feature uses file
descriptor passing, it imposes no overhead once a connection is
handed over to Postfix. See master(5) for a few details.
[Feature 20070911] Stress-adaptive behavior. When a \"public\" network
service runs into an \"all processes are busy\" condition, the master(8)
daemon logs a warning, restarts the service, and runs it with \"-o
stress=yes\" on the command line (under normal conditions it runs
the service with \"-o stress=\" on the command line). This can be
used to make main.cf parameter settings stress dependent, for
example:
/etc/postfix/main.cf:
smtpd_timeout = ${stress?10}${stress:300}
smtpd_hard_error_limit = ${stress?1}${stress:20}
Translation: under conditions of stress, use an smtpd_timeout value
of 10 seconds instead of 300, and use smtpd_hard_error_limit of 1
instead of 20. The syntax is explained in the postconf(5) manpage.
The STRESS_README file gives examples of how to mitigate flooding
problems.
Major changes - tls support
- --------------------------
[Incompat 20080109] TLS logging output has changed to make it more
useful. Existing logfile parser regular expressions may need
adjustment.
- More log entries include the \"hostnamename[ipaddress]\" of the
remote SMTP peer.
- Certificate trust chain error reports show only the first
error certificate (closest to the trust chain root), and the
reporting is more human-readable for the most likely errors.
- After the completion of the TLS handshake, the session is logged
with TLS loglevel >= 1 as either \"Untrusted\", \"Trusted\" or
\"Verified\" (SMTP client only).
- \"Untrusted\" means that the certificate trust chain is invalid,
or that the root CA is not trusted.
- \"Trusted\" means that the certificate trust chain is valid, and
that the root CA is trusted.
- \"Verified\" means that the certificate meets the SMTP client\'s
matching criteria for the destination:
- In the case of a destination name match, \"Verified\" also
implies \"Trusted\".
- In the case of a fingerprint match, CA trust is not applicable.
- The logging of protocol states with TLS loglevel >= 2 no longer
reports bogus error conditions when OpenSSL asks Postfix to refill
(or flush) network I/O buffers. This loglevel is for debugging
only; use 0 or 1 in production configurations.
[Feature 20080109] The Postfix SMTP client has a new \"fingerprint\"
security level. This avoids dependencies on CAs, and relies entirely
on bi-lateral exchange of public keys (really self-signed or private
CA signed X.509 public key certificates). Scalability is clearly
limited. For details, see the fingerprint discussion in TLS_README.
[Feature 20080109] The Postfix SMTP server can now use SHA1 instead
of MD5 to compute remote SMTP client certificate fingerprints. For
backwards compatibility, the default algorithm is MD5. For details,
see the \"smtpd_tls_fingerprint_digest\" parameter in the postconf(5)
manual.
[Feature 20080109] The maximum certificate trust chain depth
(verifydepth) is finally implemented in the Postfix TLS library.
Previously, the parameter had no effect. The default depth was
changed to 9 (the OpenSSL default) for backwards compatibility.
If you have explicity limited the verification depth in main.cf,
check that the configured limit meets your needs. See the
\"lmtp_tls_scert_verifydepth\", \"smtp_tls_scert_verifydepth\" and
\"smtpd_tls_ccert_verifydepth\" parameters in the postconf(5) manual.
[Feature 20080109] The selection of SSL/TLS protocols for mandatory
TLS can now use exclusion rather than inclusion. Either form is
acceptable; see the \"lmtp_tls_mandatory_protocols\",
\"smtp_tls_mandatory_protocols\" and \"smtpd_tls_mandatory_protocols\"
parameters in the postconf(5) manual.
Major changes - scheduler
- ------------------------
[Feature 20071130] Revised queue manager with separate mechanisms
for per-destination concurrency control and for dead destination
detection. The concurrency control supports less-than-1 feedback
to allow for more gradual concurrency adjustments, and uses hysteresis
to avoid rapid oscillations. A destination is declared \"dead\" after
a configurable number of pseudo-cohorts(
*) reports connection or
handshake failure.
(
*) A pseudo-cohort is a number of delivery requests equal to a
destination\'s delivery concurrency.
The drawbacks of the old +/-1 feedback scheduler are a) overshoot
due to exponential delivery concurrency growth with each pseudo-cohort(
*)
(5-10-20...); b) throttling down to zero concurrency after a single
pseudo-cohort(
*) failure. The latter was especially an issue with
low-concurrency channels where a single failure could be sufficient
to mark a destination as \"dead\", and suspend further deliveries.
New configuration parameters: destination_concurrency_feedback_debug,
default_destination_concurrency_positive_feedback,
default_destination_concurrency_negative_feedback,
default_destination_concurrency_failed_cohort_limit, as well as
transport-specific versions of the same.
The default parameter settings are backwards compatible with older
Postfix versions. This may change after better defaults are field
tested.
The updated SCHEDULER_README document describes the theory behind
the new concurrency scheduler, as well as Patrik Rak\'s preemptive
job scheduler. See postconf(5) for more extensive descriptions of
the configuration parameters.
Major changes - small/home office
- --------------------------------
[Feature 20080115] Preliminary SOHO_README document that combines
bits and pieces from other document in one place, so that it is
easier to find. This document describes the \"mail sending\" side
only.
[Feature 20071202] Output rate control in the queue manager. For
example, specify \"smtp_destination_rate_delay = 5m\", to pause five
minutes between message deliveries. More information in the postconf(5)
manual under \"default_destination_rate_delay\".
Major changes - smtp client
- --------------------------
[Incompat 20080114] The Postfix SMTP client now by default defers
mail after a remote SMTP server rejects a SASL authentication
attempt. Specify \"smtp_sasl_auth_soft_bounce = no\" for the old
behavior.
[Feature 20080114] The Postfix SMTP client can now avoid making
repeated SASL login failures with the same server, username and
password. To enable this safety feature, specify for example
\"smtp_sasl_auth_cache_name = proxy:btree:/var/lib/postfix/sasl_auth_cache\"
(access through the proxy service is required). Instead of trying
to SASL authenticate, the Postfix SMTP client defers or bounces
mail as controlled with the new smtp_sasl_auth_soft_bounce configuration
parameter.
[Feature 20071111] Header/body checks are now available in the SMTP
client, after the implementation was moved from the cleanup server
to a library module. The SMTP client provides only actions that
don\'t change the message delivery time or destination: warn, replace,
prepend, ignore, dunno, ok.
[Incompat 20070614] By default, the Postfix Cyrus SASL client no
longer sends a SASL authoriZation ID (authzid); it sends only the
SASL authentiCation ID (authcid) plus the authcid\'s password. Specify
\"send_cyrus_sasl_authzid = yes\" to get the old behavior.
Major changes - smtp server
- --------------------------
[Feature 20070724] Not really major. New support for RFC 3848
(Received: headers with ESMTPS, ESMTPA, or ESMTPSA); updated SASL
support according to RFC 4954, resulting in small changes to SMTP
reply codes and (DSN) enhanced status codes.
Major changes - milter
- ---------------------
[Incompat 20071224] The protocol to send Milter information from
smtpd(8) to cleanup(8) processes was cleaned up. If you use the
Milter feature, and upgrade a live Postfix system, you may see an
\"unexpected record type\" warning from a cleanup(8) server process.
To prevent this, execute the command \"postfix reload\". The
incompatibility affects only systems that use the Milter feature.
It does not cause loss of mail, just a minor delay until the remote
SMTP client retries.
[Feature 20071221] Support for most of the Sendmail 8.14 Milter
protocol features.
To enable the new features specify \"milter_protocol = 6\" and link
the filter application with a libmilter library from Sendmail 8.14
or later.
Sendmail 8.14 Milter features supported at this time:
- NR_CONN, NR_HELO, NR_MAIL, NR_RCPT, NR_DATA, NR_UNKN, NR_HDR,
NR_EOH, NR_BODY: The filter can tell Postfix that it won\'t reply
to some of the SMTP events that Postfix sends. This makes the
protocol less chatty and improves performance.
- SKIP: The filter can tell Postfix to skip sending the rest of
the message body, which also improves performance.
- HDR_LEADSPC: The filter can request that Postfix does not delete
the first space character between header name and header value
when sending a header to the filter, and that Postfix does not
insert a space character between header name and header value
when receiving a header from the filter. This fixes a limitation
in the old Milter protocol that can break DKIM and DK signatures.
- SETSYMLIST: The filter can override one or more of the main.cf
milter_xxx_macros parameter settings.
Sendmail 8.14 Milter features not supported at this time:
- RCPT_REJ: report rejected recipients to the mail filter.
- CHGFROM: replace sender, with optional ESMTP command parameters.
- ADDRCPT_PAR: add recipient, with optional ESMTP command parameters.
It is unclear when (if ever) the missing features will be implemented.
SMFIP_RCPT_REJ requires invasive changes in the SMTP server recipient
processing and error handling. SMFIR_CHGFROM and SMFIR_ADDRCPT_PAR
require ESMTP command-line parsing in the cleanup server. Unfortunately,
Sendmail\'s documentation does not specify what ESMTP options are
supported, but only discusses examples of things that don\'t work.
Major changes - address verification
- -----------------------------------
[Incompat 20070514] The default sender address for address verification
probes was changed from \"postmaster\" to \"double-bounce\", so that
the Postfix SMTP server no longer causes surprising behavior by
excluding \"postmaster\" from SMTP server access controls.
Major changes - ldap
- -------------------
[Incompat 20071216] Due to an incompatible API change between
OpenLDAP 2.0.11 and 2.0.12, an LDAP client compiled for OpenLDAP
version <= 2.0.11 will refuse to work with an OpenLDAP library
version >= 2.0.12 and vice versa.
Major changes - logging
- ----------------------
[Incompat 20080109] TLS logging output has changed to make it more
useful. Existing logfile parser regular expressions may need
adjustment.
- More log entries include the \"hostnamename[ipaddress]\" of the
remote SMTP peer.
- Certificate trust chain error reports show only the first
error certificate (closest to the trust chain root), and the
reporting is more human-readable for the most likely errors.
- After the completion of the TLS handshake, the session is logged
with TLS loglevel >= 1 as either \"Untrusted\", \"Trusted\" or
\"Verified\" (SMTP client only).
- \"Untrusted\" means that the certificate trust chain is invalid,
or that the root CA is not trusted.
- \"Trusted\" means that the certificate trust chain is valid, and
that the root CA is trusted.
- \"Verified\" means that the certificate meets the SMTP client\'s
matching criteria for the destination:
- In the case of a destination name match, \"Verified\" also
implies \"Trusted\".
- In the case of a fingerprint match, CA trust is not applicable.
- The logging of protocol states with TLS loglevel >= 2 no longer
reports bogus error conditions when OpenSSL asks Postfix to refill
(or flush) network I/O buffers. This loglevel is for debugging
only; use 0 or 1 in production configurations.
[Incompat 20071216] The SMTP \"transcript of session\" email now
includes the remote SMTP server TCP port number.
Major changes - loop detection
- -----------------------------
[Incompat 20070422] [Incompat 20070422] When the pipe(8) delivery
agent is configured to create the optional Delivered-To: header,
it now first checks if that same header is already present in the
message. If so, the message is returned as undeliverable. This test
should have been included with Postfix 2.0 when Delivered-To: support
was added to the pipe(8) delivery agent.
Tue Jan 8 13:00:00 2008 varkolyAATTsuse.de
- Remove previous fix
Sun Dec 30 13:00:00 2007 varkolyAATTsuse.de
- #301335 - [SuSEconfig]: Postfix module uses stderr
Tue Dec 4 13:00:00 2007 varkolyAATTsuse.de
- Update to Version 2.4 patchlevel 6
Bugfix (introduced Postfix 2.2.11): TLS client certificate
with unparsable canonical name caused the SMTP server\'s
policy client to allocate zero-length memory, triggering
an assertion that it shouldn\'t do such things. File:
smtpd/smtpd_check.c.
Bugfix (introduced Postfix 2.4) missing initialization of
event mask in the event_mask_drain() routine (used by the
obsolete postkick(1) command). Found by Coverity. File:
util/events.c.
Workaround: the flush daemon forces an access time update
for the per-destination logfile, to prevent an excessive
rate of delivery attempts when the queue file system is
mounted with \"noatime\". File: flush/flush.c.
- #330276 – /sbin/conf.d/SuSEconfig.postfix could copy certs into smtpd_tls_CApath
Mon Oct 22 14:00:00 2007 sbrabecAATTsuse.cz
- Use correct SuSEfirewall2 rule directory.
Wed Oct 17 14:00:00 2007 varkolyAATTsuse.de
- #333629 - saslauthd typo in SuSEconfig.postfix
Mon Oct 8 14:00:00 2007 varkolyAATTsuse.de
- #331044 - Postfix uses receive_override_options in main.cf
Sun Sep 9 14:00:00 2007 varkolyAATTsuse.de
- fix the last fix
Mon Sep 3 14:00:00 2007 cthielAATTsuse.de
- fix the last fix
Mon Sep 3 14:00:00 2007 varkolyAATTsuse.de
- Fixing bug: #297622 - SMTPD_LISTEN_REMOTE has no effect
Sun Aug 5 14:00:00 2007 mrueckertAATTsuse.de
- Update to Version 2.4 patchlevel 5
Bugfix: the loopback TCP performance workaround was ineffective
due to a wetware bit-flip during code cleanup. File:
util/vstream_tweak.c.
(patch level 4)
Bugfix: the Milter client assumed that a Milter application
does not modify the message header or envelope, after that
same Milter application has modified the message body of
that same email message. This is not a problem with updates
by different Milter applications. Problem was triggered
by Jose-Marcio Martins da Cruz. Also simplified the handling
of queue file update errors. File: milter/milter8.c.
Workaround: some non-Cyrus SASL SMTP servers require SASL
login without authzid (authoriZation ID), i.e. the client
must send only the authcid (authentiCation ID) + the authcid\'s
password. In this case the server is supposed to derive
the authzid from the authcid. This works as expected when
authenticating to a Cyrus SASL SMTP server. To get the old
behavior specify \"send_cyrus_sasl_authzid = yes\", in which
case Postfix sends the (authzid, authcid, password), with
the authzid equal to the authcid. File: xsasl/xsasl_cyrus_client.c.
Portability: /dev/poll support for Solaris chroot jail setup
scripts. Files: examples/chroot-setup/Solaris8,
examples/chroot-setup/Solaris10.
Cleanup: Milter client error handling, so that the (Postfix
SMTP server\'s Milter client) does not get out of sync with
Milter applications after the (cleanup server\'s Milter
client) encounters some non-recoverable problem. Files:
milter/milter8.c, smtpd/smtpd.c.
Performance: workaround for poor TCP performance on loopback
(127.0.0.1) connections. Problem reported by Mark Martinec.
Files: util/vstream_tweak.c, milter/milter8.c, smtp/smtp_connect.c,
smtpstone/
*source.c.
Bugfix: when a milter replied with ACCEPT at or before the
first RCPT command, the cleanup server would apply the
non_smtpd_milters setting as if the message was a local
submission. Problem reported by Jukka Salmi. Also, the
cleanup server would get out of sync with the milter when
a milter replied with ACCEPT at the DATA command. Files:
cleanup/cleanup_envelope.c, smtpd/smtpd.c, milter/milters.c.
- rediffed patches
Tue Jul 31 14:00:00 2007 varkolyAATTsuse.de
- Update to Version 2.4 patchlevel 3
(patch level 1)
Bugfix (introduced Postfix 2.3): segfault with HOLD action
in access/header_checks/body_checks on 64-bit platforms.
File: cleanup/cleanup_api.c.
Portability (introduced 20070325): the fix for hardlinks
and symlinks in postfix-install forgot to work around shells
where \"IFS=/ command\" makes the IFS setting permanent. This
is allowed by some broken standard, and affects Solaris.
File: postfix-install.
Portability (introduced 20070212): the workaround for
non-existent library bugs with descriptors >= FD_SETSIZE
broke with \"fcntl F_DUPFD: Invalid argument\" on 64-bit
Solaris. Files: master/multi_server.c,
*qmgr/qmgr_transport.c.
Cleanup: on (Linux) platforms that cripple signal handlers
with deadlock, \"postfix stop\" now forcefully stops all the
processes in the master\'s process group, not just the master
process alone. File: conf/postfix-script.
(patch level 2)
Bugfix: don\'t falsely report \"lost connection from
localhost[127.0.0.1]\" when Postfix is being portscanned.
Files: smtpd/smtpd_peer.c, qmqpd/qmqpd_peer.c.
Robustness: recommend a \"0\" process limit for policy servers
to avoid \"connection refused\" problems when the smtpd process
limit exceeds the default process limit. File:
proto/SMTPD_POLICY_README.html.
Safety: when IPv6 (or IPv4) is turned off, don\'t treat an
IPv6 (or IPv4) connection from e.g. inetd as if it comes
from localhost[127.0.0.1]. Files: smtpd/smtpd_peer.c,
qmqpd/qmqpd_peer.c.
Bugfix: Content-Transfer-Encoding: attribute values are
case insensitive. File: src/cleanup/cleanup_message.c.
Bugfix: mailbox_transport(_maps) and fallback_transport(_maps)
were broken when used with the error(8) or discard(8)
transports. Cause: insufficient documentation. Files:
error/error.c, discard/discard.c.
Bugfix (problem introduced Postfix 2.3): when DSN support
was introduced it broke \"agressive\" recipient duplicate
elimination with \"enable_original_recipient = no\". File:
cleanup/cleanup_out_recipient.c.
Bugfix (introduced Postfix 2.3): the sendmail/postdrop
commands would hang when trying to submit a message larger
than the per-message size limit. File: postdrop/postdrop.c.
Sabotage the saboteur who insists on breaking Postfix by
adding gethostbyname() calls that cause maildir delivery
to fail when the machine name is not found in /etc/hosts,
or that cause Postfix processes to hang when the network
is down.
(patch level 3)
Portability: Victor helpfully pointed out that change
20070425 broke on non-IPv6 systems. Files: smtpd/smtpd_peer.c,
qmqpd/qmqpd_peer.c.
Thu Jun 21 14:00:00 2007 varkolyAATTsuse.de
- Bug 285553 amavisd inconsistency
Tue Jun 19 14:00:00 2007 dmuellerAATTsuse.de
- provide smtp meta-service as well
Mon Jun 11 14:00:00 2007 lruppAATTsuse.de
- don\'t PreRequire /sbin/ip: removed call in SuSEconfig.postfix
Thu May 3 14:00:00 2007 varkolyAATTsuse.de
- dynamic_maps.patch: readded the chunk for dict_tcp and dict_pcre
- replaced prereq for postfix with a prereq on
%{name} = %{version}
- updated to postfix 2.4, patchlevel 0
Major changes - safety
* As a safety measure, Postfix now by default creates mailbox dotlock
files on all systems. This prevents problems with GNU POP3D which
subverts kernel locking by creating a new mailbox file and deleting
the old one
Major changes - Milter support
* The support for Milter header modification
requests was revised. With minimal change in the on-disk representation,
the code was greatly simplified, and regression tests were updated
to ensure that old errors were not re-introduced. The queue file
format is entirely backwards compatible with Postfix 2.3.
* Support for Milter requests to replace the message
body. Postfix now implements all the header/body modification
requests that are available with Sendmail 8.13.
* A new field is added to the queue file \"size\"
record that specifies the message content length. Postfix 2.3 and
older Postfix 2.4 snapshots will ignore this field, and will report
the message size as it was before the body was replaced.
Major changes - TLS support
* The check_smtpd_policy client sends TLS certificate
attributes (client ccert_subject, ccert_issuer) only after successful
client certificate verification. The reason is that the certification
verification status itself is not available in the policy request.
* The check_smtpd_policy client sends TLS certificate
fingerprint information even when the certificate itself was not
verified.
* The remote SMTP client TLS certificate fingerprint
can be used for access control even when the certificate itself was
not verified.
* The format of SMTP server TLS session cache
lookup keys has changed. The lookup key now includes the master.cf
service name.
Major changes - performance
* Better support for systems that run thousands
of Postfix processes. Postfix now supports FreeBSD kqueue(2),
Solaris poll(7d) and Linux epoll(4) as more scalable alternatives
to the traditional select(2) system call, and uses poll(2) when
examining a single file descriptor for readability or writability.
These features are supported on sufficiently recent versions of
FreeBSD, NetBSD, OpenBSD, Solaris and Linux; support for other
systems will be added as evidence becomes available that usable
implementations exist.
Major changes - delivery status notifications
* Small changes were made to the default bounce
message templates, to prevent HTML-aware software from hiding or
removing the text \"
\", and producing misleading text.
* Postfix no longer announces its name in delivery
status notifications. Users believe that Wietse provides a free
help desk service that solves all their email problems.
Major changes - ETRN support
* More precise queue flushing with the ETRN,
\"postqueue -s site\", and \"sendmail -qRsite\" commands, after
minimization of race conditions. New per-queue-file flushing with
\"postqueue -i queueid\" and \"sendmail -qIqueueid\".
Major changes - small office/home office support
* Postfix no longer requires a domain name. It
uses \"localdomain\" as the default Internet domain name when no
domain is specified via main.cf or via the machine\'s hostname.
Major changes - SMTP access control
* The check_smtpd_policy client sends TLS certificate
attributes (client ccert_subject, ccert_issuer) only after successful
client certificate verification. The reason is that the certification
verification status itself is not available in the policy request.
* The check_smtpd_policy client sends TLS certificate
fingerprint information even when the certificate itself was not
verified.
* The remote SMTP client TLS certificate fingerprint can be used for
access control even when the certificate itself was not verified.
* The Postfix installation procedure no longer
updates main.cf with \"unknown_local_recipient_reject_code = 450\".
Four years after the introduction of mandatory recipient validation,
this transitional tool is no longer neeed.
Thu Mar 29 14:00:00 2007 rguentherAATTsuse.de
- Add pwdutils BuildRequires to allow postinst script to succeed.
- Add /usr/share/omc directory.
Mon Feb 26 13:00:00 2007 varkolyAATTsuse.de
- #247351 - postfix - Ports for SuSEfirewall added via packages
- Move postfix.xml into the postfix-SuSE tarball
- #228479 - Postfix is configured for inet_protocols=all if
selecting ipv4 only support during installation.
Now we set both inet_protocols and inet_interfaces to all.
This means the available interfaces and protocols will be used.
To avoid bogus warnings inet_proto.c was patched.
- #251598 - postfix use pointers for literals
Mon Jan 15 13:00:00 2007 varkolyAATTsuse.de
- #144104 - postfix does not start
- Implementing Fate #301840: Postfix XML Service Description Document
- Enhancing /etc/sysconfig/postfix descripton to avoid problems
like Bug 228678 - Problems with setting up chroot environment if
/var/spool is not on same filesystem as /var
Wed Nov 22 13:00:00 2006 mrueckertAATTsuse.de
- moved the dict handling into a preun script instead of postun
and do not remove the dict entry on upgrade (#223176)
- removed duplicates in the filelists.
Fri Nov 10 13:00:00 2006 varkolyAATTsuse.de
- #218229 - Postfix SuSEconfig script increases the max_proc line each run in master.cf
Sat Oct 28 14:00:00 2006 varkolyAATTsuse.de
- #206414 - /usr/lib/sasl2/smtpd.conf misplaced
Tue Oct 24 14:00:00 2006 varkolyAATTsuse.de
- #202119 – SuSEconfig script for Postfix incomplete
- #202162 – Postfix 2.3.2 slightly incorrect, Cyrus SASL unavailable
- #203174 – /sbin/conf.d/SuSEconfig.postfix should configure a TLS session cache for postfix 2.2
- #203575 – postfix-2.2.9-10 chokes without scache
- #213589 - No development package/headers for postfix
Wed Aug 16 14:00:00 2006 roAATTsuse.de
- also add libpostfix-milter.so
*
Mon Aug 14 14:00:00 2006 varkolyAATTsuse.de
- updated to postfix 2.3, patchlevel 2
- Major changes
- Name server replies that contain a malformed hostname are now flagged
as permanent errors instead of transient errors.
- DSN support as described in RFC 3461 .. RFC 3464.
- The SMTP client now implements the LMTP protocol.
- Milter (mail filter) application support, compatible with Sendmail
version 8.13.6 and earlier.
- Major changes - SASL authentication
- Plug-in support for SASL authentication in the SMTP server and in the
SMTP/LMTP client.
- The Postfix-with-Cyrus-SASL build procedure has changed.
- Support for sender-dependent ISP accounts.
- Major changes - SMTP client
- The SMTP client now implements the LMTP protocol.
- This version addresses a performance stability problem with remote
SMTP servers.
- Major changes - SMTP server
- The Postfix SMTP server now refuses to receive mail from the network
if it isn\'t running with postfix mail_owner privileges.
- Optional suppression of remote SMTP client hostname lookup and hostname
verification.
- SMTPD Access control based on the existence of an address->name mapping
- Major changes - TLS
- New concept: TLS security levels (\"none\", \"may\", \"encrypt\", \"verify\"
or \"secure\") in the Postfix SMTP client.
- Both the Postfix SMTP client and server can be configured without a
client or server certificate.
- See
/usr/share/doc/packages/postfix/RELEASE_NOTES
/usr/share/doc/packages/postfix/TLS_CHANGES
/usr/share/doc/packages/postfix/README_FILES/SASL_README
for detailed informations.
Wed Aug 2 14:00:00 2006 varkolyAATTsuse.de
- Only %{conf_backup_dir} is contained by the package not /var/adm/backup
Mon Jul 10 14:00:00 2006 varkolyAATTsuse.de
- Bugfix: #190639 Default number of processes for postfix
- Bugfix: #190270 postfix-postgresql