Re: message registry for Gnus

[Ted Zlatanov <tzz@lifelogs.com>]

On Tue, 25 Feb 2003, kai.grossjohann@uni-duisburg.de wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
> 
>> OK, so where can I insert a hook for the registry, if all I care
>> for is the first time a message is seen in a group, with the
>> article's header data available?  I would prefer to avoid the
>> braindead solution of scanning all articles in a newsgroup and
>> noticing the new ones every time - although that might not be too
>> hard if I look at the "unseen" articles.
> 
> Do you want to see the article again after it has moved to another
> group?  It might not be unseen anymore at that point.

I can track the article at that point with the move hook - it's only
the first time I see it that I need to initialize its registry entry.

In other words, an article's life is like this:

spool -> group1 -> move -> group2 -> delete
          \-> copy -> group3 -> delete

I can track everything except the "spool -> group1" part.

The main reason why I want to register the article when it's in the
Gnus newsgroup data, rather than when it's spooled by nnmail, is that
at spool time the data in the article may be malformed.  For instance,
the message ID (which is crucial for tracking the message) may be
invalid when nnmail spools the article (cf. discussion on article
numbers yesterday on this list).  There's a better chance that I'll
get a "good" message ID if I grab it from the Gnus newsgroup data,
rather than parsing it out of the spooled message.

As far as the user is concerned, registering the article at spool time
vs. registering it at the time of summary entry is the same thing.  I
think.

Ted