HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   General (http://www.howtoforge.com/forums/forumdisplay.php?f=25)
-   -   ISPConfig 3 + Mailman + multiple servers (http://www.howtoforge.com/forums/showthread.php?t=57051)

dghvoip 24th April 2012 22:06

ISPConfig 3 + Mailman + multiple servers
 
Hi ISPC community,

I managed to install ISPC using the multi server howto on Squeeze as follows, tweaking the installer_base.inc.php file.

1 DB Server
1 MX Server
1 ISPC+Web+FTP Server
1 DNS Server

I installed mailman and related stuff, I changed mm_cfg.py

Code:

# cat /etc/mailman/mm_cfg.py
# -*- python -*-

# Copyright (C) 1998,1999,2000 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., 51 Franklin Street, Fifth Floor, Boston, MA
# 02110-1301 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.            #

#-------------------------------------------------------------
# The name of the list Mailman uses to send password reminders
# and similar. Don't change if you want mailman-owner to be
# a valid local part.
MAILMAN_SITE_LIST = 'mailman'

#-------------------------------------------------------------
# If you change these, you have to configure your http server
# accordingly (Alias and ScriptAlias directives in most httpds)
DEFAULT_URL_PATTERN = 'http://%s:64000/cgi-bin/mailman/'
PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private'
IMAGE_LOGOS        = '/images/mailman/'

#-------------------------------------------------------------
# Default domain for email addresses of newly created MLs
DEFAULT_EMAIL_HOST = 'mydomain.com'
#-------------------------------------------------------------
# Default host for web interface of newly created MLs
DEFAULT_URL_HOST  = 'mydomain.com'
#-------------------------------------------------------------
# Required when setting any of its arguments.
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

#-------------------------------------------------------------
# The default language for this server.
DEFAULT_SERVER_LANGUAGE = 'en'

#-------------------------------------------------------------
# Iirc this was used in pre 2.1, leave it for now
USE_ENVELOPE_SENDER    = 0              # Still used?

#-------------------------------------------------------------
# Unset send_reminders on newly created lists
DEFAULT_SEND_REMINDERS = 0

#-------------------------------------------------------------
# Uncomment this if you configured your MTA such that it
# automatically recognizes newly created lists.
# (see /usr/share/doc/mailman/README.Exim4.Debian or
# /usr/share/mailman/postfix-to-mailman.py)
# MTA=None  # Misnomer, suppresses alias output on newlist

#-------------------------------------------------------------
# Uncomment if you use Postfix virtual domains (but not
# postfix-to-mailman.py), but be sure to see
# /usr/share/doc/mailman/README.Debian first.
MTA='Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom1.com', 'dom2.com']
#-------------------------------------------------------------
# Uncomment if you want to filter mail with SpamAssassin. For
# more information please visit this website:
# http://www.jamesh.id.au/articles/mailman-spamassassin/
# GLOBAL_PIPELINE.insert(1, 'SpamAssassin')

# Note - if you're looking for something that is imported from mm_cfg, but you
# didn't find it above, it's probably in /usr/lib/mailman/Mailman/Defaults.py.
 root@ispmx1: ~

As you see I changed the DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/' into DEFAULT_URL_PATTERN = 'http://%s:64000/cgi-bin/mailman/' as the MX server is running on another machine as the web server serving the mailing lists, but I have a problem when a mailing list is created on ISPC GUI; first mm_cfg.py is changed back to some defaults I haven't figured out where are they taken from, and when I receive the "Your list has been created" email it contains the DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/' without the :64000 port I created.

I've tweaked the Defaults.py at /var/lib/mailman/data dir and the mm_cfg.py there to reflect my custom setting but they're all changed back to defaults.

I _need_ the confirmation email to arrive with the DEFAULT_URL_PATTERN = 'http://%s:64000/cgi-bin/mailman/'

How do I force ISPC to use my settings and not the defaults?.

Thanks and ISPC rocks.

till 24th April 2012 22:22

The mailman file is available as template in ispconfig so that it can be easily customized. The template is in /usr/local/ispconfig/server/conf/, save the modified copy in the conf-custom directory.

dghvoip 24th April 2012 22:35

Quote:

Originally Posted by till (Post 278137)
The mailman file is available as template in ispconfig so that it can be easily customized. The template is in /usr/local/ispconfig/server/conf/, save the modified copy in the conf-custom directory.

OMG, never thought I'd get a response so quickly, Till Thank you so very much :) Definitely ISPC rocks.

Finally, I've gotta put the modified copy mm_cfg.py.master on my MX server or on the ISPC panel server?, also do I save it as mm_cfg.py.master or just as mm_cfg.py?.

till 24th April 2012 22:53

On the mail sever. Save it as .master file in the conf-custom folder, this ensures that the file does not get overwritten by updates and files in conf-custom have precedence over files in conf.

dghvoip 24th April 2012 23:12

Quote:

Originally Posted by till (Post 278141)
On the mail sever. Save it as .master file in the conf-custom folder, this ensures that the file does not get overwritten by updates and files in conf-custom have precedence over files in conf.

@Till, thank you very much, again, it's now working fine, sending the tight URL.

You can now close this thread, although it'd be nice to have the Howto Updated with this, the multi-server howto, that is.

Now the problem I'm facing is the infamous "User Unknown" issue, and although I've read myriad of related posts I've got no solution for this.

If you can direct me to a solution, it'd be greatly apreciated.

Thanks and keep the great job you do.

till 25th April 2012 10:42

Quote:

You can now close this thread, although it'd be nice to have the Howto Updated with this, the multi-server howto, that is.
This howto exists alreay, please see here:

http://www.howtoforge.com/installing...th-ispconfig-3


All times are GMT +2. The time now is 01:48.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.