Jay Lee wrote:
On Sun, October 29, 2006 1:16 pm, Sam Varshavchik wrote:
I assume this has to be done for each user on my system right? All of
my users use the same uid/gid. What does placing in tmp do? Is that
step necessary?
Yes. Read the maildir documentation on the web for the gory details.
Finally, could maildrop be used to place the motd file on a user's
account, say on the next mail delivery?
Well, it's possible, but tricky. You'll have to write some tricky stuff
to make sure that the message only gets placed once, into the mailbox.
Not to mention that if the user doesn't receive any email that day,
maildrop wouldn't be called for them and they wouldn't get the MOTD. Why
not use a mailing list? Setup might be a little bit more involved but it
will make things easier when your CEO wants his hotmail account CCed on
the MOTD :-)
I can't understand what all the fuss is all about. This site uses LDAP
as the maildrop backend. A cron script is run every hour to see whether
any LDAP user doesn't have a $HOME dir. Whenever a new virtual
LDAP-based user (up to hundreds at a time) is made, and the user
doesn't, have a $HOME dir, vmail makes it, then it maildirmakes the
Maildir. Then it sends a welcome message to the new user. Using Postfix
2.3.3 and maildrop 2.0.2, Postfix transport uses maildrop.
maildroprc has routines for making subdirectories (e.g. for dspam
quarantine, dspam misjudged) and seds these to courierimapsubscribed so
that the idiots I have as users don't have to know their MUA (Evolution,
Squirrelmail 1.5.1 CVS, Thunderbird, Outlook Express etc.) to see which
IMAP folders they have to subscribe to.
Therefore there's no need for any script to zap stuff to Maildirs or do
anything else in that direction. Everything "just works".
God bless, in chosen order, LDAP (in particular the OpenLDAP foundation
for a multiple delta syncrepl 2.3.28 DSA), Sam Varshavchik and Wietse
Venema and the Red Hat rpm doers and the Perl and shell script inventors.
--Tonni