Thanks for the response.
My sendmail does not have smrsh enabled so this should not be an issue. Also since the initial mail is bounced for approval, it
means that the wrapper can be accessed.
Any other ideas?
> -----Original Message-----
> From: Daniel Liston [mailto:firstname.lastname@example.org]
> Sent: Tuesday, 01 Apr 01, 2003 7:22 PM
> To: email@example.com
> Cc: firstname.lastname@example.org
> Subject: Re: Sendmail upgrade breaks majordomo
> I see a couple things. It no longer appears that majordomo is a "trusted" user.
> Sendmail 8.12.x uses a mail submission program which gets configuration info
> from the submit.cf file prior to the normal MTA and the sendmail.cf file.
> Make sure you have Tmajordom or Ft/etc/mail/trusted-users in the submit.cf
> file. This will solve the Authentication-Warning: HostName.domain.net: majordom
> set sender to email@example.com using -f
> The other thing I see is in your alias for the list address. -h list-domain.org
> is redundant if you have resend_host=list-domain.org in your listname.config file.
> Some future version of majordomo is supposed to deprecate using arguments like
> this in the aliases file anyway.
> In the past I have seen "service unavailable" indicate sendmail is using the smrsh
> feature, but majordomo's wrapper is not linked into the smrsh directory. You can
> find out by `grep -i smrsh sendmail.cf`, then if/when you find P=/usr/bin/smrsh
> you `strings /usr/sbin/smrsh | grep / | grep -v #` to find the directory used to
> hold programs or links to them, that sendmail is allowed to run.
> Dan Liston
> A. I. Sinclair wrote:
> > There are some other threads on this subject, but my problem seems slightly different.
> > I was running a moderated list on freebsd 4.5 with whatever the default sendmail version was and majordomo 1.94.5_1.
> > I then upgraded freebsd to 4.7 stable which included the upgrade of sendmail to 8.12.8
> > Since the upgrade I am having a problem with majordomo.
> > What happens is :
> > - When a message is sbmitted to the list, it bounces for approval (this is correct behaviour).
> > - When the approved message is submitted to the list it does not get delivered to the list members, although it does
> get archived.
> > The message comes back into my inbox with the following text (names etc changed) :
> > ------------------------------------------
> > The original message was received at Tue, 1 Apr 2003 12:11:45 +0100 (BST)
> > from localhost [127.0.0.1]
> > ----- The following addresses had permanent fatal errors -----
> > firstname.lastname@example.org
> > (reason: 550 Error: 550 Use Received: from HostName.domain.net (localhost [127.0.0.1]))
> > (expanded from: <listname-outgoing@HostName.domain.net>)
> > ----- Transcript of session follows -----
> > ... while talking to mx1.zapp.ch.:
> >>>> DATA
> > <<< 550 Error: 550 Use Received: from HostName.domain.net (localhost [127.0.0.1])
> > 554 5.0.0 Service unavailable
> > ---------------------------------------------
> >>From maillog :
> > Apr 1 12:11:45 HostName sm-mta: h31BBjLS001905: from=<email@example.com>, size=1896, class=0, nrcpts=1,
> > msgid=<NDBBIMNLHGEMMAKNEPOBOEFFEHAA.firstname.lastname@example.org>, proto=ESMTP, daemon=MTA, relay=dns1.zapp.ch [18.104.22.168]
> > Apr 1 12:11:45 HostName sm-mta: h31BBjLS001905: h31BBjLS001906: clone: owner=me
> > Apr 1 12:11:45 HostName sendmail: h31BBjL3001910: Authentication-Warning: HostName.domain.net: majordom set sender to
> > email@example.com using -f
> > Apr 1 12:11:45 HostName sendmail: h31BBjL3001910: firstname.lastname@example.org, size=1187, class=-60, nrcpts=1,
> > msgid=<NDBBIMNLHGEMMAKNEPOBEEFFEHAA.email@example.com>, relay=majordom@localhost
> > Apr 1 12:11:45 HostName sm-mta: h31BBjLS001911: from=<firstname.lastname@example.org>, size=1518, class=-60, nrcpts=1,
> > msgid=<NDBBIMNLHGEMMAKNEPOBEEFFEHAA.email@example.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
> > Apr 1 12:11:46 HostName sendmail: h31BBjL3001910: to=list-outgoing, firstname.lastname@example.org (54/26),
> > delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=138759, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (h31BBjLS001911
> > Message accepted for delivery)
> > Apr 1 12:11:46 HostName sm-mta: h31BBjLS001906: to="|/usr/local/majordomo/wrapper resend -l ListName -h list-domain.org
> > list-outgoing", ctladdr=<email@example.com> (26/0), delay=00:00:01, xdelay=00:00:01, mailer=prog, pri=32152,
> dsn=2.0.0, stat=Sent
> > Apr 1 12:11:52 HostName sm-mta: h31BBjLS001911: firstname.lastname@example.org, delay=00:00:07, xdelay=00:00:06, mailer=esmtp,
> > pri=139789, relay=mx1.zapp.ch. [22.214.171.124], dsn=5.0.0, stat=Service unavailable
> > Apr 1 12:11:52 HostName sm-mta: h31BBjLS001911: h31BBqLS001912: DSN: Service unavailable
> > --------------------------------
> > Any help would be welcome.
> > TIA
> > ais