On Thursday, August 7, 2003, at 04:12 pm, James Pifer wrote:


Actually I did look those over, but someone on another list (before
joining this one) told me I didn't need to do all that. Obviously they
were mistaken.


And they were quite right, you do not have to do all that, just some of it. The README.SENDMAIL document doesn't say do all of this; it lists things under headings which you can apply selectively depending on your circumstances.


Given the error message you are getting from Sendmail contains the words 'smrsh: "mailman" not available for sendmail programs' I would be inclined to concentrate on the words in README.SENDMAIL that say:

<quote>
SENDMAIL `smrsh' COMPATIBILITY

    Many newer versions of Sendmail come with a restricted execution
    utility called "smrsh", which limits the executables that Sendmail
    will allow to be used as mail filter programs.  You need to
    explicitly allow Mailman's wrapper program to be used with smrsh
    before it will work.  If mail is not getting delivered to
    Mailman's wrapper program and you're getting an "operating system
    error" in your mail syslog, this could be your problem.

One good way of doing this is to:

        - cd into /etc/smrsh (or where ever it happens to reside on
          your system, such as /var/smrsh or /usr/local/smrsh).

- create a symbolic link to Mailman's wrapper program

    For example, if you've installed Mailman in the standard location,
    you can just execute these commands (you might have to do these as
    root):

        % cd /etc/smrsh
        % ln -s /usr/local/mailman/mail/mailman mailman
</quote>

I would follow those instructions rather than cooking up some cooking up some even more complicated scheme. Changing from a working Sendmail to another MTA will not be painless. Depending on your installation you will probably find the GID that it runs as is different requiring a re-run of MM ./configure and make install

If you have a working Sendmail server on your Mailman machine then all should be well if you follow the instructions.

btw: INSTALL also refers to setting up the mailman wapper to run through smrsh with the words:

<quote>
    Problem:  I send mail to the list, and get back mail saying,
              "sh: mailman not available for sendmail programs"

    Solution: Your system uses sendmail restricted shell (smrsh).  You
              need to configure smrsh by creating a symbolic link from
              the mail wrapper ($prefix/mail/mailman) to the directory
              identifying executables allowed to run under smrsh.

              Some common names for this directory are
              /var/admin/sm.bin, /usr/admin/sm.bin or /etc/smrsh.

              Note that on Debian Linux, the system makes
              /usr/lib/sm.bin, which is wrong, you will need to create
              the directory /usr/admin/sm.bin and add the link there.
              Note further any aliases newaliases spits out will need
              to be adjusted to point to the secure link to the
              wrapper.
</quote>

I looked it over again and not being a sendmail expert I'm uncomfortable
with the changes since this is my main mail server running MailScanner,
etc. So I'm going to try putting it on another machine.


Let me ask you this, more of a sendmail question. If I install Mailman
on another machine, could I have it use the same domain, and have my
main Sendmail server forward email for specific addresses, like lists,
to this other mailman server? Would that work? The mailman server would
be able to deliver directly.

Also, if I do it on another machine, should I use something other than
Sendmail? Are any of the others easier to integrate? From the files it
looks like postfix.

Thanks for your time.
James

On Thu, 2003-08-07 at 09:58, Richard Barrett wrote:
I can only assume that you haven't read all of the notes in the INSTALL
and README.SENDMAIL documentation files in the Mailman build directory.


If that is because you did not install from source then I suggest you
download the MM source distribution from:

http://sourceforge.net/project/showfiles.php?group_id=103

and unpack it to get at those two files.

On Thursday, August 7, 2003, at 02:05 pm, James Pifer wrote:

No I hadn't started that. Is that something I should add to rc.local so
it starts every time the box is restarted?



Covered in the INSTALL file


Something is still screwed up in my Sendmail config. I tried to post a
message to my new list and got the following:


   ----- The following addresses had permanent fatal errors -----
"|/usr/local/mailman/mail/mailman post stoneware-users"
    (reason: Service unavailable)
    (expanded from: <[EMAIL PROTECTED]>)

   ----- Transcript of session follows -----
smrsh: "mailman" not available for sendmail programs (stat failed)
554 5.0.0 Service unavailable
----


Covered in the README.SENDMAIL file


Thanks,
James


On Thu, 2003-08-07 at 02:45, Richard Barrett wrote:
On Thursday, August 7, 2003, at 01:50 am, James Pifer wrote:

Thanks, worked like a champ.

Now my next problem after fixing that one. Looks like the messages
are
getting stuck in the "virgin" directory?

Have you started Mailman's qrunner daemons by executing $prefix/bin/mailmanctl start?

I'm using Sendmail and not sure
I've done everything I need to do. I do have the aliases set up
assuming
I did it correctly.

I have not search the archives on this one yet, but I will.

Thanks for the help.
James

On Wed, 2003-08-06 at 14:56, Richard Barrett wrote:
See:

http://www.python.org/cgi-bin/faqw- mm.py?req=show&file=faq04.029.htp

and in particular the comment under the heading 'Existing versus new
lists'


On Wednesday, August 6, 2003, at 07:42 pm, James Pifer wrote:

I'm new to mailman and have everything setup except for one
problem.
I've tried searching the archives but didn't find my resolution.

I have it installed (version 2.1.2) and created a list. It seems
fine
except that some of the links in the forms are not using my domain
settings, rather that have an IP address in the URL like,
192.168.1.99.
For example, when you try to subscribe the Subscribe button tries
to
post to the IP address rather than the domain.


I've tried setting the defaults for HOST and URL in defaults.py,
but
still can't get it fixed.

Can anyone tell me what I might be missing?

Thanks,
James

-------------------------------------------------------------------- --
-
Richard Barrett
http://www.openinfo.co.uk


------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/
r.barrett%40openinfo.co.uk



------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/ r.barrett%40openinfo.co.uk




------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to