[email protected] wrote: |Steffen "Daode" Nurpmeso <[email protected]> wrote: |> hmmmm, well i haven't looked into this at all sofar, nor used it! |> I've placed some printf(3)s in the code to see if i can help you |> with a short hack, but it doesn't look promising -- in fact |> i began to wonder a bit how this could end up as a good database |> in the end (*at all*, that is)... | |I have been using the junk filter with Heirloom mailx some time |ago (on a 32bit system) and it worked quite well then. When I switched |to a 64bit machine, it stopped working properly for some unknown |reason. I am not a programmer myself so I have not investigated |this any further but I presumed that the data structure of the |junk "database" just has not been built with 64bit systems in |mind. After Gunnar Ritter seemed to have disappeared, I just |put up with it. When I read about your fork, I just thought I |would mention this to you...
Yes, and that was absolutely the right thing to do -- please continue to report anything that feels like a misbehaviour. |> To be honest, i remember a time of "Bayesian filtering hype" in |> the german computer magazine c't around the years 2000/2001 (or |> so), but never used such a feature on my own; i strongly believe |> that this should be done on the server side, using administrated, |> up-to-date white/grey/blacklisting, and up-to-date databases like |> SpamAssassin, that get updated by a large community of people; |> especially with IMAP, where it's easy to get just a header listing |> of some JUNK folder. | |My email does not get filtered on the server. The small amount of spam |that I get used to be filtered well enough using the junk filter |mechanismn built into nail. But I guess you are right that it is |not a solution for more advanced setups. It is just a feature that |worked well enough for my personal needs. [.] |No worries - this is not a high priority for me. When i come back to S-nail for 14.3 i'll look into this and see what i can do to get it running -- if there are real use cases for this particular feature, and it's working well, then i would rather like to keep it, at least as a optional compile-time choice. [.] |> But now that i think about it i see that it would be nice to have |> an integrated automatic classification hook or so, that could be |> triggered when messages are accessed (have to think here), and |> that would pipe the *raw* message through an external processor |> *before* we look at it, i.e., so that a local |> script/SpamAssassin/xy could modify it on the fly. If that were |> the case, you could filter on some very specific header line that |> could be injected by those filters, and as a bonus that filter |> could manage/update a local/sitewide/xy database. |> This may be an interesting addition. | |That sounds somewhat similar to how the current junk filtering |mechanism is meant to work. :) I now really think that the possibility to have an external filter that can hook the download should possibly made it into 14.3 already (if it's not too problematic in the current state of the codebase, i'll have to look). |Thanks for taking the time to look into this. I really do |appreciate that s-nail is actively being progressed. The Heirloom |project seems to be mostly inactive now, which is a shame given |the nice projects hosted there. Apart from Heirloom mailx I use |Heirloom troff for nearly all my publishing needs. Yes, bit-unrotting would surely help; i do use Heirloom software, too, the SCCS actively, it's sh for testing; but the troff cannot handle my own letter macros (long names), though for manuals etc. i use the Heirloom nroff for compatibility testing, too. |Regards |Dirk Peters Sorry that i can't help that soon with that particular problem, --steffen ------------------------------------------------------------------------------ Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 _______________________________________________ nail-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nail-devel
