[Mailman-Users] Re: Mailman private archives issue.

[Andrea Mennucci]

hi 


as lonk as I can tell, I am able to use public archives
(problem is, I have none... but when I had, I was able to)


you have to add
 
 Alias /pipermail/ /var/lib/mailman/archives/public/
 
to /etc/apache/srm.conf 

I am sending you my file mm_cfg.py
as well as the help that the Debian mantainer
wrote 

On Tue, Nov 14, 2000 at 01:05:16PM -0100, Rodrigo Moya wrote:
> Hi Andrea,
> 
> > 
> > I am  cross posting this answer to mailman-users
> > 
> > On Fri, Nov 10, 2000 at 11:02:47PM +0000, Vikas Gupta wrote:
> > > Hello,
> > > I found youur posting on the Mailman-Users archives. YOu describe not being 
> > > able to see private archives on the web. I am also having the same problem. 
> > > I was wondering if you had found a solution and could share it with me.
> > > 
> > >
> > 
> > my problem was due to the way mailman is
> > installed in Debian/GNU Linux
> > 
> > I have solved the problem
> > 
> > I corrected in the file /etc/mailman/mm_cfg.py 
> > 
> > in this way:
> > 
> > - PRIVATE_ARCHIVE_URL = '/mailman/private'
> > + PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private'
> > 
> and what about public archives? I mean, I can't make them work. In my mm_cfg.py
> file, I've got:
> 
> PUBLIC_ARCHIVE_URL = '/pipermail'
> PRIVATE_ARCHIVE_URL = '/mailman/private'
> 
> but /pipermail is not a valid path, I get always this error. I've also tried
> changing it to /mailman/public but nothing, they still don't work.
> 
> What setting have you got for the PUBLIC_ARCHIVE_URL thing?
> 
> cheers
> 

-- 
Andrea C. Mennucci,   Scuola Normale Superiore, Pisa, Italy
-------------- next part --------------
# -*- python -*-

# Copyright (C) 1998 by the Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
# 
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
# 
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software 
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.


"""This is the module which takes your site-specific settings.

>From a raw distribution it should be copied to mm_cfg.py.  If you
already have an mm_cfg.py, be careful to add in only the new settings
you want.  The complete set of distributed defaults, with annotation,
are in ./Defaults.  In mm_cfg, override only those you want to
change, after the

  from Defaults import *

line (see below).

Note that these are just default settings - many can be overridden via the
admin and user interfaces on a per-list or per-user basis.

Note also that some of the settings are resolved against the active list
setting by using the value as a format string against the
list-instance-object's dictionary - see the distributed value of
DEFAULT_MSG_FOOTER for an example."""


#######################################################
#    Here's where we get the distributed defaults.    #

from Defaults import *

##############################################################
# Put YOUR site-specific configuration below, in mm_cfg.py . #
# See Defaults.py for explanations of the values.	     #

DEFAULT_HOST_NAME = 'Tonelli.sns.it'
DEFAULT_URL       = 'http://Tonelli.sns.it/cgi-bin/mailman'
DELIVERED_BY_URL  = '/doc/mailman/images/mailman.jpg'

MAILMAN_OWNER     = 'mailman-owner@%s' % DEFAULT_HOST_NAME

PUBLIC_ARCHIVE_URL = '/pipermail'
PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private'

USE_ENVELOPE_SENDER = 0

# Note - if you're looking for something that is imported from mm_cfg, but you
# didn't find it above, it's probably in Defaults.py.
-------------- next part --------------
Notes for the debian mailman package.
=====================================

You can access the web interface of mailman on
http://<hostname>/cgi-bin/mailman/listinfo
This may not work if your webserver does not allow symlinks in the cgi-bin
directory. In this case (or in case you want to access mailman thru a
shorter URL) you should add something like the following to your webserver
configuration (this line is for apache):
ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/
In this case you need to set the DEFAULT_URL in /etc/mailman/mm_cfg.py
to http://<hostname>/mailman/ for the cookie authentication code to work.

The public archives are located in /var/lib/mailman/archives/public,
you can create a symlink from /var/www if you like, or create an alias like
the following:
Alias /pipermail/ /var/lib/mailman/archives/public/

You can create new lists with the newlist command (you have to add the
aliases it needs by hand to /etc/aliases or the corresponding database
because mailman can not know about configuration of all MTA's, but newlist 
tells you about the alias it needs).

Additionally you need a mailman-owner alias pointing probably to you.

For users of exim: if you want to use the /etc/aliases file for mailman
aliases, you'll need to specify a user=list line or something like that in
the system_aliases director.

If a broken image shows on your mailman html pages, it is probably because
you don't have the /doc/ alias enabled in your webserver. Copy the
/usr/share/doc/mailman/images/mailman.jpg to a place where your webserver can 
access it and modify the DELIVERED_BY_URL option accordingly in your 
mm_cfg.py (the default is '/doc/mailman/images/mailman.jpg').

Gergely Madarasz <gorgo at sztaki.hu>