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