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

[Barry A. Warsaw]

>>>>> "RH" == Richie Hindle <richie at entrian.com> writes:

    RH> [Richie]
    >> It would be nice if you could leverage the existing web
    >> interface - I'm working towards making it less monolithic right
    >> now, which might help.

    RH> [Barry]
    >> For configuring, yes, we'll use the Privacy -> Spam Filters
    >> page.  The trick is the admindb page, which already sucks.  But
    >> I don't intend to clean it up for the prototype.

    RH> Are we talking at cross purposes?  I meant leverage the
    RH> existing *Spambayes* web interface that's (currently) a part
    RH> of pop3proxy.py.  But it sounds like you're way ahead of me
    RH> anyway.

Oops, we're talking about different things.  I'm talking about the
hooks in Mailman to enable spambayes scoring, and what to do with
messages based on those scores.  Configuring spambayes itself is
another kettle of fish, one that I'm not planning on addressing for my
prototype.

-Barry