>>>>> "VH" == Vern Hart <[EMAIL PROTECTED]> writes:
VH> =vern:vern:2244:18:/home/vern:::
VH> +vern-:vern:2244:18:/home/vern:s/::
VH> This puts .qmail and .qmail-default in his home directory but
VH> everything else is in .qmails/. This changes ~/.qmail-foo to
VH> ~/.qmails/foo and really cleans up his home.
that is exactly what i wanted. it took a few tries to clean up all my
bugs (like the file is .qmails/foo and not .qmails/.qmail-foo).
VH> As far as the alias user goes, you could change the name in the
VH> source code or give the alias user the same uid as yourself in
VH> /etc/passwd. Or, better yet, su to alias to create lists and such.
VH> You don't have to be root, just be alias. Or, your could set up
VH> a virtualdomain for the main domain on the box and have it send the
VH> mail to your .qmail files, etc. There's lots of ways to solve that
VH> problem.
well, my current setup has ~alias symlinked to ~/Mail/alias. the dir is
setgid qmail andthe files are readable by the group.
all i have in there is .qmail-default which is set to:
&[EMAIL PROTECTED]
and an list mmg has .qmail-mmg set to:
&[EMAIL PROTECTED]
i have a shell func which makes new lists:
ezmake ()
{
ezmlm-make ~/Mail/lists/$1 ~/Mail/qmails/$1 $1 sysarch.com;
echo "&uri-$[EMAIL PROTECTED]" >~/Mail/alias/.qmail-$1
}
so for it looks good. both internal and external (via fetchmail) mail
works with the lists.
thanx,
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
