The NetBSD Project

CVS log for pkgsrc/mail/postfix/Makefile.common

[BACK] Up to [cvs.NetBSD.org] / pkgsrc / mail / postfix

Request diff between arbitrary revisions


Keyword substitution: kv
Default branch: MAIN


Revision 1.69: download - view: text, markup, annotated - select for diffs
Tue Sep 8 14:17:30 2026 UTC (2 months, 1 week ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2026Q3-base, pkgsrc-2026Q3, HEAD
Diff to: previous 1.68: preferred, colored
Changes since revision 1.68: +2 -2 lines
mail/postfix: update to 3.11.7

3.11.7 (2026-09-08)

This release addresses medium-impact problems that need to be fixed
as some enable remote DOS or SMTP smugggling.

SMTP smuggling:

  * Bug (introduced: Postfix 3.9, date: 20240106) SMTP smuggling
    was still possible with smtpd_proxy_filter (disabled by default)
    when the after-filter SMTP server used the default policy
    settings "smtpd_forbid_bare_newline_exclusions = $mynetworks"
    and "smtpd_forbid_bare_newline = normalize". Reported by OpenAI
    Security. Fix by Wietse.

    As suggested by OpenAI Security, eliminate stray CR characters
    from the smtpd_proxy_filter input stream. The before-proxy-filter
    SMTP server already eliminated stray LF.

  * Bug (introduced: Postfix 3.11, date: 20250917): SMTP smuggling
    was possible with smtpd_proxy_filter (disabled by default) when
    the before-filter SMTP server added a "Require-TLS-ESMTP: yes"
    message header, due to implementation edge cases. Adding this
    header is enabled with the "requiretls_esmtp_header = yes"
    default setting. Reported by OpenAI Security. Fix by Wietse.

Server crashes and panic()s:

  * Bug (defect introduced: Postfix 3.0, date: 20140707): null
    pointer read error after receiving MAIL FROM, RCPT TO, and VRFY
    with an UTF8 address but no SMTPUTF8 parameter. This requires
    "smtputf8_enable = yes" (the default) and "strict_smtputf8 =
    yes" (not default). With this, the SMTP server did an unnecessary
    MAIL FROM reset without RCPT TO reset. A crafted remote SMTP
    client could then send a DATA command and crash a Postfix SMTP
    server process with a null pointer read error. Reported by
    Wonyoung Jung (78ResearchLab AI).

Other bugs

  * Bug (defect introduced: Postfix 3.4, date: 20180303): the MySQL
    client setting "tls_verify_cert = yes" had no effect with Oracle
    MySQL 8 and later. Report and fix by OpenAI Security.

  * Bug (defect introduced: Postfix-beta, date: 19990119): the
    pipe(8) delivery agent deleted a command-line argument if the
    argument contained $user AND $user expanded to an empty string,
    breaking the positional order of arguments. This was a workaround
    for a problem that hopefully no longer exists. Reported by
    Qualys, assisted by Claude Mythos Preview.

  * Bug (defect introduced: Postfix 2.3, date: 20050323): the SMTP
    client enhanced status code parser could process stale data
    when a remote SMTP server sent a three-digit reply without other
    text. Reported by Qualys, assisted by Claude Mythos Preview.

TLS

  * Isolation: stamp Postfix SMTP server TLS session tickets with
    their master.cf service name. With this, an SMTP server defined
    in master.cf will no longer accept tickets issued by a different
    SMTP server defined in the same master.cf file. Fix by OpenAI
    security.

Configuration safety

  * The postmap and postalias commands now log a warning when
    creating a root-owned database file in a directory that is not
    owned by root. They log that the database source file, indexed
    file(s), and parent directory should have the same owner, to
    prevent a privilege-escalation attack. Problem reported by
    OpenAI Security, remediation strategy (don't break production
    deployment) by Wietse.

Read after free, memory over-read

  * Bug (introduced: Postfix 2.3, date: 20060629): a malicious
    Milter or attacker-in-the-middle could trigger a null-terminated
    heap memory overread in the SMTP daemon while formatting a
    malformed multiline response. Fix from OpenAI Security adopted
    with minor changes.

  * Bug (defect introduced: Postfix 3.0, date: 20141117): in the
     postqueue command don't free() text before logging a fatal error
    message. Reported by Qualys, assisted by Claude Mythos Preview.

  * Code hygiene: in the SMTP client protocol engine, evaluate a
    RETURN() macro argument before freeing resources. Reported by
    Qualys, assisted by Claude Mythos Preview.

Code hardening (defense in depth, prevention)

  * (Postfix 3.11) Hardening: in the non-BerkeleyDB migration
    service, delay the decision between running postmap or postalias
    until after the database file/directory owner/permission checks.
    The benefit from making the decision early (better error messages)
    was not worth the risk. Qualys, assisted by Claude Mythos
    Preview.

  * (Postfix-3.11) Hardened the database parent directory permission
    checks for automatic re-indexing with the non-Berkeley-DB
    migration service.

  * Hardening command-line email submission: the postdrop command
    now disallows null and line-break characters in queue file
    envelope records (line-break characters in non-envelope queue
    file records are already neutralized by default with
    "cleanup_replace_stray_cr_lf = yes").

    The new constraint not only eliminates line-break injection
    into local mailbox files as reported by OpenAI Security, but
    also prevents other forms of misuse. Later, this constraint may
    be moved into the Postfix core. Fix by Wietse.

  * Shut up nagging from multiple AIs and harden the virtual delivery
    agent against an evil (LDAP or SQL) database.

  * Code hygiene: myrealloc(ptr, 0) still resulted in a panic.
    Reported by Qualys, assisted by Claude Mythos Preview. Also
    adopt a mystrndup() fix from Postfix 3.12.

Other:

  * Portability: OpenBSD does not define NS_INT16SZ. Brad Smith.

Revision 1.65.2.2: download - view: text, markup, annotated - select for diffs
Sun Aug 16 21:05:48 2026 UTC (3 months ago) by maya
Branches: pkgsrc-2026Q2
Diff to: previous 1.65.2.1: preferred, colored; branchpoint 1.65: preferred, colored; next MAIN 1.66: preferred, colored
Changes since revision 1.65.2.1: +1 -1 lines
Pullup ticket #7228 - requested by taca
mail/postfix: Security fix

Revisions pulled up:
- mail/postfix/Makefile.common                                  1.68
- mail/postfix/distinfo                                         1.227

---
   Module Name:	pkgsrc
   Committed By:	taca
   Date:		Tue Aug 11 15:15:50 UTC 2026

   Modified Files:
   	pkgsrc/mail/postfix: Makefile.common distinfo

   Log Message:
   mail/postfix: update to 3.11.6

   This release addresses medium-impact problems that need to be fixed
   as some enable remote DOS or policy bypass.

   These defects were found by Qualys assisted by Claude Mythos Preview,
   and by OpenAI Security; more than half date from 20 or more years
   ago. When I implemented Postfix, I knew that there were going to
   be mistakes. That is the reason why Postfix has its architecture
   and safety nets. The number of defects may seem large, but considering
   that they were found in a code base of over 150 thousand lines, the
   error rate is still lower than what I designed for.

   Policy bypass:

     * Bug (introduced: Postfix 2.2, date: 20041102): missing SMTP
       server resets of MAIL FROM and RCPT TO command state after
       smtpd_end_of_data_restrictions rejected a message. This resulted
       in SMTP protocol state desynchronization between the remote
       SMTP client and the Postfix SMTP server.

       A crafted remote SMTP client could then send RCPT TO and DATA
       without MAIL FROM, and deliver a second message. Then,
       smtpd_end_of_data_restrictions skipped check_recipient_access
       constraints, because a recipient counter was > 1. Reported by
       OpenAI Security. File: smtpd/smtpd.c.

       As reported by OpenAI Security, the failure to reset MAIL FROM
       and RCPT TO state also affected Milter support (added in Postfix
       2.3). Here, after a Milter replied with "accept this message"
       based on the message envelope, and smtpd_end_of_data_restrictions
       rejected the message, the Postfix SMTP server as before accepted
       RCPT TO and DATA without MAIL FROM, and smtpd_end_of_data_restrictions
       as before skipped check_recipient_access constraints for the
       second message. Under these conditions, the Postfix Milter
       client remained in the "accept this message" state, skipping
       Milter policy enforcement for the second message.

   Denial of service:

     * Bug (defect introduced: Postfix 3.4, date: 20180805): SMTP
       server command history memory exhaustion with a large number
       of very small BDAT requests. Reported by OpenAI security. File:
       smtpd.c.

     * Bug (defect introduced: Postfix 1.1, date: 20021116): address
       verification cache poisoning. A local user could use the postdrop
       command to submit an address verification probe with envelope
       or message content that Postfix rejected later, resulting in a
       negative address verification cache entry for that address. On
       systems that enable address verification, the negative address
       verification cache entry would force the Postfix SMTP server
       to reject a message that it should accept (denial of service).
       Problem reported by OpenAI Security. File: postdrop.c.

   Server crashes and panic()s:

     * Bug (defect introduced: Postfix 3.4, date: 20180805): missing
       SMTP server reset of RCPT TO state, after a BDAT command error.
       A crafted remote SMTP client could then send a DATA command
       without MAIL FROM or RCPT TO, and crash a Postfix SMTP daemon
       process with a null pointer read error. Reported by OpenAI
       Security. File: smtpd/smtpd.c.

     * Bug (defect introduced: Postfix 2.4, date: 20051222): null
       pointer read crash while parsing a malformed Dovecot AUTH server
       response. Reported by Qualys, assisted by Claude Mythos Preview.
       File: xsasl_dovecot_server.c.

   Read after free, uninitialized read, under/over read:

     * Bug (defect introduced: Postfix 2.8, date: 20100914): read-after-free
       in the PSC_CALL_BACK_NOTIFY() macro. This had no effect on
       program execution, because myfree() wiped memory, and that
       memory was not yet reused. Problem reported by Qualys, assisted
       by Claude Mythos Preview. File: postscreen_dnsbl.c.

     * Read after free (no privilege escalation) in debug logging
       (defect introduced: Postfix 2.2, date: 20050117). Reported by
       Qualys, assisted by Claude Mythos Preview. File: util/inet_connect.c.

     * Bug (defect introduced: Postfix 2.10, date: 20120617): uninitialized
       memory read in postscreen HaProxy client after remote I/O
       exception, causing garbage to be logged. Reported by Qualys,
       assisted by Claude Mythos Preview. File: postscreen_haproxy.c.

     * Latent bug (defect introduced: Postfix 2.7, date: 20090618):
       uninitialized memory read after dnsblog(8) returns a string
       that is not an IPv4 address. Reported by Qualys, assisted by
       Claude Mythos Preview. File: postscreen_dnsbl.c.

     * Bug (defect introduced: before Postfix alpha, date 19970424):
       the DNS client could read up to two bytes past the end of an
       MX record, before discovering that the record was too short.
       This behavior was later copied with SRV records, potentially
       over-reading up to six bytes. Problem reported by Qualys,
       assisted by Claude Mythos Preview. File: dns_lookup.c.

     * Bug (defect introduced: Postfix 1,1, date: 20010524): the
       postsuper command under-read or over-read a very short queue
       filename. No crash, information leak, or privilege escalation.
       Reported by Qualys, assisted by Claude Mythos Preview. Files:
       postsuper.c, mail_queue.h.

   Other code hygiene:

     * Bug (defect introduced: before Postfix alpha, date: 19971106):
       'int' over-shift, in the queue file record-length parser. Postfix
       programs do not generate such records, but an attacker could
       cause postdrop to reject input or panic(). Reported by Qualys,
       assisted by Claude Mythos Preview. File: record.c.

     * Bug (defect introduced: Postfix 2.2, date: 20050117): non-transitive
       comparison of IPv4 addresses. Reported by Qualys, assisted by
       Claude Mythos Preview. File: sock_addr.c.

     * Bug (defect introduced: Postfix 1.0, date: 20000928): the fast
       flush server, used by the SMTP command "ETRN", and by the
       commands "postqueue -s site" and "postqueue -i queue_id" (and
       their sendmail(1) equivalents), used the wrong duplicate
       suppression API, resulting in unnecessary queue scans by the
       queue manager. Reported by Qualys, assisted by Claude Mythos
       Preview. File: flush.c.

     * Queue hygiene: the postdrop command accepted the null record
       type which the rest of Postfix ignores. Reported by OpenAI
       Security. File: postdrop.c.

Revision 1.68: download - view: text, markup, annotated - select for diffs
Tue Aug 11 15:15:50 2026 UTC (3 months ago) by taca
Branches: MAIN
Diff to: previous 1.67: preferred, colored
Changes since revision 1.67: +2 -2 lines
mail/postfix: update to 3.11.6

This release addresses medium-impact problems that need to be fixed
as some enable remote DOS or policy bypass.

These defects were found by Qualys assisted by Claude Mythos Preview,
and by OpenAI Security; more than half date from 20 or more years
ago. When I implemented Postfix, I knew that there were going to
be mistakes. That is the reason why Postfix has its architecture
and safety nets. The number of defects may seem large, but considering
that they were found in a code base of over 150 thousand lines, the
error rate is still lower than what I designed for.

Policy bypass:

  * Bug (introduced: Postfix 2.2, date: 20041102): missing SMTP
    server resets of MAIL FROM and RCPT TO command state after
    smtpd_end_of_data_restrictions rejected a message. This resulted
    in SMTP protocol state desynchronization between the remote
    SMTP client and the Postfix SMTP server.

    A crafted remote SMTP client could then send RCPT TO and DATA
    without MAIL FROM, and deliver a second message. Then,
    smtpd_end_of_data_restrictions skipped check_recipient_access
    constraints, because a recipient counter was > 1. Reported by
    OpenAI Security. File: smtpd/smtpd.c.

    As reported by OpenAI Security, the failure to reset MAIL FROM
    and RCPT TO state also affected Milter support (added in Postfix
    2.3). Here, after a Milter replied with "accept this message"
    based on the message envelope, and smtpd_end_of_data_restrictions
    rejected the message, the Postfix SMTP server as before accepted
    RCPT TO and DATA without MAIL FROM, and smtpd_end_of_data_restrictions
    as before skipped check_recipient_access constraints for the
    second message. Under these conditions, the Postfix Milter
    client remained in the "accept this message" state, skipping
    Milter policy enforcement for the second message.

Denial of service:

  * Bug (defect introduced: Postfix 3.4, date: 20180805): SMTP
    server command history memory exhaustion with a large number
    of very small BDAT requests. Reported by OpenAI security. File:
    smtpd.c.

  * Bug (defect introduced: Postfix 1.1, date: 20021116): address
    verification cache poisoning. A local user could use the postdrop
    command to submit an address verification probe with envelope
    or message content that Postfix rejected later, resulting in a
    negative address verification cache entry for that address. On
    systems that enable address verification, the negative address
    verification cache entry would force the Postfix SMTP server
    to reject a message that it should accept (denial of service).
    Problem reported by OpenAI Security. File: postdrop.c.

Server crashes and panic()s:

  * Bug (defect introduced: Postfix 3.4, date: 20180805): missing
    SMTP server reset of RCPT TO state, after a BDAT command error.
    A crafted remote SMTP client could then send a DATA command
    without MAIL FROM or RCPT TO, and crash a Postfix SMTP daemon
    process with a null pointer read error. Reported by OpenAI
    Security. File: smtpd/smtpd.c.

  * Bug (defect introduced: Postfix 2.4, date: 20051222): null
    pointer read crash while parsing a malformed Dovecot AUTH server
    response. Reported by Qualys, assisted by Claude Mythos Preview.
    File: xsasl_dovecot_server.c.

Read after free, uninitialized read, under/over read:

  * Bug (defect introduced: Postfix 2.8, date: 20100914): read-after-free
    in the PSC_CALL_BACK_NOTIFY() macro. This had no effect on
    program execution, because myfree() wiped memory, and that
    memory was not yet reused. Problem reported by Qualys, assisted
    by Claude Mythos Preview. File: postscreen_dnsbl.c.

  * Read after free (no privilege escalation) in debug logging
    (defect introduced: Postfix 2.2, date: 20050117). Reported by
    Qualys, assisted by Claude Mythos Preview. File: util/inet_connect.c.

  * Bug (defect introduced: Postfix 2.10, date: 20120617): uninitialized
    memory read in postscreen HaProxy client after remote I/O
    exception, causing garbage to be logged. Reported by Qualys,
    assisted by Claude Mythos Preview. File: postscreen_haproxy.c.

  * Latent bug (defect introduced: Postfix 2.7, date: 20090618):
    uninitialized memory read after dnsblog(8) returns a string
    that is not an IPv4 address. Reported by Qualys, assisted by
    Claude Mythos Preview. File: postscreen_dnsbl.c.

  * Bug (defect introduced: before Postfix alpha, date 19970424):
    the DNS client could read up to two bytes past the end of an
    MX record, before discovering that the record was too short.
    This behavior was later copied with SRV records, potentially
    over-reading up to six bytes. Problem reported by Qualys,
    assisted by Claude Mythos Preview. File: dns_lookup.c.

  * Bug (defect introduced: Postfix 1,1, date: 20010524): the
    postsuper command under-read or over-read a very short queue
    filename. No crash, information leak, or privilege escalation.
    Reported by Qualys, assisted by Claude Mythos Preview. Files:
    postsuper.c, mail_queue.h.

Other code hygiene:

  * Bug (defect introduced: before Postfix alpha, date: 19971106):
    'int' over-shift, in the queue file record-length parser. Postfix
    programs do not generate such records, but an attacker could
    cause postdrop to reject input or panic(). Reported by Qualys,
    assisted by Claude Mythos Preview. File: record.c.

  * Bug (defect introduced: Postfix 2.2, date: 20050117): non-transitive
    comparison of IPv4 addresses. Reported by Qualys, assisted by
    Claude Mythos Preview. File: sock_addr.c.

  * Bug (defect introduced: Postfix 1.0, date: 20000928): the fast
    flush server, used by the SMTP command "ETRN", and by the
    commands "postqueue -s site" and "postqueue -i queue_id" (and
    their sendmail(1) equivalents), used the wrong duplicate
    suppression API, resulting in unnecessary queue scans by the
    queue manager. Reported by Qualys, assisted by Claude Mythos
    Preview. File: flush.c.

  * Queue hygiene: the postdrop command accepted the null record
    type which the rest of Postfix ignores. Reported by OpenAI
    Security. File: postdrop.c.

Revision 1.65.2.1: download - view: text, markup, annotated - select for diffs
Thu Jul 16 14:10:12 2026 UTC (4 months ago) by maya
Branches: pkgsrc-2026Q2
Diff to: previous 1.65: preferred, colored
Changes since revision 1.65: +2 -2 lines
Pullup ticket #7174 - requested by taca
mail/postfix: Security fix

Revisions pulled up:
- mail/postfix/Makefile                                         1.358
- mail/postfix/Makefile.common                                  1.66-1.67
- mail/postfix/distinfo                                         1.225-1.226

---
   Module Name:	pkgsrc
   Committed By:	taca
   Date:		Sat Jul  4 04:13:48 UTC 2026

   Modified Files:
   	pkgsrc/mail/postfix: Makefile Makefile.common distinfo

   Log Message:
   mail/postfix: update to 3.11.4

   Postfix 3.11.4 (2026-06-17)

   This release addresses five low-impact problems that need to be addressed as
   they can reduce safety margins.

   * Bug 1 (defect introduced: Postfix 3.1, date 20150607): null pointer read
     and heap data overread in the Postfix SMTP client's smtp_dns_reply_filter.
     Problem reported by TristanInSec, found with ASAN.  Also reported by other
     people.  Reproduction and real-world impact researched by Wietse.

   * Bug 2 (defect introduced: Postfix 3.6, date: 20200710): panic (assertion
     failure and voluntary crash) while parsing a TLSA reply with length 3.
     Found during code maintenance.  See below for root cause, reproduction,
     and impact.

   * Bug 3 (Problem introduced: Postfix 2.9, date: 20110205) Robustness: the
     Postfix SMTP server will no longer receive (and discard) an unlimited
     amount of text while receiving a long SMTP command line.  Problem reported
     by Michael Wollner (Ibonok).  Under high load conditions, the amount of
     text was already limited by a 10-second deadline to receive an SMTP
     command.

   * Bug 4 Robustness: with the above change the Postfix SMTP client will no
     longer receive (and discard) an unlimited amount of text while receiving a
     long SMTP response line.

   * Bug 5 (Problem introduced: Postfix 3.4, date: 20180825) Robustness: do not
     receive (and discard) unlimited amounts of data with BDAT
     commands. Problem found during code maintenance. File: smtpd/smtpd.c.

   For more detail, pleare refer
   <https://www.postfix.org/announcements/postfix-3.11.4.html>.

---
   Module Name:	pkgsrc
   Committed By:	taca
   Date:		Tue Jul  7 13:48:07 UTC 2026

   Modified Files:
   	pkgsrc/mail/postfix: Makefile.common distinfo

   Log Message:
   mail/postfix: update to 3.11.5

   3.11.5 (2026-07-06)

   This release addresses medium-impact problems that need to be fixed
   as some enable remote DOS, or local memory corruption.

   For more detail, please refer:
   <https://www.postfix.org/announcements/postfix-3.11.5.html>.

Revision 1.67: download - view: text, markup, annotated - select for diffs
Tue Jul 7 13:48:07 2026 UTC (4 months, 1 week ago) by taca
Branches: MAIN
Diff to: previous 1.66: preferred, colored
Changes since revision 1.66: +2 -2 lines
mail/postfix: update to 3.11.5

3.11.5 (2026-07-06)

This release addresses medium-impact problems that need to be fixed
as some enable remote DOS, or local memory corruption.

For more detail, please refer:
<https://www.postfix.org/announcements/postfix-3.11.5.html>.

Revision 1.66: download - view: text, markup, annotated - select for diffs
Sat Jul 4 04:13:48 2026 UTC (4 months, 1 week ago) by taca
Branches: MAIN
Diff to: previous 1.65: preferred, colored
Changes since revision 1.65: +2 -2 lines
mail/postfix: update to 3.11.4

Postfix 3.11.4 (2026-06-17)

This release addresses five low-impact problems that need to be addressed as
they can reduce safety margins.

* Bug 1 (defect introduced: Postfix 3.1, date 20150607): null pointer read
  and heap data overread in the Postfix SMTP client's smtp_dns_reply_filter.
  Problem reported by TristanInSec, found with ASAN.  Also reported by other
  people.  Reproduction and real-world impact researched by Wietse.

* Bug 2 (defect introduced: Postfix 3.6, date: 20200710): panic (assertion
  failure and voluntary crash) while parsing a TLSA reply with length 3.
  Found during code maintenance.  See below for root cause, reproduction,
  and impact.

* Bug 3 (Problem introduced: Postfix 2.9, date: 20110205) Robustness: the
  Postfix SMTP server will no longer receive (and discard) an unlimited
  amount of text while receiving a long SMTP command line.  Problem reported
  by Michael Wollner (Ibonok).  Under high load conditions, the amount of
  text was already limited by a 10-second deadline to receive an SMTP
  command.

* Bug 4 Robustness: with the above change the Postfix SMTP client will no
  longer receive (and discard) an unlimited amount of text while receiving a
  long SMTP response line.

* Bug 5 (Problem introduced: Postfix 3.4, date: 20180825) Robustness: do not
  receive (and discard) unlimited amounts of data with BDAT
  commands. Problem found during code maintenance. File: smtpd/smtpd.c.

For more detail, pleare refer
<https://www.postfix.org/announcements/postfix-3.11.4.html>.

Revision 1.65: download - view: text, markup, annotated - select for diffs
Sun May 17 15:03:51 2026 UTC (6 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2026Q2-base
Branch point for: pkgsrc-2026Q2
Diff to: previous 1.64: preferred, colored
Changes since revision 1.64: +2 -2 lines
mail/postfix: update to 3.11.3

3.11.3 (2026-05-17)

Fixed in Postfix 3.8-3.11:

  * Bitrot: builds with musl libc broke, because they were using an
    obsolete NO_SNPRINTF code path that had not been updated for Claude
    Code findings.

  * Two fixes for a signed integer overshift condition (a left shift into
    the sign bit). This "works" on contemporary CPUs, but may break in
    the future. One reported by Kamil Frankowicz, and one by Robert Sayre.

  * Viktor Dukhovni fixed an 'uninitialized value' error in the
    'collate.pl' script.

Fixed in Postfix 3.11:

  * Test code fixes by Viktor Dukhovni for a deprecation warning with
    OpenSSL 4.0, and for a race condition that caused a test script
    to fail.

Revision 1.63.2.1: download - view: text, markup, annotated - select for diffs
Thu May 7 22:40:07 2026 UTC (6 months, 1 week ago) by maya
Branches: pkgsrc-2026Q1
Diff to: previous 1.63: preferred, colored; next MAIN 1.64: preferred, colored
Changes since revision 1.63: +2 -2 lines
Pullup ticket #7098 - requested by taca
mail/postfix: Security fix

Revisions pulled up:
- mail/postfix/Makefile.common                                  1.64
- mail/postfix/distinfo                                         1.223
- mail/postfix/patches/patch-ag                                 1.43
- mail/postfix/patches/patch-ai                                 1.48

---
   Module Name:	pkgsrc
   Committed By:	taca
   Date:		Mon May  4 23:58:58 UTC 2026

   Modified Files:
   	pkgsrc/mail/postfix: Makefile.common distinfo
   	pkgsrc/mail/postfix/patches: patch-ag patch-ai

   Log Message:
   mail/postfix: update to 3.11.2

   Postfix 3.11.2 (2026-05-03)

   Fixed in Postfix 3.11:

     * Bugfix (defect introduced: Postfix 3.11): the proxymap(8) daemon
       dereferenced an uninitialized pointer after a request protocol
       error. This daemon is not exposed to local or remote users.
       Found by Claude Opus 4.6.

     * Bugfix (defect introduced: 20260309) a change, to set the
       service_name default value to "amnesiac", violated a test that
       parameter names in postconf output must match 1:1 with parameter
       names in the postlink script.

   Fixed in Postfix 3.8, 3.9, 3.10. 3.11:

     * Portability: support for recent FreeBSD, NetBSD, and OpenBSD
       versions. Brad Smith.

     * Bugfix (defect introduced: Postfix 2.2, date 20041207): When
       truncating a database file, the cdb: database client looked at
       the file size from before requesting an exclusive lock on a
       database file, instead of the file size after the exclusive
       lock was granted. Found by Claude Opus 4.6.

     * Bugfix (defect introduced: Postfix alpha, date 19980309): file
       descriptor leak after fork() failure. Found by Claude Opus 4.6.

     * Mistakes in debug logging. Found by Claude Opus 4.6. This
       affected two files in Postfix 3.8 and 3.9, three files in Postfix
       3.10 and 3.11.

     * Unchecked null pointer results after an out-of-memory condition
       in a library dependency. Found by Claude Opus 4.6. The fix is
       to return an error status or to log a fatal error. This affected
       three source files.

     * Missing or incomplete guards for ssize_t or int overflow, found
       by Claude Opus 4.6. This affected three source files. These
       limits are unlikely to be exceeded because the size of in-memory
       objects is limited by design (the number of in-memory objects
       is also limited).

Revision 1.64: download - view: text, markup, annotated - select for diffs
Mon May 4 23:58:58 2026 UTC (6 months, 1 week ago) by taca
Branches: MAIN
Diff to: previous 1.63: preferred, colored
Changes since revision 1.63: +2 -2 lines
mail/postfix: update to 3.11.2

Postfix 3.11.2 (2026-05-03)

Fixed in Postfix 3.11:

  * Bugfix (defect introduced: Postfix 3.11): the proxymap(8) daemon
    dereferenced an uninitialized pointer after a request protocol
    error. This daemon is not exposed to local or remote users.
    Found by Claude Opus 4.6.

  * Bugfix (defect introduced: 20260309) a change, to set the
    service_name default value to "amnesiac", violated a test that
    parameter names in postconf output must match 1:1 with parameter
    names in the postlink script.

Fixed in Postfix 3.8, 3.9, 3.10. 3.11:

  * Portability: support for recent FreeBSD, NetBSD, and OpenBSD
    versions. Brad Smith.

  * Bugfix (defect introduced: Postfix 2.2, date 20041207): When
    truncating a database file, the cdb: database client looked at
    the file size from before requesting an exclusive lock on a
    database file, instead of the file size after the exclusive
    lock was granted. Found by Claude Opus 4.6.

  * Bugfix (defect introduced: Postfix alpha, date 19980309): file
    descriptor leak after fork() failure. Found by Claude Opus 4.6.

  * Mistakes in debug logging. Found by Claude Opus 4.6. This
    affected two files in Postfix 3.8 and 3.9, three files in Postfix
    3.10 and 3.11.

  * Unchecked null pointer results after an out-of-memory condition
    in a library dependency. Found by Claude Opus 4.6. The fix is
    to return an error status or to log a fatal error. This affected
    three source files.

  * Missing or incomplete guards for ssize_t or int overflow, found
    by Claude Opus 4.6. This affected three source files. These
    limits are unlikely to be exceeded because the size of in-memory
    objects is limited by design (the number of in-memory objects
    is also limited).

Revision 1.63: download - view: text, markup, annotated - select for diffs
Wed Mar 11 15:25:57 2026 UTC (8 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2026Q1-base
Branch point for: pkgsrc-2026Q1
Diff to: previous 1.62: preferred, colored
Changes since revision 1.62: +3 -3 lines
mail/postfix: update to 3.11.1

3.11.1 (2026-03-10)

* Bugfix (defect introduced: 20260219): alias_maps errors when
  default_database_type was not set in main.cf. Fix by Michael
  Tokarev.

* Bugfix (defect introduced: Postfix 3.0): buffer over-read when
  Postfix is configured with an enhanced status code not followed
  by other text. For example, "5.7.2" without text after the
  three-number code, in an access(5) table, header or body checks,
  or with "$rbl_code $rbl_text" in rbl_reply_maps or default_rbl_reply.
  These are all uncommon configurations. Problem reported by Kamil
  Frankowicz.

* Bugfix (defect introduced: Postfix 3.3): null pointer in
  nbdb_reindexd(8) because the "service_name" value was not
  propagated. Report by Michael Tokarev.

* During Postfix start-up, avoid a spurious error message from
  nbdb_reindexd(8), when non_bdb_migration_level disables automatic
  re-indexing.

Revision 1.62: download - view: text, markup, annotated - select for diffs
Sun Mar 8 14:13:42 2026 UTC (8 months, 1 week ago) by taca
Branches: MAIN
Diff to: previous 1.61: preferred, colored
Changes since revision 1.61: +2 -2 lines
mail/postfix: update to 3.11.0

Postfix 3.11.0 (2026-03-05)

Berkeley DB migration:

  * Some (Linux) distributions are removing support for BerkeleyDB
    databases (In Postfix, this means we lose support for the hash:
    and btree: lookup tables). See NON_BERKELEYDB_README for manual and
    partially automatic migration from btree: to lmdb:, and from hash:
    to lmdb: or cdb:.

  * The loss of BerkeleyDB affects Mailman versions that want to execute
    commands like "postmap hash:/path/to/file" when a mailing list is
    added or removed. Postfix provides a way to redirect such commands
    to a supported database type.

  * You don't have to wait until BerkeleyDB support is removed. It can
    make sense to migrate while BerkeleyDB support is still available
    (mainly, less downtime).

Changes in TLS support:

  * Default TLS security. The Postfix SMTP client smtp_tls_security_level
    default value is "may" if Postfix was built with TLS support, and
    the compatibility_level is 3.11 or higher.

  * Support for the RFC 8689 "REQUIRETLS" verb in ESMTP. This requires
    that every SMTP (and LMTP) server in the forward path is strongly
    authenticated with DANE, STS, or equivalent, and that every server
    announces REQUIRETLS support.

    See REQUIRETLS_README for suggestions to carefully enforce REQUIRETLS
    without causing massive mail delivery problems.

  * Logging the TLS security level. This shows the desired and actual
    TLS security level enforcement status and, if a message requests
    REQUIRETLS, the REQUIRETLS policy enforcement status. For a list of
    examples see smtp_log_tls_feature_status

  * Workaround for an interface mismatch between the Postfix SMTP
    client and MTA-STS policy plugins. This introduces a new parameter
    smtp_tls_enforce_sts_mx_patterns (default: "yes"). The MTA-STS
    plugin configuration needs to enable TLSRPT support, so that it
    forwards STS policy attributes to Postfix. Both postfix-tlspol and
    postfix-mta-sts-resolver have been updated accordingly.

    With this, the Postfix SMTP client will connect to an MX host only
    if its name matches any STS policy MX host pattern, and will match
    a server certificate against the MX hostname. Otherwise, the old
    behavior stays in effect: connect to any MX host listed in DNS,
    and match a server certificate against any STS policy MX host pattern.

  * Post-quantum cryptography support. With OpenSSL 3.5 and later, change
    the tls_eecdh_auto_curves default value to avoid problems with network
    infrastructure that mishandles TLS hello messages larger than one
    (Ethernet) TCP segment. This problem is more generally known as
    "protocol ossification".

Miscellaneous changes:

  * Deprecation of obsolete parameters. Postfix programs log a warning
    that these parameters will be removed. See DEPRECATION_README for
    a list of deprecated parameters.

  * JSON output support with "postconf -j|-jM|-jF|-jP", "postalias
    -jq|-js", "postmap -jq|-js", and "postmulti -jl". No support is
    planned for JSON input support.

  * Milter support: improved Milter error handling for messages that
    arrive over a long-lived SMTP connection, by changing the default
    milter_default_action from "tempfail" to the new "shutdown" action
    (i.e. disconnect the remote SMTP client). This was already back-ported
    to earlier stable releases.

Revision 1.61: download - view: text, markup, annotated - select for diffs
Sun Mar 1 08:01:11 2026 UTC (8 months, 2 weeks ago) by taca
Branches: MAIN
Diff to: previous 1.60: preferred, colored
Changes since revision 1.60: +2 -2 lines
mail/postfix: update to 3.10.8

3.10.8 (2026-02-19)

Fixes for all supported Postfix releases:

  * Improved Milter error handling for messages that arrive over a
    long-lived SMTP connection, by changing the default
    milter_default_action from "tempfail" to the new "shutdown"
    action (i.e. disconnect the remote SMTP client).

    The problem was that after a single Milter error, Postfix could
    tempfail all messages that the client sends over a long-lived
    connection, even if the Milter error was only temporary. This
    problem was reported by Ankit Kulkarni.

  * Bugfix (defect introduced: Postfix 2.11): "posttls-finger -v
    -v -v" terminated with a panic, caused by recursive logging.
    Reported by Geert Hendrickx, diagnosed by Viktor Dukhovni, and
    fixed by Wietse.

Revision 1.60: download - view: text, markup, annotated - select for diffs
Tue Dec 9 14:21:03 2025 UTC (11 months, 1 week ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2025Q4-base, pkgsrc-2025Q4
Diff to: previous 1.59: preferred, colored
Changes since revision 1.59: +2 -2 lines
mail/postfix: update to 3.10.7

3.10.6 (2025-11-25)

  * Bugfix (defect introduced: Postfix 3.10, date: 20250117).
    Symptom: warning messages that smtp_tls_wrappermode requires
    "smtp_tls_security_level = encrypt".
    Root cause: support for "TLS-Required: no" broke client-side
    TLS wrappermode support, by downgrading a connection to TLS
    security level 'may'.
    The fix changes the downgrade level for wrappermode connections
    to 'encrypt'. Rationale: by design, TLS can be optional only
    for connections that use STARTTLS. The downgrade to unauthenticated
    'encrypt' allows a sender to avoid an email delivery problem.
    Problem reported by Joshua Tyler Cochran.

  * New logging: the Postfix SMTP client will log a warning when
    an MX hostname does not match STS policy MX patterns, with
    "smtp_tls_enforce_sts_mx_patterns = yes" in Postfix, and with
    TLSRPT support enabled in a TLS policy plugin. It will log a
    successful match only when verbose logging is enabled.

  * Bugfix (defect introduced: Postfix 3.10, date: 20240902): SMTP
    client null pointer crash when an STS policy plugin sends no
    policy_string or no mx_pattern attributes. This can happen only
    during tests with a fake STS plugin.

  * Bugfix (defect introduced: Postfix 2.9, date: 20120307): segfault
    when a duplicate parameter name is given to "postconf -X" or
    "postconf -#'.

  * Documentation: removed incorrect text from the parameter
    description for smtp_cname_overrides_servername. File:
    proto/postconf.proto.


3.10.7 (2025-12-07)

  * This patch addresses build errors on recent Linux distributions. With
    the patch, Postfix builds will run the compiler with a backwards
    compatibility option that is supported by Gcc and Clang. For other
    compilers, an error message provides hints.

    Background: the build errors are caused by C compilers that by
    default define a 'bool' type (size=1) that conflicts with Postfix's
    'bool' type (an alias for 'int', typically size=4). Postfix 3.11
    will support the new bool type, but that change is too large for
    stable Postfix releases (too many lines in too many files).

    This patch will also apply to Postfix 3.6 all the way back to
    Postfix 3.0 with a simple change: remove the Prereq: line, and
    remove the part that updates the HISTORY file.

Revision 1.59: download - view: text, markup, annotated - select for diffs
Mon Nov 3 08:59:18 2025 UTC (12 months, 1 week ago) by taca
Branches: MAIN
Diff to: previous 1.58: preferred, colored
Changes since revision 1.58: +2 -2 lines
mail/postfix: update to 3.10.5

Postfix 3.10.5 (2025-10-27)

Fixes for Postfix 3.10 only:

  * Workaround for an interface mis-match between the Postfix SMTP
    client and MTA-STS policy plugins.

      * The existing behavior is to connect to any MX host listed
        in DNS, and to match the server certificate against any STS
        policy MX host pattern.

      * The corrected behavior is to connect to an MX host only if
        its name matches any STS policy MX host pattern, and to
        match the server certificate against the MX hostname.

    The corrected behavior must be enabled in two places: in Postfix
    with a new parameter "smtp_tls_enforce_sts_mx_patterns" (default:
    "yes") and in an MTA-STS plugin by enabling TLSRPT support, so
    that the plugin forwards STS policy attributes to Postfix. This
    works even if Postfix TLSRPT support is disabled at build time
    or at runtime.

  * TLSRPT Workaround: when a TLSRPT policy-type value is
    "no-policy-found", pretend that the TLSRPT policy domain value
    is equal to the recipient domain. This ignores that different
    policy types (TLSA, STS) use different policy domains. But this
    is what Microsoft does, and therefore, what other tools expect.

Fixes for Postfix 3.10, 3.9, 3.8, 3.7:

  * Bugfix (defect introduced: Postfix 3.0): the Postfix SMTP
    client's connection reuse logic did not distinguish between
    sessions that require SMTPUTF8 support, and sessions that do
    not. The solution is 1) to store sessions with different SMTPUTF8
    requirements under distinct connection cache storage keys, and
    2) to not cache a connection when SMTPUTF8 is required but the
    server does not support that feature.

  * Bugfix (defect introduced: Postfix 3.0, date 20140731): the
    smtpd 'disconnect' command statistics did not count commands
    with "bad syntax" and "bad UTF-8 syntax" errors.

  * Bugfix: the August 2025 patch broke DBM library support which
    is still needed on Solaris; and the same change could result
    in warnings with "database X is older than source file Y".

  * Postfix 3.11 forward compatibility: to avoid ugly warnings when
    Postfix 3.11 is rolled back to an older version, allow a
    preliminary 'size' record in maildrop queue files created with
    Postfix 3.11 or later.

  * Bugfix (defect introduced: Postfix 3.8, date 20220128):
    non-reproducible build, because the 'postconf -e' output order
    for new main.cf entries was no longer deterministic. Problem
    reported by Oleksandr Natalenko, diagnosis by Eray Aslan.

  * To make builds predictable, add missing meta_directory and
    shlib_directory settings to the stock main.cf file. Problem
    diagnosed by Eray Aslan.

Fixes for Postfix 3.10, 3.9, 3.8:

  * Bugfix (defect introduced: Postfix 3.9, date 20230517):
    posttls-finger(1) logged an incorrectly-formatted port number.
    Viktor Dukhovni.

Revision 1.58: download - view: text, markup, annotated - select for diffs
Sun Aug 24 22:07:34 2025 UTC (14 months, 3 weeks ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2025Q3-base, pkgsrc-2025Q3
Diff to: previous 1.57: preferred, colored
Changes since revision 1.57: +2 -2 lines
mail/postfix: update to 3.10.4

Postfix 3.10.4 (2025-08-19)

Fixes for Postfix 3.10, 3.9, 3.8, 3.7:

  * Fixes for postscreen(8):

      * Bugfix (defect introduced: Postfix 2.2, date 20050203): after
        detecting a lookup table change, and after starting a new
        postscreen process, the old postscreen process logged an ENOTSOCK
        error while attempting to accept a connection on a socket that
        it was no longer listening on. This error was introduced first
        in the multi_server skeleton code, and was five years later
        duplicated in the event_server skeleton that was created for
        postscreen. Problem reported by Florian Piekert.

      * Bugfix (defect introduced: Postfix 2.8, date 20101230):
        after detecting a cache table change and before starting a new
        postscreen process, the old postscreen process did not close the
        postscreen_cache_map, and therefore kept an exclusive lock that
        could prevent a new postscreen process from starting. Problem
        reported by Florian Piekert.

  * Fixes for tlsproxy(8):

      * Bugfix (defect introduced: Postfix 3.7): incorrect backwards
        compatible support for the legacy configuration parameters
        tlsproxy_client_level and tlsproxy_client_policy. This
        disabled the tlsproxy TLS client role when a legacy parameter
        was set (instead of the newer tlsproxy_client_security_level
        or tlsproxy_client_policy_maps). Reported by John Doe,
        diagnosed by Viktor Dukhovni.

      * Bugfix (defect introduced: Postfix 3.4): with the TLS client role
        disabled by configuration, the tlsproxy daemon dereferenced a
        null pointer while handling a tlsproxy client request. Reported by
        John Doe.

  * Reducing process churn: Postfix daemons no longer automatically
    restart after a btree:, dbm:, hash:, lmdb:, or sdbm: table file
    modification time change, when they opened that table for writing.

  * Portability: deleted an <openssl/engine.h> build dependency,
    because the feature is being removed from OpenSSL, and Postfix
    no longer needs it.

Fixes for Postfix 3.10 only:

  * Cleanup: with "tls_required_enable = yes", the Postfix SMTP client
    will no longer maintain TLSRPT statistics for messages that contain
    a "TLS-Required: no" header. This can prevent TLSRPT notifications
    for TLSRPT notifications.

  * Bugfix (defect introduced: Postfix 3.6, date 20200710): Postfix TLS
    client code logged "Untrusted TLS connection" (wrong) instead of
    "Trusted TLS connection" (right), for a new or resumed TLS session,
    when a server offered a trusted (valid PKI trust chain) certificate
    that did not match the expected server name pattern. Fix by Viktor
    Dukhovni.

Revision 1.57: download - view: text, markup, annotated - select for diffs
Sat Jul 26 06:56:45 2025 UTC (15 months, 3 weeks ago) by taca
Branches: MAIN
Diff to: previous 1.56: preferred, colored
Changes since revision 1.56: +2 -2 lines
mail/postfix: update to 3.10.3

Postfix 3.10.3 (2025-07-10)

This release fixes defects that were introduced in Postfix 3.10.
These were fixed first in the Postfix 3.11 unstable release.

The defects exist only with the default configuration "tls_required_enable
= yes".

* Bugfix (defect introduced: Postfix-3.10, date 20250117): include
  the current TLS security level in the SMTP connection cache
  lookup key for lookups by next-hop destination, to avoid reusing
  the same SMTP connection when sending messages with and without
  a "TLS-Required: no" header. Likewise, include the current TLS
  security level in the TLS session lookup key, to avoid reusing
  the same TLS session info when sending messages with and without
  a "TLS-Required: no" header.

* Bugfix (defect introduced: Postfix-3.10, date 20250117): the
  Postfix SMTP client attempted to look up TLSA records even with
  "TLS-Required: no". This could result in unnecessary failures.
  Fix by Viktor Dukhovni & Wietse.

Revision 1.56: download - view: text, markup, annotated - select for diffs
Mon May 19 15:56:57 2025 UTC (17 months, 4 weeks ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2025Q2-base, pkgsrc-2025Q2
Diff to: previous 1.55: preferred, colored
Changes since revision 1.55: +2 -2 lines
mail/postfix: update to 3.10.2

Postfix 3.10.2 (2025-04-22)

* Bugfix (defect introduced: date 19991116): when appending a
  setting to a main.cf or master.cf file that did not end in a
  newline character, the "postconf -e" command did not add an
  extra newline character before appending the new setting, causing
  information to become garbled. Fix by Michael Tokarev.

* Bugfix (defect introduced: Postfix 2.3, date 20051222): the
  Dovecot auth client did not attempt to create a new connection
  after an I/O error on an existing connection. Reported by
  Oleksandr Kozmenko.

* Improved and corrected error messages when converting (host or
  service) information to (symbolic text, numerical text, or
  binary) form.

* Documentation: updated link to Dovecot documentation.

Revision 1.55: download - view: text, markup, annotated - select for diffs
Tue May 6 12:07:33 2025 UTC (18 months, 1 week ago) by wiz
Branches: MAIN
Diff to: previous 1.54: preferred, colored
Changes since revision 1.54: +3 -3 lines
*: SOEXT -> SHLIB_EXT

Revision 1.54: download - view: text, markup, annotated - select for diffs
Tue Mar 11 18:11:58 2025 UTC (20 months ago) by nia
Branches: MAIN
CVS tags: pkgsrc-2025Q1-base, pkgsrc-2025Q1
Diff to: previous 1.53: preferred, colored
Changes since revision 1.53: +14 -1 lines
postfix: Build fixes for OpenBSD and Linux

Found by drecklypkg ci.

Revision 1.53: download - view: text, markup, annotated - select for diffs
Tue Mar 11 16:49:20 2025 UTC (20 months ago) by nia
Branches: MAIN
Diff to: previous 1.52: preferred, colored
Changes since revision 1.52: +5 -2 lines
postfix: Prefer HTTPS for MASTER_SITES

Revision 1.52: download - view: text, markup, annotated - select for diffs
Thu Feb 27 15:42:54 2025 UTC (20 months, 2 weeks ago) by taca
Branches: MAIN
Diff to: previous 1.51: preferred, colored
Changes since revision 1.51: +2 -2 lines
mail/postfix: update to 3.10.1

3.10.1 (2025-02-24)

Fix for Postfix 3.10, 3.9, 3.8, 3.7, 3.6:

  * Bugfix (defect introduced: 20250210): a recent 'fix' for the
    default smtp_tls_dane_insecure_mx_policy setting resulted in
    unnecessary 'dnssec_probe' warnings, on systems that disable
    DNSSEC lookups (which is the default).

Revision 1.51: download - view: text, markup, annotated - select for diffs
Sat Feb 22 16:00:18 2025 UTC (20 months, 3 weeks ago) by taca
Branches: MAIN
Diff to: previous 1.50: preferred, colored
Changes since revision 1.50: +2 -2 lines
mail/postfix: update to 3.10.0

Postfix 3.10.0 (2025/02/17)

Postfix stable release 3.10.0 is available. Postfix 3.6 - 3.9 were updated
earlier this week; after that, Postfix 3.6 will no longer be updated.

The main changes are below. See the RELEASE_NOTES file for further
details.

Changes that need restart:

  * Internal protocol change: Postfix needs "postfix reload" (or "postfix
    stop" and "postfix start") after upgrade, because of a change in the
    delivery agent protocol. If this step is skipped, Postfix delivery
    agents will log a warning:

	unexpected attribute smtputf8 from xxx socket (expecting: sendopts)

    where xxx is the delivery agent service name.

Changes in TLS support:

  * Forward compatibility: Support for OpenSSL 3.5 post-quantum
    cryptography. To manage algorithm selection, OpenSSL introduces new
    TLS group syntax that Postfix will not attempt to imitate. Instead,
    Postfix now allows the tls_eecdh_auto_curves and tls_ffdhe_auto_groups
    parameter values to have an empty value. When both are set empty, the
    algorithm selection can be managed through OpenSSL configuration. For
    more, look for "Post-quantum" in the postconf(5) manpage.

  * Support for the RFC 8689 "TLS-Required: no" message header to request
    delivery of messages (such as TLSRPT summaries) even if the preferred
    TLS security policy cannot be enforced. This limits the Postfix SMTP
    client to "smtp_tls_security_level = may" which does not authenticate
    server certificates and which allows falling back to plaintext.

  * Support for the REQUIRETLS SMTP service extension will evolve in
    Postfix 3.11.

  * Support for the TLSRPT protocol (defined in RFC 8460). With this,
    a domain can publish a policy in DNS that requests daily summary
    reports for successful and failed SMTP-over-TLS connections to that
    domain's MX hosts. This supports both DANE (built-in) and MTA-STS
    (via an smtp_tls_policy_maps plugin). The implementation uses a
    TLSRPT library and reporting infrastructure that are maintained by
    sys4. For details, see TLSRPT_README.

Miscellaneous changes:

  * Privacy: With "smtpd_hide_client_session = yes", the Postfix
    SMTP server generates a Received: header without client session
    info. This setting may be used with the MUA submission services
    (port 465 and 587).

  * Support for RFC 2047 encoding of non-ASCII "full name" information
    in Postfix-generated From: message headers. Encoding non-ASCII full
    names can avoid the need to use SMTPUTF8, and therefore can avoid
    incompatibility with sites that do not support SMTPUTF8. See the
    full_name_encoding_charset parameter description for details.

  * Database performance: When mysql: or pgsql: configuration specifies
    a single host, assume that it is a load balancer and reconnect
    immediately after a single failure, instead of failing all requests
    for 60s.

Changes in logging:

  * The Postfix Milter implementation now logs the reason for a
    'quarantine' action, instead of "milter triggers HOLD action".

  * The SMTP server now logs the queue ID (or "NOQUEUE") when a connection
    ends abnormally (timeout, lost connection, or too many errors),
    and the cleanup server now logs "queueid: canceled" when a message
    transaction is started but not completed. These changes simplify
    logfile analysis.

  * Dovecot SASL client logging for "Invalid authentication mechanism"
    now includes the name of that mechanism.

  * Postfix SMTP server 'reject' logging now shows the sasl_method,
    sasl_username, and sasl_sender if available.

Revision 1.50: download - view: text, markup, annotated - select for diffs
Mon Feb 17 15:31:51 2025 UTC (20 months, 4 weeks ago) by taca
Branches: MAIN
Diff to: previous 1.49: preferred, colored
Changes since revision 1.49: +2 -2 lines
mail/postfix: update to 3.9.2

Postfix 3.9.2 (2025-02-17)

  * Forward compatibility: Support for OpenSSL 3.5 post-quantum
    cryptography. To manage algorithm selection, OpenSSL introduces new
    TLS group syntax that Postfix will not attempt to imitate. Instead,
    Postfix now allows the tls_eecdh_auto_curves and tls_ffdhe_auto_groups
    parameter values to have an empty value. When both are set
    empty, the algorithm selection can be managed through OpenSSL
    configuration. Viktor Dukhovni.

  * Forward compatibility: ignore new queue file flag bits that may be
    used with Postfix 3.10 and later. This is a safety in case a Postfix
    3.10 upgrade needs to be rolled back, after the new TLS-Required
    feature has been used.

  * Performance: when a mysql: or pgsql: configuration specifies a single
    host, assume that it is a load balancer and reconnect immediately
    after a single failure, instead of failing all requests for 60s.

  * Bugfix (defect introduced: Postfix 3.4, date 20181113): a server with
    multiple TLS certificates could report, for a resumed TLS session,
    the wrong server-signature and server-digest names in logging and
    Received: message headers. Viktor Dukhovni.

  * Bugfix (defect introduced: Postfix 3.3, date 20180107) small memory
    leak in the cleanup daemon when generating a "From: full-name "
    message header. The impact is limited because the number of requests
    is bounded by the "max_use" configuration parameter. Found during
    code maintenance.

  * Bugfix (defect introduced: Postfix 3.0): the bounce daemon mangled
    a non-ASCII address localpart in the "X-Postfix-Sender:" field of
    a delivery status notification. It backslash-escaped each byte in a
    multi-byte character. This behavior was implemented in Postfix 2.1
    (no support for UTF8 local-parts), but it became incorrect after
    SMTPUTF8 support was implemented in Postfix 3.0.

  * Bugfix (defect introduced: Postfix 3.6): Reverted the default
    smtp_tls_dane_insecure_mx_policy setting to "dane" as of Postfix
    3.6.17, 3.7.13, 3.8.8, 3.9.2, and 3.10.0. By mistake the default was
    dependent on the smtp_tls_security_level setting. Problem reported
    by ?mer G?ven.

  * Portability: added "include <sys_socket.h>" for a SUNOS5
    workaround. Gary R. Schmidt.

Revision 1.49: download - view: text, markup, annotated - select for diffs
Sat Dec 7 06:08:57 2024 UTC (23 months, 1 week ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2024Q4-base, pkgsrc-2024Q4
Diff to: previous 1.48: preferred, colored
Changes since revision 1.48: +2 -2 lines
mail/postfix: update to 3.9.1

Postfix 3.9.1 (2024-12-04)

Postfix stable release 3.9.1, and legacy releases 3.8.7, 3.7.12,
3.6.16 [An on-line version of this announcement will be available
at https://www.postfix.org/announcements/postfix-3.9.1.html]

Fixed with Postfix 3.9.1:

  * The mail_version configuration parameter did not have a
    three-number value (3.9 instead of 3.9.0 (it still had the
    two-number version from the development releases postfix-3.9-yyyymmdd).
    This broke pathnames derived from the mail_version value, such
    as shlib_directory. Problem reported by Michael Orlitzky.

Fixed with Postfix 3.9.1, 3.8.7, 3.7.12, 3.6.16:

  * Bugfix (defect introduced: Postfix 2.9, date 20111218): with
    "smtpd_sasl_auth_enable = no", the permit_sasl_authenticated
    feature ignored information that was received with the XCLIENT
    LOGIN command, so that the client was treated as unauthenticated.
    This was fixed by removing an unnecessary test. Problem reported
    by Antonin Verrier.

  * Bugfix (defect introduced: postfix 3.0): the default master.cf
    multi-instance information, which complicated logfile analysis.
    Found during a support discussion.

  * Bugfix (defect introduced: Postfix 2.3, date 20051222): file
    descriptor leak after failure to connect to a Dovecot auth
    server. The impact is limited because Dovecot auth failures are
    rare, there are limits on the number of retries (one), on the
    number of errors per SMTP session (smtpd_hard_error_limit), on
    the number of sessions per SMTP server process (max_use), and
    on the number of file handles per process (managed with sysctl).
    Found during code maintenance.

  * Bugfix (defect introduced: Postfix 3.4, date 20190121): the
    postsuper command failed with "open logfile '/path/to/file':
    Permission denied" when the maillog_file parameter specified a
    filename and Postfix was not running. This was fixed by opening
    the maillog_file before dropping root privileges. Found during
    code maintenance.

  * Bugfix (defect introduced Postfix 3.0). No autodetection of
    UTF8 text when missing message headers were automatically
    added by Postfix (for example, a From: header with UTF8 full
    name information from the password file). This caused Postfix
    to send UTF8 in message headers without using the SMTPUTF8
    protocol. Problem reported by Michael Tokarev.

Revision 1.48: download - view: text, markup, annotated - select for diffs
Sun Jun 2 15:43:31 2024 UTC (2 years, 5 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2024Q3-base, pkgsrc-2024Q3, pkgsrc-2024Q2-base, pkgsrc-2024Q2
Diff to: previous 1.47: preferred, colored
Changes since revision 1.47: +2 -2 lines
mail/postfix: update to 3.9.0

From release announce
<https://www.postfix.org/announcements/postfix-3.9.0.html>:

Postfix stable release 3.9.0 is available. Postfix 3.5 - 3.8 were
updated earlier this week; after that, Postfix 3.5 will no longer
be updated.

The main changes are below. See the RELEASE_NOTES file for further
details.

Removed functionality:

  * As described in DEPRECATION_README, the SMTP server features
    "permit_naked_ip_address", "check_relay_domains", and
    "reject_maps_rbl" have been removed, after they have been logging
    a warning for some 20 years. These features now log a warning
    and return a "server configuration error" response.

  * The MySQL client no longer supports MySQL versions < 4.0. MySQL
    version 4.0 was released in 2003.

Officially obsolete functionality:

  * As covered in DEPRECATION_README, the configuration parameter
    "disable_dns_lookup" and about a dozen TLS-related parameters
    are now officially obsolete. These parameters still work, but
    the postconf command logs warnings that they will be removed
    from Postfix.

  * As covered in DEPRECATION_README, "permit_mx_backup" logs a
    warning that it will be removed from Postfix.

Changed functionality:

  * In message headers, Postfix now formats numerical days as
    two-digit days, i.e. days 1-9 have a leading zero instead of a
    leading space. This change was made because the RFC 5322 date
    and time specification recommends (i.e. SHOULD) that a single
    space be used in each place that folding white space appears.
    This change avoids a breaking change in the length of a date
    string.

  * The MySQL client default characterset is now configurable with
    the "charset" configuration file attribute. The default is
    "utf8mb4", consistent with the MySQL 8.0 built-in default, but
    different from earlier MySQL versions where the built-in default
    was "latin1".

New functionality:

  * Support to query MongoDB databases, contributed by Hamid Maadani,
    based on earlier code by Stephan Ferraro. See MONGODB_README
    and mongodb_table(5)

  * The RFC 3461 envelope ID is now exported in the local(8) delivery
    agent with the ENVID environment variable, and in the pipe(8)
    delivery agent with the ${envid} command-line attribute.

  * Configurable idle and retry timer settings in the mysql: and
    pgsql: clients. A shorter than default retry timer can sped up
    the recovery after error, when Postfix is configured with only
    one server in the "hosts" attribute. After the code was frozen
    for release, we have learned that Postfix can recover faster
    from some errors when the single server is specified multiple
    times in the "hosts" attribute.

  * Optional Postfix TLS support to request an RFC7250 raw public
    key instead of an X.509 public-key certificate. The configuration
    settings for raw key public support will be ignored when there
    is no raw public key support in the local TLS implementation
    (i.e. Postfix with OpenSSL versions before 3.2). See RELEASE_NOTES
    for more information.

  * Preliminary support for OpenSSL configuration files, primarily
    OpenSSL 1.1.1b and later. This introduces two new parameters
    "tls_config_file" and "tls_config_name", which can be used to
    limit collateral damage from OS distributions that crank up
    security to 11, increasing the number of plaintext email
    deliveries. Details are in the postconf(5) manpage under
    "tls_config_file" and "tls_config_name".

Attack resistance:

  * With "smtpd_forbid_unauth_pipelining = yes" (the default),
    Postfix defends against multiple "blind" SMTP attacks. This
    feature was back-ported to older stable releases but disabled
    by default.

  * With "smtpd_forbid_bare_newline = normalize" (the default)
    Postfix defends against SMTP smuggling attacks. See RELEASE_NOTES
    for details. This feature was back-ported to older stable
    releases but disabled by default.

  * Prevent outbound SMTP smuggling, where an attacker uses Postfix
    to send email containing a non-standard End-of-DATA sequence,
    to exploit inbound SMTP smuggling at a vulnerable remote SMTP
    server. With "cleanup_replace_stray_cr_lf = yes" (the default),
    the cleanup daemon replaces each stray <CR> or <LF> character
    in message content with a space character. This feature was
    back-ported to older stable releases with identical functionality.

  * The Postfix DNS client now limits the total size of DNS lookup
    results to 100 records; it drops the excess records, and logs
    a warning. This limit is 20x larger than the number of server
    addresses that the Postfix SMTP client is willing to consider
    when delivering mail, and is far below the number of records
    that could cause a tail recursion crash in dns_rr_append() as
    reported by Toshifumi Sakaguchi. This also introduces a similar
    limit on the number of DNS requests that a check_*_*_access
    restriction can make. All this was back-ported to older stable
    releases with identical functionality.

Revision 1.47: download - view: text, markup, annotated - select for diffs
Wed Feb 28 15:16:19 2024 UTC (2 years, 8 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2024Q1-base, pkgsrc-2024Q1
Diff to: previous 1.46: preferred, colored
Changes since revision 1.46: +2 -2 lines
mail/postfix: upadte to 3.8.5

3.8.5 (2024-01-22)

Security: this release improves support to defend against an email
spoofing attack (SMTP smuggling) on recipients at a Postfix server. For
background, see https://www.postfix.org/smtp-smuggling.html.

The improvements provide better logging, and better compatibility with
existing SMTP clients (less need to allowlist clients).

Sites concerned about SMTP smuggling attacks should enable this feature
on Internet-facing Postfix servers. For compatibility with non-standard
clients, Postfix by default excludes clients in mynetworks from this
countermeasure.

The recommended settings are:

    # Require the standard End-of-DATA sequence <CR><LF>.<CR><LF>.
    # Otherwise, allow bare <LF> and process it as if the client sent
    # <CR><LF>.
    #
    # This maintains compatibility with many legitimate SMTP client
    # applications that send a mix of standard and non-standard line
    # endings, but will fail to receive email from client implementations
    # that do not terminate DATA content with the standard End-of-DATA
    # sequence <CR><LF>.<CR><LF>.
    #
    # Such clients can be allowlisted with smtpd_forbid_bare_newline_exclusions.
    # The example below allowlists SMTP clients in trusted networks.
    #
    smtpd_forbid_bare_newline = normalize
    smtpd_forbid_bare_newline_exclusions = $mynetworks

Notes:

  * The default setting is "smtpd_forbid_bare_newline = no" in Postfix
    releases < 3.9, for compatibility reasons. This means that Postfix
    is by default vulnerable to SMTP smuggling.

  * The new setting "smtpd_forbid_bare_newline = normalize" is the
    default for Postfix releases 3.9 and later.

  * The old setting "smtpd_forbid_bare_newline = yes" is now an alias for
    "smtpd_forbid_bare_newline = normalize".

  * The new setting "smtpd_forbid_bare_newline = reject" will refuse
    commands or message content with a bare newline. For details see
    the RELEASE_NOTES or the postconf(5) documentation.

Revision 1.46: download - view: text, markup, annotated - select for diffs
Fri Dec 22 17:29:17 2023 UTC (2 years, 10 months ago) by wiz
Branches: MAIN
CVS tags: pkgsrc-2023Q4-base, pkgsrc-2023Q4
Diff to: previous 1.45: preferred, colored
Changes since revision 1.45: +2 -2 lines
postfix*: update to 3.8.4

20230815

	Bugfix (bug introduced: 20140218): when opportunistic TLS fails
	during or after the handshake, don't require that a probe
	message spent a minimum time-in-queue before falling back to
	plaintext. Problem reported by Serg. File: smtp/smtp.h.

20230819

	Bugfix (defect introduced: 19980207): the valid_hostname()
	check in the Postfix DNS client library was blocking unusual
	but legitimate wildcard names (*.name) in some DNS lookup
	results and lookup requests. Examples:

            name          class/type value
            *.one.example   IN CNAME *.other.example
            *.other.example IN A     10.0.0.1
            *.other.example IN TLSA  ..certificate info...

	Such syntax is blesed in RFC 1034 section 4.3.3.

	This problem was reported first in the context of TLSA
	record lookups. Files: util/valid_hostname.[hc],
	dns/dns_lookup.c.

20230929

	Bugfix (defect introduced Postfix 2.5, 20080104): the Postfix
	SMTP server was waiting for a client command instead of
	replying immediately, after a client certificate verification
	error in TLS wrappermode. Reported by Andreas Kinzler. File:
	smtpd/smtpd.c.

20231006

	Usability: the Postfix SMTP server now attempts to log the
	SASL username after authentication failure. In Postfix
	logging, this appends ", sasl_username=xxx" after the reason
	for SASL authentication failure. The logging replaces an
	unavailable reason with "(reason unavailable)", and replaces
	an unavailable sasl_username with "(unavailable)". Based
	on code by Jozsef Kadlecsik. Files: xsasl/xsasl_server.c,
	xsasl/xsasl_cyrus_server.c, smtpd/smtpd_sasl_glue.c.

20231026

	Bugfix (defect introduced: Postfix 2.11): in forward_path,
	the expression ${recipient_delimiter} would expand to an
	empty string when a recipient address had no recipient
	delimiter. Fixed by restoring Postfix 2.10 behavior to use
	a configured recipient delimiter value. Reported by Tod
	A. Sandman. Files: proto/postconf.proto, local/local_expand.c.

20231221

	Security: with "smtpd_forbid_bare_newline = yes" (default
	"no" for Postfix < 3.9), reply with "Error: bare <LF>
	received" and disconnect when an SMTP client sends a line
	ending in <LF>, violating the RFC 5321 requirement that
	lines must end in <CR><LF>. This prevents SMTP smuggling
	attacks that target a recipient at a Postfix server. For
	backwards compatibility, local clients are excluded by
	default with "smtpd_forbid_bare_newline_exclusions =
	$mynetworks". Files: mantools/postlink, proto/postconf.proto,
	global/mail_params.h, global/smtp_stream.c, global/smtp_stream.h,
	smtpd/smtpd.c.

Revision 1.45: download - view: text, markup, annotated - select for diffs
Sat Jul 15 14:56:26 2023 UTC (3 years, 4 months ago) by otis
Branches: MAIN
CVS tags: pkgsrc-2023Q3-base, pkgsrc-2023Q3
Diff to: previous 1.44: preferred, colored
Changes since revision 1.44: +2 -2 lines
postfix: Update to 3.8.1

Major changes with Postfix 3.8.1
================================

- Security: the Postfix SMTP server optionally disconnects remote SMTP clients
  that violate RFC 2920 (or 5321) command pipelining constraints. The server
  replies with "554 5.5.0 Error: SMTP protocol synchronization" and logs the
  unexpected remote SMTP client input. Specify "smtpd_forbid_unauth_pipelining
  = yes" to enable. This feature is enabled by default in Postfix 3.9 and
  later.

- Workaround to limit collateral damage from OS distributions that crank up
  security to 11, increasing the number of plaintext email deliveries. This
  introduces basic OpenSSL configuration file support, with two new parameters
  "tls_config_file" and "tls_config_name". Details are in the postconf(5)
  manpage under "tls_config_file" and "tls_config_name".

Full release notes:
http://cdn.postfix.johnriley.me/mirrors/postfix-release/official/postfix-3.8.1.RELEASE_NOTES

Revision 1.44: download - view: text, markup, annotated - select for diffs
Mon May 8 04:30:44 2023 UTC (3 years, 6 months ago) by triaxx
Branches: MAIN
CVS tags: pkgsrc-2023Q2-base, pkgsrc-2023Q2
Diff to: previous 1.43: preferred, colored
Changes since revision 1.43: +2 -2 lines
postfix: Update to 3.8.0

upstream changes:
-----------------
Postfix 3.7.8
  o Support to look up DNS SRV records in the Postfix SMTP/LMTP client, Based
    on code by Tomas Korbar (Red Hat). For example, with "use_srv_lookup =
    submission" and "relayhost = example.com:submission", the Postfix SMTP
    client will look up DNS SRV records for _submission._tcp.example.com, and
    will relay email through the hosts and ports that are specified with those
    records.
  o TLS obsolescence: Postfix now treats the "export" and "low" cipher grade
    settings as "medium". The "export" and "low" grades are no longer supported
    in OpenSSL 1.1.1, the minimum version required in Postfix 3.6.0 and later.
    Also, Postfix default settings now exclude deprecated or unused ciphers
    (SEED, IDEA, 3DES, RC2, RC4, RC5), digest (MD5), key exchange algorithms
    (DH, ECDH), and public key algorithm (DSS).
  o Attack resistance: the Postfix SMTP server can now aggregate
    smtpd_client_*_rate and smtpd_client_*_count statistics by network block
    instead of by IP address, to raise the bar against a memory exhaustion
    attack in the anvil(8) server; Postfix TLS support unconditionally disables
    TLS renegotiation in the middle of an SMTP connection, to avoid a CPU
    exhaustion attack.
  o The PostgreSQL client encoding is now configurable with the "encoding"
    Postfix configuration file attribute. The default is "UTF8". Previously the
    encoding was hard-coded as "LATIN1", which is not useful in the context of
    SMTP.
  o The postconf command now warns for #comment in or after a Postfix parameter
    value. Postfix programs do not support #comment after other text, and treat
    that as input.

Revision 1.43: download - view: text, markup, annotated - select for diffs
Sat Jan 28 09:28:30 2023 UTC (3 years, 9 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2023Q1-base, pkgsrc-2023Q1
Diff to: previous 1.42: preferred, colored
Changes since revision 1.42: +2 -2 lines
mail/postfix: update to 3.7.4

Postfix 3.7.4 (2023-01-22)

  * Workaround: with OpenSSL 3 and later always turn on
    SSL_OP_IGNORE_UNEXPECTED_EOF, to avoid warning messages and missed
    opportunities for TLS session reuse. This is safe because the SMTP
    protocol implements application-level framing, and is therefore not
    affected by TLS truncation attacks. Fix by Viktor Dukhovni.

  * Workaround: OpenSSL 3.x EVP_get_digestbyname() can return
    lazily-bound handles for digest implementations. In sufficiently
    hostile configurations, Postfix could mistakenly believe that a digest
    algorithm is available, and fail when it is not. A similar workaround
    may be needed for EVP_get_cipherbyname(). Fix by Viktor Dukhovni.

  * Bugfix (bug introduced in Postfix 2.11): the checkok() macro in
    tls/tls_fprint.c evaluated its argument unconditionally; it should
    evaluate the argument only if there was no prior error. Found during
    code review.

  * Bugfix (bug introduced in Postfix 2.8): postscreen died with a
    segmentation violation when postscreen_dnsbl_threshold < 1. It
    should reject such input with a fatal error instead. Discovered by
    Benny Pedersen.

  * Bitrot: fixes for linker warnings from newer Darwin (MacOS)
    versions. Viktor Dukhovni.

  * Portability: Linux 6 support.

  * Added missing documentation that cidr:, pcre: and regexp: tables
    support inline specification only in Postfix 3.7 and later.

Revision 1.42: download - view: text, markup, annotated - select for diffs
Sat Oct 15 20:34:57 2022 UTC (4 years, 1 month ago) by triaxx
Branches: MAIN
CVS tags: pkgsrc-2022Q4-base, pkgsrc-2022Q4
Diff to: previous 1.41: preferred, colored
Changes since revision 1.41: +2 -2 lines
postfix: Update to 3.7.3

upstream changes:
Postfix 3.7.3
  o This fixes a bug where some messages were not delivered after "warning:
    Unexpected record type 'X'.

Revision 1.41: download - view: text, markup, annotated - select for diffs
Thu Jul 21 15:08:39 2022 UTC (4 years, 3 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2022Q3-base, pkgsrc-2022Q3
Diff to: previous 1.40: preferred, colored
Changes since revision 1.40: +2 -2 lines
mail/postfix: update to 3.7.2

3.7.0 (2022-02-07)

  * Support to inline the content of small cidr:, pcre:, and regexp:
    tables in Postfix parameter values. An example is the new
    smtpd_forbidden_commands default value, "CONNECT GET POST
    regexp:{{/^[^A-Z]/ Thrash}}", to quickly drop connections from
    clients that send garbage.

  * To make the maillog_file feature more useful, including stdout
    logging from a container, the postlog(1) command is now set-gid
    postdrop, so that unprivileged programs can use it to write
    logging through the postlogd(8) daemon. This required hardening
    the postlog(1) command against privilege escalation attacks.

  * Support for library APIs: OpenSSL 3.0.0, PCRE2, Berkeley DB 18.

  * Postfix programs now randomize the initial state of in-memory
    hash tables, to defend against hash collision attacks involving
    a large number of attacker-chosen lookup keys. Presently, the
    only known opportunity for such attacks involves remote SMTP
    client IPv6 addresses in the anvil(8) service, and requires
    making hundreds of short-lived connections per second while
    cycling through thousands of different client IP addresses.

  * Updated defense against remote clients or servers that 'trickle'
    SMTP or LMTP traffic. This replaces the old per-record deadlines
    with per-request deadlines and minimum data rates.

  * Many typofixes by raf and Wietse.


3.7.1 (2022-04-18)

  * (problem introduced: Postfix 2.7) The milter_header_checks maps
    are now opened before the cleanup(8) server enters the chroot
    jail. Problem reported by Jesper Dybdal.

  * In an internal client module, "host or service not found" was
    a fatal error, causing the milter_default_action setting to be
    ignored. It is now a non-fatal error, just like a failure to
    connect. Problem reported by Christian Degenkolb.

  * The proxy_read_maps default value was missing up to 27 parameter
    names. The corresponding lookup tables were not automatically
    authorized for use with the proxymap(8) service. The parameter
    names were ending in _checks, _reply_footer, _reply_filter,
    _command_filter, and _delivery_status_filter.

  * (problem introduced: Postfix 3.0) With dynamic map loading
    enabled, an attempt to create a map with "postmap regexp:path"
    would result in a bogus error message "Is the postfix-regexp
    package installed?" instead of "unsupported map type for this
    operation". This happened with all non-dynamic map types (static,
    cidr, etc.) that have no 'bulk create' support. Problem reported
    by Greg Klanderman.

  * In PCRE_README, "pcre2 --libs" should be "pcre2 --libs8". Problem
    reported by Carlos Velasco.

  * Documented in the postlogd(8) daemon manpage that the Postfix
    >= 3.7 postlog(1) command can run with setgid permissions.

3.7.2 (2022-04-28)

This reverts an overly complex change in the postscreen SMTP engine
(made during Postfix 3.7 development), and replaces it with much
simpler code. The bad change was crashing postscreen on some systems
after receiving malformed input (for example, a TLS "hello" message).

Revision 1.40: download - view: text, markup, annotated - select for diffs
Wed Jan 26 17:41:31 2022 UTC (4 years, 9 months ago) by triaxx
Branches: MAIN
CVS tags: pkgsrc-2022Q2-base, pkgsrc-2022Q2, pkgsrc-2022Q1-base, pkgsrc-2022Q1
Diff to: previous 1.39: preferred, colored
Changes since revision 1.39: +2 -2 lines
postfix: Update to 3.6.4

upstream changes:
-----------------
 Fixed in Postfix 3.6.4, 3.5.14, 3.4.24, 3.3.21:
  o Bug introduced in bugfix 20210708: duplicate bounce_notice_recipient
    entries in postconf output. This was caused by an incomplete fix to send
    SMTP session transcripts to $bounce_notice_recipient. Reported by Vincent
    Lefevre.
  o Bug introduced in Postfix 3.0: the proxymap daemon did not automatically
    authorize proxied maps inside pipemap (example:
    pipemap:{proxy:maptype:mapname, ...}) or inside unionmap. Problem reported
    by Mirko Vogt.
  o Bug introduced in Postfix 2.5: off-by-one error while writing a string
    terminator. This code passed all memory corruption tests, presumably
    because it wrote over an alignment padding byte, or over an adjacent
    character byte that was never read. Reported by Robert Siemer.

Fixed in Postfix 3.6.4, 3.5.14, 3.4.24:
  o The proxymap daemon did not automatically authorize map features added
    after Postfix 3.3, caused by missing *_maps parameter names in the
    proxy_read_maps default value. Found during code maintenance.

Revision 1.39: download - view: text, markup, annotated - select for diffs
Sat Dec 18 10:50:33 2021 UTC (4 years, 10 months ago) by adam
Branches: MAIN
CVS tags: pkgsrc-2021Q4-base, pkgsrc-2021Q4
Diff to: previous 1.38: preferred, colored
Changes since revision 1.38: +2 -1 lines
postfix: add -headerpad_max_install_names for Darwin builds

Revision 1.38: download - view: text, markup, annotated - select for diffs
Mon Nov 8 13:58:09 2021 UTC (5 years ago) by taca
Branches: MAIN
Diff to: previous 1.37: preferred, colored
Changes since revision 1.37: +2 -2 lines
mail/postfix: update to 3.6.3

Quote from release announce:

Fixed in Postfix 3.6.3, 3.5.13, 3.4.23, 3.3.20:

  * (problem introduced in Postfix 2.4, released in 2007): queue
    file corruption after a Milter (for example, MIMEDefang) made
    a request to replace the message body with a copy of that message
    body plus additional text (for example, a SpamAssassin report).

    The most likely impacts were a) the queue manager reporting a
    fatal error resulting in email delivery delays, or b) the queue
    manager reporting the corruption and moving the message to the
    corrupt queue for damaged messages.

    However, a determined adversary could craft an email message
    that would trigger the bug, and insert into its queue file a
    content filter destination or a redirect email address. Postfix
    would then deliver the message headers there, in most cases
    without delivering the message body. With enough experimentation,
    an attacker could make Postfix deliver both the message headers
    and body.

    Some details of a successful attack depend on the Milter
    implementation, and on the Postfix and Milter configuration
    details; these can be determined remotely through experimentation.
    Failed experiments may be detected when the queue manager
    terminates with a fatal error, or when the queue manager moves
    damaged files to the "corrupt" queue as evidence.

    Technical details: when Postfix executes a "replace body" Milter
    request it will reuse queue file storage that was used by the
    existing email message body. If the new body is larger, Postfix
    will append body content to the end of the queue file. The
    corruption happened when a Milter (for example, MIMEDefang)
    made a request to replace the body of a message with a new body
    that contained a copy of the original body plus some new text,
    and the original body contained a line longer than $line_length_limit
    bytes (for example, an image encoded in base64 without hard or
    soft line breaks). In queue files, Postfix stores a long text
    line as multiple records with up to $line_length_limit bytes
    each. Unfortunately, Postfix's "replace body" support did not
    account for the additional queue file space needed to store the
    second etc. record headers. And thus, the last record(s) of a
    long text line could overwrite one or more queue file records
    immediately after the space that was previously occupied by the
    original message body.

    Problem report by Benoit Panizzon.

  * (problem introduced in Postfix 2.10, released in 2012): The
    postconf "-x" option could produce incorrect output, because
    multiple functions were implicitly sharing a buffer for
    intermediate results. Problem report by raf, root cause analysis
    by Viktor Dukhovni.

  * (problem introduced in Postfix 2.11, released in 2013): The
    check_ccert_access feature worked as expected, but produced a
    spurious warning when Postfix was built without SASL support.
    Fix by Brad Barden.

  * Fix for a compiler warning due to a missing 'const' qualifier
    when compiling Postfix with OpenSSL 3. Depending on compiler
    settings this could cause the build to fail.

Fixed in Postfix 3.6:

  * The known_tcp_ports settings had no effect. It also wasn't fully
    implemented. Problem report by Peter.

  * Fix for missing space between a hostname and warning text.

Revision 1.37: download - view: text, markup, annotated - select for diffs
Mon Jul 26 15:38:10 2021 UTC (5 years, 3 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2021Q3-base, pkgsrc-2021Q3
Diff to: previous 1.36: preferred, colored
Changes since revision 1.36: +2 -2 lines
mail/postfix: update to 3.6.2

* pkgsrc change: Add supportfor blocklistd(3) (and blacklistd(3)).

* From release annuonce:

Fixed in Postfix 3.6.2, 3.5.12, 3.4.22, 3.3.19:

  * In Postfix 3.6, fixed a false "Result too large" (ERANGE) fatal
    error in the compatibility_level parser, because there was no
    'errno = 0' statement before an strtol() call. In Postfix
    3.3-3.5, fixed two older latent bugs of this kind (introduced
    in 1999 and in Postfix 2.11). Problem reported by David Bohman.

  * (problem introduced in Postfix 3.3) "Null pointer read" error
    in the cleanup daemon when "header_from_format = standard" (the
    default as of Postfix 3.3), and email was submitted with
    /usr/sbin/sendmail without From: header, and an all-space full
    name was specified in 1) the password file, 2) with "sendmail
    -F", or 3) with the NAME environment variable. Found by Renaud
    Metrich.

  * (problem introduced in Postfix 2.4) False "too many reverse
    jump" warnings in the showq daemon, because loop detection code
    was comparing memory addresses instead of queue file names.
    Reported by Mehmet Avcioglu.

  * (problem introduced in 1999) The Postfix SMTP server was sending
    all session transcripts to the error_notice_recipient (default:
    postmaster), instead of sending transcripts of bounced mail to
    the bounce_notice_recipient (default: postmaster). Reported by
    Hans van Zijst.

Fixed in Postfix 3.6.2, 3.5.12, 3.4.22:

  * The texthash: map implementation broke tls_server_sni_maps,
    because it did not support multi-file inputs. Reported by
    Christopher Gurnee, who also found an instance of the missing
    code in the "postmap -F" source code. File: util/dict_thash.c.

Revision 1.36: download - view: text, markup, annotated - select for diffs
Mon Jun 14 14:29:47 2021 UTC (5 years, 5 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2021Q2-base, pkgsrc-2021Q2
Diff to: previous 1.35: preferred, colored
Changes since revision 1.35: +2 -2 lines
mail/postfix: update to 3.6.1

3.6.1 (2021-06-14)

Fixed in Postfix 3.6.1, 3.5.11, 3.4.21, 3.3.18:

  * Bugfix (introduced: Postfix 2.11): the command "postmap
    lmdb:/file/name" (create LMDB database from textfile) handled
    duplicate input keys ungracefully, discarding entries stored
    up to and including the duplicate key, and causing a double
    free() call with lmdb versions 0.9.17 and later. Reported by
    Adi Prasaja; double free() root cause analysis by Howard Chu.

Fixed in Postfix 3.6.1, 3.5.11, 3.4.21:

  * Typo (introduced: Postfix 3.4): silent_discard should be
    silent-discard in BDAT_README.

Revision 1.35: download - view: text, markup, annotated - select for diffs
Wed Jun 2 15:29:56 2021 UTC (5 years, 5 months ago) by taca
Branches: MAIN
Diff to: previous 1.34: preferred, colored
Changes since revision 1.34: +2 -2 lines
mail/postfix: update to 3.6.0

Postfix stable release 3.6.0 is available. This ends the support
for legacy release Postfix 3.2.

The main changes are below. See the RELEASE_NOTES file for further
details.

Incompatible changes:

  * This release requires "postfix stop" before updating, or before
    backing out to an earlier release, because some internal protocols
    have changed. Otherwise, long-running daemons (pickup, qmgr,
    verify, tlsproxy, postscreen) may fail to communicate with the
    rest of Postfix, causing mail delivery delays until Postfix is
    restarted.

  * Respectful logging. Postfix version 3.6 deprecates terminology
    that implies white is better than black. Instead, Postfix prefers
    'allowlist', 'denylist', and variations on those words. This
    change affects Postfix documentation, and postscreen parameters
    and logging.

    To keep the old postscreen logging set "respectful_logging =
    no" in main.cf before setting "compatibility_level = 3.6".  In
    any case, the old postscreen parameter names will keep working
    as before.

Other changes:

  * The minimum supported OpenSSL version is 1.1.1, which will reach
    the end of life by 2023-09-11. Postfix 3.6 is expected to reach
    the end of support in 2025. Until then, Postfix will be updated
    as needed for compatibility with OpenSSL.

    The default fingerprint digest has changed from md5 to sha256
    (Postfix 3.6 with compatibility_level >= 3.6). With a lower
    compatibility_level setting, Postfix defaults to using md5, and
    logs a warning when a Postfix configuration specifies no explicit
    digest type.

    The export-grade Diffie-Hellman key exchange is no longer
    supported, and the tlsproxy_tls_dh512_param_file parameter is
    ignored,

  * Better error messages when someone configures an incorrect
    program in master.cf. To recognize such mistakes, every Postfix
    internal service, including the postdrop command, announces the
    name of its protocol before doing any other I/O, and every
    Postfix client program, including the Postfix sendmail command,
    will verify that the protocol name matches what it expects.

  * Fine-grained control over the envelope sender address for
    submission with the Postfix sendmail (or postdrop) commands.

    Example:

    /etc/postfix/main.cf:
        # Allow root and postfix full control, anyone else can only
        # send mail as themselves. Use "uid:" followed by the numerical
        # UID when the UID has no entry in the UNIX password file.
        local_login_sender_maps =
            inline:{ { root = *}, { postfix = * } },
            pcre:/etc/postfix/login_senders

    /etc/postfix/login_senders:
       # Allow both the bare username and the user@domain forms.
        /(.+)/ $1 $1@example.com

  * Threaded bounces. This allows mail readers to present a
    non-delivery, delayed delivery, or successful delivery notification
    in the same email thread as the original message.

    Unfortunately, this also makes it easy for users to mistakenly
    delete the whole email thread (all related messages), instead
    of deleting only the delivery status notification.

    To enable, specify "enable_threaded_bounces = yes".

  * Postfix by default no longer uses the services(5) database to
    look up the TCP ports for SMTP and LMTP services. Instead, this
    information is configured with the new known_tcp_ports configuration
    parameter (default: lmtp=24, smtp=25, smtps=submissions=465,
    submission=587). When a service is not specified in known_tcp_ports,
    Postfix will still query the services(5) database.

  * Starting with Postfix version 3.6, the compatibility level is
    "3.6". In future Postfix releases, the compatibility level will
    be the Postfix version that introduced the last incompatible
    change. The level is formatted as 'major.minor.patch', where
    'patch' is usually omitted and defaults to zero. Earlier
    compatibility levels are 0, 1 and 2.

    This also introduces main.cf and master.cf support for the
    <=level, < level, and other operators to compare compatibility
    levels. With the standard <=, <, etc. operators, compatibility
    level 3.10 would be less than 3.9, which is undesirable.

Revision 1.34: download - view: text, markup, annotated - select for diffs
Sun May 2 12:11:51 2021 UTC (5 years, 6 months ago) by wiz
Branches: MAIN
Diff to: previous 1.33: preferred, colored
Changes since revision 1.33: +1 -2 lines
postfix: remove non-existent download site

Revision 1.33: download - view: text, markup, annotated - select for diffs
Mon Apr 26 15:26:08 2021 UTC (5 years, 6 months ago) by triaxx
Branches: MAIN
Diff to: previous 1.32: preferred, colored
Changes since revision 1.32: +2 -2 lines
postfix: Update to 3.5.10

upstream changes:
-----------------
Fixed in 3.5.10:
  o Missing null pointer checks (introduced in Postfix 3.4) after an internal I/O error during the smtp(8) to tlsproxy(8) handshake. Found by Coverity, reported by Jaroslav Skarvada. Based on a fix by Viktor Dukhovni.
  o Null pointer bug (introduced in Postfix 3.0) and memory leak (introduced in Postfix 3.4) after an inline: table syntax error in main.cf or master.cf. Found by Coverity, reported by Jaroslav Skarvada. Based on a fix by Viktor Dukhovni.
  o Incomplete null pointer check (introduced: Postfix 2.10) after truncated HaProxy version 1 handshake message. Found by Coverity, reported by Jaroslav Skarvada. Fix by Viktor Dukhovni.
  o Missing null pointer check (introduced: Postfix alpha) after null argv[0] value.

Revision 1.32: download - view: text, markup, annotated - select for diffs
Thu Jan 21 16:37:59 2021 UTC (5 years, 9 months ago) by triaxx
Branches: MAIN
CVS tags: pkgsrc-2021Q1-base, pkgsrc-2021Q1
Diff to: previous 1.31: preferred, colored
Changes since revision 1.31: +2 -2 lines
postfix: Update to 3.5.9

upstream changes:
-----------------
This update improves the reporting of DNSSEC problems that may affect DANE
security. DNSSEC support may unavailable because of local configuration, libc
incompatibility, or other infrastructure issues. This was backported from
Postfix 3.6.

Background: DNSSEC validation is needed for Postfix DANE support; this ensures
that Postfix receives TLSA records with secure TLS server certificate info.
When DNSSEC validation is unavailable, mail deliveries using opportunistic DANE
(security level 'dane') will not be protected by server certificate info in
TLSA records, and mail deliveries using mandatory DANE (security level
'dane-only') will not be made at all.

This update introduces the following behavior: when a process requests DNSSEC
support (typically, for Postfix DANE support), the process may now do a runtime
test to determine if DNSSEC validation is available.

The new dnssec_probe parameter specifies a DNS query type (default: "ns") and
DNS query name (default: ".") that Postfix may use to determine whether DNSSEC
validation is available. Specify an empty value to disable this feature.

When dnssec_probe is enabled, a Postfix process will send a DNSSEC probe after
1) the process made a DNS query that requested DNSSEC validation, 2) the
process did not receive a DNSSEC validated response to this query or to an
earlier query, and 3) the process did not already send a DNSSEC probe.

When the DNSSEC probe has no response, or when the response is not DNSSEC
validated, Postfix logs a warning that DNSSEC validation may be unavailable.
Examples:

warning: DNSSEC validation may be unavailable
warning: reason: dnssec_probe 'ns:.' received a response that is not DNSSEC validated
warning: reason: dnssec_probe 'ns:.' received no response: Server failure

With this update, the Postfix build system will no longer automatically disable
DNSSEC support when it determines that Postfix will use libc-musl. This removes
the earlier libc-musl workaround introduced with Postfix 3.2.15, 3.3.10,
3.4.12, and 3.5.2.

Revision 1.31: download - view: text, markup, annotated - select for diffs
Sun Nov 22 11:14:44 2020 UTC (5 years, 11 months ago) by adam
Branches: MAIN
CVS tags: pkgsrc-2020Q4-base, pkgsrc-2020Q4
Diff to: previous 1.30: preferred, colored
Changes since revision 1.30: +2 -2 lines
postfix: updated to 3.5.8

Fixed in Postfix version 3.5.8:

[Postfix 3.5 and later] The Postfix SMTP client inserted <CR><LF> into message headers with lines longer than $line_length_limit (default: 2048), causing all subsequent header content to become message body content. Reported by Andreas Weigel.

Fixed in Postfix versions 3.5.8, 3.4.18, 3.3.15, 3.2.20:

[Postfix 2.8 and later] The postscreen daemon did not save a copy of the postscreen_dnsbl_reply_map lookup result. This has no effect when the recommended texthash: lookup table is used, but it could result in stale data with other lookup tables.

[Postfix 2.3 and later] After deleting a recipient with a Milter, the Postfix recipient duplicate filter was not updated; the filter suppressed requests to add the recipient back. Reported by Mehmet Avcioglu.

[Postfix 2.3 and later] Memory leak: the static: maps did not free their casefolding buffer.

[Postfix 2.2 and later] With "smtpd_tls_wrappermode = yes", the smtps service was waiting for a TLS handshake, after processing an XCLIENT command. Reported by Aki Tuomi.

[Postfix 2.0 and later] The smtp_sasl_mechanism_filter implementation ignored table lookup errors, treating them as 'not found'.

[Postfix alpha and later] The code that looks for Delivered-To: headers ignored headers longer than $line_length_limit (default: 2048).

Revision 1.30: download - view: text, markup, annotated - select for diffs
Mon Aug 31 13:07:46 2020 UTC (6 years, 2 months ago) by otis
Branches: MAIN
CVS tags: pkgsrc-2020Q3-base, pkgsrc-2020Q3
Diff to: previous 1.29: preferred, colored
Changes since revision 1.29: +2 -2 lines
mail/postfix: Update to 3.5.7

Changelog:
With "smtp_tls_connection_reuse = yes", tlsproxy(8) was using the wrong global
TLS context for connections that use DANE trust anchors or that use non-DANE
trust anchors. This resulted in a global certificate verify function pointer
race, between TLS handshakes that use trust achors and concurrent TLS
handshakes that use PKI. No memory was corrupted in the course of all this.

Reference: http://www.postfix.org/announcements/postfix-3.5.7.html

Revision 1.29: download - view: text, markup, annotated - select for diffs
Thu Aug 27 13:57:14 2020 UTC (6 years, 2 months ago) by triaxx
Branches: MAIN
Diff to: previous 1.28: preferred, colored
Changes since revision 1.28: +2 -2 lines
postfix: Update to 3.5.6

upstream changes:
-----------------
Fixed in Postfix versions 3.5.6, 3.4.16, 3.3.14, 3.2.19:

  * One fix for memory leaks in the Postfix TLS library was back-ported to the wrong place, resulting in undefined program behavior.

Fixed in Postfix versions 3.5.6, 3.4.16:

  * The workaround for allowed TLS protocol versions did not explictly override the system-wide OpenSSL configuration, for sessions where the remote SMTP client sends SNI. It's better to be safe than sorry.

 Fixed in Postfix versions 3.5.5, 3.4.15, 3.3.13, 3.2.18:

  * Workaround for unexpected TLS interoperability problems when Postfix runs on OS distributions with system-wide OpenSSL configurations.

  * Memory leaks in the Postfix TLS library, the largest one involving multiple kBytes per peer certificate.

Revision 1.28: download - view: text, markup, annotated - select for diffs
Tue Jun 30 15:00:45 2020 UTC (6 years, 4 months ago) by taca
Branches: MAIN
Diff to: previous 1.27: preferred, colored
Changes since revision 1.27: +2 -2 lines
mail/postfix: update to 3.5.4

Update postfix to 3.5.4.


Fixed in Postfix 3.5.4, 3.4.14:

  * The connection_reuse attribute in smtp_tls_policy_maps always
    resulted in an "invalid attribute name" error. Fix by Thorsten
    Habich.

  * SMTP over TLS connection reuse always failed for Postfix SMTP
    client configurations that specify explicit trust anchors (remote
    SMTP server certificates or public keys). Reported by Thorsten
    Habich.

Fixed in Postfix versions 3.5.4, 3.4.14, 3.3.12, 3.2.17:

  * The Postfix SMTP client's DANE implementation would always send
    an SNI option with the name in a destination's MX record, even
    if the MX record pointed to a CNAME record. MX records that
    point to CNAME records are not conformant with RFC5321, and so
    are rare.

    Based on the DANE survey of ~2 million hosts it was found that
    with the corrected SMTP client behavior, sending SNI with the
    CNAME-expanded name, the SMTP server would not send a different
    certificate. This fix should therefore be safe.

Revision 1.27: download - view: text, markup, annotated - select for diffs
Mon Jun 15 15:43:32 2020 UTC (6 years, 5 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2020Q2-base, pkgsrc-2020Q2
Diff to: previous 1.26: preferred, colored
Changes since revision 1.26: +2 -2 lines
mail/postfix: update to 3.5.3

Update postfix and related pacakges to 3.5.3.


Quote freom release announce.

Postfix 3.5.3, 3.4.13:

  * TLS handshake failure in the Postfix SMTP server during SNI
    processing, after the server-side TLS engine sent a TLSv1.3
    HelloRetryRequest (HRR) to a remote SMTP client. Reported by
    J??n M??t??, fixed by Viktor Dukhovni.

Postfix versions 3.5.3, 3.4.13, 3.3.11, 3.2.16:

  * The command "postfix tls deploy-server-cert" did not handle a
    missing optional argument. This bug was introduced in Postfix
    3.1.

Revision 1.26: download - view: text, markup, annotated - select for diffs
Mon May 18 14:21:53 2020 UTC (6 years, 6 months ago) by triaxx
Branches: MAIN
Diff to: previous 1.25: preferred, colored
Changes since revision 1.25: +2 -2 lines
postfix: update to 3.5.2

upstream changes:
-----------------
 Postfix versions 3.5.2, 3.4.12, 3.2.10, 3.2.15:
  * A TLS error for a database client caused a false 'lost connection' error for an SMTP over TLS session in the same Postfix process. Reported by Alexander Vasarab, diagnosed by Viktor Dukhovni. This bug was introduced with Postfix 2.2.
  * The same bug existed in the tlsproxy(8) daemon, where a TLS error for one TLS session could cause a false 'lost connection' error for a concurrent TLS session in the same process. This bug was introduced with Postfix 2.8.
  * The Postfix build now disables DANE support on Linux systems with libc-musl, because libc-musl provides no indication whether DNS responses are authentic. This broke DANE support without a clear explanation.
  * Due to implementation changes in the ICU library, some Postfix daemons reported file access errrors (U_FILE_ACCESS_ERROR) after chroot(). This was fixed by initializing the ICU library before making the chroot() call.
  * Minor code changes to silence a compiler that special-cases string literals.

Postfix 3.5.2, 3.4.12:
  * Segfault in the tlsproxy(8) client role when the server role was disabled. This typically happened on systems that do not receive mail, after configuring connection reuse for outbound SMTP over TLS.
  * The date portion of the maillog_file_rotate_suffix default value used the minute (%M) instead of the month (%m). Reported by Larry Stone.

Revision 1.25: download - view: text, markup, annotated - select for diffs
Sun Apr 26 09:33:25 2020 UTC (6 years, 6 months ago) by taca
Branches: MAIN
Diff to: previous 1.24: preferred, colored
Changes since revision 1.24: +2 -2 lines
mail/postfix: update to 3.5.1

Update postfix to 3.5.1.


3.5.0 (2020-03-16)

Postfix stable release 3.5.0 is available. Support has ended for
legacy release Postfix 3.1.

The main changes are below. See the RELEASE_NOTES file for further details.

  * Support for the haproxy v2 protocol. The Postfix implementation
    supports TCP over IPv4 and IPv6, as well as non-proxied
    connections; the latter are typically used for heartbeat tests.

  * Support to force-expire email messages. This introduces new
    postsuper(1) command-line options to request expiration, and
    additional information in mailq(1) or postqueue(1) output.

  * The Postfix SMTP and LMTP client support a list of nexthop
    destinations separated by comma or whitespace. These destinations
    will be tried in the specified order. Examples:

    /etc/postfix/main.cf:
        relayhost = foo.example, bar.example
        default_transport = smtp:foo.example, bar.example

Incompatible changes:

  * Logging: Postfix daemon processes now log the from= and to=
    addresses in external (quoted) form in non-debug logging (info,
    warning, etc.). This means that when an address localpart
    contains spaces or other special characters, the localpart will
    be quoted, for example:

	from=<"name with spaces"@example.com>

    Specify "info_log_address_format = internal" for backwards compatibility.

  * Postfix now normalizes IP addresses received with XCLIENT,
    XFORWARD, or with the HaProxy protocol, for consistency with
    direct connections to Postfix. This may change the appearance
    of logging, and the way that check_client_access will match
    subnets of an IPv6 address.


3.5.1 (2020-04-20)

Postfix versions 3.5.1, 3.4.11, 3.3.9, 3.2.14:

  * Bitrot workaround for broken builds after an incompatible change
    in GCC 10.

  * Bitrot workaround for broken DANE/DNSSEC support after an
    incompatible change in GLIBC 2.31. This change avoids the need
    for new options in /etc/resolv.conf.

Revision 1.24: download - view: text, markup, annotated - select for diffs
Tue Feb 11 20:40:27 2020 UTC (6 years, 9 months ago) by triaxx
Branches: MAIN
CVS tags: pkgsrc-2020Q1-base, pkgsrc-2020Q1
Diff to: previous 1.23: preferred, colored
Changes since revision 1.23: +2 -2 lines
postfix: update to 3.4.9

upstream changes:
-----------------
 Fixed in all supported stable releases:

    Bug (introduced: Postfix 3.1): smtp_dns_resolver_options were broken while adding support for negative DNS response caching in postscreen. Postfix was inadvertently changed to call res_query() instead of res_search(). Reported by Jaroslav Skarvada.

    Bug (introduced: Postfix 2.5): Postfix ignored the CONNECT macro overrides from a Milter application. Postfix now evaluates the Milter macros for an SMTP CONNECT event after the Postfix-to-Milter connection is negotiated. Problem reported by David Bürgin.

    Bug (introduced: Postfix 3.0): sanitize (remote) server responses before storing them in the verify database, to avoid Postfix warnings about malformed UTF8. Found during code maintenance.

Revision 1.23: download - view: text, markup, annotated - select for diffs
Tue Jan 28 08:16:51 2020 UTC (6 years, 9 months ago) by triaxx
Branches: MAIN
Diff to: previous 1.22: preferred, colored
Changes since revision 1.22: +3 -1 lines
mail/postfix: fix insufficient permissions for var/spool/postfix/...

pkgsrc changes:
---------------
  * Remove the subdirectories of var/spool/postfix to avoid insufficient
    permissions when upgrading (Thanks Matthias!).

Revision 1.22: download - view: text, markup, annotated - select for diffs
Mon Dec 9 08:45:14 2019 UTC (6 years, 11 months ago) by triaxx
Branches: MAIN
CVS tags: pkgsrc-2019Q4-base, pkgsrc-2019Q4
Diff to: previous 1.21: preferred, colored
Changes since revision 1.21: +2 -2 lines
postfix: update to 3.4.8

upstream changes:
-----------------
    Fix for an Exim interoperability problem when postscreen after-220 checks
    are enabled. Bug introduced in Postfix 3.4: the code that detected
    "PIPELINING after BDAT" looked at the wrong variable. The warning now says
    "BDAT without valid RCPT", and the error is no longer treated as a command
    PIPELINING error, thus allowing mail to be delivered. Meanwhile, Exim has
    been fixed to stop sending BDAT commands when postscreen rejects all RCPT
    commands.

    Usability bug, introduced in Postfix 3.4: the parser for key/certificate
    chain files rejected inputs that contain an EC PARAMETERS object. While
    this is technically correct (the documentation says what types are allowed)
    this is surprising behavior because the legacy cert/key parameters will
    accept such inputs. For now, the parser skips object types that it does not
    know about for usability, and logs a warning because ignoring inputs is not
    kosher.

    Bug introduced in Postfix 2.8: don't gratuitously enable all after-220
    tests when only one such test is enabled. This made selective tests
    impossible with 'good' clients. This will be fixed in older Postfix
    versions at some later time.

Revision 1.21: download - view: text, markup, annotated - select for diffs
Sat Nov 2 16:25:26 2019 UTC (7 years ago) by rillig
Branches: MAIN
Diff to: previous 1.20: preferred, colored
Changes since revision 1.20: +2 -2 lines
mail: align variable assignments

pkglint -Wall -F --only aligned -r

No manual corrections.

Revision 1.20: download - view: text, markup, annotated - select for diffs
Mon Sep 23 20:00:07 2019 UTC (7 years, 1 month ago) by triaxx
Branches: MAIN
CVS tags: pkgsrc-2019Q3-base, pkgsrc-2019Q3
Diff to: previous 1.19: preferred, colored
Changes since revision 1.19: +2 -2 lines
postfix: Update to 3.4.7

upstream changes:
-----------------
* Robustness: the tlsproxy(8) daemon could go into a loop, logging a flood of
  error messages. Problem reported by Andreas Schulze after enabling SMTP/TLS
  connection reuse.
* Workaround: OpenSSL changed an SSL_Shutdown() non-error result value into an
  error result value, causing logfile noise.
* Configuration: the new 'TLS fast shutdown' parameter name was implemented
  incorrectly. The documentation said "tls_fast_shutdown_enable", but the code
  said "tls_fast_shutdown". This was fixed by changing the code, because no-one
  is expected to override the default.
* Performance: workaround for poor TCP loopback performance on LINUX, where
  getsockopt(..., TCP_MAXSEG, ...) reports a bogus TCP maximal segment size that
  is 1/2 to 1/3 of the real MSS. To avoid client-side Nagle delays or
  server-side delayed ACKs caused by multiple smaller-than-MSS writes, Postfix
  chooses a VSTREAM buffer size that is a small multiple of the reported bogus
  MSS. This workaround increases the multiplier from 2x to 4x.
* Robustness: the Postfix Dovecot client could segfault (null pointer read) or
  cause an SMTP server assertion to fail when talking to a fake Dovecot server.
  The Postfix Dovecot client now logs a proper error instead. Problem reported
  by Tim Düsterhus.

Revision 1.19: download - view: text, markup, annotated - select for diffs
Wed Jul 17 13:33:00 2019 UTC (7 years, 4 months ago) by triaxx
Branches: MAIN
Diff to: previous 1.18: preferred, colored
Changes since revision 1.18: +2 -2 lines
postfix: update to 3.4.6

pkgsrc changes:
---------------
  * change COMMENT to make pkglint happy (inspired by http://www.postfix.org/)
  * update PLIST using make print-PLIST (missing @pkgdir)

upstream changes:
-----------------
20181125

	Cleanup: dict_file_to_xxx() takes a list of file names
	separated by CHARS_COMMA_SP. Shoe-horned into the existing
	API, make it nicer when there is time. File: util/dict_file.c.

20181127

	Cleanup: encapsulated clumsy 'read into VSTRING' code with
	easier-to-use vstream_fread_buf() and vstream_fread_app()
	primitives. Files: global/memcache_proto.c, global/record.c,
	global/smtp_stream.c, global/smtp_stream.h, global/uxtext.c,
	global/xtext.c, milter/milter8.c, util/dict_file.c,
	util/hex_quote.c, util/netstring.c, util/vstream.c,
	util/vstream.h. Verified with "make tests".

	Cleanup: simplified the smtp_fread() API (introduced for
	BDAT support), and changed the name to smtp_fread_buf().
	Files: global/smtp_stream.c, smtpd/smtpd.c. Verified with
	~megabyte BDAT commands.

	Cleanup: simplified a tlsproxy-internal API. File:
	tlsproxy/tlsproxy.c.

20181128

	Initial support for key/certificate chain files that will
	replace the proliferation of separate parameters for
	RSA/DSA/ECC/etc. key and certificate files. Viktor
	Dukhovni.

20181201

	Cleanup: replaced the remaining unsafe VSTRING_AT_OFFSET()
	calls with safe vstring_set_payload_size() calls, in code
	that directly writes into VSTRING. Files: tls/tls_session.c,
	tlsmgr/tlsmgr.c, util/casefold.c, util/vstring.c, util/vstring.h,
	xsasl/xsasl_cyrus_client.c.

	Cleanup: postscreen_command_time_limit did not need to be
	a 'raw' parameter. This makes "postconf -x" behavior more
	consistent. Files: global/mail_params.h, postscreen/postscreen.c.

	Documentation: added text that the following parameter
	values are not subject to Postfix parameter $name expansion:
	default_rbl_reply, command_execution_directory, luser_relay,
	smtpd_reject_footer. These have their own documented $name
	substitution mechanism. File: proto/postconf.proto.

20181202

	Bugfix: posttls-finger reported an error for UNIX-domain
	connections, even if they did not fail. Found by Coverity.
	File: posttls-finger/posttls-finger.c.

20181208

	Documentation: add even more redundancy to the rate-delay
	description. File: proto/postconf.proto.

20181210

	Cleanup: code deduplication. File: util/dict_file.c.

20181226

	Cleanup: code deduplication and better encapsulation with
	PSC_DEL_CLIENT_STATE() and PSC_DEL_SERVER_STATE() macros.
	Files: postscreen/postscreen.h, postscreen/postscreen_state.c.

	Documentation: POSTSCREEN_README did not describe the
	postscreen_post_queue_limit, and attributed the wrong reject
	message to the postscreen_pre_queue_limit. Problem reported
	by Michael Orlitzky. File: proto/POSTSCREEN_README.html.

	(20181226-nonprod) Compatibility: removed support for OpenSSL
	1.0.1 (not supported since December 31, 2016) and earlier
	releases. This eliminated a large number of #ifdefs with
	bitrot workarounds.  Viktor Dukhovni. Files: global/mail_params.h,
	posttls-finger/posttls-finger.c, tls/tls.h, tls/tls_certkey.c,
	tls/tls_client.c, tls/tls_dane.c, tls/tls_dh.c, tls/tls_misc.c,
	tls/tls_proxy_client_scan.c, tls/tls_rsa.c, tls/tls_server.c,
	tls/tls_session.c.

	(20181226-nonprod) Use the OpenSSL 1.0.2 and later API for
	setting ECDHE curves. Viktor Dukhovni. Files: tls/tls.h,
	tls/tls_client.c, tls/tls_dh.c.

	(20181226-nonprod) Documentation update for TLS support.
	Viktor Dukhovni. Files: mantools/postlink, proto/TLS_README.html,
	proto/postconf.proto, src/sendmail/sendmail.c, src/smtpd/smtpd.c.

20181229

	Explicit maps_file_find() and dict_file_lookup() methods
	that decode base64 content. Decoding content is not built
	into the dict->lookup() method, because that would complicate
	the implementation of map nesting (inline, thash), map
	composition (pipemap, unionmap), and map proxying.  For
	consistency, decoding base64 file content is also not built
	into the maps_find() method. Files: util/dict.h.
	util/dict_file.c, global/maps.[hc], postmap/postmap.c.

20190106

        Documentation: documented the SRC_RHS_IS_FILE flag in
        dict_open.c, and updated the -F description in the postmap
        manpage. Files: util/dict_open.c, postmap/postmap.c.

	(20190106-nonprod) Feature: support for files that combine
	multiple (key, certificate, trust chain) instances in one
	file, to avoid separate files for RSA, DSA, Elliptic Curve,
	and so on. Viktor Dukhovni. Files: .indent.pro,
	global/mail_params.h, posttls-finger/posttls-finger.c,
	smtp/lmtp_params.c, smtp/smtp.c, smtp/smtp_params.c,
	smtp/smtp_proto.c, smtpd/smtpd.c, tls/tls.h, tls/tls_certkey.c,
	tls/tls_client.c, tls/tls_proxy.h, tls/tls_proxy_client_print.c,
	tls/tls_proxy_client_scan.c, tls/tls_proxy_server_print.c,
	tls/tls_proxy_server_scan.c, tls/tls_server.c, tlsproxy/tlsproxy.c.

	(20190106-nonprod) Create a second, no-key no-cert, SSL_CTX
	for use with SNI. Viktor Dukhovni. Files: src/tls/tls.h,
	src/tls/tls_client.c, src/tls/tls_misc.c, src/tls/tls_server.c.

	(20190106-nonprod) Server-side SNI support. Viktor Dukhovni.
	Files: src/global/mail_params.h, src/smtp/smtp.c,
	src/smtpd/smtpd.c, src/tls/tls.h, src/tls/tls_certkey.c,
	src/tls/tls_misc.c, src/tlsproxy/tlsproxy.c,

	(20190106-nonprod) Configurable client-side SNI signal.
	Viktor Dukhovni. Files: global/mail_params.h,
	posttls-finger/posttls-finger.c, smtp/lmtp_params.c,
	smtp/smtp.c, smtp/smtp.h, smtp/smtp_params.c, smtp/smtp_proto.c,
	smtp/smtp_tls_policy.c, tls/tls.h, tls/tls_client.c,
	tls/tls_proxy.h, tls/tls_proxy_client_print.c,
	tls/tls_proxy_client_scan.c.

20190121

	Logging: support for internal logging file, without using
	syslog (it uses the new postlogd daemon instead). This
	solves a usability problem for MacOS, may help getting
	around systemd, and solves 99% of the problem for logging
	to stdout in a container (hopefully we have 100% soon).
	Enable by setting, for example, "maillog_file =
	/var/log/postfix.log").  This works fine for daemons, and
	with some limitations for non-daemon programs.  See
	RELEASE_NOTES for more details.  Files: conf/master.cf,
	conf/post-install, conf/postfix-files, conf/postfix-script,
	mantools/postlink, proto/master, proto/postconf.proto,
	global/mail_params.c, global/mail_params.h, global/mail_proto.h,
	global/maillog_client.c, global/maillog_client.h,
	master/dgram_server.c, master/event_server.c, master/mail_server.h,
	master/master.c, master/master.h, master/master_ent.c,
	master/master_listen.c, master/master_proto.h,
	master/master_wakeup.c, master/multi_server.c,
	master/single_server.c, master/trigger_server.c,
	postalias/postalias.c, postconf/postconf_master.c,
	postdrop/postdrop.c, postfix/postfix.c, postkick/postkick.c,
	postlog/postlog.c, postlogd/postlogd.c, postmap/postmap.c,
	postmulti/postmulti.c, postqueue/postqueue.c,
	postsuper/postsuper.c, sendmail/sendmail.c, util/connect.h,
	util/listen.h, util/logwriter.c, util/logwriter.h,
	util/msg_logger.c, util/msg_logger.h, util/msg_output.c,
	util/msg_output.h, util/unix_dgram_connect.c,
	util/unix_dgram_listen.c.

	Cleanup: cert/key/chain loading, plus unit tests to exercise
	non-error and error cases. Viktor Dukhovni. Files: tls/*.pem,
	tls*.pem.ref, tls/tls_certkey.c.

20190126

	Safety: Postfix programs will log to either syslog or postlog
	but not both; and postlogd forwards postlog logging to
	syslog, when a configuration change removes the maillog_file
	pathname, but some programs still use the old configuration.
	Files: util/msg_syslog.[hc], util/msg_logger.c,
	global/maillog_client.c, postlogd/postlogd.c,

	Bugfix (introduced: Postfix 20110109, Postfix 2.10): watchdog
	pipe file descriptor leak. This pipe provides one source
	of liveness, data from this pipe is discarded, and therefore
	this does not enable privilege escalation or DOS. File:
	util/watchdog.c.

	Feature: stdout logging support; requires "postfix start-fg"
	and "maillog_file = /dev/stdout". Files: master/master.c,
	conf/postfix-script.

20190127

	Safety: when maillog_file is specified, 'postfix check' now
	requires that the postlog service is enabled in master.cf.
	Otherwise 'postfix start' etc. will log a fatal error. File:
	conf/postfix-script.

	Documentation: added policy_context example. File:
	proto/SMTPD_POLICY_README.html.

20190128

	Testing: run libtls tests under Valgrind. File tls/Makefile.in.

20190129

	Safety: require that $maillog_file matches one of the
	pathname prefixes specified in $maillog_file_prefixes. The
	maillog file is created by root, and the prefixes limit the
	damage from a single configuration error. Files:
	global/mail_params.[hc], global/maillog_client.c.

20191201

	Feature: "postfix logrotate" command with configurable
	compression program and datestamp filename suffix. File:
	conf/postfix-script.

20190202

	Cleanup: log a warning when the client sends a malformed
	SNI; log an info message when the client sends a valid SNI
	that does not match the SNI lookup tables; update the
	FORWARD_SECRECY_README logging examples. Viktor Dukhovni.
	Files: proto/FORWARD_SECRECY_README.html, tls/tls.h,
	tls/tls_client.c, tls/tls_misc.c.

20190208

	Debugging: the master(8) daemon now logs a warning if a
	master.cf entry is defined multiple times. File:
	src/master/master_conf.c.

20190209

	Debugging: tlsproxy(8) now logs more details about unexpected
	configuration differences between the Postfix SMTP client
	and the tlsproxy(8) daemon.

20190210

	Documentation: Postfix 3.4.0 RELEASE NOTES.

	Documentation: added BDAT_README.

	Documentation: global TLS settings. Files: mantools/postlink,
	smtp/smtp.c, tlsproxy/tlsproxy.c.

20190211

	Cleanup: removed obsolete parameters: tls_dane_digest_agility,
	tls_dane_trust_anchor_digest_enable; removed openssl_path
	parameter from configuration difference checks in tlsproxy.
	Files: global/mail_params.h, tls/tls_misc.c,
	tls/tls_proxy_client_misc.c, tls/tls_proxy_client_print.c,
	tls/tls_proxy_client_scan.c, tls/tls_proxy.h.

20190212

	Cleanup: missing #ifdef USE_TLS. Files: smtp/smtp_session.c,
	posttls-finger/posttls-finger.c.

20190217

	Cleanup: when the master daemon runs with PID=1 (init mode),
	reap orhpan processes from non-Postfix code running in the
	same container, instead of terminating with a panic. File:
	master/master_spawn.c.

20190218

	Bugfix: tlsproxy did not enable DANE-style PKI because
	libtls seems to have to accreted multiple init functions
	instead of reusing the tls_client_init() and tls_client_start()
	API. And some functions that do initialization don't even
	have init in their name! Problem report by Andreas Schulze.
	Viktor Dukhovni. Files: tls/tls_misc.c, tlsproxy/tlsproxy.c.

	Workaround: Postfix libtls makes DANE-specific changes to
	the shared SSL_CTX. To avoid false sharing, tlsproxy needs
	to label the SSL_CTX cache with DANE bits until we can
	remove the code that modifies SSL_CTX. File: tlsproxy/tlsproxy.c.

	Cleanup: Postfix libtls changed the shared SSL_CTX to
	override ciphers. instead of changing the SSL handle. To
	avoid false sharing in tlsproxy, the changes are now made
	to the SSL handle. Viktor Dukhovni. Files: tls/tls.h,
	tls/tls_client.c, tls/tls_misc.c, tls/tls_server.c.

20190219

	Bugfix: in the Postfix SMTP client, TLS wrappermode was not
	tested in tlsproxy mode. It needed some setup for buffering
	and timeouts. Problem report by Andreas Schulze. File:
	smtp/smtp_proto.c.

20190304

	Bugfix: a reversed test broke TLS configurations that specify
	the same filename for a private key and certificate. Reported
	by Mike Kazantsev. Fix by Viktor Dukhovni. Wietse fixed the
	test. Files: tls/tls_certkey.c, tls/Makefile.in.

20190310

	Bitrot: LINUX5s support, after some sanity checks with a
	rawhide prerelease version. Files: makedefs, util/sys_defs.h.

	Bugfix (introduced: 20181226): broken DANE trust anchor
	file support, caused by left-over debris from the 20181226
	TLS library overhaul. By intrigeri. File: tls/tls_dane.c.

	Bugfix (introduced: Postfix-1.0.1): null pointer read, while
	logging a warning after a corrupted bounce log file. File:
	global/bounce_log.c.

	Bugfix (introduced: Postfix-2.9.0): null pointer read, while
	logging a warning after a postscreen_command_filter read
	error. File: postscreen/postscreen_smtpd.c. global/bounce_log.c

20190312

	Bugfix (introduced: Postfix 2.2): reject_multi_recipient_bounce
	has been producing false rejects starting with the Postfix
	2.2 smtpd_end_of_data_restrictons, and for the same reasons,
	does the same with the Postfix 3.4 BDAT command. The latter
	was reported by Andreas Schulze. File: smtpd/smtpd_check.c.

20190319

	With message_size_limit=0 (which is NOT DOCUMENTED), BDAT
	chunks were always rejected as too large. File: smtpd/smtpd.c

20190328

	Bugfix (introduced: Postfix 3.0): LMTP connections over
	UNIX-domain sockets were cached but not reused, due to a
	cache lookup key mismatch. Therefore, idle cached connections
	could exhaust LMTP server resources, resulting in two-second
	pauses between email deliveries. This problem was investigated
	by Juliana Rodrigueiro. File: smtp/smtp_connect.c.

20190331

	Documentation: tlsext_padding is not a tls_ssl_options
	feature. File: proto/postconf.proto.

20190401

	Portability: added "#undef sun" to util/unix_dgram_connect.c.

20190403

	Bugfix (introduced: Postfix 2.3): a censoring filter broke
	multiline Milter responses for header/body events. Problem
	report by Andreas Thienemann. Files: util/printable.c,
	util/stringops.h, smtpd/smtpd.c

	Bugfix (introduced: Postfix 3.3): "smtp_mx_address_limit =
	0" no longer meant 'unlimited'. Problem report by Luc Pardon.
	File: smtp/smtp_addr.c.

20190615

	Documentation: updated the BUGS section in the smtp(8) manpage
	about TLS connection reuse. File: smtp/smtp.c.

	Workaround for implementations that hang Postfix while
	shutting down a TLS session, until Postfix times out. With
	"tls_fast_shutdown_enable = yes" (the default), Postfix no
	longer waits for the TLS peer to respond to a TLS 'close'
	request. This is recommended with TLSv1.0 and later. Files:
	global/mail_params.h, tls/tls_session.c, and documentation.

20190621

	Bugfix (introduced: Postfix 3.0): the code to reset Postfix
	SMTP server command counts was not called after a HaProxy
	handshake failure, causing stale numbers to be reported.
	The command counts are now reset in the function that reports
	the counts. File: smtpd/smtpd.c.

Revision 1.18: download - view: text, markup, annotated - select for diffs
Tue Apr 30 03:41:51 2019 UTC (7 years, 6 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2019Q2-base, pkgsrc-2019Q2
Diff to: previous 1.17: preferred, colored
Changes since revision 1.17: +2 -2 lines
mail/postfix: update to 3.3.3

This announcement concerns fixes for problems that were introduced
with Postfix 3.0 and later. This is the final update for Postfix
3.0.

Fixed in Postfix 3.3 and later:

  * When the master daemon runs with PID=1 (init mode), it will now
    reap child processes from non-Postfix code running in the same
    container, instead of terminating with a panic. Reported by
    Tamas Gerczei.

Fixed in Postfix 3.0 and later:

  * With smtputf8_enable=yes, table lookups could casefold the
    search string when searching a lookup table that does not use
    fixed-string keys (regexp, pcre, tcp, etc.).

  * With the posttls-finger test program, connections to unix-domain
    servers always resulted in "Failed to establish session" even
    after a connection was established. Reported by Jaroslav Skarva.

Revision 1.17: download - view: text, markup, annotated - select for diffs
Sat Dec 15 16:35:23 2018 UTC (7 years, 11 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2019Q1-base, pkgsrc-2019Q1, pkgsrc-2018Q4-base, pkgsrc-2018Q4
Diff to: previous 1.16: preferred, colored
Changes since revision 1.16: +2 -2 lines
mail/postfix: update to 3.3.2

Changes for all supported stable releases:

  * Support for OpenSSL 1.1.1, and support for TLSv1.3-specific
    features.

      - Updated Postfix TLS documentation examples for TLSv1.3. See
        FORWARD_SECRECY_README.

      - New TLSv1.3-specific attributes in Postfix logging and in
        Postfix "Received:" message headers: key exchange, server
        signature, client signature.

      - New option to selectively disable TLSv1.3 in *_tls_protocols
        settings.

      - New server-side support to avoid issuing multiple session
        tickets.

      - New support to allow OpenSSL >= 1.1.0 run-time micro version
        bumps without logging Postfix warnings about library version
        mismatches.

Fixed in all stable releases:

  * Bugfix: smtpd_discard_ehlo_keywords could not disable "SMTPUTF8",
    because some lookup table was using "EHLO_MASK_SMTPUTF8" instead.

  * Bugfix: minor memory leak in DANE support when minting issuer
    certs. This affects a tiny minority of use cases.

Fixed in Postfix 3.3.2:

  * Bugfix: the Postfix build did not abort if the m4 command was
    not installed, resulting in a broken postconf command.

Revision 1.16: download - view: text, markup, annotated - select for diffs
Mon May 21 14:49:47 2018 UTC (8 years, 5 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2018Q3-base, pkgsrc-2018Q3, pkgsrc-2018Q2-base, pkgsrc-2018Q2
Diff to: previous 1.15: preferred, colored
Changes since revision 1.15: +2 -2 lines
mail/postfix: update to 3.3.1

[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-3.3.1.html]

Fixed in Postfix 3.3:

  * Postfix did not support running as a PID=1 process, which
    complicated Postfix deployment in containers. The "postfix
    start-fg" command will now run the Postfix master daemon as a
    PID=1 process if possible. Thanks for inputs from Andreas
    Schulze, Eray Aslan, and Viktor Dukhovni.

  * Segfault in the postconf(1) command after it could not open a
    Postfix database configuration file due to a file permission
    error (dereferencing a null pointer). Reported by Andreas
    Hasenack, fixed by Viktor Dukhovni.

Fixed in Postfix 3.3, 3.2, 3.1, 3.0:

  * The luser_relay feature became a black hole, when the luser_relay
    parameter was set to a non-existent local address (i.e. mail
    disappeared silently). Reported by J?rgen Thomsen.

  * Missing error propagation in the tlsproxy(8) daemon could result
    in a segfault after TLS handshake error (dereferencing a
    0xffff...ffff pointer). This daemon handles the TLS protocol
    when a non-whitelisted client sends a STARTTLS command to
    postscreen(8).

Revision 1.15: download - view: text, markup, annotated - select for diffs
Wed Mar 21 15:28:45 2018 UTC (8 years, 7 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2018Q1-base, pkgsrc-2018Q1
Diff to: previous 1.14: preferred, colored
Changes since revision 1.14: +2 -2 lines
mail/postfix: update to 3.3.0

Postfix stable release 3.3.0 is available. This release ends support
for legacy release Postfix 2.11.

The main changes are:

  * Dual license: in addition to the historical IBM Public License
    1.0, Postfix is now also distributed with the more recent Eclipse
    Public License 2.0. Recipients can choose to take the software
    under the license of their choice. Those who are more comfortable
    with the IPL can continue with that license.

  * The postconf command now warns about unknown parameter names
    in a Postfix database configuration file. As with other unknown
    parameter names, these warnings can help to find typos early.

  * Container support: Postfix 3.3 will run in the foreground with
    "postfix start-fg". This requires that Postfix multi-instance
    support is disabled (the default). To collect Postfix syslog
    information on the container's host, mount the host's /dev/log
    socket into the container, for example with "docker run -v
    /dev/log:/dev/log ...other options...", and specify a distinct
    Postfix syslog_name setting in the container (for example with
    "postconf syslog_name=the-name-here").

  * Milter support: applications can now send RET and ENVID parameters
    in SMFIR_CHGFROM (change envelope sender) requests.

  * Postfix-generated From: headers with 'full name' information
    are now formatted as "From: name <address>" by default. Specify
    "header_from_format = obsolete" to get the earlier form "From:
    address (name)".

  * Interoperability: when Postfix IPv6 and IPv4 support are both
    enabled, the Postfix SMTP client will now relax MX preferences
    and attempt to schedule similar numbers of IPv4 and IPv6
    addresses. This works around mail delivery problems when a
    destination announces lots of primary MX addresses on IPv6, but
    is reachable only over IPv4 (or vice versa). The new behavior
    is controlled with the smtp_balance_mx_inet_protocols parameter.

  * Compatibility safety net: with compatibility_level < 1, the
    Postfix SMTP server now warns for mail that would be blocked
    by the Postfix 2.10 smtpd_relay_restrictions feature, without
    blocking that mail. There still is a steady trickle of sites
    that upgrade from an earlier Postfix version.

Revision 1.14: download - view: text, markup, annotated - select for diffs
Sun Feb 25 12:27:49 2018 UTC (8 years, 8 months ago) by taca
Branches: MAIN
Diff to: previous 1.13: preferred, colored
Changes since revision 1.13: +2 -2 lines
mail/postfix: update to 3.2.5

Update mail/postfix to 3.2.5.

[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-3.2.4.html]

This announcement concerns fixes for problems that were introduced
with Postfix 3.0 and later. Older supported releases are unaffected.

Fixed in Postfix 3.1 and later:

  * DANE interoperability. Postfix builds with OpenSSL 1.0.0 or
    1.0.1 failed to send email to some sites with "TLSA 2 X X" DNS
    records associated with an intermediate CA certificate. Problem
    report and initial fix by Erwan Legrand.

Fixed in Postfix 3.0 and later:

  * Missing dynamicmaps support in the Postfix sendmail command.
    This broke authorized_submit_users settings that use a
    dynamically-loaded map type. Problem reported by Ulrich Zehl.

Revision 1.13: download - view: text, markup, annotated - select for diffs
Sat Dec 9 02:34:48 2017 UTC (8 years, 11 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2017Q4-base, pkgsrc-2017Q4
Diff to: previous 1.12: preferred, colored
Changes since revision 1.12: +2 -2 lines
mail/postfix: Update to 3.2.4

[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-3.2.4.html]

This announcement concerns fixes for problems that were introduced
with Postfix 3.0 and later. Older supported releases are unaffected.

Fixed in Postfix 3.1 and later:

  * DANE interoperability. Postfix builds with OpenSSL 1.0.0 or
    1.0.1 failed to send email to some sites with "TLSA 2 X X" DNS
    records associated with an intermediate CA certificate. Problem
    report and initial fix by Erwan Legrand.

Fixed in Postfix 3.0 and later:

  * Missing dynamicmaps support in the Postfix sendmail command.
    This broke authorized_submit_users settings that use a
    dynamically-loaded map type. Problem reported by Ulrich Zehl.

Revision 1.12: download - view: text, markup, annotated - select for diffs
Fri Oct 13 17:13:19 2017 UTC (9 years, 1 month ago) by taca
Branches: MAIN
Diff to: previous 1.11: preferred, colored
Changes since revision 1.11: +2 -2 lines
pkgsrc/mail: Update to 3.2.3

[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-3.2.3.html]

This announcement concerns fixes for problems that were introduced
with Postfix 3.2. Older releases are unaffected.

Fixed in Postfix 3.2 and later:

 * Extension propagation was broken with "recipient_delimiter = .".
   This change reverts a change that was trying to be too clever.

 * The postqueue command would abort with a panic message after it
   experienced an output write error while listing the mail queue.
   This change restores a write error check that was lost with the
   Postfix 3.2 rewrite of the vbuf_print formatter.

 * Restored sanity checks for dynamically-specified width and precision
   in format strings (%*, %.*, and %*.*). These checks were lost with
   the Postfix 3.2 rewrite of the vbuf_print formatter.

Revision 1.11: download - view: text, markup, annotated - select for diffs
Mon Jun 19 06:54:15 2017 UTC (9 years, 4 months ago) by wiz
Branches: MAIN
CVS tags: pkgsrc-2017Q3-base, pkgsrc-2017Q3, pkgsrc-2017Q2-base, pkgsrc-2017Q2
Diff to: previous 1.10: preferred, colored
Changes since revision 1.10: +1 -3 lines
Remove two non-working mirror sites.

Revision 1.10: download - view: text, markup, annotated - select for diffs
Sat Jun 17 08:02:22 2017 UTC (9 years, 5 months ago) by taca
Branches: MAIN
Diff to: previous 1.9: preferred, colored
Changes since revision 1.9: +2 -2 lines
Update postfix to 3.2.2.

pkgsrc change: Add support for NetBSD 8.

This announcement (June 13, 2017) includes changes that were released
with an earlier update (June 10, 2017). The announcement was postponed
to avoid confusion due to repeated notification.

Fixed in all supported releases:

  * Security: Berkeley DB versions 2 and later try to read settings
    from a file DB_CONFIG in the current directory. This undocumented
    feature may introduce undisclosed vulnerabilities resulting in
    privilege escalation with Postfix set-gid programs (postdrop,
    postqueue) before they chdir to the Postfix queue directory,
    and with the postmap and postalias commands depending on whether
    the user's current directory is writable by other users. This
    fix does not change Postfix behavior for Berkeley DB versions
    < 3, but it does reduce postmap and postalias 'create' performance
    with Berkeley DB versions 3.0 .. 4.6.

Fixed in Postfix 3.2 and later:

  * The SMTP server receive_override_options were not restored at
    the end of an SMTP session, after the options were modified by
    an smtpd_milter_maps setting of "DISABLE". Milter support
    remained disabled for the life time of the smtpd process.

  * After the Postfix 3.2 address/domain table lookup overhaul, the
    check_sender_access and check_recipient_access features ignored
    a non-default parent_domain_matches_subdomains setting.

Revision 1.9: download - view: text, markup, annotated - select for diffs
Mon Apr 24 20:11:40 2017 UTC (9 years, 6 months ago) by fhajny
Branches: MAIN
Diff to: previous 1.8: preferred, colored
Changes since revision 1.8: +2 -2 lines
Update mail/postfix to 3.2.0.

- Elliptic curve negotiation with OpenSSL >= 1.0.2. This changes the
  default smtpd_tls_eecdh_grade setting to "auto", and introduces a
  new parameter tls_eecdh_auto_curves with the names of curves that may
  be negotiated.
- Stored-procedure support for MySQL databases.
- Cidr: table support for if/endif and negation (by prepending ! to a
  pattern), just like regexp: and pcre: tables. See the cidr_table(5)
  manpage for details.
- The postmap command and the inline: and texthash: maps now support
  spaces in left-hand field of lookup table source text. Use double
  quotes (") around a left-hand field that contains spaces, and use
  backslash (\) to protect quotes in a left-hand field.
- Support for per-client Milter configuration (smtpd_milter_maps) that
  overrides the main.cf smtpd_milters setting, and that has the same
  syntax. A lookup result of "DISABLE" turns off Milter support for that
  client.
- The local SMTP server IP address and port are available in the
  policy delegation protocol (attribute names: server_address,
  server_port), in the Milter protocol (macro names: {daemon_addr},
  {daemon_port}), and in the XCLIENT protocol (attribute names:
  DESTADDR, DESTPORT).
- For safety reasons, the Postfix sendmail -C option must specify an
  authorized directory: the default configuration directory, a
  directory that is listed in the default main.cf file with
  alternate_config_directories or multi_instance_directories, otherwise
  the command must be invoked with root privileges. This mitigates a
  recurring "jail break" problem with the PHP mail() function.
- "PASS" and "STRIP" actions in header/body_checks. "STRIP" is similar
  to "IGNORE" but also logs the action, and "PASS" disables header,
  body, and Milter inspection for the remainder of the message content.
- The collate.pl script by Viktor Dukhovni for grouping Postfix
  logfile records into "sessions" based on queue ID and process ID
  information, in the auxiliary/collate directory of the Postfix source
  tree.

Disabled or removed behavior:
- SMTPUTF8 support: Postfix 3.2 disables the 'transitional'
  compatibility between the IDNA2003 and IDNA2008 standards for
  internationalized domain names (domain names beyond the limits of
  US-ASCII). This makes Postfix behavior consistent with contemporary
  web browsers.
- Postfix 3.2 removes tentative features that were implemented before
  the DANE spec was finalized: support for certificate usage
  PKIX-EE(1), the ability to disable digest agility, and the ability to
  disable support for "TLSA 2 [01] [12]" records that specify the digest
  of a trust anchor.

Revision 1.8: download - view: text, markup, annotated - select for diffs
Sat Mar 4 06:26:24 2017 UTC (9 years, 8 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2017Q1-base, pkgsrc-2017Q1
Diff to: previous 1.7: preferred, colored
Changes since revision 1.7: +2 -2 lines
Update postfix to 3.1.4.

Postfix stable release 3.1.4 is available, as well as legacy releases
3.0.8 and 2.11.9. There will be no further updates for Postfix 2.10.

Fixed with Postfix 3.1.4, 3.0.8, and 2.11.9:

  * The postscreen daemon did not merge the client test status
    information for concurrent sessions from the same IP address.
    Thus, after one session recorded its successful tests in the
    postscreen cache, a concurrent session from that same IP address
    that passed fewer tests could later "wipe out" some of that
    progress in the postscreen cache. The fix has proven itself for
    five months in the development release, and should be safe to
    use in the stable releases.

  * The Postfix SMTP server falsely rejected a sender address when
    validating a sender address with "smtpd_reject_unlisted_recipient
    = yes" or with "reject_unlisted_sender". Cause: the address
    validation code did not query sender_canonical_maps.

  * The virtual delivery agent did not detect failure to skip to
    the end of a mailbox file, so that mail would be delivered to
    the beginning of the file. This could happen when a mailbox
    file was already larger than the virtual mailbox size limit.

  * The postsuper command logged an incorrect rename operation count
    after creating a missing directory.

Fixed with Postfix 3.1.4 and 3.0.8:

  * The Postfix SMTP server falsely rejected mail when a sender-dependent
    "error" transport was configured. Cause: the SMTP server address
    validation code was not updated when the
    sender_dependent_default_transport_maps feature was introduced.
    The fix has proven itself for six months in the development
    release, and should be safe to use in the stable releases.
    Unfortunately, Postfix 2.11 is too different to benefit from
    the same fix.

  * The Postfix SMTP server falsely rejected an SMTPUTF8 sender
    address, when "smtpd_delay_reject = no".

Fixed with Postfix 3.1.4:

  * The "postfix tls deploy-server-cert" command used the wrong
    certificate and key file. This was caused by a cut-and-paste
    error in the postfix-tls-script file.

Revision 1.7: download - view: text, markup, annotated - select for diffs
Sat Jan 21 23:49:02 2017 UTC (9 years, 9 months ago) by rillig
Branches: MAIN
Diff to: previous 1.6: preferred, colored
Changes since revision 1.6: +1 -2 lines
Fixed PKGREVISION to be only defined directly in the package Makefile.

Revision 1.6: download - view: text, markup, annotated - select for diffs
Mon Oct 31 04:19:07 2016 UTC (10 years ago) by maya
Branches: MAIN
CVS tags: pkgsrc-2016Q4-base, pkgsrc-2016Q4
Diff to: previous 1.5: preferred, colored
Changes since revision 1.5: +2 -1 lines
postfix: use pkgconfig instead of icu-config to find icu cflags
and ldflags. should help PR pkg/51354: mail/postfix eai option does not
work because of test in makedef.

bump PKGREVISION

Revision 1.5: download - view: text, markup, annotated - select for diffs
Fri Oct 28 16:10:51 2016 UTC (10 years ago) by jperkin
Branches: MAIN
Diff to: previous 1.4: preferred, colored
Changes since revision 1.4: +11 -3 lines
Make the postfix user/group names variables.

Revision 1.4: download - view: text, markup, annotated - select for diffs
Sun Oct 9 12:28:19 2016 UTC (10 years, 1 month ago) by taca
Branches: MAIN
Diff to: previous 1.3: preferred, colored
Changes since revision 1.3: +2 -2 lines
Update postfix to 3.1.3.

Fixed with Postfix 3.1.3 and 3.0.7:

  * The Postfix SMTP server did not reset a previous session's
    failed/total command counts before rejecting a client that
    exceeds request or concurrency rates. This resulted in incorrect
    failed/total command counts being logged at the end of the
    rejected session.

  * The unionmap multi-table interface did not propagate table
    lookup errors, resulting in false "user unknown" responses.

  * The documentation was updated with a workaround for false "not
    found" errors with MySQL map queries that contain UTF8-encoded
    text. The workaround is to specify "option_group = client" in
    Postfix MySQL configuration files. This will be the default
    setting with Postfix 3.2 and later.

Revision 1.3: download - view: text, markup, annotated - select for diffs
Sun Sep 18 17:10:28 2016 UTC (10 years, 1 month ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2016Q3-base, pkgsrc-2016Q3
Diff to: previous 1.2: preferred, colored
Changes since revision 1.2: +2 -2 lines
Update postfix to 3.1.2.

3.1.0

The main changes in no particular order are:

  * "postfix tls" command to simplify setup of opportunistic TLS,
    and to simplify SMTP server key/certificate management.

  * Positive and negative DNS reply TTL support in postscreen(8).

  * SASL AUTH rate limit in the Postfix SMTP server.

  * A safety limit on the number of address verify requests.

  * JSON-format Postfix queue listing.

  * Destination-independent delivery rate delay

For details, see the RELEASE_NOTES file.


3.1.1

Fixed in all supported releases:

  * The Milter "replace sender" (SMFIR_CHGFROM) request lost an
    address that was added with sender_bcc_maps, resulting in a
    "rcpt count mismatch" warning. Reported by Joerg Backschues.
    This defect was introduced with Postfix 2.6.

  * The "bad filetype" example in the header_checks(5) manpage
    falsely rejected Content- headers with ``name="example";
    x-apple-part-url="example.com"''.  Reported by Cedric Knight.
    This defect was introduced with Postfix 2.6.


3.1.2

Fixed with Postfix 3.1.2:

  * Changes to make Postfix build with OpenSSL 1.1.0.

Fixed with Postfix 3.1.2 and 3.0.6:

  * The makedefs script ignored readme_directory=pathname overrides.
    Fix by Todd C. Olson.

  * The tls_session_ticket_cipher documentation says that the default
    cipher for TLS session tickets is aes-256-cbc, but the implemented
    default was aes-128-cbc. Note that TLS session ticket keys are
    rotated after 1/2 hour, to limit the impact of attacks on session
    ticket keys.

Revision 1.2: download - view: text, markup, annotated - select for diffs
Sun Apr 10 16:39:28 2016 UTC (10 years, 7 months ago) by joerg
Branches: MAIN
CVS tags: pkgsrc-2016Q2-base, pkgsrc-2016Q2
Diff to: previous 1.1: preferred, colored
Changes since revision 1.1: +1 -3 lines
Adjust checks for _USE_DESTDIR != no or incorrect references to
USE_DESTDIR.

Revision 1.1: download - view: text, markup, annotated - select for diffs
Mon Sep 7 09:47:01 2015 UTC (11 years, 2 months ago) by fhajny
Branches: MAIN
CVS tags: pkgsrc-2016Q1-base, pkgsrc-2016Q1, pkgsrc-2015Q4-base, pkgsrc-2015Q4, pkgsrc-2015Q3-base, pkgsrc-2015Q3
Update mail/postfix to 3.0.2.

Database and regexp map functionality is now split into separate packages:

- postfix-cdb
- postfix-ldap
- postfix-lmdb
- postfix-mysql
- postfix-pcre
- postfix-pgsql
- postfix-sqlite

Upstream changelog follows.


Postfix 3.0.2
-------------
No delta against 2.11.6.

Postfix 3.0.1
-------------
- Build error when compiling the Postfix SMTP server with SASL support
  but no TLS support.
- The DNS "resource record to text" converter, used for xxx_dns_reply_filter
  pattern matching, appended a '.' to TXT record resource values.
- The postscreen(8) manpage specified an incorrect Postfix version number
  for the postscreen_dnsbl_timeout parameter.
- The postfix-install script expanded macros in parameter values when
  trying to detect parameter overrides, causing unnecessary main.cf updates
  during "postfix start" etc.
- Some low-level cleanup of UTF-8 string handling with no visible change
  in behavior (besides better performance).

Postfix 3.0.0
-------------
- SMTPUTF8 support for internationalized domain names and address
  localparts as defined in RFC 6530 and related documents.
- Support for Postfix dynamically-linked libraries and database plugins.
- An OPT-IN safety net for the selective adoption of new Postfix default
  settings. If you do nothing, the old Postfix default settings *should*
  remain in effect (complain to your downstream maintainer if that is not
  the case).
- Support for operations on multiple lookup tables. The
  pipemap:{map1,map2...} database type implements a pipeline of lookup
  tables where the result from one lookup table becomes a query for
  the next table; the unionmap:{map1,map2,...} database type sends the

Diff request

This form allows you to request diffs between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.

Log view options

CVSweb <webmaster@jp.NetBSD.org>