I know how to hide outgoing aliases -- and digest doesn't use a
parameter file, so things are a little different (it would be nice if
it did ;). Using this wonderful web site
I read of someone else who had the same problem, and people's
suggestions. I don't have a owner-blah-outgoing (what would be the
point?) and I have ,nobody where it was suggested that I have it
. . . and still, when the digest is created, there's the outgoing
alias, plain as day. (I'm having the digest created automagically
based on length.) Here are my aliases (I don't really use -outgoing,
but I'd prefer not to post what I do use ;).
guru-request: "|/usr/local/majordomo-1.94.1/wrapper request-answer guru"
guru-archive: "|/usr/local/majordomo-1.94.1/wrapper archive2.pl -f /usr/local/majordomo-1.94.1/lists/archive/guru.archive/ -m -a"
guru: "|/usr/local/majordomo-1.94.1/wrapper resend @/usr/local/majordomo-1.94.1/lists/guru.parms"
guru-digest-request: "|/usr/local/majordomo-1.94.1/wrapper request-answer guru-digest"
guru-digestify: "|/usr/local/majordomo-1.94.1/wrapper digest -r -C -l guru-digest guru-digest-outgoing,nobody"
What am I missing here? Do I need ,nobody after the double-quotes on
the digestify line, like this:
guru-digestify: "|/usr/local/majordomo-1.94.1/wrapper digest -r -C -l guru-digest guru-digest-outgoing,nobody",nobody
Or is it not possible to hide this if you have them generated based on
length (i.e., using the above scheme, though it is the way that I
found documented and liked the most)?
TIA, and sorry if I missed something blindingly obvious.