OpenSMTPD 5.7.1 has just been released.

OpenSMTPD is a FREE implementation of the SMTP protocol with some common
extensions. It allows ordinary machines to exchange e-mails with systems
speaking the SMTP protocol. It implements a fairly large part of RFC5321
and can already cover a large range of use-cases.

It runs on OpenBSD, NetBSD, FreeBSD, DragonFlyBSD, OSX and Linux.

The archives are now available from the main site at www.OpenSMTPD.org

We would like to thank the OpenSMTPD community for their help in testing
the snapshots, reporting bugs, contributing code and packaging for other
systems.

This is a major release with many new features, many minor bugfixes, and
a lot of internal changes.

New features since last stable release (5.4.6):
===============================================

  * Improved logging
    - logging format has changed to ease parsing and be less verbose
    - multi-line responses are now logged

  * Improved documentation
    - portions of man pages have been rewritten to clarify them
    - more examples for common use-cases have been added
    - format specifiers have been documented
    - forward-only has been documented
    
  * Improved TLS / crypto
    - privileges-separated RSA engine
    - better cope with errors in opportunistic TLS
    - ciphers and curves can now be selected
    - pki/ca interface has been reworked to allow custom CA
    - certificate verification code has been greatly simplified
    - SNI code has been simplified too
    - switched to 2048-bits DH params by default

  * Assorted improvements
    - domain-append is now supported
    - support for SMTP-level filtering of users-provided senders
    - initial support for masquerading
    - usernames no longer need to be restricted to MAX_LOG_NAME
    - DSN can now be generated without content or with headers only
    - better handle IPv6 addresses in relay via rules
    - fix unnecessary long delays relaying from backup to primary MX
    - fd-exhaustion detection has been simplified
    - reworked enqueuer
    - the +-tag uses .tag folder if it exists, Maildir otherwise
    - maildir:/path is now a supported expansion for aliases
    

  Experimental:

  * filters plumbing is now always enabled
  * the filter API is now available, though considered experimental


Checksums:
==========

  SHA256 (opensmtpd-5.7.1.tar.gz) =
  b078de0e7d3ad3ca849974be2a079e2961b793525465312f074d1c0a818cacf9

  SHA256 (opensmtpd-5.7.1p1.tar.gz) =
  67e9dd9682ca8c181e84e66c76245a4a8f6205834f915a2c021cdfeb22049e3a


Verify:
=======

Starting with version 5.7.1, releases are signed with signify(1).

You can obtain the public key from our website, check with our community
that it has not been altered on its way to your machine.

Once you are confident the key is correct, you can verify the release as
described below:

1- get the signature file corresponding to the tarball you're installing

   $ wget https://www.opensmtpd.org/archives/opensmtpd-5.7.1.sum.sig


2- check that the tarball matches the checksum:

   $ sha256 opensmtpd-5.7.1.tar.gz
   SHA256 (opensmtpd-5.7.1.tar.gz) =
   b078de0e7d3ad3ca849974be2a079e2961b793525465312f074d1c0a818cacf9
   $ cat opensmtpd-5.7.1.sum.sig |tail -1
   b078de0e7d3ad3ca849974be2a079e2961b793525465312f074d1c0a818cacf9


3- verify that the signature file was not forged:

   $ signify -V -e -p opensmtpd.pub -m opensmtpd-5.7.1.sum
   Signature Verified


Support:
========

You are encouraged to register to our general purpose mailing-list:
    http://www.opensmtpd.org/list.html

The "Official" IRC channel for the project is at:
    #OpenSMTPD @ irc.freenode.net


Reporting Bugs:
===============

Please read http://www.opensmtpd.org/report.html
Security bugs should be reported directly to [email protected]
Other bugs may be reported to [email protected]

OpenSMTPD is brought to you by Gilles Chehade, Eric Faurot and
Sunil Nimmagadda.

-- 
Gilles Chehade

https://www.poolp.org                                          @poolpOrg

-- 
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]

Reply via email to