I hate to sound like a broken record, but the owner-anything and anything-owner
aliases are still a potential mail loop.
Unless you have a real human user named majordomo at the
address in the alias, when majordomo has a problem and must contact a human to
maintain or correct a configuration, the message is going to be sent to another
automated majordomo address. THIS IS BAD! These aliases MUST point to a human
address or group of human addresses, not an automated program.
I hope you noticed the warning in my previous message that there are some
pre-requisite settings in your majordomo.cf and on the file system in order to
support the digest and archive aliases which you did not remove. Please walk
before you try to run. Get one thing working, then add another. Keep configs
simple until you are comfortable adding complexity.
Let me back up a step in regards to testing your list. If you send a message
to test (at) your (dot) domain, are you still the only one that receives the
message? What if you send that message to test-outgoing (at) your (dot) domain?
Does anyone else receive the message? I hate to ask the obvious, but how many
email addresses are listed in the file /var/lib/majordomo/lists/test? If they
are all local users, and all aliases to the same mailbox, your MTA may be the
one condensing the distribution down to one user. Is this file owned by the
majordomo account? The sendmail user? Root?
I never did see your original post containing what version of OS, MTA, and
majordomo you are running. What was the result `wrapper config-test` as the
root or majordomo user? What was the result as a non-root non-majordomo user?
What does /var/log/maillog or /var/lib/majordomo/Log show when you send a
message to your test list?
Dan Liston
Correction... here is the current /etc/aliases file in use:
majordomo: "|/usr/lib/majordomo/wrapper majordomo"
majordomo-owner: majordomo
BAD! ^^^^ if nothing else, say owner-majordomo
owner-majordomo: majordomo @ mils.example.com
BAD! ^^^^ if you don't want to ever see messages to the list or majordomo
owner address redirect the alias to nobody(at)your(dot)domain or /dev/null.
Otherwise, point them to YOUR real email address. I seriously doubt that
majordomo (at) anydomain (dot) com is a REAL or HUMAN address.
test: "|/usr/lib/majordomo/wrapper resend -l test test-outgoing,nobody"
test-outgoing: :include:/var/lib/majordomo/lists/test,test-digestify,test-archiver
Change this one to...
test-outgoing: :include:/var/lib/majordomo/lists/test,
test-digestify: "|/usr/lib/majordomo/wrapper digest -r -C -l test-digest
test-digest-outgoing,nobody"
Delete the previous two lines...
owner-test: majordomo @ mils.example.com
BAD! ^^^^ same as above. Point this to YOUR address or /dev/null.
test-owner: owner-test
test-digest: test
test-digest-outgoing: :include:/var/lib/majordomo/lists/test-digest,nobody
test-digest-owner: owner-test
Delete the previous three lines...
test-request: "|/usr/lib/majordomo/wrapper majordomo -l test"
test-digest-request: "|/usr/lib/majordomo/wrapper majordomo -l test-digest"
Delete the line/alias above ^^^
test-approval: owner-test
test-digest-approval: owner-test
Delete this last line/alias ^^^
-------------- Original message from Daniel Liston
The majordomo-owner:majordomo owner-test and test-owner aliases are
potential
> mail loops. In other words, why are you redirecting address that
should reach a human, to a
> program?
> And unless you are on a hosted domain, why are you using -C
name-of-config-file? Why do you have a test-list and a
test-outgoing? Use one or the other, but use
> one. The final argument of your pipe to wrapper is missing the
recipient address.
> This is how/where you make a call to test-list or test-outgoing.
See my aliases below;
> In your case, you should probably remove aliases and recipients
containing archive or
> digest. If you use these exactly as posted, you will need to
solve dependencies in your
> majordomo.cf
> and file system directory structure.
>
> majordomo: "|/usr/lib/majordomo/wrapper majordomo"
> majordomo-owner: owner-majordomo
> owner-majordomo: real-person (at) anydomain (dot) com,
> # The above address is obfuscated, please use a real address.
>
> test: "|/usr/lib/majordomo/wrapper resend -l test
test-outgoing,nobody"
> test-outgoing:
> :include:/var/lib/majordomo/lists/test,test-digestify,test-archiver
> test-archiver: "|/usr/lib/majordomo/wrapper archive2.pl -f
> /var/lib/majordomo/archive/test/test -a -M"
> test-digestify: "|/usr/lib/majordomo/wrapper digest -r -C -l
test-digest
> test-digest-outgoing,nobody"
> owner-test: some-person (at) anydomain (dot) net,
> # The above address is obfuscated, please use a real address.
> test-owner: owner-test
> test-digest: test
> test-digest-outgoing:
:include:/var/lib/majordomo/lists/test-digest,nobody
> test-digest-owner: owner-test
> test-request: "|/usr/lib/majordomo/wrapper majordomo -l test"
> test-digest-request: "|/usr/lib/majordomo/wrapper majordomo -l
test-digest"
> test-approval: owner-test
> test-digest-approval: owner-test
>
> Dan Liston
>
> The aliases presented are for a sendmail MTA. If you are using
qmail, postfix,
> exim, or some other
> MTA, please adjust accordingly.
>
> Never make untested changes to a production server. Do all
testing in a
> dedicated test environment.
>
> > I'm doing so testing of my configuration, and the message is
returned, but it
> only comes back to me and not the remainder of the subscribers on
the list. Is
> there something misconfigured in the config file?
> >
> >
> > majordomo: "|/usr/lib/majordomo/wrapper majordomo -C
/etc/majordomo.cf"
> > majordomo-owner: majordomo
> >
> > test: "|/usr/lib/majordomo/wrapper resend -l test -C
> test-list"
> > test-list: :include:/var/lib/majordomo/lists/test
> > owner-test: majordomo
> > test-owner: majordomo
> > test-outgoing: :include:/var/lib/majordomo/lists/test
> > test-request: "|/usr/lib/majordomo/wrapper majordomo -l test -C
> /etc/majordomo.cf"
> >
>
|
