infrastructure/mox
1
0
Fork 0
mirror of https://github.com/mjl-/mox.git synced 2025-06-28 07:48:13 +03:00
Code Issues Packages Projects Releases Wiki Activity

add fail2ban snippet to FAQ

Browse Source 
from unguamorray in issue #274
This commit is contained in:
Mechiel Lukkien 2025-01-29 20:58:31 +01:00
parent df17ae2321
commit ec7904c0ee
No known key found for this signature in database
2 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -533,3 +533,13 @@ ensuring they don't become too large. The message index database file for an
account is at `data/accounts/<account>/index.db`, accessed with the bstore account is at `data/accounts/<account>/index.db`, accessed with the bstore
database library, which uses bbolt (formerly BoltDB) for storage, a database library, which uses bbolt (formerly BoltDB) for storage, a
transactional key/value library/file format inspired by LMDB. transactional key/value library/file format inspired by LMDB.
## How do I block IPs with authentication failures with fail2ban?
Mox includes a rate limiter for IPs/networks that cause too many authentication
failures. It automatically unblocks such IPs/networks after a while. So you may
not need fail2ban. If you want to use fail2ban, you could use this snippet:
[Definition]
failregex = .*failed authentication attempt.*remote=<HOST>
ignoreregex =

8
develop.txt
View File

@ -101,10 +101,10 @@ Large files (images/videos) are in https://github.com/mjl-/mox-website-files to
keep the repository reasonably sized. keep the repository reasonably sized.
The public website may serve the content from the "website" branch. After a The public website may serve the content from the "website" branch. After a
release release, the main branch (with latest development code and release, the main branch (with latest development code and corresponding
corresponding changes to the website about new features) is merged into the changes to the website about new features) is merged into the website branch.
website branch. Commits to the website branch (e.g. for a news item, or any Commits to the website branch (e.g. for a news item, or any other change
other change unrelated to a new release) is merged back into the main branch. unrelated to a new release) is merged back into the main branch.
# TLS certificates # TLS certificates