Thanks Alvin,
The reason I listed the smrsh in the assumptions section is because of
the differences related to OS and distribution, and since it is already
mentioned in the FAQ, didn't feel it was any more important to stress
for archiving or digesting than any other "wrapper" related tool. I
will probably refer to the FAQ, or the specific locations you mentioned
in the next revision.
Virtual domains are a completely different recipe that I have submitted
to this list back in June this year. I touched it up slightly and
reposted it again this evening. (Sample aliases and virtusertable
entries included)
Dan Liston
Alvin Oga wrote:
>
> hi ya daniel
>
> very nice...
>
> a few comments....
> - /etc/smrsh is a different path on different distro
> ( /usr/adm/sm.bin , /var/adm/sm.bin ...
>
> - an issue since lots of people having problems with "wrapper"
> errors
>
> the mj (config-test) script can check to see that wrapper is linked
> at the right place... ( minor patches ?? )
>
> how about adding a virtual domain section for its syntax
> - in one /etc/aliases file.. the examples could be very messy
> - in multiple alias.Vdomain1 and alias.Vdomain2, and alias.Vdomin3 is nicer
> ( but trickier to implement with sendmail
>
> thanx
> alvin
> http://www.Linux-Consulting.com/Majordomo
> http://www.Linux-Consulting.com/FAQ_Virtual
> - maybe its long past over for me to go clean up my virtual domain/mj section
>
> > Daniel Liston wrote:
> >
> > Disclaimer: I am not a professional writer or programmer. Please report any/all
> > discrepencies in this document to me via the majordomo-users or majordomo-docs
> > mailing lists at greatcircle.com.
> >
> > Majordomo list owners often have trouble setting up a digest version of their list.
> > I am writing this in hopes of clearing up some of this confusion. Successfully
> > archiving your lists could be a side effect of implementing the knowledge gained
> > from the examples included.
> >
> > Assumptions:
> > Majordomo version 1.94.5
> > Sendmail version 8.8 (or higher)
> > You have root permission to create users, modify the aliases file, and rebuild the aliases database.
> > You have created a majordomo user and majordomo group.
> > The majordomo $HOME directory is /usr/local/majordomo and is owned by user majordomo and group majordomo.
> > The smrsh directory (if used) is /etc/smrsh and holds a link owned by root to /usr/local/majordomo/wrapper.
> > There are no group or world "writable" directories in the path to /usr/local/majordomo, including / (root).
> > Sendmail "trusts" majordomo. (you have a Tmajordomo line in sendmail.cf).
> > Sendmail only recognizes one "/etc/aliases" file.
> > Sendmail uses the "always_add_domain" feature.
> > The majordomo config file is /etc/majordomo.cf
> > The majordomo.cf variables are defined statically. (no `/bin/dnsdomainname` in the $whereami variable).
> > You already have a working list that utilizes resend. (wrapper resend -l <listname> <listname>-outgoing).
> > Your aliases file contains "nobody: /dev/null".
> >
> > Preface:
> > The directories above may be different, but in that case, you will modify anything stated further to
> > match your installation. To set up a digest, you must also have a handle on archiving. Digest has
> > some dependencies, or I should say makes some assumptions. One is that you have an archive directory
> > configured to hold the digestified message before delivery, and another is that you will call your
> > delivery address <list>-digest-outgoing.
[snip]
> > PS. Please feel free to add comments/criticisms about this document. It is after all
> > my first revision at explaining the steps necessary to archive/digest a mailing list.
> > It is possible that I may have still omitted something useful.
> >
|
|
