Mailman mailing list management users

Mark Sapiro | 2 Jan 2011 21:44

Re: List on a different domain name?

Chris Arnold wrote:

>Just upgraded to 2.1.14 on sles 10 sp3 with oes2. We use to have a domain that mailman was used on, this domain
has since expired. We have a couple of other domains that I would like to use mailman on. Maybe I don't fully
understand mailman but is there a way to use mailman on other domains?

You can use Mailman on any number of domains. The only restriction with
standard GNU Mailman 2.1.x is tha list names must be globally unique
in the installation.

There are 3 components to this.

1) The web server must recognize the appropriate Mailman ScriptAlias,
Alias, etc. directives in all the domains.

2) The MTA must know how to deliver the mail to Mailman for all the
list addresses.

3) There should be appropriate add_virtualhost() directives and for
Postfix integration with Postfix virtual domains, appropriate
POSTFIX_STYLE_VIRTUAL_DOMAINS entries in mm_cfg.py.

See the FAQ at http://wiki.list.org/x/gIA9 for more, particularly the
part about fix_url.

>Internal users can still access the expired domain and access mailman but external users can not access
mailman from valid domains (did that make sense?).

Maybe. You need to make sure the web server will apply the Mailman
related configuration directives to the host(s) yoiu want to use.

(Continue reading)

Chris Arnold | 8 Jan 2011 03:20

Re: List on a different domain name?

>You can use Mailman on any number of domains. The only restriction with
>standard GNU Mailman 2.1.x is tha list names must be globally unique
>in the installation.

>There are 3 components to this.

>1) The web server must recognize the appropriate Mailman ScriptAlias,
>Alias, etc. directives in all the domains.
Here is the vhost mailman section:
ScriptAlias /mailman/ "/usr/lib/mailman/cgi-bin/"

    # "/srv/www/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have one, and where ScriptAlias points to.
    #
    <Directory "/usr/lib/mailman/cgi-bin/">
	AllowOverride None
	Options +ExecCGI -Includes
	Order allow,deny
	Allow from all
    </Directory>

>2) The MTA must know how to deliver the mail to Mailman for all the
>list addresses.
I have created these on the MTA

>3) There should be appropriate add_virtualhost() directives and for
>Postfix integration with Postfix virtual domains, appropriate
>POSTFIX_STYLE_VIRTUAL_DOMAINS entries in mm_cfg.py.
Here is the mm_cfg.py config:
##################################################

(Continue reading)

Mark Sapiro | 8 Jan 2011 03:48

Re: List on a different domain name?

Chris Arnold wrote:

[...]
>Here is the mm_cfg.py config:
>##################################################
># Put YOUR site-specific settings below this line.
>DEFAULT_URL_PATTERN = 'http://%s/mailman/'
>DEFAULT_NNTP_HOST = 'FQDN'
>DEFAULT_EMAIL_HOST = 'mail.domain.com'
>DEFAULT_URL_HOST = 'web.domain.com'
>MTA = 'Postfix'
>POSTFIX_ALIAS_CMD = '/usr/sbin/postalias'
>POSTFIX_MAP_CMD = '/usr/sbin/postmap'
>DELIVERY_MODULE = 'SMTPDirect'
>SMTPHOST = 'localhost'
>SMTPPORT = '25'
>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>#IMAGE_LOGOS = '/mailmanicons/'
>add_virtualhost('web.domain.com', 'mail.domain.com')

This duplicates the preceding add_virtualhost() because the literal
domain names are the same as the values of DEFAULT_URL_HOST and
DEFAULT_EMAIL_HOST.

>POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.domain.com']

If some lists are in the 'lists.domain.com' domain, there should be

add_virtualhost('someotherweb.domain.com', 'lists.domain.com')

(Continue reading)

Chris Arnold | 8 Jan 2011 04:17

Re: List on a different domain name?

CA put forth:

