On Sun, Sep 11, 2016 at 12:15:45PM +0000, Michal Krzysztofowicz wrote: > > > On 6 Sep 2016, at 14:10, Edgar Pettijohn <[email protected]> wrote: > > > > I'm thinking of starting a support group for others suffering from filter > > withdrawal. Upgraded to 6.0 over the weekend and went back to using spampd > > and sieve. Is there any other options besides amavis? I really miss > > filter-regex. Haven't had any luck finding a replacement just curious if > > anyone out there has any suggestions. > > Hi, > > I???d be up for it. Although I???m still running 5.9 on my mail server, I???m > thinking of upgrading. I knew that filters are experimental (and really to > test the API, not the filters themselves), however I???ve decided to use some > of them and would like to continue doing so. The dnsbl is the one I???d miss > the most. > > All other functionality in my config uses traditional approach, with relaying > over smtp to a daemon (spamd, clamav, dkim_proxy, etc) listening on lo > interface, and all seems to be working fine. > > Best Regards, > mike >
I'll stress it out one *last* time: - Running with filters will make your smtpd unstable and anyone taking a look at sources may figure ways to crash it. Many users who have hit a crash are now aware of how to crash other people's smtpd so every time you mention on the list that you are using them, you are exposing your server to any of these people messing with you. - You'll be on your own when it comes to troubleshooting issue, from now on I will simply ignore all mails related to filters until we are done with the work we want to achieve. I've wasted way too much time trying to understand why an instance fails, before realizing that the user is actually running with a broken filter and "forgot" to mention it. Because we provide an experimental feature that *seems* to work does not mean it really works. It does not work. It works only if the clients are doing exactly what they are supposed to do, and trust me many aren't. Just this morning, I received a mail about a crash that any client would be able to trigger as long as they can connect to a smtpd that's running a filter. I won't say how, but someone on this list knows now. You've been warned. As a side note: - we'll disable the "filter" keyword soon and we'll require patching the source to reenable it. - people insisting on using this experimental feature despite developers warning that it's not meant for users yet has sent us a big signal for other upcoming features that could have been released "early" for test purposes, we're going to be taking much more time from now on before a new feature is disclosed. -- Gilles Chehade https://www.poolp.org @poolpOrg -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
