On Thu, May 26, 2022 at 09:42:51AM +0100, Stuart Henderson wrote:
> let's move this to ports@ ..
> 
> On 2022-05-26, Avon Robertson <[email protected]> wrote:
> > On Wed, May 25, 2022 at 12:03:00PM -0000, Stuart Henderson wrote:
> >> On 2022-05-22, Avon Robertson <[email protected]> wrote:
> >> > The libcrypto build and install as outlined above by Theo was completed
> >> > without error a few minutes ago on the Dell M6600. It was then rebooted
> >> > and mutt's G command was invoked to fetch mail from pop3.xtra.co.nz.
> >> >
> >> > Sadly the attempt failed and mutt's error-history command displayed the
> >> > same error as above.
> >> 
> >> I've just tested with the current snapshot:
> >> 
> >> $ TZ=UTC ls -l /usr/lib/libssl.so.52.0 /usr/local/bin/mutt
> >> -r--r--r--  1 root  bin  1509824 May 25 06:51 /usr/lib/libssl.so.52.0
> >> -rwxr-xr-x  1 root  bin  1318616 May 24 02:11 /usr/local/bin/mutt
> >> 
> >> Testing with pop3.xtra.co.nz, I don't have an account but a bogus
> >> username is good enough to check that TLS works, so I added this to
> >> the default muttrc
> >> 
> >> set pop_host=pops://[email protected]/
> >> 
> >> Run mutt and press G - no TLS failure.
> >> 
> >> 
> > Thanks for your response Stuart.
> >
> > Last night I downloaded and reinstalled, bsd.rd 'i' not 'u', the then
> > latest -current snapshot from mirror.aarnet.edu.au/pub/OpenBSD, and
> > reinstalled the packages that I wanted/needed on the M6600 laptop. 
> >
> > Then coincidently, invoking your TZ... ls -l command above outputs the
> > same information.
> >
> > Changing the set_host=... line in my ~/.muttrc file however, fails and
> > the error-history command displays the same error information shown in
> > several of the earlier posts in this thread.
> 
> Can you share the whole muttrc (obviously mask passwords/usernames as
> necessary)?
> 
Certainly. The unedited/unmasked file is 139781 bytes. Would you prefer
it to be attached as a .xz or .gz file, or inline when I send it? It is
after midnight here so I will send it with other minor information
tomorrow.

-- 
aer

Reply via email to