On Mon, 9 Jun 2014 10:16:43 +0200, you wrote:
On Mon, Jun 09, 2014 at 08:39:52AM +0100, John Cox wrote:
Hi
That's not correct no, I get plenty of TLS 1.0 trafic and it has been
the case for many years
To parrot this on all of my various instances OpenSMTPD and not I get tons
of TLS 1.0
a different approach was used for this, we reserve 100 blocks at startup
which is what Sendmail does on OpenBSD, if it has worked for years, it
should keep working.
On Tue, May 20, 2014 at 02:29:41PM -0700, Barbier, Jason wrote:
restart away good man it is a topic that should be discussed
User gilles has just rebuilt a master snapshot, available from:
http://www.OpenSMTPD.org/archives/opensmtpd-201406110039.tar.gz
Checksum:
SHA256 (opensmtpd-201406110039.tar.gz) =
9082a22615dba0fc4979ba82396dc5e5c1d879db2e02c2e5970eeec8decd7624
A summary of the content of this
User gilles has just rebuilt a portable snapshot, available from:
http://www.OpenSMTPD.org/archives/opensmtpd-201406110044p1.tar.gz
Checksum:
SHA256 (opensmtpd-201406110044p1.tar.gz) =
316caf50217726c9cc4872d255613684febf7fa2c9d2c6138c2d067463ce8e85
A summary of the content of this
On Wed, Jun 11, 2014 at 12:45:20AM +0200, gil...@poolp.org wrote:
User gilles has just rebuilt a portable snapshot, available from:
http://www.OpenSMTPD.org/archives/opensmtpd-201406110044p1.tar.gz
[...]
- OpenSSL version detection was broken, the following fixes it for 1.0.0
Hi,
After spending the last hour on this:
https://github.com/poolpOrg/OpenSMTPD/commit/452d68767cd616cfa92606258119b74308c3edc7#diff-ceef0aa7bec5d64345287a4bc2c23cba
I'm actually wondering why we bother, and if we should not just kill the
support for pre-1.0.0 OpenSSL at configure time
Sounds like a good solution :D
On 06/10/14 10:20, Gilles Chehade wrote:
a different approach was used for this, we reserve 100 blocks at startup
which is what Sendmail does on OpenBSD, if it has worked for years, it
should keep working.
On Tue, May 20, 2014 at 02:29:41PM -0700, Barbier, Jason
