tags #394598 confirmed pending
thanks
On Sat, Oct 21, 2006 at 10:05:05PM -0500, John Goerzen wrote:
This is a serious upgrade-from-sarge issue that could break things.
Agreed. I have committed a patch to exim4-base.postinst that will
check file(1)'s output and zap the file if it is classified
On Mon, Oct 23, 2006 at 02:25:18PM -0500, John Goerzen wrote:
On Mon, Oct 23, 2006 at 08:39:22PM +0200, Marc Haber wrote:
On Sat, Oct 21, 2006 at 10:05:05PM -0500, John Goerzen wrote:
This is a serious upgrade-from-sarge issue that could break things.
Agreed. I have committed a patch to
On Mon, Oct 23, 2006 at 08:39:22PM +0200, Marc Haber wrote:
tags #394598 confirmed pending
thanks
On Sat, Oct 21, 2006 at 10:05:05PM -0500, John Goerzen wrote:
This is a serious upgrade-from-sarge issue that could break things.
Agreed. I have committed a patch to exim4-base.postinst that
Package: exim4-daemon-heavy
Version: 4.63-7
Severity: serious
I have upgraded from exim4 4.50-8sarge2.
Now, whenever a client attempts to use TLS, I see:
2006-10-21 22:00:08 TLS error on connection from xxx (yyy) [x.x.x] (DH params
import): Base64 decoding error.
Nothing has changed with my
4 matches
Mail list logo
