From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] No StartTLS with Kmail
Date: Sun, 28 Mar 2021 15:18:53 +0200 [thread overview]
Message-ID: <20210328131853.akxvAWf9CJ-N0_Ml4Bu4ORfG56oZTcQji-cCjQRwfeo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29739@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
Closed issue by Justinizer on void-packages repository
https://github.com/void-linux/void-packages/issues/29739
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
* Void 5.11.9_1 x86_64 GenuineIntel uptodate rrrmFFFFFF
* package:
* kmail-20.12.3_1
### Expected behavior
* Should receive e-mail over StartTLS
### Actual behavior
* Throws error: `SASL(-4): no mechanism available: No worthy mechs found`
### Steps to reproduce the behavior
* Use Kmail and connect to an E-mail Server over StartTLS (Port: 143) with plain mechanism per IMAP. The server is using ECC certificates based on letsencrypt.
* I checked kmail with another system (ArchLinux and Debian) and used thunderbird on VoidLinux to exclude errors based on server. On ArchLinux and Debian KMail works.
(Personally I think that the SASL Plugin for PLAIN is missing)
prev parent reply other threads:[~2021-03-28 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 5:58 [ISSUE] " Justinizer
2021-03-28 13:18 ` Johnnynator
2021-03-28 13:18 ` Johnnynator [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210328131853.akxvAWf9CJ-N0_Ml4Bu4ORfG56oZTcQji-cCjQRwfeo@z \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).