It sounds like the best "tool" for the general case would be something
that maintains an index on delivery, similar to what a bayesian spam filter
would do.
The qmail list might be a better place to ask/look for pre-built stuff.
Take a look at exmlm(-idx) to see how messages are delivered when archiving
is turned on. There might be some ideas/code to borrow.
If I were deriving a solution, the basic problem is to maintain an index.
If write a replacement delivery agent that qmail-local could spawn (via
.qmail file). You could just store in a maildir as normal or something
different structure if you don't need "normal" programs to access the
messages. Once successfully delivered, the delivery agent can update an
index/database. Or in an extreme case, store the messages in an indexed
database.
Received on Mon Sep 10 13:52:27 2007
This archive was generated by hypermail 2.1.8 : Mon Sep 10 2007 - 14:11:01 CST