When replying, please strip mailto: URLs and @domain's from the
quoted headers so addresses are not farmable by webcrawlers.
At this point, I would have to guess that your domain is hosted,
your sendmail.cf is very far from a default install, sendmail
does not have the proper trust relationship with majordomo,
and/or the majordomo wrapper was not compiled properly.
>>>O/S: RedHat 8.0
The only difference between your installation and mine from the
information posted is that I am currently on sendmail 8.12.8.
The aliases I posted have been working since sendmail 8.8.8,
possibly longer. My memory isn't what it used to be. :(
I have no idea what dependencies or configuration requirements
there are between majordomo and postfix, but I am sure there
are plenty of users that follow this list that can help in that
Considering you built majordomo from scratch, rather than using
the RPM install, is it possible the wrapper does not match your
majordomo environment? What uid:gid is your majordomo user?
Does `su - majordomo; wrapper config-test` look good? Does
the config-test report the same uid:gid as /etc/passwd does?
Even though the wrapper is suid root, it still needs to be
compiled with the correct majordomo ENVironment.
As for sendmail, considering the "test" aliases did not work,
but writing to an alias with an :include: directly works, I
could not say with high confidence that it's a sendmail issue.
Can you `grep -i "safe" sendmail.cf` and tell us what comes
back? What about smrsh (redhat default) and smmsp? Do you
have a link to /usr/local/majordomo/wrapper in /etc/smrsh?
Does your sendmail and your smmsp "trust" the majordomo user?
Is the clientmqueue directory read/write for smmsp? RedHat
sets procmail as the local delivery agent, which negates the
security benefit of smrsh. This may as well be removed from
the sendmail.mc file.
Since you are on a RedHat 8.0 OS, you might consider the RPM.
The differences, are uid:gid=91:91, $HOME=/usr/lib/majordomo,
the link for smrsh is created automatically, and your lists
would be located in /var/lib/majordomo/lists. I think the
RPM even puts majordomo.cf in /etc. One thing about that
file though, the $whereami variable needs to be modified from
the default RPM install to match your hostname instead of
using a `hostname` or `dnsdomainname` command.
Ohrberg, Mick (OTP-KC) wrote:
> See responses below.
> -----Original Message-----
> From: Daniel Liston
> Sent: Friday, September 12, 2003 11:43 AM
> To: Ohrberg, Mick (OTP-KC)
> Cc: majordomo-users
> Subject: Re: Resend issues with sendmail
> Did you "try" my aliases to see if a list called test would work?
> - Yes, I did. It did not work.
> Is it possible that in the file named /usr/local/majordomo/lists/sysmgt you
> have a line containing :include: something? This would be very bad. The
> file should contain ONE RFC822 email address per line.
> - Yes. I have one email address per line, and no recursive include's.
> Are you positive, that no directory in the path to your membership files is
> group or world writable? This includes the / directory, /usr, /usr/local,
> /usr/local/majordomo, and /usr/local/majordomo/lists.
> - Yes, I am positive.
> Before trying my aliases, ... assuming you are the root user; echo
> 'email@example.com' > /usr/local/majordomo/lists/test chown
> majordomo.majordomo /usr/local/majordomo/lists/test
> - It gives the same error message. Please ask for any logs you may want, or
> let me know if you think it may actually be sendmail related (it seems like
> sendmail refuses to expand recursive aliases?). Should I switch to postfix?
> :P Thanks for your help!
> Dan Liston
> Ohrberg, Mick (OTP-KC) wrote:
>>Thank you for your response. Unfortunately it didn't seem to make a
>>difference. I'm still getting the error of not being able to send to
>>:include:s, as if sendmail doesn't expand the included file if it's an
>>alias refering to another alias (in your example, test pointing to
>>test-outgoing, in turn doing the :include:. The -h and -s flags came
>>from some old documentation (snippet from an O'Reilly "Managing
>>Internet Information Services" book). Is there anything else about the
>>syntax that shouldn't be there?
>>If you or anyone else have any suggestions, please let me know.
>>From: Daniel Liston [mailto:firstname.lastname@example.org]
>>Sent: Thursday, September 11, 2003 2:07 AM
>>To: Ohrberg, Mick (OTP-KC)
>>Subject: Re: Resend issues with sendmail
>>You do not have the syntax to "resend" correct in your alias. Here is
>>a sample set of aliases that work, to use as a template.
>>Of course, your pathnames will not be the same, and if you are not
>>archiving or digesting your lists, just remove everything after the
>>first comma in the
>>test-outgoing: alias. If you are archiving, you need to make sure the
>>majordomo.cf file is using the proper filedir and filedir_suffix for the
>>test-archiver: alias to work.
>>Ohrberg, Mick (OTP-KC) wrote:
>>>O/S: RedHat 8.0
>>>I have looked high and low for this, but nowhere can I find an answer.
>>>I have a mailing list named sysmgt. My sendmail is instructed to look
>>>for /etc/aliases and /etc/majordomo.aliases (or the .db versions
>>>thereof). My majordomo.aliases contains (amongst other things):
>>>sysmgt: "|/usr/local/majordomo/wrapper resend -l sysmgt -h
>><hostname> -s sysmgt-list"
>>>However, this fails with:
>>> ----- The following addresses had permanent fatal errors -----
>>> (expanded from: sysmgt-list)
>>> ----- Transcript of session follows -----
>>>550 5.7.1 :include:/usr/local/majordomo/lists/sysmgt... Cannot mail
>>>directly to :include:s Message delivered to mailing list
>>>If I remove the resend entry:
>>>...it works fine and sends out emails.
>>>And yes, I do sendmail -bi/newaliases every time :) And wrapper is
>>>setuid etc etc. I am at a loss...
>>>Thanks in advance!
>>> /Mick Ohrberg
>>> Proprietary brain. Please put in shred bin only.