From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] AUTHENTICATE failed can't get challenge (imap4d)
Date: Fri, 3 May 2024 14:51:33 -0500 [thread overview]
Message-ID: <4f9bde56-04c9-4ded-b7c1-1eac44b81198@posixcafe.org> (raw)
In-Reply-To: <ca57c270-2b84-4681-970d-78fd428cc794@sirjofri.de>
On 5/3/24 13:23, sirjofri wrote:
> 03.05.2024 14:12:18 Alex Musolino <alex@musolino.id.au>:
>
>>> Does someone know what could cause this?
>>
>> Is your server hosted with vultr?
>
> Nope, netcup. It's the cheapest plan there, but I never had issues so far.
>
> sirjofri
We've seen it happen to folks primarily in vultr but I don't think there is currently
any reason to believe vultr specifically is a target. Getting a list of every machine
with ports open on the ipv4 net these days is really not much of a task, so I wouldn't
be surprised if they were just spamming any address they know of listening on web ports.
Either way, I'd update your kernel and userspace and see if that fixes the problem.
Thanks,
moody
next prev parent reply other threads:[~2024-05-03 19:53 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 [this message]
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 ` [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=4f9bde56-04c9-4ded-b7c1-1eac44b81198@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).