Thanks for the reply. I think you'll it pretty much vanilla. mm_py.cfg ------------------------------------------------------------------------------------------------------------------------------- # -*- python -*-
# Copyright (C) 1998,1999,2000,2001,2002 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 module contains your site-specific settings. From a brand new 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. Mailman's installation procedure will never overwrite your mm_cfg.py file. The complete set of distributed defaults, with documentation, are in the file Defaults.py. In mm_cfg.py, 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 administrator and user interfaces on a per-list or per-user basis. """ ############################################### # Here's where we get the distributed defaults. from Defaults import * import pwd, grp ################################################## # Put YOUR site-specific settings below this line. #ATTENTION: when you use SELinux, mailman might not #be able to recompile the configuration file #due to policy settings. If this is the case, #please run (as root) the supplied "mailman-update-cfg" script ############################################################## # Here's where we override shipped defaults with settings # # suitable for the RPM package. # MAILMAN_UID = pwd.getpwnam('mailman')[2] MAILMAN_GID = grp.getgrnam('mailman')[2] ############################################################## # Set URL and email domain names # # # Mailman needs to know about (at least) two fully-qualified domain # names (fqdn) # # 1) the hostname used in your urls (DEFAULT_URL_HOST) # 2) the hostname used in email addresses for your domain (DEFAULT_EMAIL_HOST) # # For example, if people visit your Mailman system with # "http://www.dom.ain/mailman" then your url fqdn is "www.dom.ain", # and if people send mail to your system via "yourl...@dom.ain" then # your email fqdn is "dom.ain". DEFAULT_URL_HOST controls the former, # and DEFAULT_EMAIL_HOST controls the latter. Mailman also needs to # know how to map from one to the other (this is especially important # if you're running with virtual domains). You use # "add_virtualhost(urlfqdn, emailfqdn)" to add new mappings. # Default to using the FQDN of machine mailman is running on. # If this is not correct for your installation delete the following 5 # lines that acquire the FQDN and manually edit the hosts instead. from socket import * try: fqdn = getfqdn() except: fqdn = 'mm_cfg_has_unknown_host_domains' DEFAULT_URL_HOST = fqdn DEFAULT_EMAIL_HOST = fqdn # Because we've overriden the virtual hosts above add_virtualhost # MUST be called after they have been defined. ############################################################## # Put YOUR site-specific configuration below, in mm_cfg.py . # # See Defaults.py for explanations of the values. # # 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. ----------------------------------------------------------------------------------------------------------------------- mailman.conf ---------------------------------------------------------------------------------------------------------------------- # Directives for the mailman web interface Alias /pipermail/ "/var/lib/mailman/archives/public/" ScriptAliasMatch ^/mailman/([^/]*)(.*)$ "/usr/lib/mailman/cgi-bin/$1.cgi$2" # For the archives <Directory "/var/lib/mailman/archives/public"> Options +FollowSymLinks Order allow,deny Allow from all </Directory> ----------------------------------------------------------------------------------------------------------------------- On 5/9/2012 4:07 PM, Mark Sapiro wrote: > Dennis Putnam wrote: >> I've made the decision to abandon Mandriva and migrate to Centos. I have >> mailman up an running (sort of) but now have the opposite problem. This >> is a vanilla install of Apache so the only config file is mailman.conf >> at this time. The cgi extension does not exist, in cgi-bin, on this >> installation of mailman. However, apache is looking for <command>.cgi. I >> don't understand why this is a problem out of the box. Shouldn't a >> vanilla install have this configured correctly? In any case what is the >> correct way to configure this? Thanks. > > Please post /etc/httpd/conf.d/mailman.conf and /etc/mailman/mm_cfg.py > or /usr/lib/Mailman/mm_cfg.py (I think one will be a symlink to the > other). >
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------ 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