On Wed, 2022-12-28 at 15:38 +0200, Henrik K wrote: > > Disabling default plugins solves nothing, just creates a worse experience > for user. Educating and guiding users to use DNS properly does not require > this.
Gentoo builds everything from source and allows the user to enable/disable some options for each package, called USE flags. In the context of a C program, you might have USE=spf which would translate to an additional dependency on libspf2 and passing ./configure --enable-spf at build time to enable that feature. These map less well to scripting languages where features are often enabled at runtime based on the existence of some optional package. In 2005, we had a flag for USE=spf in spamassassin that was supposed to control whether or not spamassassin used SPF. Without disabling the plugin, how would that work? If the user happens to install Mail::SPF as a dependency of something else and if the plugin is *not* disabled, spamassassin will (surprise!) start using SPF against the user's wishes. There's no reason for it today because there's no USE=spf flag for spamassassin, and it wasn't implemented very well back in 2005 (only certain plugins should have been disabled, and only conditionally). But the idea isn't as crazy as it first sounds.
