[Spambayes] what else is needed for a first (source) release?

[Richie Hindle]

[Anthony]
> Ok, can people nominate things that they think would be good before a
> first release? I'd like to try and get one out before the spam
> conference (it's as good a date as any :) 

When is that date?  The Linux Journal articles on Spambayes are due out at
the beginning of February, so we should aim for whichever date is sooner.

I have two lists of things that I think need doing:

1. Things that my Linux Journal article implies will be ready by the time
   the article is published:

    o Integration with Mutt (and other clients) via a single-shot script
      (like a single-message version of Hammie, or new switches to Hammie
      itself) See http://www.linuxjournal.com/article.php?sid=6439  Does
      anyone have something like this already, or any requirements?  And I
      don't like to ask, but would anyone like to write this?  8-)  I was
      intending to do it myself (and still will if no-one else fancies the
      job) but I'm going to be rushed off my feet these next two weeks...

    o Web-based configuration, and new doco on setting up the POP3 proxy
      using it.  This is nearly there - I'm combining the pop3proxy.py web
      UI and Tim Stone's OptionConfig.py into one unified web interface.

    o Security for the web interface - done but not yet checked in.  All
      this can do at the moment is limit web connections to localhost, but
      at least it means you're not opening up your Spambayes system to all
      and sundry.


2. Things that have cropped up recently and need sorting out:

    o Silly memory usage by the POP3 proxy.  Done and awaiting checkin.

    o The Eudora problem.  This is nasty - I think we'll end up with a
      compromise here (as proposed by Jeremy) because I don't see a clean
      solution out there.  (See
      http://mail.python.org/pipermail/spambayes/2002-November/002054.html
      for an explanation of why combining the hostname and the username is
      not a perfect solution).

    o Integration of papaDoc's documentation into the website.

-- 
Richie Hindle
richie at entrian.com