From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id 2DD6222215 for ; Fri, 3 May 2024 13:54:17 +0200 (CEST) Received: from vultr.musolino.id.au ([45.76.123.158]) by 9front; Fri May 3 07:53:05 -0400 2024 Received: from stinger.home.musolino.id.au ([180.150.112.77]) by vultr; Fri May 3 21:52:10 +1000 2024 Message-ID: To: 9front@9front.org From: Alex Musolino Date: Fri, 03 May 2024 21:22:09 +0930 In-Reply-To: <4d331fb9-20cd-4b61-953f-5df6e5a03f8f@sirjofri.de> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: content-addressed API self-signing generator Subject: Re: [9front] AUTHENTICATE failed can't get challenge (imap4d) Reply-To: 9front@9front.org Precedence: bulk > Does someone know what could cause this? Is your server hosted with vultr? Some problems have started recently with this service provider and some kernel fixes have been made that, so far, seem to have at least improved things. -- Cheers, Alex Musolino