* Gilles Chehade <[email protected]> le [02-09-2016 14:57:46 +0200]: > On Fri, Sep 02, 2016 at 01:57:18PM +0200, Thuban wrote: > > Hello, > > I just upgraded openbsd 5.9 to 6.0. As announced on the upgrade page, > > some parts of opensmtpd-extras disappeared. Okay. > > > > I'm actually very surprised to see that simple filters like regexp, or > > the very useful spamassassin are gone. > > > > This experimental API has been enabled for developers to help us find if > there are shortcomings, design errors and bugs in the filter layer so we > can make this whole mechanism stable both in terms of the interface, and > the reliability of the daemon. > > Instead, filters were written to please users primarily. > > And since there were written to please the users and not to help us make > the API better several filters actually worked-around limitations rather > than helping fix them. Some went as far as tweaking fields of structures > that were meant to be opaque to filters. > > Most filters were broken in one or many ways making the daemon unstable, > yet people kept telling other people to run this or that filter. Then we > receive bug reports and have to investigate if they are because of layer > or because of half-baked filter. > > The very useful spamassassin filter was also very broken, several issues > were fixed in the last few months that were specifically filter related, > and there are still a few issues with it. The API is not ready for users > and we can't cope with troubleshooting issues that aren't related to the > API itself but with individual filters. > > To make it crystal clear: > > ANY setup running with filters is broken. > > Some setups will crash, others will leak descriptors, others will block, > and some will simply work fine as long as you don't enter an error path. > > Some filters may work, I don't know, all the ones I read were bad. > > > > Anyway, is there any plan to include them in opensmtpd-extras in the > > future? > > > > Yes, when we have solved some of the shortcomings with the API and we're > happy enough with it that we actually start writing filters. > > Today, we need to be able to learn what's wrong with the API and make as > many changes as we want without people yelling that their setup is kaput > which is not what's been happening lately. > > > > How can I replace these filters? > > > > spamassassin can be used with spampd as a proxy, I don't know if there's > a similar tool for regex. > >
Thank you for these very interesting explanations. I'll find my way with spampd. Thank you again an dkeep on the good work. Regards, thuban
signature.asc
Description: PGP signature
