Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: a short introduction to Gnus vs. Spam with spam.el
Date: Tue, 21 Jan 2003 11:43:37 -0500	[thread overview]
Message-ID: <4ny95e313a.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <d6mvj1qh.fsf@random.localnet.unwireduniverse.com> (Derrell.Lipman@UnwiredUniverse.com's message of "Fri, 17 Jan 2003 09:21:42 -0500")

On Fri, 17 Jan 2003, Derrell.Lipman@UnwiredUniverse.com wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
> 
>> At http://lifelogs.com/spam/ 

> Just a few comments:
> 
> - The diagram in the introduction shows Spam and Ham going into the
>   MTA, but the Concepts section defines Spam and Ham as distinct
>   from "undetermined messages" Shouldn't the diagram really show
>   just "Undetermined Messages" (possibly with Spam/Ham in
>   parenthesis or something)?

Messages are never "undetermined" except as far as Gnus is concerned,
that's what I was trying to show.  Mail is always either spam or ham
(but one man's spam is another's ham :)

> - In Spliting Incoming Mail, spam-use-ifile says that the user has a
>   choice of using ifile for all classification or using it only for
>   spam, but there's no indication (at least not in this section) of
>   how to specify that choice.

I would prefer to leave such details for the Gnus manual.  The
presentation is meant to be an introduction, so I'd like to keep it
brief and focused on explaining to new users why they want Gnus +
spam.el.

> - While reading this, I'm asking myself why I can't use multiple
>   spam splitters and processors.  Is there some reason not to use
>   bogofilter and blacklist, for example?  It seems from the early
>   text, that the user must choose one.  The later screen shots
>   indicate that multiple processors may be checked.

The answer is yes and no.  It wouldn't make sense to use ifile and
bogofilter together, for instance.  Also, ifile won't coexist well
with the other splitters if it is used to split into all folders, not
just spam/non-spam.  I didn't want to bring up those issues in the
presentation.

> - 'H' as a spam mark seems counter-intuitive when the opposite is
>   Ham.  (I realize that 'S' isn't available, but this is worth some
>   consideration.)

I know, I know.  Fortunately it's just a character, and can be
customized.  I tried hard to eliminate direct dependence on the 'H'
character in spam.el, but it could be a problem depending on how Gnus
stores old marks, and whether there's any other code that doesn't use
the spam-mark as a symbol but directly as a character value.  I would
assume that won't be a problem.

So, the question is: what should the new "spam" mark be?  "$" seems an
obvious choice; I personally don't like the way it looks in the
summary buffer with a monospaced font but that's hardly crucial.
Also, "$" is not as meaningful in countries that don't use dollars.  I
would love to use an extended Unicode character, but that will annoy
everyone.  So maybe "@" would be good?  What do you (the spam.el
current and potential users) think?

Ted



  parent reply	other threads:[~2003-01-21 16:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-17 11:44 Ted Zlatanov
2003-01-17 14:21 ` Derrell.Lipman
2003-01-17 22:56   ` Andreas Fuchs
2003-01-21  6:00     ` Lars Magne Ingebrigtsen
2003-01-21  9:45       ` Andreas Fuchs
2003-01-21 16:43   ` Ted Zlatanov [this message]
2003-01-21 16:46     ` Lars Magne Ingebrigtsen
2003-01-21 17:48       ` Ted Zlatanov
2003-01-21 19:26       ` Raja R Harinath
2003-01-22 12:36         ` Ted Zlatanov
2003-01-22 13:23           ` Please help me unsubscribe smarks
2003-01-22 18:45           ` a short introduction to Gnus vs. Spam with spam.el Danny Siu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ny95e313a.fsf@lockgroove.bwh.harvard.edu \
    --to=tzz@lifelogs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).