[Users] How to check if Bogofilter is still working?

[Dustin Miller]

On Fri, 31 May 2024 12:13:06 -0400
Gil Weber <gilweber at bellsouth.net> wrote:

> On Fri, 31 May 2024 22:00:21 +0600
> Dustin Miller <dustbiz at gmail.com> wrote:
> 
> > On Fri, 31 May 2024 10:50:47 -0400
> > Gil Weber <gilweber at bellsouth.net> wrote:
> >   
> > > On Thu, 30 May 2024 16:30:38 +0200
> > > Michael Schwendt <bugs.michael at gmx.net> wrote:
> > >     
> > > > On Thu, 30 May 2024 09:35:25 -0400, Gil Weber wrote:
> > > >       
> > > > > I do not see anywhere to mark as either "/Mark/Mark
> > > > > as spam" and "/Mark/Mark as ham".        
> > > > 
> > > > Either right-click on a message summary line in the folder view,
> > > > or use the "Message" menu where it's found near the bottom.
> > > 
> > > OK, so for thousands of messages I have been using the drop-down
> > > in the top bar and selecting either "learn as spam" or "learn as
> > > ham."
> > > 
> > > Has all of that been wasted effort trying to teach Bogofilter? Is
> > > it instead **required** to so as you suggest and select either
> > > "Mark as spam" or "Mark as ham?"
> > >     
> > DM: Hi, Gil. 🙂️ I don't use bogofilter or other spam filter with
> > Claws, but I'm assuming that these are just two different ways of
> > doing the same thing. It is pretty common with Claws and many other
> > pieces of software to have multiple ways of doing things. Different
> > users prefer doing it different ways, so when they give an answer to
> > a question like yours, they will normally describe the way they do
> > it, especially if that's the only one they use. I guess if you feel
> > you need certainty on this, then probably only the developers (or
> > other users who would know how to check the code or do the testing)
> > would be able to answer your specific question. If they do end up
> > being the same thing, then perhaps you could create an enhancement
> > request in the issue tracker to have text strings used be the same
> > for all instances of the same action, in case that would help to
> > avoid confusion for some people. Cheers, ---Dustin  
> 
> Thanks, Dustin! Appreciate your insight.
> 
DM: You're welcome, Gil. 🙂️ ---Dustin