redis history configuration: what to store and how long

[Felix Schwarz]

Hey,

recently I enabled redis globally and I noticed rspamd will store much more
detailed data about processed messages then. Specifically this includes email
addresses and the message subject.

However I think we must not store these details due to legal requirements
(Germany/EU). However I like to use redis for data storage in general.

Now my questions:
1. Is it possible to configure what is stored in redis?

2. Can we configure how long redis stores historic items? In the configuration
I noticed the "nrows" parameter but I'm not sure what it is used for.
Maximum number of items in history? Is there a time-based option (e.g.
store historic items for 3 days)?

Thank you,
Felix

[Andrew Lewis]

Hi,

> 1. Is it possible to configure what is stored in redis?

Generally so- ie. you can configure which modules use redis (either by
supplying redis config for each module or disabling modules in the
global redis configuration):
https://rspamd.com/doc/configuration/redis.html

WebUI history is *not* configurable. However you could fairly easily
patch history_redis.lua to see that certain items are censored.

> 2. Can we configure how long redis stores historic items? In the
> configuration
> I noticed the "nrows" parameter but I'm not sure what it is used for.
> Maximum number of items in history?

Yes.

> Is there a time-based option (e.g. store historic items for 3 days)?

No.

Best,
-AL.

[Felix Schwarz]

thanks for your answers.

Am 04.12.2017 um 13:22 schrieb Andrew Lewis:
>> 1. Is it possible to configure what is stored in redis?
>
> Generally so- ie. you can configure which modules use redis (either by
> supplying redis config for each module or disabling modules in the global
> redis configuration): https://rspamd.com/doc/configuration/redis.html
>
> WebUI history is *not* configurable. However you could fairly easily patch
> history_redis.lua to see that certain items are censored.

Ok, that's what I figured from reading the lua code. The reason I was asking
this was the history_redis documentation:

> Redis history module
>
> This module is intended to store history in Redis list with more
> fine-grained control over fields, (...)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
source: https://rspamd.com/doc/modules/history_redis.html

I'd like to patch rspamd as little as possible right now to simplify future
upgrades. We disabled history_redis for now and will revisit the situation
later (carrying a custom patch in our RPMs isn't that much more effort but
requires some testing).

thanks again,
Felix