Re: imap4d: unable to connect via TLS

[Maurizio Avogadro]

Il 17/02/22 20:33, Sergey Poznyakoff ha scritto:
> To begin with, enable transcript in your server section:
>
> server 0.0.0.0:993 {
>     transcript yes;
>     ...
> }
>
> > Could the segfaults be related with the attempt Thunderbird does to
> > create the other folders (Sent, Drafts and Trash),
>
> Judging by the output you got, it doesn't get this far.  It looks like the
> coredump occurs during TLS handshake.

It seems to occur in the authentication phase.

I attached 2 syslog snippets obtained with 'transcript yes':

- auth_plain.log is the result of an authentication attempt in PLAIN mode
  Also contains the output of ltrace and strace during a PLAIN auth attempt.

- auth_cram-md5.log is the result of two authentication attempt in "encrypted"
  mode: the client reports that password wasn't accepted and I tried to input
  it a second time, then I cancelled the attempt.

I also tried with other MUAs getting identical outcomes (some also attempt to
login with 'authenticate LOGIN', but fail just the same).

I checked and reinstalled all the dependencies.

Summing up: the only authentication method accepted seems to be from command
line, openssl s_connect, '. LOGIN <username> <password>' (which doesn't require
any hashing), every other method fails.

Can you figure out what's going on? Is there a way to get further info?

> That's intended.  If you don't need your home directory to be visible
> within your personal namespace, create a directory for imap
> (e.g. ~/.imap) and add the following to your imap4d configuration:
>
>    namespace personal {
>      prefix "";
>      directory "$home/.imap";
>    }
>
> Please read
>
>   https://mailutils.org/manual/html_node/Namespace.html
>
> for a detailed discussion on how to configure imap4d namespaces.

Thanks, this seems indeed to stop $home listing.

Thank you!

auth_plain.txt
Description: Text document

auth_cram-md5.txt
Description: Text document