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 8F66723D4C for ; Mon, 6 May 2024 13:14:07 +0200 (CEST) Received: from sirjofri.de ([5.45.105.127]) by 9front; Mon May 6 07:12:52 -0400 2024 Received: from dummy.faircode.eu ([95.90.217.91]) by sirjofri.de; Mon May 6 13:12:44 +0200 2024 Date: Mon, 6 May 2024 13:12:09 +0200 (GMT+02:00) From: sirjofri To: 9front@9front.org Message-ID: In-Reply-To: References: <4d331fb9-20cd-4b61-953f-5df6e5a03f8f@sirjofri.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Correlation-ID: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: content-addressed extensible map/reduce wrapper JSON realtime-java map/reduce-based controller Subject: Re: [9front] AUTHENTICATE failed can't get challenge (imap4d) Reply-To: 9front@9front.org Precedence: bulk Hello all, a simple reboot fixed it for me for some reason. In the end it was so borked that I couldn't even connect in any way, so I used the VPS panel to reboot it. According to the panel, that machine was up for about 860 days, though I have no idea about the accuracy of those numbers, and I couldn't confirm using uptime. Btw, the VPS panel reports a disk usage of 19GB/20GB, which wouldn't be good. I really hope that's just due to formatting. What's the best way to ask cwfs for accurate numbers? (I run a cwfs without worm). sirjofri