[Rspamd-Users] Rspamd 3.11.0, what is new?

[Vsevolod Stakhov]

On 16/12/2024 18:46, Peter Reinhold wrote:
> I was happy to see a new release of rspamd pop up in my RSS feed, but 
> after reading the announcement, https://rspamd.com/announce/2024/12/16/ 
> rspamd-3.11.0.html, I am a bit hesitant before upgrading.
> 
> Is there a more detailed changelog available anywhere?

git log -r 3.10.2..HEAD 
--grep="Fix\|CritFix\|Feature\|Rework\|Project\|Rules\|Conf"

I'm sorry, but expanding each commit is a bit boring task, so I rarely 
spend a lot of time on it.

> 
> For instance, mentioned directly are "Extended configuration options for 
> greater flexibility", but there is no list or hint of what those options 
> are or where to find them?

This is fixed.

> 
> A _lua.local.d_ folder is mentioned, alongside a mention the 
> documentation has been improved and examples added, but searching for 
> lua.local.d on the documentation site yields 0 hits.

https://github.com/rspamd/rspamd/blob/master/conf/lua.local.d/module.lua.example

> The worst offenders are in the upgrade notes, where its mentioned that 
> the new header processing should be tested, but, what has changed, what 
> should we look out for?

It is fixed, AI has made some hallucinations about that it seems.

> The same goes for the ratelimit changes, I know that there has been some 
> debate about those multiple times here on the list, but I can't find out 
> what has changed and how or if I should change my existing ratelimit setup.

No, same here - there is just a helper tool that might (or might not) be 
useful to check limits.

> Don't get me wrong, I am a long-time user of rspamd and have had almost 
> nothing but a great experience working with it, but when you add new 
> features you urge us to try out, some links or hints to what we should 
> look at would be greatly appreciated, I don't fiddle with the configs 
> very often as my setup "Just Works", and i'm not all that interested in 
> having to re-read the entire docs and compare with my in-production one 
> to find placed where I could potentially optimize my setup :)

After another look on the upgrade notes, I think they are fine in terms 
of the changes description. This release is mostly bug fixes release, 
but some of those fixes were quite large to merge them into previous 
minor release. There's also a total rewrite of the elasticsearch plugin. 
Therefore, I have decided to change the feature version.

> Even just linking to merges/commits for the features would be helpful.
>