![](https://secure.gravatar.com/avatar/1cf2bba37b49076248ff5c53bed257a4.jpg?s=120&d=mm&r=g)
Hello all,
I'm running Linux 6.1, Mailman 1.1, Python 1.5.1 and Apache 1.3.11 and sendmail.
My project here is to setup a list server for faculty and students to create their own lists.
I followed the Mailman installation instruction and run
./configure with all default options.
my aliases file looks like this:
/etc/aliases
#Test mailing list test: "|/home/mailman/mail/wrapper post test" test-admin: "|/home/mailman/mail/wrapper mailowner test" test-request: "|/home/mailman/mail/wrapper mailcmd test" owner-test: test-admin owner-test: test-admin
I run newaliases after I update my aliases file.
I also setup a test list. I was able to create the list, login the admin web page and subscribe to the list. I got a Confirmation email from test-request@lqldap.mydomain.edu.
However, I was not be able to send mail to test-request@lqldap.mydomain.edu. Here is what I got :
----- The following addresses had permanent fatal errors ----- "|/home/mailman/mail/wrapper mailcmd test" (expanded from: <test-request@lqldap.mydomain.edu>)
----- Transcript of session follows ----- sh: wrapper not available for sendmail programs 554 "|/home/mailman/mail/wrapper mailcmd test"... Service unavailable
When I send a email to test@lqldap.mydomain.edu, I did not get rebound. from maillog it lists:
lqldap smrsh: uid 8: attempt to use wrapper mailowner test lqldap sendmail[1234]: MAA01234: to="|/home/mailman/mail/wrapper post test", ...miler=prog, stat=Service unavailable lqldap sendmail[1234]: MAA01234: MAB01234: DSN: Service unavailable lqldap sendmail[1234]: MAB01234: MAC01234: return to sender: Service unavailable
I look up the installation guide, it said I need to "configure smrsh by creating a symbolic link from the mail wrapper to the directory identifying executables allowed to run under smrsh."
I look up my /etc/smrsh, there is no files there in the directory.
Would someone show me how to configure the smrsh and create the symbolic link ?
Thanks.
Lin
![](https://secure.gravatar.com/avatar/e581953d89ec0856dc9b4ade54076cca.jpg?s=120&d=mm&r=g)
Well, first day on the list and I get to answer a question, neato! Here is the documentation from the INSTALL file:
Problem: I send mail to the list, and get back mail saying,
"sh: wrapper not available for sendmail programs"
Solution: Your system uses sendmail restricted shell. You need to
configure smrsh by creating a symbolic link from the
mail wrapper ($prefix/mail/wrapper) 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.
and here is the command line that you would use from the information you gave in your email.
ln -s /home/mailman/mail/wrapper /etc/smrsh/wrapper
Enjoy!
On Tue, 29 Feb 2000, Lin Qiu wrote:
,-----------------------------------------------------------------------------.
`-----------------------------------------------------------------------------'
![](https://secure.gravatar.com/avatar/1cf2bba37b49076248ff5c53bed257a4.jpg?s=120&d=mm&r=g)
Bill,
Thanks for the information. I did the symbolic link, it takes care one problem. This time I have:
----- The following addresses had permanent fatal errors ----- "|/home/mailman/mail/wrapper mailcmd test" (expanded from: <test-request@lqldap.admin.sunyrockland.edu>)
----- Transcript of session follows ----- Traceback (innermost last): File "/home/mailman/scripts/mailcmd", line 49, in ? list = MailList.MailList(sys.argv[1]) File "/home/mailman/Mailman/MailList.py", line 62, in __init__ self.Load() File "/home/mailman/Mailman/MailList.py", line 804, in Load self.Lock() File "/home/mailman/Mailman/MailList.py", line 1373, in Lock self.__lock.lock() File "/home/mailman/Mailman/LockFile.py", line 186, in lock os.link(self.__lockfile, self.__tmpfname) OSError: [Errno 13] Permission denied 554 "|/home/mailman/mail/wrapper mailcmd test"... unknown mailer error 1
Could this cause by "using the wrong GID or UID for mail" as indicated in the installation menu? I look up the syslog, and did not find anything there.
Thanks.
Lin
Bill DeVos wrote:
![](https://secure.gravatar.com/avatar/e581953d89ec0856dc9b4ade54076cca.jpg?s=120&d=mm&r=g)
On Tue, 29 Feb 2000, Lin Qiu wrote:
Although I'm very new to Python (haven't written a program in it yet) looking at the traceback the last line mentions os.link(self.__lockfile..., this appears to me that it was (at the time of the error) attempting to create it's lock file, yes? Looking at the actuall error "Permission denied" I would guess that the OS has refused permission to create a lock file. Again from the INSTALL docs: 3. Check your installation
To check that your installation has all the correct permissions
and group ownerships, you should run the check_perms script:
- cd to $prefix
- Run bin/check_perms
Have you done this? What was the result?
,-----------------------------------------------------------------------------.
![](https://secure.gravatar.com/avatar/e581953d89ec0856dc9b4ade54076cca.jpg?s=120&d=mm&r=g)
Please notice in the cut of my confirmation below that although the body of the message contains the addresses as I want them all to be, the headers addresses have been altered to unusable addresses. I can't imagine that this is being done by any mailer and if I alter the addresses to what they are in the body they work just fine. I hope this information makes it easier to determine the problem.
<Paste> From: python-request@stercomm.com Received: from watcher (watcher.nsg.stercomm.com [192.168.160.153]) by imx1.stercomm.com with ESMTP id NAA12176 for <watcher@stercomm.com>; Tue, 29 Feb 2000 13:54:23 -0500 (EST) Date: Tue, 29 Feb 2000 13:54:23 -0500 (EST) Message-Id: <200002291854.NAA12176@imx1.stercomm.com> Subject: Python -- confirmation of subscription -- request 828536 To: watcher@stercomm.com Reply-to: python-request@stercomm.com Errors-To: python-admin@stercomm.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Discussion or assistance about Python. <python.watcher.nsg.stercomm.com>
Python -- confirmation of subscription -- request 828536
We have received a request from watcher for subscription of your email address, <watcher@stercomm.com>, to the python@watcher.nsg.stercomm.com mailing list. To confirm the request, please send a message to python-request@watcher.nsg.stercomm.com, and either: </Paste>
,-----------------------------------------------------------------------------.
![](https://secure.gravatar.com/avatar/e581953d89ec0856dc9b4ade54076cca.jpg?s=120&d=mm&r=g)
On a totally unrelated note, I've been trying to figure out why I'm getting the same type of error I see in your log with reference to DSN. I realize this is in no way related to Mailman, but does anyone know what DSN is and why it seems to generate an error on at least a daily basis?
On Tue, 29 Feb 2000, Lin Qiu wrote:
,-----------------------------------------------------------------------------.
![](https://secure.gravatar.com/avatar/e581953d89ec0856dc9b4ade54076cca.jpg?s=120&d=mm&r=g)
Well, first day on the list and I get to answer a question, neato! Here is the documentation from the INSTALL file:
Problem: I send mail to the list, and get back mail saying,
"sh: wrapper not available for sendmail programs"
Solution: Your system uses sendmail restricted shell. You need to
configure smrsh by creating a symbolic link from the
mail wrapper ($prefix/mail/wrapper) 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.
and here is the command line that you would use from the information you gave in your email.
ln -s /home/mailman/mail/wrapper /etc/smrsh/wrapper
Enjoy!
On Tue, 29 Feb 2000, Lin Qiu wrote:
,-----------------------------------------------------------------------------.
`-----------------------------------------------------------------------------'
![](https://secure.gravatar.com/avatar/1cf2bba37b49076248ff5c53bed257a4.jpg?s=120&d=mm&r=g)
Bill,
Thanks for the information. I did the symbolic link, it takes care one problem. This time I have:
----- The following addresses had permanent fatal errors ----- "|/home/mailman/mail/wrapper mailcmd test" (expanded from: <test-request@lqldap.admin.sunyrockland.edu>)
----- Transcript of session follows ----- Traceback (innermost last): File "/home/mailman/scripts/mailcmd", line 49, in ? list = MailList.MailList(sys.argv[1]) File "/home/mailman/Mailman/MailList.py", line 62, in __init__ self.Load() File "/home/mailman/Mailman/MailList.py", line 804, in Load self.Lock() File "/home/mailman/Mailman/MailList.py", line 1373, in Lock self.__lock.lock() File "/home/mailman/Mailman/LockFile.py", line 186, in lock os.link(self.__lockfile, self.__tmpfname) OSError: [Errno 13] Permission denied 554 "|/home/mailman/mail/wrapper mailcmd test"... unknown mailer error 1
Could this cause by "using the wrong GID or UID for mail" as indicated in the installation menu? I look up the syslog, and did not find anything there.
Thanks.
Lin
Bill DeVos wrote:
![](https://secure.gravatar.com/avatar/e581953d89ec0856dc9b4ade54076cca.jpg?s=120&d=mm&r=g)
On Tue, 29 Feb 2000, Lin Qiu wrote:
Although I'm very new to Python (haven't written a program in it yet) looking at the traceback the last line mentions os.link(self.__lockfile..., this appears to me that it was (at the time of the error) attempting to create it's lock file, yes? Looking at the actuall error "Permission denied" I would guess that the OS has refused permission to create a lock file. Again from the INSTALL docs: 3. Check your installation
To check that your installation has all the correct permissions
and group ownerships, you should run the check_perms script:
- cd to $prefix
- Run bin/check_perms
Have you done this? What was the result?
,-----------------------------------------------------------------------------.
![](https://secure.gravatar.com/avatar/e581953d89ec0856dc9b4ade54076cca.jpg?s=120&d=mm&r=g)
Please notice in the cut of my confirmation below that although the body of the message contains the addresses as I want them all to be, the headers addresses have been altered to unusable addresses. I can't imagine that this is being done by any mailer and if I alter the addresses to what they are in the body they work just fine. I hope this information makes it easier to determine the problem.
<Paste> From: python-request@stercomm.com Received: from watcher (watcher.nsg.stercomm.com [192.168.160.153]) by imx1.stercomm.com with ESMTP id NAA12176 for <watcher@stercomm.com>; Tue, 29 Feb 2000 13:54:23 -0500 (EST) Date: Tue, 29 Feb 2000 13:54:23 -0500 (EST) Message-Id: <200002291854.NAA12176@imx1.stercomm.com> Subject: Python -- confirmation of subscription -- request 828536 To: watcher@stercomm.com Reply-to: python-request@stercomm.com Errors-To: python-admin@stercomm.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Discussion or assistance about Python. <python.watcher.nsg.stercomm.com>
Python -- confirmation of subscription -- request 828536
We have received a request from watcher for subscription of your email address, <watcher@stercomm.com>, to the python@watcher.nsg.stercomm.com mailing list. To confirm the request, please send a message to python-request@watcher.nsg.stercomm.com, and either: </Paste>
,-----------------------------------------------------------------------------.
![](https://secure.gravatar.com/avatar/e581953d89ec0856dc9b4ade54076cca.jpg?s=120&d=mm&r=g)
On a totally unrelated note, I've been trying to figure out why I'm getting the same type of error I see in your log with reference to DSN. I realize this is in no way related to Mailman, but does anyone know what DSN is and why it seems to generate an error on at least a daily basis?
On Tue, 29 Feb 2000, Lin Qiu wrote:
,-----------------------------------------------------------------------------.
participants (2)
-
Bill DeVos
-
Lin Qiu