[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

spam2.el (was: How to unregister message as spam/ham?)

From: Ted Zlatanov
Subject: spam2.el (was: How to unregister message as spam/ham?)
Date: Thu, 10 Sep 2009 09:31:31 -0500
User-agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1.50 (gnu/linux)

On Wed, 09 Sep 2009 23:24:04 +0200 (Adam Sjøgren) wrote: 

AS> On Wed, 09 Sep 2009 16:15:32 -0500, Ted wrote:
>> I think your solution is fine.  It's been a while since I looked at the
>> code, but I probably made a mistake with the duplicate elimination.

AS> Great! Or, well, you understand what I mean, I trust.

AS> (The patch does work for me, though - so in the specific case is isn't
AS> necessarily defective as such.)

>> I'm OK with you comitting it.  I personally use a server-based solution
>> so I haven't needed this functionality in years.

AS> I haven't got a commit bit, so if someone who has would like to, please
AS> feel free. (I have signed papers.)

Can you prepare a full patch, with a ChangeLog entry?

>> I think spam.el has been around long enough that we should consider
>> redesigning it with what we've learned from the users' experience and
>> feedback.  For instance, setting it up is much too complicated for 99%
>> of the users, while mentats like it just fine.

AS> I don't know what mentats are, but I agree. I wrote down a recipe way
AS> back when, and have used that since.

Mentats are in the Dune books by Frank Herbert.  Basically human

Anyone using spam.el:

What parts of spam.el do you like?  How do you use it?

What parts are too complicated?

What does it not do today but should?

I'll start:

- I like the automatic message moving (ham out of spam groups and spam
  out of non-spam groups).  I use that in conjunction with server-based
  CRM114 filtering completely outside Gnus.

- the backend setup in the spam.el code is complicated.  The
  server/topic spam-related parameters are too numerous and probably
  should be outside it.

- first-time setup is unpleasantly complex

- today it does not interact with GMail's built-in spam folders.
  There's been recipes for that, but it probably should just work with a
  simple setup statement (spam-backend-gmail?).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]