Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: chaloner on October 13, 2004, 04:30:50 AM
-
I had tried a few times to make this go and never had too much luck with it. I decided to give it another stab, and I finally got it to work.
Easy way to do this is;
1) Add a DNS entry for 'lists.yourdomain.com' with your DNS provider.
2) Add 'lists.yourdomain.com' as a Virtual Domain using the server-manager.
Untar the package with;
# tar -xvf mailman.tar
Install with;
# rpm -Uvh *.rpm
Update the mailman site password with;
# /opt/mailman/bin/mmsitepass
Fire it up with;
http://lists.yourdomain.com/mailman
Access the main "mailman" list;
http://lists.yourdomain.com/mailman/admin/mailman
Tarball Package contains;
e-smith-mailman-1.0-7.noarch.rpm
htdig-3.1.6-6.i386.rpm
mailman-2.1.3-1.i386.rpm
mhonarc-2.6.8-1.noarch.rpm
-
I have renamed the tarball to mailman-2.1.3.tar and you can find it at ftp://chaloner.ca.
Have a nice day,
Chaloner Hale
-
This file is the one we need to figure out;
/etc/e-smith/templates/opt/mailman/Mailman/mm_cfg.py/40hostname
Contents;
##############################################################
# IMPORTANT! - You must set these 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 "yourlist@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_URL_HOST = 'lists.{ $DomainName }'
DEFAULT_EMAIL_HOST = 'lists.{ $DomainName }'
# Because we've overriden the virtual hosts above add_virtualhost
# MUST be called after they have been defined.
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
Chaloner Hale
-
There is another way to modify this beast. If you prefer not to use "lists.yourdomain.com" then you need to modify this file;
First stop mailman;
# service mailman stop
/etc/e-smith/templates/opt/mailman/Mailman/mm_cfg.py/40hostname
Just edit out the 2 occurences of "lists.".
Original file modifed;
##############################################################
# IMPORTANT! - You must set these 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 "yourlist@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_URL_HOST = 'lists.{ $DomainName }'
# DEFAULT_EMAIL_HOST = 'lists.{ $DomainName }'
DEFAULT_URL_HOST = '{ $DomainName }'
DEFAULT_EMAIL_HOST = '{ $DomainName }'
# Because we've overriden the virtual hosts above add_virtualhost
# MUST be called after they have been defined.
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
Then re-expand the template with;
# /sbin/e-smith/expand-template /opt/mailman/Mailman/mm_cfg.py
And then start mailman;
# service mailman start
And that should do it.
Chaloner Hale
-
Hi Chaloner,
This install works beautifully but...
You need to reboot after the install. I had a lot of trouble cos I expected it to just work, and it didn't. Only when I rebooted did all the emails come through!
Also, how do I upgrade to 2.1.6 - the current Mailman version?
And, how do I delete the original "Mailman" list? I will be establishing my own named lists, and not using the original one. I have changed the flag so that the list owner can delete the list, and I can for lists which I create, but not for the original list.
All help is greatly appreciated :-)
Hamish
Melbourne, AU
-
Hi again Chaloner,
Got another small problem....
When I send out emails to the list, I get the list page in the footer as being the following:
http://server/mailman/listinfo/<list-name>
The hostname of my server, is obviously "server", but where is the host_name bit gone? I have had a look at the /opt/mailman/Mailman/mm_cfg.py file, and can see that the DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST are set correctly. Why do they not show up in the footer correctly?
(PS: The email address that appears in the footer is correct)
Thanks in advance,
Hamish
Melbourne, AU
-
Hi,
I can't add a new DNS, so I changed the following files:
I changed the /opt/mailman/Mailman/mm_cfg.py file:
DEFAULT_URL_HOST = 'focus.demon.nl'
DEFAULT_EMAIL_HOST = 'focus.demon.nl'
# Because we've overriden the virtual hosts above add_virtualhost
# MUST be called after they have been defined.
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
and I changed the /etc/e-smith/templates/opt/mailman/Mailman/mm_cfg.py/40hostname file:
DEFAULT_URL_HOST = '{ $DomainName }'
DEFAULT_EMAIL_HOST = '{ $DomainName }'
# Because we've overriden the virtual hosts above add_virtualhost
# MUST be called after they have been defined.
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
The list runs. I can add a new list, add members and so on.
When I tried to restart Mailman with:
service mailman restart
I get the message:
[root@mlkserver root]# service mailman restart
id
[Errno 2] No such file or directory: '/opt/mailman/data/master-qrunner.pid'
Is qrunner even running?
and when I try to send a email to the list it says the email-address doesn't exists.
What could be wrong?