Re: Unable to connect with sieveshell - compile options?

Janos Dohanics <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <[email protected]>
On Tue, 14 Jun 2022 12:23:41 +0200
"Niels Dettenbach via Info" <[email protected]> wrote:

> Am Dienstag, 14. Juni 2022, 11:30:52 CEST schrieb Janos Dohanics:
> > Well, doesn't the error message "unable to connect to server" imply
> > that authentication couldn't have even been attempted because no
> > connection was established?
> depends from the definition / interpretation of "connection"...

You are right, just did tcpdump, sieveshell does connect and
authentication fails (but the output is "unable to connect to server").

I have recompiled security/cyrus-sasl2-saslauthd to include security/krb5:

# make showconfig
===> The following configuration options are available for cyrus-sasl-saslauthd-2.1.28:
     DOCS=off: Build and/or install documentation
     HTTPFORM=off: Enable HTTP form authentication
     OPENLDAP=off: Use OpenLDAP
     SASLDB_IN_VAR=off: sasldb in /var/db/sasl2
====> GSSAPI Security API support: you can only select none or one of them
     GSSAPI_BASE=off: GSSAPI support via base system (needs Kerberos)
     GSSAPI_HEIMDAL=off: GSSAPI support via security/heimdal
     GSSAPI_MIT=on: GSSAPI support via security/krb5
====> Experimental SASLdb authentication module: you can only select none or one of them
     BDB1=on: Berkeley DB 1.85 support
     BDB=off: Berkeley DB support
     GDBM=off: GNU dbm library support
     LMDB=off: OpenLDAP Lightning Memory-Mapped Database support
===> Use 'make config' to modify these settings

...but no success.

It would be great to have clearer guidance on this issue...

-- 
Janos Dohanics

------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/T7345c00a04173773-Me2b619eb0f7e3c6121a70a98
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.