Path to this page:
./
mail/postfix,
Postfix SMTP server and tools
Branch: pkgsrc-2015Q2,
Version: 2.11.6,
Package name: postfix-2.11.6,
Maintainer: pkgsrc-usersPostfix aims to be an alternative to the widely-used sendmail
program. Sendmail is responsible for 70% of all e-mail delivered
on the Internet. With an estimated 100 million users, that's an
estimated 10 billion (10^10) messages daily. A stunning number.
Although IBM supported the Postfix development, it abstains from
control over its evolution. The goal is to have Postfix installed
on as many systems as possible. To this end, the software is given
away with no strings attached to it, so that it can evolve with
input from and under control by its users.
In other words, IBM releases Postfix only once. I will be around
to guide its development for a limited time.
MESSAGE.NetBSD [+/-]===========================================================================
$NetBSD: MESSAGE.NetBSD,v 1.5 2010/03/02 08:07:36 martti Exp $
The existing /etc/rc.d/postfix can be forced to start ${PREFIX}/sbin/postfix
instead of /usr/sbin/postfix, by adding the following lines to
/etc/rc.conf.d/postfix:
postfix_command='${PREFIX}/sbin/postfix'
required_files='${PKG_SYSCONFDIR}/main.cf'
start_cmd='${PREFIX}/sbin/postfix start'
stop_cmd='${PREFIX}/sbin/postfix stop'
reload_cmd='${PREFIX}/sbin/postfix reload'
postconf='${PREFIX}/sbin/postconf'
Please note that /etc/rc.conf.d/postfix does not exist by default so
you need to create that file if you need to override the default settings.
Remember to modify /etc/mailer.conf to use ${PREFIX}/sbin/sendmail instead
of /usr/libexec/postfix/sendmail.
===========================================================================
MESSAGE.sasl [+/-]===========================================================================
$NetBSD: MESSAGE.sasl,v 1.8 2005/03/28 08:53:07 jlam Exp $
To enable SASL authentication in the SMTP server, you may want to edit
${SASLLIBDIR}/smtpd.conf
and change the method used to check plaintext passwords. To use
security/cyrus-saslauthd, you should change the contents of smtpd.conf
to:
pwcheck_method: saslauthd
You may also want to edit
${PKG_SYSCONFDIR}/main.cf
and set the smtpd_sasl_* variables to appropriate values.
To enable SASL authentication in the SMTP client, you may want to edit
${PKG_SYSCONFDIR}/main.cf
and set the smtp_sasl_* variables to appropriate values.
The corresponding SASL authentication plugins will also need to be
installed. Please consult:
${DOCDIR}/SASL_README
and the SASL documentation for more information on setting up SASL
authentication.
===========================================================================
Package options: tls
Master sites: (Expand)
SHA1: 005f84264ae8fa6989181bc61b756a0fd8e99dfa
RMD160: 54a35e148ec169d86528857484e002e9326dc56e
Filesize: 3935.951 KB
Version history: (Expand)
- (2015-07-23) Updated to version: postfix-2.11.6
- (2015-07-04) Package added to pkgsrc.se, version postfix-2.11.5nb1 (created)
CVS history: (Expand)
2015-07-22 22:16:13 by Matthias Scheler | Files touched by this commit (3) | |
Log message:
Pullup ticket #4780 - requested by taca
mail/postfix: security update
Revisions pulled up:
- mail/postfix/Makefile 1.284
- mail/postfix/distinfo 1.160
- mail/postfix/patches/patch-ai 1.33
---
Module Name: pkgsrc
Committed By: taca
Date: Wed Jul 22 00:25:37 UTC 2015
Modified Files:
pkgsrc/mail/postfix: Makefile distinfo
pkgsrc/mail/postfix/patches: patch-ai
Log message:
Update postfix to 2.11.6, security release.
With all supported Postfix releases, the default settings have been
updated so that they no longer enable export-grade ciphers, and no
longer enable the SSLv2 and SSLv3 protocols. These ciphers and
protocols have little if any legitimate use today, and have instead
become a vehicle for downgrade attacks. There are no other code
changes.
Postfix documentation has been updated to reflect the new default
settings and their rationale; the RELEASE_NOTES give suggestions
for how to enable the old ciphers and protocols if your infrastructure
requires them.
Finally, abandoning deprecated ciphers and protocols does not really
improve TLS security without measures to better authenticate remote
servers. Secure DNS and TLSA are steps in that direction.
|