On 10 Jun 98 at 13:17, Darren G. Pifer <pifer@algol.larc.nasa.gov>
wrote:
> Hello,
>
> I need a way to allow an owner of a list to update his/her
> list, rather than use the subscribe/unsubscribe mechanism to add/
> remove e-mail addresses. Basically, the user needs to transfer the
> file (list) with ftp to the list management machine. This works for
> our non-Majordomo aliases because the owner of the file is the list
> owner. However, in the case of the majordomo lists, the owner of the
> list is the Majordomo owner.
>
> As an alternative, is there a 'get' and corresponding 'put'
> command that can grab and install the list, similarly to the way the
> 'get config' command works?
>
> Any suggestions?
>
> Please email me directly because I am not a member of this
> list.
One way: set subscribe_policy and unsubscribe_policy to closed, then
just make sure the list file is readable by Majordomo (e.g. set the
file group to daemon, assuming you've got a standard setup). Transfer
the file by your favorite (and hopefully secure) route.
We do something similar for most of our local lists; the lists are
built from a central database, and stored in a mailing lists directory.
These are symlinked into the Majordomo lists directory, along with a
generic config file. The actual list files are globally readable, so
majordomo/sendmail handles 'em just fine, regardless of the file owner.
There is a small risk that the files will be used while they're being
modified, but so far we haven't had any problems. If that's an issue
for your situation, you might want to look at locking the file(s)
and/or pausing your MTA during an update.
Another possibility, if you want to have the list look like a 'normal'
MD list, is to have your list owner transfer the file into a holding
directory. Set up a cron job that compares the time stamp on the new
version and the old, and copies the new one if they differ and if the
new one hasn't been modified for, say, 5-10 minutes (so that you don't
copy the new one before the remote transfer finishes). Throw in a
chown and or a chmod command to enforce the correct permissions, and
you should be ready to go. Note that the above caveat about files
being modified while is use still applies.
HTH.
--------------------------------------------------------------------
Rick Owens <rowens@fvcc.cc.mt.us> | FVCC, Kalispell, MT, USA, Sol 3
#include <std-disclaim.h>
"Out of the mouth of babes comes .. *yuck*"
--------------------------------------------------------------------
References:
|
|
