[Mailman-Users] Creating a new list fails

[LuKreme]

$ bin/newlist -l en --urlhost=mailman.covisp.net --emailhost=kreme.com hgt-***@kreme.com
***@kreme.com
Initial hgt-school password:
Create a new, unpopulated mailing list.

Usage: bin/newlist [options] [listname [listadmin-addr [admin-
password]]]

[ bunch of stuff]

Illegal list name: hgt-***@akane

(akane is the hostname of the local machine. I have existing lists at http://mailman.covisp.net/mailman/admin
but none are public)

[Mark Sapiro]

Post by LuKreme
Create a new, unpopulated mailing list.
Usage: bin/newlist [options] [listname [listadmin-addr [admin-
password]]]
[ bunch of stuff]

The short answer is DEFAULT_EMAIL_HOST must be a fully qualified doman
name.

The underlying issue is the MailList.Create() method as called by
bin/newlist validates the list name by checking that
***@DEFAULT_EMAIL_HOST is a valid email address. This check in
turn requires at least one dot '.' in the domain part.

[LuKreme]

Post by Mark Sapiro

Post by LuKreme
$ bin/newlist -l en --urlhost=mailman.covisp.net --
Create a new, unpopulated mailing list.
Usage: bin/newlist [options] [listname [listadmin-addr [admin-
password]]]
[ bunch of stuff]

The short answer is DEFAULT_EMAIL_HOST must be a fully qualified doman
name.

kreme.com _IS_ a fqdn. Or are we talking about a setting somwhere
else? I do have several lists up and running, but they were all
created years ago and have been pretty much left alone. If I trey to
create a list via the web interface I get a different error:

Error: Unknown virtual host: mailman.covisp.net

Post by Mark Sapiro
The underlying issue is the MailList.Create() method as called by
bin/newlist validates the list name by checking that

So I need to create the listname aliases before the list is created?

Post by Mark Sapiro
This check in
turn requires at least one dot '.' in the domain part.

I which domain part? My mm_cfg.py is very simple:

###############################################
# Here's where we get the distributed defaults.

from Defaults import *

##################################################
# Put YOUR site-specific settings below this line.

VERP_CONFIRMATIONS = Yes
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = 1
ADMIN_MEMBER_CHUNKSIZE = 100
OWNERS_CAN_ENABLE_PERSONALIZATION = Yes
ADMINDB_PAGE_TEXT_LIMIT = 4096
OWNERS_CAN_DELETE_THEIR_OWN_LISTS = Yes
HOLD_MESSAGES_AS_PICKLES = No

[LuKreme]

OK, I fixed this by editing Defaults.py

[LuKreme]

I managed to fix this by editing Defaults.py

DEFAULT_EMAIL_HOST = 'mail.covisp.net'
DEFAULT_URL_HOST = 'mailman.covisp.net'

Everything seems to work as it did before. Yay!

(both values were set to 'akane' before, which is an alias for the
machine)

[Mark Sapiro]

LuKreme <***@kreme.com>
Date: Sat, 30 May 2009 14:55:44 -0600

Post by LuKreme

Post by Mark Sapiro

Post by LuKreme
$ bin/newlist -l en --urlhost=mailman.covisp.net --
Create a new, unpopulated mailing list.
Usage: bin/newlist [options] [listname [listadmin-addr [admin-
password]]]
[ bunch of stuff]

The short answer is DEFAULT_EMAIL_HOST must be a fully qualified doman
name.

kreme.com _IS_ a fqdn. Or are we talking about a setting somwhere
else?

Yes, and this is really a bug in newlist in that you supplied an email
host, but it didn't put it in the initial Create() method call, so
create uses DEFAULT_EMAIL_HOST (from Defaults.py or mm_cfg.py) as the
domain to validate the list posting address. This setting is

DEFAULT_EMAIL_HOST = 'akane'.

Post by LuKreme
I do have several lists up and running, but they were all
created years ago and have been pretty much left alone. If I trey to
Error: Unknown virtual host: mailman.covisp.net

This is because you went to the create page via a URL with hostname
mailman.covisp.net, and that name is not in your VIRTUAL_HOSTS
dictionary. See below.

Post by LuKreme

Post by Mark Sapiro
The underlying issue is the MailList.Create() method as called by
bin/newlist validates the list name by checking that

So I need to create the listname aliases before the list is created?

No. the check is for 'syntactically valid', not 'deliverable'

Post by LuKreme

Post by Mark Sapiro
This check in
turn requires at least one dot '.' in the domain part.

###############################################
# Here's where we get the distributed defaults.
from Defaults import *
##################################################
# Put YOUR site-specific settings below this line.
VERP_CONFIRMATIONS = Yes
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = 1
ADMIN_MEMBER_CHUNKSIZE = 100
OWNERS_CAN_ENABLE_PERSONALIZATION = Yes
ADMINDB_PAGE_TEXT_LIMIT = 4096
OWNERS_CAN_DELETE_THEIR_OWN_LISTS = Yes
HOLD_MESSAGES_AS_PICKLES = No

You also want (guessing based on above)

DEFAULT_URL_HOST = 'mailman.covisp.net'
DEFAULT_EMAIL_HOST = 'kreme.com'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

because the Defaults.py entries for these are not correct, and possibly
more add_virtualhost('www.example.com', 'example.com') entries if you
have other domains.

[Mark Sapiro]

Post by LuKreme
I managed to fix this by editing Defaults.py
DEFAULT_EMAIL_HOST = 'mail.covisp.net'
DEFAULT_URL_HOST = 'mailman.covisp.net'

See the FAQ at <http://wiki.list.org/x/fIA9> for why you should make
this change in mm_cfg.py, not Defaults.py.

It's a bit more complicated in this case than just adding the above two
lines to mm_cfg.py (although that would suffice for the newlist issue)
because those settings are used in an additional definition in
Defaults.py so you also need

VIRTUAL_HOSTS.clear()

to undo what was done in Defaults.py, and

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

to redo it with the correct values.

[LuKreme]

Post by Mark Sapiro
See the FAQ at <http://wiki.list.org/x/fIA9> for why you should make
this change in mm_cfg.py, not Defaults.py.

OK, but the settings in Defaults.py were from 2007, when the machine
was named 'akane' and it had an alias as 'mail'. Now the machine is
named mail and 'akane' is just a DNS alias. I went ahead and added the
lines to mm_cfg.py so they won't get blow away, but don't see any
reason to restore the lines in Defaults.py as it will be overwritten
when I finally get around to updating.

[Mark Sapiro]

Post by LuKreme

Post by Mark Sapiro
See the FAQ at <http://wiki.list.org/x/fIA9> for why you should make
this change in mm_cfg.py, not Defaults.py.

OK, but the settings in Defaults.py were from 2007, when the machine
was named 'akane' and it had an alias as 'mail'. Now the machine is
named mail and 'akane' is just a DNS alias. I went ahead and added the
lines to mm_cfg.py so they won't get blow away, but don't see any
reason to restore the lines in Defaults.py as it will be overwritten
when I finally get around to updating.

That's fine. You now have the correct settings in mm_cfg.py so it
doesn't matter what's in Defaults.py for these. What will be in
Defaults.py after an upgrade depends on how you upgrade. If you
upgrade from our source, you set these things in Defaults.py with the
--with-urlhost= and --with-mailhost= options to configure.