--
Postfix 19991231 patch 09 fixes a memory corruption problem, and
includes a long list of minor bugfixes and robustness improvements
that already featured in snapshot releases (or that will feature
in the next one).
- When propagating an address extension to the right-hand side
of a virtual or canonical mapping, the cleanup server could
access memory that was no longer allocated and die with signal
11. This would happen when the result address length was more
than about 100 characters. Credit to Adi Prasaja @ satunet.com
for coming up with a small reproducible demo.
This patch provides an emergency band-aid for the next wave of
MicroSoft email worms, fixes one bug, and makes external content
filtering a bit more robust.
- Feature: specify "body_checks = regexp:/etc/postfix/body_checks"
for an emergency content filter that looks at non-header lines
one line at a time (including MIME headers inside the message
body). This feature uses the same syntax as the header_checks
patterns. Details in conf/sample-filter.cf.
This feature is also available in Postfix snapshot 20000528.
- Bugfix: the masquerade_exceptions feature was case sensitive.
- Robustness: upon receipt of mail, Postfix maps MAILER-DAEMON@myorigin
sender address back into the magic null string, which prevents
mail from looping after processing by an external content filter.
- RFC 822 requires the presence of at least one destination
message header. Postfix now generates a generic "To:
undisclosed-recipients:;" message header when no destination
header is present. The header content is specified with the
new undisclosed_recipients_header parameter.
- Postfix now understands <(comment)> as SMTP MAIL FROM address,
because some broken software needs it. Postfix rejects such
illegal address forms with "strict_rfc821_envelopes = yes".
- Configuration parameters for one mysql dictionary would become
default settings for the next one. This patch was merged into
the development Postfix version a while back but apparently
that version was on a dead branch. Update by Scott Cotton.
- Some Postfix delivery agents would abort on addresses of the
form `stuff@.' which could unfortunately be generated locally.
- With local delivery, Postfix could insert > or . into the middle
of very long lines.
- SMTP sessions could time out when the remote client attempted
to deliver to a large number of rejected recipients. The SMTP
server now flushes unwritten output in-between tarpit delays,
to avoid protocol timeouts in pipelined SMTP sessions.
- Postfix would incorrectly reject domain names with adjacent `-'
characters.
remove ftp.win.ne.jp from master sites -- it will not allow the port
to be fetched because it does not like the format of the "password"
sent by the ftp client
