Re: OpenSMTPD 7.3.0p0 rc1 -- please test!

2023-06-04 Thread Richard Narron
On Sun, 4 Jun 2023, Omar Polo wrote:

> On 2023/06/03 09:08:05 -0700, Richard Narron  wrote:
> > In order to use the bundled libasr, I had to uninstall my existing libasr
> > slackware build (port).
> >
> > It would be nice to have a --with-bundled-libasr option for the build.
> > Then It could ignore an existing installed libasr.
>
> Haven't noticed that there isn't a way to force the usage of the
> bundled libasr.  I've added the configure knob --with-bundled-libasr
> and included it in the release-7.3 branch (no new RC this time though)
>

Thanks for the fix!

The --with-bundled-libasr option works well.
If I use it it ignores an existing libasr library.
If I don't use it, and don't have a libasr library then it uses the
bundled libasr anyway.

To Build it I downloaded the OpenSMTPD.zip, unpacked it and then
ran the "bootstrap" script which calls autoconf.

It looks good and runs fine so far.





Re: OpenSMTPD 7.3.0p0 rc1 -- please test!

2023-06-04 Thread Frank de Bruijn
I built 7.3.0p0 rc2 on Debian Bookworm and it seems to work ok so far. 
Just one thing: I had to change my smtpd.conf, because starting 
initially failed with:


 smtpd: invalid listen option: pki required for tls/smtps

My smtpd.conf has four pki sets, because the server serves several 
domains. Up to now, I never needed to use pki in a listen directive, as 
OpenSMTPD would pick the correct pki depending on the hostname.


It appears this no longer works. Is that a bug or a deliberate change? 
If the latter, what to do now? For the tests, I used one of the pkis in 
the listen directive, but I really need all four of them. Would 
specifying them all work?


Regards,
Frank



Re: OpenSMTPD 7.3.0p0 rc1 -- please test!

2023-06-04 Thread Omar Polo
On 2023/06/03 09:08:05 -0700, Richard Narron  wrote:
> In order to use the bundled libasr, I had to uninstall my existing libasr
> slackware build (port).
> 
> It would be nice to have a --with-bundled-libasr option for the build.
> Then It could ignore an existing installed libasr.

Haven't noticed that there isn't a way to force the usage of the
bundled libasr.  I've added the configure knob --with-bundled-libasr
and included it in the release-7.3 branch (no new RC this time though)

> So far it looks good.  I will keep testing.

Thanks!