Skip to content
This repository has been archived by the owner on May 27, 2024. It is now read-only.

Support for intelmq-cb-mailgen #40

Open
bernhardreiter opened this issue Feb 27, 2018 · 4 comments
Open

Support for intelmq-cb-mailgen #40

bernhardreiter opened this issue Feb 27, 2018 · 4 comments

Comments

@bernhardreiter
Copy link
Contributor

bernhardreiter commented Feb 27, 2018

It would be nice to support https://github.com/Intevation/intelmq-mailgen-release setups.

Mainly this means that the path of the outgoing information has to be steered.
This can be done by a combination of

  • adding additional input via the webfrontend
  • documenting how to add additional configuration (e.g. rule scripts or mailgen scripts).

The design and data flow of intemq-cb-mailgen can best be learned from reading:

@bernhardreiter
Copy link
Contributor Author

bernhardreiter commented Feb 27, 2018

Technical ideas

Level 1: manual configuration by administrators

  • Test and fix ability of webinput-csv to run on intelmy-cb-mailgen installations (Version of intelmq. Bring in Flask. Integrate into webserver) may include packaging
  • Pointing towards the documentation of writing rule scripts, mailgen template and mailgen scripts.
  • Testing for results have to be done on a staging system.

Disadvantages: Needs an admin trained for the task. Does not hold records of what has been done (would need to be done externally to the system).

Level 2: usable by abuse-operators

  • Create an additional table in the eventdb, working title inserts at to be able to hold texts for a notification batch.
  • Extend webinput-cvs to be able to write to inserts and to add a special feedname so that
    mailgen can notice which text to use.
  • Extend mailgen to access inserts and make the specific entry available to the scripts.
  • Extend Fody to show details about the past inserts so it is on record.
  • (Will still be tested on a stating system).

Level 3: additional testing mode

This is level 2 extended to have a testing mode within the system.

@bernhardreiter
Copy link
Contributor Author

Starting with level 1 (but on an intelmq-cb-mailgen setup on an old Ubuntu 16.04 LTS).

Other ideas include to partially rewrite, e.g. the backend or the frontend.

@ghost
Copy link

ghost commented Jan 18, 2021

Starting with level 1 (but on an intelmq-cb-mailgen setup on an old Ubuntu 16.04 LTS).

That's waste of resources. Ubuntu 16.04 has Python 3.5 which won't be supported by IntelMQ's next feature release 2.3.0

@bernhardreiter
Copy link
Contributor Author

bernhardreiter commented Jan 19, 2021

@wagner-certat I agree that it is suboptimal, thus I've suggested to change that requirement.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant