Dan / All:
If I send a message directly to the newsletter-dist address, I get the
same message, unable to expand the distribution list. This looks like a
sendmail problem. Everything in the path (/, /home, /home/majordomo,
/home/majordomo/runtime, /home/majordomo/runtime/lists) is all 751 for
the directories. Everything in the lists directory is 640. Everything
past /home/majordomo is owned majordomo:majordomo. The /etc/aliases file
is 644 root:root. The contents of the resend (newsletter.resend) file
are as follows:
-l newsletter -h listserv.capwin.org newsletter-dist,nobody
...At wit's end!!
From: Daniel Liston [mailto:email@example.com]
Sent: Tuesday, July 15, 2003 4:28 PM
To: Dave Fontaine
Subject: Re: Unable to expand a distribution list
Dave Fontaine wrote:
> Thank you SO much for responding to this!!!
> Here are all my aliases:
> majordomo: "|/home/majordomo/runtime/wrapper majordomo"
> owner-majordomo: firstname.lastname@example.org,nobody
> majordom: owner-majordomo
If majordom is the actual passwd file entry, the alias for majordom
"should" redirect to the majordomo alias, not the owner. Then again,
I could think up some useful ways to make use of the configuration
the way it is. Do you have Tmajordom in the sendmail.cf and the
submit.cf files? Tmajordomo will not help if the passwd file entry
is just majordom.
> Majordomo-Owner: owner-majordomo
> owner-newsletter: email@example.com,nobody
> newsletter: "|/home/majordomo/runtime/wrapper
The above implies that you have "-l newsletter newsletter-dist" in the
newsletter.resend file. What are the attributes on this file? Who
are the owner and group that it belongs to?
> newsletter-approval: owner-newsletter
> newsletter-dist: :include:/home/majordomo/runtime/lists/newsletter
Same question about attributes, ownership, and group for this file.
There should NOT be any group or world "writable" directories in the
path on the way to this file either. Group and/or world "readable"
is OK, and the directories should all be at least user and group
> owner-newsletter-dist: owner-newsletter
> newsletter-request: "|/home/majordomo/runtime/wrapper
> request-answer newsletter"
> owner-newsletter-request: owner-newsletter
You can test how well sendmail likes your distribution list by
attempting to send directly to the firstname.lastname@example.org
address, preferably from an account on the same machine as your
majordomo. If this file is fully populated with active email
addresses, you might want to replace it with a set of test accounts
before doing your test.
> Thank you thank you thank you....
> -----Original Message-----
> From: Daniel Liston [mailto:dliston (at) sonny.org]
> Sent: Monday, July 14, 2003 4:27 PM
> To: Dave Fontaine
> Cc: email@example.com
> Subject: Re: Unable to expand a distribution list
> Please post the section of /var/log/maillog related to this error
> so we can try to diagnose your situation.
> What does the alias for newsletter-dist: look like?
> What does the alias for newsletter: look like?
> Dan Liston
> Dave Fontaine wrote:
>> Hello all,
>> Have run into a problem while attempting to make a submission. I can
>> execute the config, lists, help type commands with no hitches
>> whatsoever. The error that I am getting is:
>> firstname.lastname@example.org on 7/10/2003 5:40 PM
>> Unable to expand a distribution list to deliver the
>> to its members. Try again or contact your system administrator.
>> < listserv.mydomain.org #5.2.4>
>> I am running Redhat 8.0, sendmail 8.12.5-7, and Majordomo 1.94.5.
>> I have done the following to try to correct the problem, but still
>> I have added 'Tmajordomo' to the sendmail.cf and submit.cf files and
>> ensured that the Trusted users line was NOT commented out. I have
>> majordomo to the trusted-users file in '/etc/mail/'.
>> I have verified permissions and ownerships as per section 2.1 of the
>> Great Circle Majordomo FAQs, 640 for files, 751 for directories and x
>> bit set for all major scripts - wrapper, resend, etc.
>> I have verified that wrapper was installed setuid.
>> I have run the './wrapper config-test' as a third party user and the
>> results were 100% positive. Which leads me to believe that this is a
>> sendmail problem.
>> PLEASE help, anyone! :)