
Hi Matt - ( from Kim )

I dunno if this is related to it happening just at the end-of-February,
but it sure seems like that is probably the cause ...

The NEWGROUPS nntp cmd has been working just fine, since the end-of-
year rollover problems that I previously mentioned to you.

Until today.

Seems that all-of-a-sudden, newgroups are showing up, but not getting
reported back to the newsreader in response to a NEWGROUPS cmd.

I'll try manually setting the "last-new-group-added" history timestamp



--

    remove message-id from precommit cache on article rejection for certain
    (filtering) raesons.

---

    Add byte/article count logging

    Update overview range in dactive.kp when it is determined that the spool 
    does not contain the lowest numbered articles in a group range.

    Add support for error return if POST server(s) not active, or queue the 
    POST into the posting queue.

    Return a 5xx code and disconnect if spools are not online and someone
    tries to retrieve an article.  Have a special 'R' flag in dserver.hosts
    to mark required spoolers.

    Add support for xpath and add support to return proper Xref: header
    when an article is retrieved by Message-ID, even though this is somewhat
    expensive to do.

    Sanity synchro on slave mode for NE.

---

    fix USE_SPAM_SHM requirement in lib/seq.c

    minimum, maximum shared memory segment sizes, warn specifically in
    syslog on failure.

    feedlist command to dump current group filters

    compression patch

    resetarts

