Now that we know the what there is to configure let’s look at the how.
Let’s have a look at rspamd’s default scores. As mentioned, this is kind of a moving target, the scores in the default configuration can in theory change anytime unless you disable rspamd_update, so you should verify a particular score you want to override in your installation.
Updated August, 24th, 2018 We already learned that the choice of modules basically determines which tests rspamd executes in analyzing a message. But what are the modules we can choose from? The official documentation has an alphabetical list but let’s instead approach them differently here.
rspamd is a mighty spam filtering solution but it can be hard to get a grip on its configuration. For this reason I’m starting a small blog posts series to write down a few things I have learned, current for rspamd version 1.7.x.
On my laptop I use a dual-boot setup with a NTFS partition shared between Windows and Linux, containing eg. music. Because the Windows version installed is Windows 10, it could sometimes happen that, in spite of having turned off hybrid shutdown, ntfs-3g would refuse to mount the shared data partition because it was in an… Continue reading Let systemd automount NTFS partitions to ensure successful booting
On my Dell Latitude E7450 notebook I regularly update to current versions of the Linux kernel. Along with such a Kernel update my notebook’s SD card reader could no longer be initialized properly:
It is August 2015. Unfortunately it is still not possible to manually specify the MTU to be used on non-Ethernet NetworkManager connections (eg. VPN connections but also PPP).
Quite simple actually: # sudo zypper ar -f http://download.opensuse.org/repositories/X11:/xfce/openSUSE_13.2/ XFCE_13.2 # sudo zypper dup –from XFCE_13.2
libvirt supports the concept of so-called channels that represent private communication channels between a libvirt guest and its host.
Recently I’ve been working a lot with the SilverStripe CMS/framework written in PHP (as one could undoubtedly deduce from my earlier post). The context involved porting a custom application from SilverStripe 2.4 to 3.1. Naturally this also involved dealing with the formerly used DataObjectManager module and 3.x’s new ORM and GridField components.