nnmaildir - The ATV of mail backends

nnmaildir - The ATV of mail backends

[Harry Putnam]

 He he... That dumb subject line was just to get Paul J's attention.

Honestly though, nnmaildir does have certain characteristics that make
it a tough customer.  Something like an All Terrain Vehicle.  It has the
earmarks of being more robust and harder to corrupt or screw up than
some of the others while allowing great flexibility.

Just getting back into using the gnus-agent after a bout with several
attempts to turn news to mail with various schemes.  I think the
gnus-agent is more reliable for acquiring the news to begin with than
piping a newsfeed thru other processes.

The problem is that agentized messages lack some of the functions that
mail messages enjoy, like editing in place, or deleting on demand.  Or
the multitude of sophisticated expiry/scoring  stuff that mail can be
subjected to. 

In short, acting as if you really do own them. (on disk) The agent is
still suffering under the illusion that it is really dealing with nntp
messages on a foreign host.

OK, now to cut to the chase here:

Is it concievable that the messages the agent downloads could be plopped
into nnmaildir groups.  Or that gnus-agent could become nnagent mail
backend that is really an nnmaildir setup.

Could the process inside nnmaildir that moves messages from `new' to
`cur' be made to grab gnus-agent downloads in progress being dumped into
`new' and process them to `cur' as it does other messages?

They would have unique numbers already from the server, which seems to
be the only real requirement for nnmaildir to be able to handle stuff it
finds in new.

I'm talking about this being built into the agent, not some scheme
imposed after the fact.