[Mailman-Users] HELP: Mailman 2.1.X, Sendmail, smrsh not playing well together!
Dave Stern - Former Rocket Scientist
dave at umiacs.umd.edu
Mon Apr 28 20:47:53 CEST 2003
On Mon, 28 Apr 2003, David J. Duffner - NWCWEB.com wrote:
> >-----Original Message-----
> >From: Jon Carnes [mailto:jonc at nc.rr.com]
> >Sent: Monday, April 28, 2003 1:49 PM
> >To: mmuserslist at nwcweb.com
> >Cc: MailMan Users
> >Subject: Re: [Mailman-Users] HELP: Mailman 2.1.X, Sendmail, smrsh
> >notplaying well together!
> >On Mon, 2003-04-28 at 10:21, David J. Duffner - NWCWEB.com wrote:
> >> But it still comes down to the fact Mailman can't
> >> call Sendmail for handling as 'smrsh' stops the process
> >> call for security reasons. Sun/Cobalt/RH doesn't place
> >> the possible directories as have been discussed here as
> >> a possible solution, such as '/etc/smrsh' where I could
> >> place config files or anything that would tell smrsh to
> >> let the traffic pass. So I'm clueless at that point.
> >Are you sure at this point that smrsh is the problem?
> ><you are getting a log entry in maillog indicating a bounce
> >because of smrsh>
> Yes, discussions here in the Archive and on the Cobalt
> Lists have detailed that Service Unavilable replies from
> the Server are due to Sendmail using smrsh restrictions.
> I have the latest Solarspeed Sendmail patch, including the
> second recent bug found, so it's mandatorily running smrsh
> as the guard-dog for Sendmail.
> >If so, there could be a few things at work here (depending on if your
> >sendmail is running chrooted or not. If sendmail is running in a
> >chroot, then you have to setup the smrsh to work inside the chrooted
> Unfortunately I'm not that heavily versed in Sendmail
> and how the RaQ4x series w/RH Linux are configured to have an
> answer to that question. Any more details I could search for
> on the box for an answer?
> >An other alternative is that your smrsh my not be setup to use
> >/etc/smrsh (which is a redhat-ism); the default smrsh path is
> >/usr/adm/sm.bin. You can find further discussion of this in the
> >archives (or by looking up smrsh in google.
> Yes, it is the sm.bin path on this box. I did find further
> discussions, but nothing that cause anything other than the
> Service Unavailable errors to occur. Only way that stopped was
> configuring the alternative wrapper for the Mailman directory
> in an attempt to have Sendmail/smrsh find whatever it needed
> to run without a security issue. In that case, it now 'eats'
> all messages sent to the List e-mail address with no replies.
> >What version of mailman are you running?
> 2.1.1, the last stable version released when I attempted
> this a couple of weeks ago. I used instructions from a gent who
> got this to work pre-Sendmail patches last October to do the
> complete install. Those instructions used an older version of
> Mailman, but the only difference I found was the pathing being
> more free-form on the newer edition which I adjusted for.
> Python 2.2.2, Cobalt RH Linux, Sendmail 8.??.?? w/patch
> on a Sun/Cobalt RaQ4r.
> David J. Duffner
> VP Operations
> NWC Corporation - Global E-Pay Solutions
> www.nwcxpress.com - POSA, Merchant Accounts, E-payment solutions
> NWCWEB - Your design, hosting and e-commerce solution!
> www.nwcweb.com - Featuring Miva e-commerce and Sun Cobalt RaQ
I vaguely recall having a similar problem but ultimately got it working
so sendmail-8.12.9 will work with smrsh and mailman. One of the things to
check is that you have that default mailman list that everyone forgets to
=-=-=-=-=-=-=-=-=-=-=-=- generated by /dev/dave -=-=-=-=-=-=-=-=-=-=-=-=-=-=
David Stern University of Maryland
Institute for Advanced Computer Studies
More information about the Mailman-Users