9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Roberto E. Vargas Caballero" <k0ga@shike2.com>
To: 9front@9front.org
Subject: Re: [9front] AUTHENTICATE failed can't get challenge (imap4d)
Date: Fri, 3 May 2024 23:09:07 +0200	[thread overview]
Message-ID: <ZjVSc2QGON2Bx+P/@simple-cc.openbsd.amsterdam> (raw)
In-Reply-To: <4d331fb9-20cd-4b61-953f-5df6e5a03f8f@sirjofri.de>

Hi,

On Fri, May 03, 2024 at 01:12:48PM +0200, sirjofri wrote:
> Hey all,
> 
> for a few days now my mobile mail client (FairEmail) receives the message "AUTHENTICATE failed can't get challenge" together with log messages about failed SSL handshakes and connection resets by the server.

I had a similar problem fetching hotmail with imap. I didn't try after the last changes.
I will try in the coming days.

Regards,

  parent reply	other threads:[~2024-05-03 21:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 11:12 sirjofri
2024-05-03 11:52 ` Alex Musolino
2024-05-03 18:23   ` sirjofri
2024-05-03 19:51     ` Jacob Moody
2024-05-03 21:09 ` Roberto E. Vargas Caballero [this message]
2024-05-06 11:12   ` sirjofri
2024-05-06 12:59     ` qwx
2024-05-06 14:34       ` Stanley Lieber
2024-05-06 14:50         ` qwx
2024-05-06 15:30           ` sirjofri
2024-05-06 15:40           ` Stanley Lieber
2024-05-06 16:03             ` qwx
2024-05-06 16:24               ` Stanley Lieber
2024-05-06 16:03             ` Stanley Lieber
2024-05-06 16:08             ` [9front] cwfs no-worm + venti (was: AUTHENTICATE failed can't get challenge (imap4d)) sirjofri
2024-05-06 16:21               ` [9front] " Stanley Lieber
2024-05-06 16:37                 ` [9front] Re: [9front] cwfs no-worm + venti Jacob Moody
2024-05-06 13:56     ` [9front] AUTHENTICATE failed can't get challenge (imap4d) Jacob Moody
2024-05-06 14:32     ` Stanley Lieber

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=ZjVSc2QGON2Bx+P/@simple-cc.openbsd.amsterdam \
    --to=k0ga@shike2.com \
    --cc=9front@9front.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).