I can confirm that the bug with resolving has been fixed.

But there is another issue introduced recently:

-----
Dec 14 05:49:30 build1-amd64 smtpd[21332]: smtp-out: Connecting to
smtp+tls://74.125.136.27:25 (ea-in-f27.1e100.net) on session
259e78f2fa313865...
Dec 14 05:49:30 build1-amd64 smtpd[21332]: smtp-out: Connected on session
259e78f2fa313865
Dec 14 05:49:31 build1-amd64 smtpd[21332]: smtp-out: Started TLS on session
259e78f2fa313865: version=TLSv1/SSLv3, cipher=ECDHE-RSA-AES128-GCM-SHA256,
bits=128
Dec 14 05:49:31 build1-amd64 smtpd[21330]: warn: unable to load CA file
/etc/ssl/cert.pem: No such file or directory
Dec 14 05:49:31 build1-amd64 smtpd[21332]: smtp-out: Server certificate
verification failed on session 259e78f2fa313865
Dec 14 05:49:32 build1-amd64 smtpd[21332]: relay: Ok for 00bf9ff6d76de8d3:
session=259e78f2fa313865, from=<[email protected]>, to=<
[email protected]>, rcpt=<->, source=xxx.xxx.xxx.xxx, relay=74.125.136.27 (
ea-in-f27.1e100.net), delay=2s, stat=250 2.0.0 OK 1418514572
r5si7625960wju.58 - gsmtp
Dec 14 05:49:43 build1-amd64 smtpd[21332]: smtp-out: Closing session
259e78f2fa313865: 1 message sent.
-----

"warn: unable to load CA file /etc/ssl/cert.pem: No such file or directory"
although opensmtpd has been built with
"--with-ca-file=%{_sysconfdir}/pki/tls/cert.pem", and it always worked for
me.

-- 
wbr, Denis.

On Sat, Dec 13, 2014 at 9:44 PM, Gilles Chehade <[email protected]> wrote:
>
> On Mon, Dec 08, 2014 at 09:31:29AM +0100, Gilles Chehade wrote:
> > Do you mind opening a ticket ?
> >
> > I was talking to eric@ and asking him if he had a chance to look at this
> > and he had missed this :-/
> >
>
> The bug was in the portable layer of libasr.
>
> Eric committed the fix yesterday and I have published a new libasr
> snapshot today, it would be great if you could give it a run using
> opensmtpd-5.4.4rc1
>
> Besides that, we've received no report of regressions, I dont know
> if it's because no one tested or because there's really none :-/
>
> We'll release 5.4.4 by the end of the year and resume working with
> our devel branch to move things forward.
>

Reply via email to