|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: ??: vacation solution
From: Bennett Todd (bet
rahul.net)Date: Thu Jun 29 2000 - 11:35:55 CDT
- Next message: Ronny Haryanto: "Re: Relay problem"
- Previous message: Mark Hoffman: "RE: Performance ...."
- In reply to: Peng Gao: "??: vacation solution"
- Reply: Bennett Todd: "Re: ??: vacation solution"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2000-06-29-07:15:16 Peng Gao:
> but my site is very large, so user account are
> in ldap server. there is no ~/.forward
Well, in that case, you're going to need to do something different
from the normal vacation program.
A vacation program needs to access two pieces of information,
per-user: it needs a database for keeping track of the addresses it
has already blatted, and it needs a message body to send back.
If your LDAP delivery setup is delivering all messages for all users
into a system of folders that are all owned by one common mail
system owner --- all deliveries with the same uid, in other words
--- then this should be quite easy to set up. Arrange say a web
interface giving people a toggle to enable or disable vacation
processing, a message fill-in button for setting their vacation
message, and a separate submit button that they can hit to clear the
database so people can get new vacations. Or just some logic to
clear the database if they enable vacation processing and the
database is more than some configurable age, say 3 months.
Then just place one copy of the vacation procmailrc script where it
can be executed by the LDAP-delivery userid, give it a working
directory it can write to, and place the messages and databases in
per-user subdirectories of that working directory. Modify the
procmailrc script to use the message text and vacation database
found in that directory, and finally have the CGI either add and
remove aliases to enable or disable the vacation processing, like
e.g.
user: user, "|/usr/bin/procmail /path/to/vacation/procmailrc"
or else achieve the same effect by having the CGI modify the LDAP
database so its delivery address for the user adds or removes the
extra recipient.
Alternatively you could route _all_ deliveries through procmail, and
rig the vacation logic to only operate if a flag file (e.g. the
message text file) exists for that user.
-Bennett
- application/pgp-signature attachment: stored
- Next message: Ronny Haryanto: "Re: Relay problem"
- Previous message: Mark Hoffman: "RE: Performance ...."
- In reply to: Peng Gao: "??: vacation solution"
- Reply: Bennett Todd: "Re: ??: vacation solution"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]