I searched the archives for the past several months and found very little mention of anyone running Mailman on Mac OS X. Back in January, when I was setting up a new mail server for our agency, I went with Mac OS X 10.1 for the plain old SMTP/POP needs, but I also needed a listserv package. At the time, I tried unsuccessfully to get Mailman set up but had no luck in the timeframe I was allotted. Instead, I've been running Majordomo pretty successfully since then, using Webmin for my various list administrators to do their thing.
I'm now in a position to re-evaluate our listserv options as I'm planning to step up to Mac OS X Server 10.2 (Jaguar) in the next month or two (probably implementing over the Thanksgiving break.) I like the features it includes and it integrates perfectly with our all-Mac network. I'd like to take another look at Mailman, but this time I'm not too proud to ask for help.
Long story short, I'm running Mac OSXS 10.2 on a development machine. I spent the better part of this afternoon trying to get it configured. I've got the developer tools installed, of course, and followed the MM directions to the absolute letter. I've created the mailman user and group as directed. I created the mailman directory with proper permissions. Everything looked good when I did config and 'make install' but when I use the check_perms script (after creating a test list) I get the following:
directory permissions must be at least 02775: /usr/local/mailman/archives/private/test.mbox directory permissions must be at least 02775: /usr/local/mailman/archives/public/test.mbox directory permissions must be at least 02775: /usr/local/mailman/lists/test Traceback (most recent call last): File "bin/check_perms", line 281, in ? checkmail() File "bin/check_perms", line 202, in checkmail mode = statmode(wrapper) File "bin/check_perms", line 74, in statmode return os.stat(path)[ST_MODE] OSError: [Errno 2] No such file or directory: '/usr/local/mailman/mail/wrapper'
The first three lines I understand the problem, although I don't know why MM didn't set the permissions properly when I created the list. I have no idea what the rest is saying. I know the last line is looking for the file in question, which apparently wasn't created during the install process. The 'wrapper' file is simply missing -- why, I have no idea. I should note here that aside from the first three lines, I got exactly the same error immediately after running the make and before any lists were created. I reinstalled MM from scratch twice with identical results. Using the -f flag didn't fix anything, nor did running the entire install and post-test process as root (and I know that's discouraged; I was trying everything I could think of to get it to work.)
If anyone has successfully installed MM on Mac OS X, I'd love to get some pointers. Majordomo is working adequately, but I'd like my listserv package to be more than just "adequate." Any help is greatly appreciated!
Thanks, Brent
How helpful this is remains to be seen, but I have been running mailman with qmail under OS X for a couple of months now. I installed under 10.1 first, using fink to install python, and installing qmail essentially from scratch. After I installed qmail I did a fair amount of testing to ensure that qmail was accepting and delivering mail properly. This is running on my home system, but my daughters' systems are networked via a router, and the whole network is accessing the net through an ADSL connection with static IP and my own domain name. I didn't install mailman until I had mail working properly for everyone and was sure that there were no open relays.
I installed 2.0.12 first, then upgraded almost immediately to 2.0.13. I had a couple of problems with permissions, so I reconfigured with various options set. All of this was still under 10.1. After the upgrade to 10.2 I had no obvious problems - everything worked - but when I checked the system log I found I was getting a lot of complaints about pre-binding on python. I haven't worked out what's going on there. It's not that the message doesn't make sense, but that it is intermittent. If I reboot, sometimes the pre-binding message goes away. I haven't spent much time on it, and won't as long as the system operates properly. Eventually fink will catch up with 10.2 or I'll rebuild with the system's version of python - but not today.
My needs are light. On a busy day I might get ten incoming messages and direct them to a couple of hundred address. I've had one glitch so far, but it was a qmail freeze which resulted from the trigger file being left in an odd state after I killed the system one night while playing with some early software. I should know better than to run version 0.01 of anything.... I reset the perms on the trigger and rebooted, and eventually qmail came out of its trance. Mailman itslef has been solid. I was running LetterRip under OS 9, and my users really appreciate the web interface and archiving which mailman provides.
Bottom line is, mailman can run under 10.2 but since I haven't tried to install directly I doubt I can help with your problem, though I'm willing to try. I just hope this is encouraging enough that you persevere.
What are you using for mail service?
On Sunday, September 29, 2002, at 08:23 PM, Brent Rossow wrote:
I searched the archives for the past several months and found very little mention of anyone running Mailman on Mac OS X. Back in January, when I was setting up a new mail server for our agency, I went with Mac OS X 10.1 for the plain old SMTP/POP needs, but I also needed a listserv package.
At the time, I tried unsuccessfully to get Mailman set up but had no luck in the timeframe I was allotted. Instead, I've been running Majordomo pretty successfully since then, using Webmin for my various list administrators to do their thing.I'm now in a position to re-evaluate our listserv options as I'm planning to step up to Mac OS X Server 10.2 (Jaguar) in the next month or two (probably implementing over the Thanksgiving break.) I like the features it includes and it integrates perfectly with our all-Mac network. I'd like to take another look at Mailman, but this time I'm not too proud to ask for help.
Long story short, I'm running Mac OSXS 10.2 on a development machine.
I spent the better part of this afternoon trying to get it configured.
I've got the developer tools installed, of course, and followed the MM directions to the absolute letter. I've created the mailman user and group as directed. I created the mailman directory with proper permissions. Everything looked good when I did config and 'make install' but when I use the check_perms script (after creating a test list) I get the following:directory permissions must be at least 02775: /usr/local/mailman/archives/private/test.mbox directory permissions must be at least 02775: /usr/local/mailman/archives/public/test.mbox directory permissions must be at least 02775: /usr/local/mailman/lists/test Traceback (most recent call last): File "bin/check_perms", line 281, in ? checkmail() File "bin/check_perms", line 202, in checkmail mode = statmode(wrapper) File "bin/check_perms", line 74, in statmode return os.stat(path)[ST_MODE] OSError: [Errno 2] No such file or directory: '/usr/local/mailman/mail/wrapper'
The first three lines I understand the problem, although I don't know why MM didn't set the permissions properly when I created the list. I have no idea what the rest is saying. I know the last line is looking for the file in question, which apparently wasn't created during the install process.
The 'wrapper' file is simply missing -- why, I have no idea. I should note here that aside from the first three lines, I got exactly the same error immediately after running the make and before any lists were created.
I reinstalled MM from scratch twice with identical results. Using the -f flag didn't fix anything, nor did running the entire install and post-test process as root (and I know that's discouraged; I was trying everything I could think of to get it to work.)If anyone has successfully installed MM on Mac OS X, I'd love to get some pointers. Majordomo is working adequately, but I'd like my listserv package to be more than just "adequate." Any help is greatly appreciated!
Thanks, Brent
Mailman-Users mailing list Mailman-Users@python.org 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/
The only real stumbling block I found to setting up Mailman with Postfix on OS X client was making sure to run the install as the mailman user. I don't know anything about OS X Server's configuration, nor about using Mailman with sendmail or qmail or anything. I am going to sit down with a clean system this week, though, and figure out just what you need to do to install Mailman properly on OS X (Client), and I will be posting the instructions online. I will post the link to this mailing list when I finish.
Greg
On Sunday, September 29, 2002, at 08:23 PM, Brent Rossow wrote:
I searched the archives for the past several months and found very little mention of anyone running Mailman on Mac OS X. [...] Long story short, I'm running Mac OSXS 10.2 on a development machine. [...] If anyone has successfully installed MM on Mac OS X, I'd love to get some pointers. Majordomo is working adequately, but I'd like my listserv package to be more than just "adequate." Any help is greatly appreciated!
-- greg@gregwestin.com http://www.gregwestin.com Contact info: http://www.gregwestin.com/contact.php
On Monday, 30 September 2002 00:53 -0400, Greg Westin <greg@gregwestin.com> wrote:
The only real stumbling block I found to setting up Mailman with Postfix on OS X client was making sure to run the install as the mailman user. I don't know anything about OS X Server's configuration, nor about using Mailman with sendmail or qmail or anything. I am going to sit down with a clean system this week, though, and figure out just what you need to do to install Mailman properly on OS X (Client), and I will be posting the instructions online. I will post the link to this mailing list when I finish.
I've been running MailMan under Mac OS X Server for quite a while now, using Postfix as the MTA. The process for running under Client is virtually the same. You may find the article on AFP548.com (URL: http://www.afp548.com/Articles/mail/python-mailman.html) to be of help, if you also use Postfix.
-- David B. O'Donnell - atropos@fates.org - www.fates.org Help cats in need: http://www.fancycats.org/ "Thoughtful consumption is the enemy of marketing." -- Scott Hazen Mueller
"DBO" == David B O'Donnell <atropos@fates.org> writes:
DBO> I've been running MailMan under Mac OS X Server for quite a
DBO> while now, using Postfix as the MTA. The process for running
DBO> under Client is virtually the same. You may find the article
DBO> on AFP548.com (URL:
DBO> http://www.afp548.com/Articles/mail/python-mailman.html) to
DBO> be of help, if you also use Postfix.I'm going to start a MacOSX README. Mind if I included this url?
-Barry
Hi Folks,
I'm on the tail end of migrating my mail server & lists from one OS X machine to another. Everything has gone reasonably fine, except my qrunner cron job. I am getting the following email every minute:
"shell-init: could not get current directory: getcwd: cannot access parent directories: Permission denied"
I have checked the permissions with mailman/bin/check_perms and I get no errors.
Can anyone offer me some insights?
Thanks,
michael
michael geary The Treeline Group, Inc. 560 S. State Street, E-2 Orem, UT 84058
(801) 225-1414 x 1002 http://www.treelinegroup.com
Barry hit the nail on the head regarding python2-devel being needed for RedHat users. I installed that package and 2.1b3 compiled in just a few minutes, and ran the first time. (Well, at least I can get to the admin interface.)
I went to setup a new list, ran newlist from the mailman/bin collection, and was immediately able to connect to setup the normal minimal things. It accepted the list password and the site password without problem, the frustration was how often it accepted them. I would make a change, hit submit, and it wanted my password to get back to the page. I click to another page, it wanted my password. Make a change there, it wanted my password. This from the same installation of Netscape 4.78 that has long been my default browser. It is not a problem for Opera 6.05 or MSIE.
Okay, now I have sent the first test message, and it is returned to me with this text:
Final-Recipient: rfc822; test@virtuoso.domainvanhorn.com Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; Command died with status 1: "/home/mailman/mail/wrapper post test"
What does that mean?
Van
--
Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted@whidbey.com?subject=Subscribe_QOTD
For web hosting and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/
On Wed, 2002-10-09 at 03:19, G. Armour Van Horn wrote:
Okay, now I have sent the first test message, and it is returned to me with this text:
Final-Recipient: rfc822; test@virtuoso.domainvanhorn.com Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; Command died with status 1: "/home/mailman/mail/wrapper post test"
What does that mean?
your post command didn't work. The alias translated to a program, and that program exited with a status 1.
Check the mailman logs to see what it didn't like.
My suspicion is a permissions issue.
LER
Van
--
Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted@whidbey.com?subject=Subscribe_QOTD
For web hosting and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/
Mailman-Users mailing list Mailman-Users@python.org 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/
-- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Well, at the time I had a permissions issue. So I chowned the whole tree to mailman:mailman, and went back and did "config.status" and "make install" to ratify it. Then I did a couple of other little things I had overlooked in the INSTALL file. Nothing is being logged in the mailman/logs to speak of, certainly none of my test messages.
I discovered from the /var/log/maillog file that I had a problem with my aliases, and came to figure out that I was editing /etc/postfix/aliases but newaliases was using the /etc/aliases file to create an aliases.db file I now have added all the correct aliases (from bin/genaliases) to the /etc/aliases file, run newaliases, and just in case, copied both to /etc/postfix/.
Here's the maillog tail from my last attempt to post:
Oct 9 02:25:41 virtuoso postfix/smtpd[1487]: 8702E2D7B2:
client=mailout.whidbey.net[209.166.64.124]
Oct 9 02:25:41 virtuoso postfix/cleanup[1488]: 8702E2D7B2:
message-id=<3DA3F63C.6D2DCC90@whidbey.com>
Oct 9 02:25:42 virtuoso postfix/smtpd[1487]: disconnect from
mailout.whidbey.net[209.166.64.124]
Oct 9 02:25:42 virtuoso postfix/qmgr[841]: 8702E2D7B2:
from=<vanhorn@whidbey.com>, size=1258, nrcpt=1 (queue active)
Oct 9 02:25:42 virtuoso postfix/local[1490]: fatal: open database
/etc/postfix/aliases.db: Invalid argument
Oct 9 02:25:43 virtuoso postfix/qmgr[841]: warning: premature end-of-input
from private/local socket while reading input attribute name
Oct 9 02:25:43 virtuoso postfix/qmgr[841]: warning: private/local socket:
malformed response
Oct 9 02:25:43 virtuoso postfix/qmgr[841]: warning: transport local failure
-- see a previous warning/fatal/panic logfile record for the problem
description
Oct 9 02:25:43 virtuoso postfix/master[823]: warning: process
/usr/libexec/postfix/local pid 1490 exit status 1
Oct 9 02:25:43 virtuoso postfix/master[823]: warning:
/usr/libexec/postfix/local: bad command startup -- throttlingIncidentally, this message has not been bounced.
I have to get on a plane in a few hours, and would like not to leave the system in this state for the next week!
Van
--
Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted@whidbey.com?subject=Subscribe_QOTD
For web hosting and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/
On Wed, 2002-10-09 at 04:33, G. Armour Van Horn wrote:
I discovered from the /var/log/maillog file that I had a problem with my aliases, and came to figure out that I was editing /etc/postfix/aliases but newaliases was using the /etc/aliases file to create an aliases.db file I now have added all the correct aliases (from bin/genaliases) to the /etc/aliases file, run newaliases, and just in case, copied both to /etc/postfix/. [snip]
Oct 9 02:25:42 virtuoso postfix/qmgr[841]: 8702E2D7B2: from=<vanhorn@whidbey.com>, size=1258, nrcpt=1 (queue active) Oct 9 02:25:42 virtuoso postfix/local[1490]: fatal: open database /etc/postfix/aliases.db: Invalid argument
This looks like a DB version mismatch... (I'm not a postfix guy)...
Incidentally, this message has not been bounced.
I have to get on a plane in a few hours, and would like not to leave the system in this state for the next week! Understand that one. I'd check the makemap version and postfix version for what DB (DBM) they are using. Somethings not matched right.
LER
-- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Alls well that ends ...
I cured the problem, finally, by deleting all the aliases in my virtual domain setup, which I had created following one of the explanations in the README.POSTFIX file. Of course I was then running Mailman 2.0.13.
If anyone has a better checklist of things to do to setup "postfix virtual domains", please post here and possibly send it to roadstar@verbose.twistedhistory.com - the address I'll be checking for the next week while I'm out of town.
Van
Larry Rosenman wrote:
On Wed, 2002-10-09 at 04:33, G. Armour Van Horn wrote:
I discovered from the /var/log/maillog file that I had a problem with my aliases, and came to figure out that I was editing /etc/postfix/aliases but newaliases was using the /etc/aliases file to create an aliases.db file I now have added all the correct aliases (from bin/genaliases) to the /etc/aliases file, run newaliases, and just in case, copied both to /etc/postfix/. [snip]
Oct 9 02:25:42 virtuoso postfix/qmgr[841]: 8702E2D7B2: from=<vanhorn@whidbey.com>, size=1258, nrcpt=1 (queue active) Oct 9 02:25:42 virtuoso postfix/local[1490]: fatal: open database /etc/postfix/aliases.db: Invalid argumentThis looks like a DB version mismatch... (I'm not a postfix guy)...
Incidentally, this message has not been bounced.
I have to get on a plane in a few hours, and would like not to leave the system in this state for the next week! Understand that one. I'd check the makemap version and postfix version for what DB (DBM) they are using. Somethings not matched right.
LER
-- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
--
Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted@whidbey.com?subject=Subscribe_QOTD
For web hosting and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/
On Sunday, Sep 29, 2002, at 18:23 Canada/Mountain, Brent Rossow wrote:
If anyone has successfully installed MM on Mac OS X, I'd love to get some pointers. Majordomo is working adequately, but I'd like my listserv package to be more than just "adequate." Any help is greatly appreciated!
I built and installed mailman as root, then chmodded the install to mailman.
If you get errors during the make then you need to let us know what THOSE errors are.
-- Adopted kids are such a pain -- you have to teach them how to look like you ... -- Gilda Radner
participants (9)
-
barry＠python.org -
Brent Rossow -
David B. O'Donnell -
G. Armour Van Horn -
Greg Westin -
Larry Rosenman -
LuKreme -
Michael Geary -
Peter Tattersall