[Mailman-Users] Snow Leoparrd (MacOS X 10.6) CLIENT installation steps for Mailman (CORRECTED)

[Larry Stone]

Sorry to take up list space resending this but I caught an error in the
Apache configuration section of this (some additional lines needed in Step
4b due to increased security in Apache2 vs. original Apache).

===

In September 2004, I posted on this topic with instructions for installing
mailman on the client version of MacOS X 10.3 (Panther). Later, I updated it
for OS X 10.4 (Tiger) as well as notes (but not full instructions) for OS X
10.5 (Leopard). Just recently, I did a test installation on my 10.6 (Snow
Leopard) laptop in anticipation of a new desktop to become my new server
later this year. In all cases, these were the CLIENT version of Mac OS X
(Mac OS X Server comes with a bastardized version of Mailman).

So here, once again for purposes of getting it in the archives, are my
instructions for installing mailman on MacOS X 10.6.x. With this version,
I've made some changes to bring the mailman home directory in line with
Mailman "standards" (i.e. using /usr/local/mailman instead of
/Applications/mailman), improved the system startup procedure, and some
other miscellaneous cleanup.

=

Snow Leopard (MacOS X 10.6) installation steps for Mailman

This document is based on my experience installing Mailman 2.1.4 on MacOS X
10.3 (Panther) and subsequently upgrading to Tiger (Mac OS X 10.4) and to
mailman 2.1.6 and now to Snow Leopard (Mac OS X 10.6) with mailman 2.1.13.
It is largely based on Kathleen Webb's document on installing Mailman and
Sendmail on MacOS X 10.2 (Jaguar)
()
which contains some information on tools that can be useful that will not be
repeated here.

This guide assumes that you have Postfix (which comes with Snow Leopard)
already configured and operating, that you have the built-in web server
running (if not, enable it by going to the Sharing pane of System
Preferences and turning on Web Sharing), and that you are familiar with the
Unix shell and basic text editing from the shell (vi or emacs). It is
intended to help you get Mailman installed. It does not deal with actually
using Mailman as there are plenty of other sources of help for that.

This is based on a new install on a Snow Leopard system that has never had
Mailman on it before. Questions are best asked through the mailman-users
mailing list.


Step 1) Collect all the things you need.

a) You need to download and decompress the Mailman software. (The
installation instructions are in step 3.) Download the software from:
http://www.list.org/
Download the latest 2.1.x.tgz which is a gzip compressed tar file (.tgz).
Just leave it for now and we'll expand it later.

b) You need to be an administrator of your computer. If you do not have
administrator privileges, you will not be able to do this.

c) Python comes pre-installed on your computer. It is already
functioning and ready for use by Mailman. (To verify you have Python, open
the Terminal application. at the  % prompt, type:
sudo Python -V
and then hit the enter/return key. You'll be prompted for your password.
When you enter it, the terminal will respond with the Python version.

d) Apache web server software comes pre-installed on your computer and has
already been configured and is running.

e) Postfix is already installed on your computer but is not running by
default. You will need to get Postfix configured and started but how to do
that is beyond the scope of this document. An excellent way of getting
Postfix up and running, along with a POP and IMAP server, is with MailServe
Snow . Note that
MailServe Snow is not free - as all the underlying software is freely
available, you're paying for the configuration and installation tool, not
the underlying software.

f) You may need to know how to get into hidden subdirectories. In the
Finder, use the Go menu and choose Go to Folder. Type in the path to the
hidden folder you need to open.

g) You may need to know how to make a new user. You use the System
Preferences application [from the Apple menu]. Use the Accounts panel in the
System section.

h) You need to install the Developer Tools that came with your Snow Leopard
disks or several of the steps won't work.



>From this point on, we will do everything in Terminal and as root. So open
Terminal and then become root by typing 'sudo su'. You will be prompted for
your password and then get a # as a prompt.

Step 2) Verify the user and group needed to run Mailman.

All versions of OS X since at least Panther have come with the needed users
and groups already created. We will be using _mailman for mailman and _www
for the webserver.

To verify they're there, type 'grep _mailman /etc/group' and 'grep _mailman
/etc/passwd. Both should return one line starting with _mailman:*:78:. If
they do, they exist. You can repeat that with _www and the number you see

Re: [Mailman-Users] Block reply to all

[Mark Sapiro]

On 5/1/2010 2:27 PM, Schwartz, Robert - IS wrote:
> That seems to be the issue.  When I looked at the email from my work
> email I saw the header text that was added, but my message was added
> as an attachment.  I like the header text to be added and the message
> not to appear as an attachment.  If there is no way to do this, I'll
> just live with it.


As it says in the FAQ at  (option 2), if
the incoming post is plain text only or if the list's content filtering
is set to remove all non-plain text parts, the msg_header text will be
prepended to the plain text message body. Otherwise the msg_header text
will be added as a separate MIME part (attachment).