[...]
>>Here is the mm_cfg.py config:
>>##################################################
>># Put YOUR site-specific settings below this line.
>>DEFAULT_URL_PATTERN = 'http://%s/mailman/'
>>DEFAULT_NNTP_HOST = 'FQDN'
>>DEFAULT_EMAIL_HOST = 'mail.domain.com'
>>DEFAULT_URL_HOST = 'web.domain.com'
>>MTA = 'Postfix'
>>POSTFIX_ALIAS_CMD = '/usr/sbin/postalias'
>>POSTFIX_MAP_CMD = '/usr/sbin/postmap'
>>DELIVERY_MODULE = 'SMTPDirect'
>>SMTPHOST = 'localhost'
>>SMTPPORT = '25'
>>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>>#IMAGE_LOGOS = '/mailmanicons/'
>>add_virtualhost('web.domain.com', 'mail.domain.com')

>This duplicates the preceding add_virtualhost() because the literal
>domain names are the same as the values of DEFAULT_URL_HOST and
>DEFAULT_EMAIL_HOST.

>POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.domain.com']

>If some lists are in the 'lists.domain.com' domain, there should be

>add_virtualhost('someotherweb.domain.com', 'lists.domain.com')

(Continue reading)

Chris Arnold | 8 Jan 2011 04:21

Re: List on a different domain name?

CA put forth:

[...]
>>Here is the mm_cfg.py config:
>>##################################################
>># Put YOUR site-specific settings below this line.
>>DEFAULT_URL_PATTERN = 'http://%s/mailman/'
>>DEFAULT_NNTP_HOST = 'FQDN'
>>DEFAULT_EMAIL_HOST = 'mail.domain.com'
>>DEFAULT_URL_HOST = 'web.domain.com'
>>MTA = 'Postfix'
>>POSTFIX_ALIAS_CMD = '/usr/sbin/postalias'
>>POSTFIX_MAP_CMD = '/usr/sbin/postmap'
>>DELIVERY_MODULE = 'SMTPDirect'
>>SMTPHOST = 'localhost'
>>SMTPPORT = '25'
>>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>>#IMAGE_LOGOS = '/mailmanicons/'
>>add_virtualhost('web.domain.com', 'mail.domain.com')

>This duplicates the preceding add_virtualhost() because the literal
>domain names are the same as the values of DEFAULT_URL_HOST and
>DEFAULT_EMAIL_HOST.

>POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.domain.com']

>If some lists are in the 'lists.domain.com' domain, there should be

>add_virtualhost('someotherweb.domain.com', 'lists.domain.com')

(Continue reading)

Mark Sapiro | 8 Jan 2011 08:11

Re: List on a different domain name?

Chris Arnold wrote:

>We have 2 domains that i want to use with mailman, firstdomain.com and seconddomain.net. Should i have
lists.firstdomain.com and lists.seconddomain.net?

Let's say you want the web interfaces at lists.firstdomain.com and
lists.seconddomain.net respectively and the list email addresses to be
like list1 <at> firstdomain.com and list2 <at> seconddomain.net respectively.

Let's further assume that there will be more lists in the
firstdomain.com domain.

Then you would have

DEFAULT_URL_HOST = 'lists.firstdomain.com'
DEFAULT_EMAIL_HOST = 'firstdomain.com'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('lists.seconddomain.net', 'seconddomain.net')

You also want

MTA = 'Postfix'

and if both the mail domains are virtual in Postfix

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['firstdomain.com', 'seconddomain.net']

If one or both email domains is local in Postfix, it wouldn't appear in
the above. If the email addresses should also be in the lists.

(Continue reading)

Chris Arnold | 8 Jan 2011 18:03

Re: List on a different domain name?

CA scratched his head and then wrote:

>We have 2 domains that i want to use with mailman, firstdomain.com and seconddomain.net. Should i have
lists.firstdomain.com and lists.seconddomain.net?

>Let's say you want the web interfaces at lists.firstdomain.com and
lists.seconddomain.net respectively and the list email addresses to be
like list1 <at> firstdomain.com and list2 <at> seconddomain.net respectively.

>Let's further assume that there will be more lists in the
firstdomain.com domain.

>Then you would have

