On July 31, 1998 at 11:19, Achim Bohnet wrote:
What I want to do:
o rebuild all the archives so they get a consistent layout.
o remove spam
o my procmail recipes where to lax at times so I have to filter
out other some messages
o Some list are so small that an archive once per month is an
overkill so I would like to group them to bigger chunk.
Everything besides the first item changes the number of a message
and therefore the URL.
Which will not hurt anything except for the condition Geoff Wing
mentioned: People reference archive messages by absolute URL.
For this case, since messages already exist that do this, there
is nothing (within reason) that can be done.
MHonArc will do the right thing if a message is referenced by
message-id (and the message-id is in the current archive).
But wait I just realized that I jumpedto fast into an implementation
issue. What I would really like to have is
o ARI (Archive Msg Identifier)
o extention to mhonarc to use the $w3archive/$ARI instead of
o ARI -> filename translation table
I have played with an idea similiar to this. What I was thinking
was using the DB_File module to map message-ids to pathnames. Hence,
given a message-id, the pathname of the HTML message file can be
retrieved. The DB_File can be global across archives. I am
unsure of the cross-platform support issues and performance.
Also need to consider how to handle cases if an archives location
This feature will fit into the v2 code-base.