I use a perl script to parse a file and create a maildrop filter file
(that is included by the "main" maildrop file). if interested, mail me.
having maildrop to create folders automatically will make you
vulnerable to a "random folders creation" attack. I mean, if you just
look up some header and create a folder automatically, then someone
can you send you messages with random values (or even real ones) so
you'll get a lot of folders for MLs you never subscribed to (and that
may not exist).
Also, for some MLs, I prefer to have a single folder for a group of
multiple MLs, while for others (each has too many messages), I prefer
to use a folder for each ML.
I agree. Actually in my case I validate the input.
However, I also have a number of virtual users with a complicated
maildrop script. Lets suppose tomorrow I decide to add Spam filtering
to our services, it them means having to write another script to go
through and the relevant subfolders to all the virtual accounts. Much
easier to be able to just make the script deliver to the new folder and
have it auto created...
Anyway, I have worked around it by creating a small script which uses a
global variable, validates it for nasty characters, then creates the
folder and adds it to the subscribed folder file. I just include it
where I need to create a new folder. Not that fast, but good enough.
Thanks
4 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Feature request