>DEFAULT_URL_HOST = 'lists.firstdomain.com'
>DEFAULT_EMAIL_HOST = 'firstdomain.com'
>VIRTUAL_HOSTS.clear()
>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>add_virtualhost('lists.seconddomain.net', 'seconddomain.net')
This use to work on a domain we had that has expired now and in fact when internal network users goto that old
address, we can still use the old existing list. So i am not sure about the downstream and upstream packages
you referred to.
I have tried everything you have suggested and nothing seems to work. You helped me get the old expired
domain list working and i seem to remember something about split lists or something split. Maybe i should
bring forth the network servers setup:
-mailman host= installed on domain.com which is our webserver (apache2 2.2.3), SLES10 SP3 with OES2 SP3.
Has a separate postfix install that is not used (i seem to remember having to have this postfix instance
send the email to our email server, more on this next).
-email server= separate server with Zimbra 6.0.9 FOSS (this uses postfix) running on SLES10 SP3 with OES2
SP3.The maillist users have been created. I'm not sure what else info to give you from this server.

(Continue reading)

Mark Sapiro | 8 Jan 2011 20:23

Re: List on a different domain name?

On 1/8/2011 9:03 AM, Chris Arnold wrote:

> This use to work on a domain we had that has expired now and in fact
> when internal network users goto that old address, we can still use
> the old existing list. So i am not sure about the downstream and
> upstream packages you referred to.

The upstream product is GNU Mailman as distributed by the Mailman
project. This can be downloaded and installed following our installation
documentation. It is also packaged by value-added resellers/distributors
for "turn-key" installation on their systems (In your case apparently
Novell/SLES). These are referred to as downstream packagers because they
are downstream in the flow from the base or upstream product to you.

Downstream packagers do many things to make a turn-key package that
integrates Mailman with a web server and MTA. They may or may not do
things in ways that we recommend, and except for the most common
packages, we don't have a clue as to what they have done. That's why
your first recourse for support should always be the packager.

> I have tried everything you have
> suggested and nothing seems to work. You helped me get the old
> expired domain list working and i seem to remember something about
> split lists or something split. Maybe i should bring forth the
> network servers setup: -mailman host= installed on domain.com which
> is our webserver (apache2 2.2.3), SLES10 SP3 with OES2 SP3. Has a
> separate postfix install that is not used (i seem to remember having
> to have this postfix instance send the email to our email server,
> more on this next). -email server= separate server with Zimbra 6.0.9
> FOSS (this uses postfix) running on SLES10 SP3 with OES2 SP3.The

(Continue reading)

Chris Arnold | 10 Jan 2011 20:45

Re: List on a different domain name?

On 1/8/2011 9:03 AM, C A wrote:

> This use to work on a domain we had that has expired now and in fact
> when internal network users goto that old address, we can still use
> the old existing list. So i am not sure about the downstream and
> upstream packages you referred to.

>The upstream product is GNU Mailman as distributed by the Mailman
>project. This can be downloaded and installed following our installation
>documentation. It is also packaged by value-added resellers/distributors
>for "turn-key" installation on their systems (In your case apparently
>Novell/SLES). These are referred to as downstream packagers because they
>are downstream in the flow from the base or upstream product to you.

>Downstream packagers do many things to make a turn-key package that
>integrates Mailman with a web server and MTA. They may or may not do
>things in ways that we recommend, and except for the most common
>packages, we don't have a clue as to what they have done. That's why
>your first recourse for support should always be the packager.
I did not install mailman from Novell/SuSE. I downloaded and installed from source.

> I have tried everything you have
> suggested and nothing seems to work. You helped me get the old
> expired domain list working and i seem to remember something about
> split lists or something split. Maybe i should bring forth the
> network servers setup: -mailman host= installed on domain.com which
> is our webserver (apache2 2.2.3), SLES10 SP3 with OES2 SP3. Has a
> separate postfix install that is not used (i seem to remember having
> to have this postfix instance send the email to our email server,
> more on this next). -email server= separate server with Zimbra 6.0.9

(Continue reading)

Return

Return to gmane.mail.mailman.user.

Search Archive

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane