From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: imaps.ipfire.org down?
Date: Tue, 29 Aug 2023 11:46:04 +0100 [thread overview]
Message-ID: <6DBFA118-F7C5-4B4F-BE2F-0F6477AF5C9E@ipfire.org> (raw)
In-Reply-To: <573e2b20-88dc-1660-9924-33bb2ded4e0a@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Let me know if this happens again…
> On 29 Aug 2023, at 11:41, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> On 29.08.2023 10:21, Michael Tremer wrote:
>> Hello,
>
> Hi,
>
>> It is working fine for me, too.
>>
>> There is fail2ban running, so you might have been blocked because of too many failed login attempts from your IP address maybe?!
>
> No attempts that I'm aware of. I only noticed it because Thunderbird
> suddenly couldn't retrieve or send mails anymore. Today its working
> normal again. Strange.
>
> Best,
> Matthias
>
>> -Michael
>>
>>>> On 28 Aug 2023, at 15:06, jon <jon.murphy(a)ipfire.org> wrote:
>>>
>>> I tried these two commands and it seems OK:
>>>
>>> openssl s_client -connect submissions.ipfire.org:465
>>>
>>> openssl s_client -connect imaps.ipfire.org:993
>>>
>>>
>>>
>>> From bottom of this wiki page: https://wiki.ipfire.org/accounts
>>>
>>> Jon
>>>
>>>
>>>
>>>> On Aug 28, 2023, at 8:45 AM, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>>
>>>> Hi,
>>>>
>>>> since a few minutes, 'imaps.ipfire.org' seems to be down - doesn't respond.
>>>>
>>>> Anyone else?
>>>>
>>>> Best,
>>>> Matthias
>>>
>>
>
prev parent reply other threads:[~2023-08-29 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 13:45 Matthias Fischer
2023-08-28 14:06 ` jon
2023-08-29 8:21 ` Michael Tremer
2023-08-29 10:41 ` Matthias Fischer
2023-08-29 10:46 ` Michael Tremer [this message]
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=6DBFA118-F7C5-4B4F-BE2F-0F6477AF5C9E@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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