Hi,
A long long time ago, you could never hit that fatal() because it meant we
had a logic error somewhere in the startup code.
After the many simplifications we did, bad configuration/permissions could
lead you to hit that message and fatal() with this cryptic unrelated error
when it should have
I'll just add that I was testing this with the 5.3 release so it doesn't
appear to be related to the recent "pki" changes.
.joel
On Tue, Dec 31, 2013 at 4:26 PM, Mikolaj Kucharski
wrote:
> Joel Knight had similar problem in the past and he gave me a clue that
> the problem my be related to mu
Joel Knight had similar problem in the past and he gave me a clue that
the problem my be related to multiple certificates in one single file
(lile cert.pem has). Below change makes OpenSMTPD running again for me:
--- /etc/mail/smtpd.confWed Jan 1 00:23:52 2014
+++ /etc/mail/smtpd.confWed
Hi,
I've just upgraded my OpenBSD-based mail server to:
OpenBSD 5.4-current (GENERIC.MP) #187: Sat Dec 28 17:15:20 MST 2013
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
and I cannot figure out where is the problem in my smtpd config:
# /etc/mail/smtpd.conf
ext_if =
4 matches
Mail list logo