From: Tim FitzGeorge <ipfr@tfitzgeorge.me.uk>
To: development@lists.ipfire.org
Subject: Status emails and IP Blocklists
Date: Thu, 29 Nov 2018 21:11:54 +0000 [thread overview]
Message-ID: <0239e84a-5ef4-12cb-216c-109ac6918dc2@tfitzgeorge.me.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
I've written a couple of addons for my installations of IPFire. They're
available on github and some other people have tried them; they seem to
be fairly well received and it's been suggested that it may be worth
making them available through pakfire as official addons.
The first addon provides the ability to send status emails. You can
define multiple schedules and the items to be included in each email.
By choosing parameters carefully it's possible to get it to send emails
on some error conditions. The emails can be encrypted with GPG. The
architecture makes it easy to add further items to be reported on.
The second addon handles the setting up and updating of IP Address
Blocklists in the firewall. It includes options to select which lists
to use, and some control over how frequently to check for updates.
Both include WUI pages for configuration and language files. They're
fully functional, but would require some checking and minor updates.
The source can be seen at https://github.com/timfprogs .
I'm aware that there other people have made addons for both these
purposes, which maybe suggests that it's functionality that is worth adding.
next reply other threads:[~2018-11-29 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 21:11 Tim FitzGeorge [this message]
[not found] <745dc6bc-4ac4-8b43-415b-17c35d2fb219@tfitzgeorge.me.uk>
2018-12-01 19:46 ` Michael Tremer
[not found] <1c66503b47593dd61f22167c559fe81cde60bf5c.camel@ipfire.org>
2018-12-01 20:18 ` Peter Müller
2018-12-02 11:12 ` Michael Tremer
2018-12-02 12:08 ` Peter Müller
2018-12-02 12:10 ` Michael Tremer
[not found] <c4c6137e-5f6a-8ee7-c36e-8deded18f28a@tfitzgeorge.me.uk>
2019-04-01 11:07 ` Michael Tremer
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=0239e84a-5ef4-12cb-216c-109ac6918dc2@tfitzgeorge.me.uk \
--to=ipfr@tfitzgeorge.me.uk \
--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