[prev] [thread] [next] [lurker] [Date index for 2003/07/31]
On Wed, 30 Jul 2003, Richard Clamp wrote: > > 4) creating a list seems to work, but the if you really insist on doing > > this in two steps > > you can at least tell the user to write > > nacho show-alias mambo will show you what to include in /etc/aliases > > > > > > [root@pc10 siesta]# /usr/local/perl580/bin/nacho create-list mambo > > mambo-admin@xxxx.xxx.xx mambo@xxxx.xxx.xx mambo-bounce@xxxx.xxx.xx > > /usr/local/siesta/siesta.conf: No such file or directory > > Created the new list 'mambo' <mambo@xxxx.xxx.xx> > > nacho show-alias will show you what to include in /etc/aliases > > I don't follow, are you suggesting just wedging some more spaces in > there? That's simple enough. > > The more useful fix is to undo the quick pre-release hack that was > #1256 and allow nacho to take a config file on its command-line. That > will allow t/30nacho.t pass on an uninstalled copy. If I get a tuit > I'll do this tomorrow. Probably adding more spaces will help as I did not notice that line telling about show-alias until you mentioned it in this e-mail :-) IMHO the user should supply only the name of the list and maybe the real e-mail of the administrator. All the rest should be optional and either configurable in a file or passable (?) via the command line as real --gnu like options. nacho create-list mambo gabor@xxxx.xxx.xx should be enough but could also give: nacho create-list mambo gabor@xxxx.xxx.xx --subscribe \ mambo-hidden-subscribe@xxxx.xxx.xx if one wants to avoid people subscribing to mambo. GaborThere's stuff above here
Generated at 13:56 on 01 Jul 2004 by mariachi 0.52