Postfix attempts to be fast, easy to administer, and secure, while at the same
time being sendmail compatible enough to not upset existing users. Thus, the
outside has a sendmail-ish flavor, but the inside is completely different.
Some features:
Connection cache for SMTP, DSN status notifications, IP version 6, Plug-in
support for multiple SASL implementations (Cyrus, Dovecot), TLS encryption and
authentication, Configurable status notification message text, Access control
per client/sender/recipient/etc, Content filter (built-in, external before
queue, external after queue), Berkeley DB database, LDAP database, MySQL
database, PostgreSQL database, Maildir and mailbox format, Virtual domains,
VERP envelope return addresses and others.
===> The following configuration options are available for postfix-current-3.12.20260925_4,6:
BDB=off: Berkeley DB support
BLOCKLISTD=on: Enable blocklistd support
CDB=on: CDB maps lookups
DOCS=on: Build and/or install documentation
EAI=on: Email Address Internationalization (SMTPUTF8) support
INST_BASE=off: Install into /usr and /etc/postfix
LDAP=off: LDAP maps (uses WITH_OPENLDAP_VER)
LMDB=on: LMDB maps
MONGO=off: MongoDB support
MYSQL=off: MySQL database support
NIS=off: Network Information Services/YP support
PCRE2=on: Use Perl Compatible Regular Expressions, version 2
PGSQL=off: PostgreSQL database support
SASL=off: Cyrus SASL support (Dovecot SASL is always built in)
SQLITE=off: SQLite database support
TEST=off: SMTP/LMTP test server and generator
TLS=on: Secure network connection support via TLS
TLSRPT=on: Enable sending RFC 8460 TLS reports
====> LMDB library to use: you can only select none or one of them
LMDB0=on: Use LMDB 0.9 library
LMDB1=off: Use LMDB 1.0 library
====> Kerberos network authentication protocol type: you can only select none or one of them
SASLKMIT=off: If your SASL req. MIT Kerberos5, select this
SASLKRB5=off: If your SASL req. Kerberos5, select this
===> Use 'make config' to modify these settings
Reason:
mail/postfix-current now can depend on either databases/lmdb0 or
databases/lmdb. The default is lmdb0 for now.
If you want/need to use lmdb1, you will need to build the package
with apropriate lmdb version selected.
Number of commits found: 557 (showing only 100 on this page) #
mail/postfix-current: Fix race between stop and start
Try to avoid race condition between stop and start as
LOCALBASE/sbin/postfix is non-blocking and start might be
executed sooner than stop actually finishes (esp. with long mail
queues).
Regenerate blocklistd and blacklistd patches [2]
Reported by: Viktor Štujber <viktor.stujber+freebsd-bugs_v4CCPfay@gmail.com>
[1]
PR: 300389
PR: 300255
databases/lmdb: allow to install both 0.x and 1.x together
LMDB 1.0 and the legacy 0.9 ABI cannot be mixed, the datanase format are
incompatibles as well.
Rename or relocate everything databases/lmdb0 installs so that it no
longer overlaps with databases/lmdb:
- the utilities are now mdb_copy0, mdb_dump0, mdb_load0 and mdb_stat0
- the header is include/lmdb0/lmdb.h
- the linker name is liblmdb0.so, the shared object keeps its ABI name
liblmdb.so.0 so already linked programs are unaffected
- the pkg-config file is lmdb0.pc
A compatibility prefix holding the previous layout is also installed
under ${PREFIX}/lmdb0/ (include/, lib/ and libdata/pkgconfig/) so that
build systems which expect to find lmdb.h and -llmdb relative to a
single directory only need a path change.
Now all ports should migrate to lmdb 1.X and use the lmdb 0.9 port to ease
in the migration path, lmdb, the lmdb 0.x is supposed to get removed at
some point.
Approved by: mat (portmgr)
Reviewed by: mat
Differential Revision: https://reviews.freebsd.org/D60741
databases/lmdb0: Add port for LMDB 0.9.x legacy ABI
LMDB 1.0 introduced an incompatible on-disk format change and subtle
API breakage: applications that compiled cleanly against 1.0 headers
could fail silently at run time. Known affected ports include dns/knot3,
mail/bogofilter, and mail/postfix; the postfix issue has been confirmed
upstream. Linux distributions such as Arch Linux have observed the same
breakage. Samba can also be affected in certain configurations.
Because the regression is not detectable in an -exp build run -- the
postfix failure only manifests at run time, and bogofilter was caught
only because post-build self-tests happen to exercise this path -- we
cannot rely on package builds to validate the 1.0 upgrade.
This commit introduces databases/lmdb0 as a holding port for the 0.9.35
(Only the first 15 lines of the commit message are shown above )
mail/postfix-current: Fix build on 15.0 with SASLKRB5
Kerberos in 15.0 does not provide the old libraries.
PR: 291605
Reported by: Christian Hennig <zeha@ccsej.de>
mail/postfix-current: Update to 3.11-20250928
- Update to 3.11-20250928
- Make postscreen blacklistd-aware [1]
- Fix the build on FreeBSD 16.0-CURRENT
Co-authored-by: Michael Grimm <trashcan@ellael.org>
PR: 289737
mail/postfix-current: Update to 3.11-20250606 and add TLSRPT support
- Update to 3.11-20250606
- Add option to enable TLSRPT functionality
Co-authored by: Matthew Seaman <matthew@FreeBSD.org>
PR: 287297
mail/postfix-current: Update to 3.11.20250304
And while here, also fix pkg-install in the same way as in mail/postfix
Reported by: Herbert J. Skuhra <herbert@gojira.at>
mail/postfix-current: Update to 20240603 and enable service jail
- Update to 3.10-20240603
- Make rc script ready for service jails (contributed by netchild@)
Mk/**ldap.mk: Convert USE_LDAP to USES=ldap
Convert the USE_LDAP=yes to USES=ldap and adds the following features:
- Adds the argument USES=ldap:server to add openldap2{4|5|6}-server as
RUN_DEPENDS
- Adds the argument USES=ldap<version> and replaces WANT_OPENLDAP_VER
- Adds OPENLDAP versions in bsd.default-versions.mk
- Adds USE_OPENLDAP/WANT_OPENLDAP_VER in Mk/bsd.sanity.mk
- Changes consumers to use the features
Reviewed by: delphij
Approved by: portmgr
Differential Revision: https://reviews.freebsd.org/D38233
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
mail/postfix-current: Unbreak build
Unbreak build after update to recent 3.8. The breakage was caused
by a patch generated using makepatch. Local patches are now applied
in post-patch stage.
*/*: Remove redundant '-[0-9]*' from CONFLICTS_INSTALL
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Approved by: portmgr (blanket)
mail/postfix-current{,-sasl}: Flavorize
* Add entry for slave port to MOVED
* Pet portlint and portclippy
* Reformat Makefile with portfmt
PR: 255647
Approved by: maintainer timeout (> 2 months)
Differential Revision: https://reviews.freebsd.org/D32362
mail/postfix-current: Update to 3.7-20210707
- Update to 3.7-20210707
- Check if OpenSSL at least 1.1.1a is being used
- LibreSSL is not supported as it dos not (yet) provide the
TLSv1.3 API found in OpenSSL 1.1.1 API.
- update to 3.6-20210110
Major changes with snapshot 20210109
====================================
Starting with Postfix version 3.6, the "latest" compatibility level
is 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 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.