I may seem obtuse about this, but it would help me to help you if you
explained in terms of simple scenarios what it is you want.

For example, user x sends a post to list y. user z receives the post
from the list.

a) I want user z to only be able to reply to user x and otherwise to be
required to send a new, original, non-reply message to the list, or
b) I want user z to be able to reply to user x only or to the list only,
but not to both, or
c) I want user z to be able to reply only to the list and not directly
to user x at all.

Those are only examples, but I would like to know what you would like to
have happen.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Block reply to all

[Schwartz, Robert - IS]

That seems to be the issue.  When I looked at the email from my work email I 
saw the header text that was added, but my message was added as an attachment.  
I like the header text to be added and the message not to appear as an 
attachment.  If there is no way to do this, I'll just live with it.

Robert P. Schwartz
CAS, Inc.
A wholly owned subsidiary of ITT Corporation
100 Quality Circle
Huntsville, AL 35806

Phone: 256.922.4203
Fax:  256.922.4243

E-mail:  robert.schwa...@itt.com


-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Saturday, May 01, 2010 4:23 PM
To: rpsch...@knology.net; Schwartz, Robert - IS; 'Terri Oda'; 
mailman-users@python.org
Subject: RE: [Mailman-Users] Block reply to all

Robert P. Schwartz wrote:

>I tried this an I'm not getting any header.  I tried it for non-digest
>options and digest options.


If you put text in msg_header and saved that change and then sent a
post to that list and the post as received from the list didn't
contain the header text, it may be because the post to the list was
multipart or HTML and the header was added as a separate MIME part
which your mail client doesn't display.

See the FAQ at  for more on this.

If the header is not added in any form at all, I cannot explain why. Do
messages from your lists contain the default (or other) msg_footer?

--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan


This e-mail and any files transmitted with it may be proprietary and are 
intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this e-mail in error please notify the sender.
Please note that any views or opinions presented in this e-mail are solely 
those of the author and do not necessarily represent those of ITT Corporation. 
The recipient should check this e-mail and any attachments for the presence of 
viruses. ITT accepts no liability for any damage caused by any virus 
transmitted by this e-mail.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] get list of users

[Robert P. Schwartz]

This did exactly what I needed.  Thanks. If I want others to be able to do
this, will they need to download
http://www.python.org/ftp/python/2.6.5/python-2.6.5.msi?


-Original Message-
From: mailman-users-bounces+rpschwar=knology@python.org
[mailto:mailman-users-bounces+rpschwar=knology@python.org] On Behalf Of
Mark Sapiro
Sent: Friday, April 30, 2010 11:34 PM
To: Schwartz, Robert - IS; mailman-users@python.org
Subject: Re: [Mailman-Users] get list of users

Schwartz, Robert - IS wrote:
>
>I do not know how to do this from a cmd prompt.  The usage says:
>
>Usage: %(PROGRAM)s [options] hostname listname password
>
>Do I do this from a cmd prompt.  What would be the syntax for my site?


You first need to download and install Python on your Windows XP box.
The windows installer for Python 2.6.5 is at


Then, if your list's web admin interface were for example
, you would at a cmd
prompt type

cd (the folder where you saved mailman-subscribers.py)
python mailman-subscribers.py -c -o output-file.csv www.example.com
listname password

The last line starting with python and ending with password is all one
line, not wrapped as here. output-file.csv is the name of the file to
receive the csv and password is the list's admin password.

You might also need to use the -u option if the admin interface URL is
not of the above form.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/rpschwar%40knology.net

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.801 / Virus Database: 271.1.1/2846 - Release Date: 04/30/10
13:27:00

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Block reply to all

[Mark Sapiro]

Robert P. Schwartz wrote:

>I tried this an I'm not getting any header.  I tried it for non-digest
>options and digest options.


If you put text in msg_header and saved that change and then sent a
post to that list and the post as received from the list didn't
contain the header text, it may be because the post to the list was
multipart or HTML and the header was added as a separate MIME part
which your mail client doesn't display.

See the FAQ at  for more on this.

If the header is not added in any form at all, I cannot explain why. Do
messages from your lists contain the default (or other) msg_footer?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Block reply to all

[Robert P. Schwartz]

I tried this an I'm not getting any header.  I tried it for non-digest
options and digest options.

-Original Message-
From: mailman-users-bounces+rpschwar=knology@python.org
[mailto:mailman-users-bounces+rpschwar=knology@python.org] On Behalf Of
Mark Sapiro
Sent: Friday, April 30, 2010 11:06 PM
To: Schwartz, Robert - IS; Terri Oda; mailman-users@python.org
Subject: Re: [Mailman-Users] Block reply to all

Schwartz, Robert - IS wrote:

>Maybe I can put a message at the top of every mail being send "Do not do a
reply all".  How do you do this?


The list admin interface Non-digest options -> msg_header

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/rpschwar%40knology.net

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.801 / Virus Database: 271.1.1/2846 - Release Date: 04/30/10
13:27:00

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org