2 quick feature requests, or can someone suggest better ways to do this in maildrop.

1) I (for example) subscribe to loads of mailing lists and so would like to have a generic rule which reads the Mailing list header and dumps stuff in a subfolder with the same name (maildir). However, maildrop doesn't seem to autocreate folders when using the "to folder/" syntax and so we end up with a bunch of messy and repeated code to check for existence of folder, create of folder, etc.

In a complicated script with a whole bunch of subfolders which is supposed to be rolled out to more than one user this gets really messy real quick. It would be nice if maildrop could try to deliver and create missing subfolders (even if this was a compile time feature only).

Is there a "subroutine" kind of syntax I could use to at least not duplicate this bunch of code each time? (I can sort of see a way with a global var and an include script).

2) My script is spending a whole bunch of time (like most of it) dropping into a subshell to do tests to see if folders exist. Would it be worth extending the syntax for maildrop to have an inprocess test for folder existence?

Thanks

Ed W