autoupdate
[postfix-master.git] / postfix-master / announcements / postfix-2.5.7.html
blob0a4258d68da7d96cb23bafbb614d8a23ed1951f3
1 <!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"
2 "http://www.w3.org/TR/html4/loose.dtd">
4 <html>
6 <head>
8 <title> Postfix legacy releases 2.5.7, 2.4.11 and 2.3.17 </title>
10 <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
12 </head>
14 <body>
16 <h1> Postfix legacy releases 2.5.7, 2.4.11 and 2.3.17 </h1>
18 <p>
19 An on-line version of this announcement is available at
20 <a href="http://www.postfix.org/announcements/postfix-2.5.7.html">http://www.postfix.org/announcements/postfix-2.5.7.html</a>
21 </p>
23 <p>
24 Postfix legacy releases 2.5.7, 2.4.11 and 2.3.17 contain fixes that
25 were already included with Postfix versions 2.6 and 2.7.
26 </p>
28 <h3> Fixed with Postfix 2.5.7 </h3>
30 <ul>
32 <li>
33 <p>
34 (low) The installation/upgrade procedure did not automatically
35 create the <a href="../postconf.5.html#data_directory">data_directory</a>.
36 </p>
38 <li> <p>
39 (medium) In the "new queue manager", the _destination_rate_delay
40 code needed to postpone the job scheduler updates after delivery
41 completion, otherwise the scheduler could loop on blocked jobs.
42 </p>
44 <li> <p>
45 (low) The queue manager used <i>transport</i>_concurrency_failed_cohort_limit
46 instead of <a href="../postconf.5.html#transport_destination_concurrency_failed_cohort_limit"><i>transport</i>_destination_concurrency_failed_cohort_limit</a>
47 as documented.
48 </p>
50 <li> <p>
51 (low) The SMTP client disabled MIME parsing despite non-empty
52 settings for <a href="../postconf.5.html#smtp_header_checks">smtp_header_checks</a>, <a href="../postconf.5.html#smtp_mime_header_checks">smtp_mime_header_checks</a>,
53 <a href="../postconf.5.html#smtp_nested_header_checks">smtp_nested_header_checks</a>, or <a href="../postconf.5.html#smtp_body_checks">smtp_body_checks</a>.
54 </p>
56 </ul>
58 <h3> Fixed with Postfix 2.5.7, 2.4.11, 2.3.17 </h3>
60 <ul>
62 <li> <p>
63 (medium) The postsuper command re-enabled the SIGHUP signal when
64 it was set to "ignore". This could result in random "Postfix
65 integrity check failed" errors at boot time (POSIX SIGHUP death),
66 causing Postfix not to start automatically.
67 </p>
69 </ul>
71 <p>
72 You can find the source code and patches at the mirrors listed at
73 <a href="http://www.postfix.org/>http://www.postfix.org/</a>
74 </p>
76 </body>
78 </html>