OK, answer my own question #1. Maildir is exposed as default and home seems
to be initialized to the value in the db. So something like
`if [ ! -d "$HOME/$DEFAULT" ]; then
if [ ${DEFAULT:0:1} == "/" ]; then
maildirmake "$DEFAULT";
else
maildirmake "$HOME/$DEFAULT";
fi
fi
if [ -n $MAILDIRQUOTA ]; then
if [ ${DEFAULT:0:1} == "/" ]; then
maildirmake "$DEFAULT" -q $MAILDIRQUOTA;
else
maildirmake "$HOME/$DEFAULT" -q $MAIDIRQUOTA;
fi
fi`
I think this should create the maildir if it is missing and set the quota if
specified using just the stock maildrop. I will test, but if this is true,
IMHO it should be made a part of the docs/FAQ or something...
Thanks,
Rob
-----Original Message-----
From: cour...@lists.sourceforge.net
[mailto:cour...@lists.sourceforge.net]On Behalf Of Rob
Hutton
Sent: Tuesday, August 26, 2003 12:09 PM
To: cour...@lists.sourceforge.net
Subject: [maildropl] Thoughts about preferences and auto creating
maildirs
After reading some of the comments about automaticly creating
maildirs using
mail filtering, it seems to me that this would be the best, most flexible
way to go. In relation to this, I have some questions/comments:
1) Does the $HOME variable reflect the home retreived from the
database, or
is it stricktly the user this maildrop is excecuted as? Is the
maildir path
exposed as a variable like $MAILDIRPATH or something?
2) This would allow you to leverage the per user preferences in such a way
as
if (/^X-Spam-Flag: YES/ && getpref("USESPAMFOLDER") == "YES") {
`if [ ! -d "$" ]; then \
maildirmake "$HOME/$MAILDIRPATH/.spam"; \
fi`
to "$HOME/$MAILDIRPATH/.spam"
}
Thoughts, comments, questions...
2 messages in net.sourceforge.lists.courier-maildropRE: [maildropl] Thoughts about prefer...
