From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] AUTHENTICATE failed can't get challenge (imap4d)
Date: Mon, 6 May 2024 08:56:07 -0500 [thread overview]
Message-ID: <9f19b15d-61f1-4c49-b640-68a8a8809917@posixcafe.org> (raw)
In-Reply-To: <f874287e-7f91-4822-974c-9b36cff74b16@sirjofri.de>
On 5/6/24 06:12, sirjofri wrote:
> 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.
Yes it will with this issue, but if it is what I think it is than it will just come back.
Why not just update the machine?
>
> 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).
Without a worm you can not get this information.
next prev parent reply other threads:[~2024-05-06 13:57 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
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 ` Jacob Moody [this message]
2024-05-06 14:32 ` [9front] AUTHENTICATE failed can't get challenge (imap4d) 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=9f19b15d-61f1-4c49-b640-68a8a8809917@posixcafe.org \
--to=moody@posixcafe.org \
--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).