Creating a new list fails
$ bin/newlist -l en --urlhost=mailman.covisp.net --emailhost=kreme.com hgt-school@kreme.com kreme@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-school@akane
(akane is the hostname of the local machine. I have existing lists at http://mailman.covisp.net/mailman/admin but none are public)
-- No one ever thinks of themselves as one of Them. We're always one of Us. It's Them that do the bad things.
LuKreme wrote:
$ bin/newlist -l en --urlhost=mailman.covisp.net --emailhost=kreme.com hgt-school@kreme.com kreme@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-school@akane
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 LISTNAME@DEFAULT_EMAIL_HOST is a valid email address. This check in turn requires at least one dot '.' in the domain part.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 30-May-2009, at 12:53, Mark Sapiro wrote:
LuKreme wrote:
$ bin/newlist -l en --urlhost=mailman.covisp.net -- emailhost=kreme.com hgt-school@kreme.com kreme@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-school@akane
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
The underlying issue is the MailList.Create() method as called by bin/newlist validates the list name by checking that LISTNAME@DEFAULT_EMAIL_HOST is a valid email address.
So I need to create the listname aliases before the list is created?
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
-- The person on the other side was a young woman. Very obviously a young woman. There was no possible way that she could have been mistaken for a young man in any language, especially Braille.
LuKreme <kremels@kreme.com> Date: Sat, 30 May 2009 14:55:44 -0600 To: mailman-users@python.org
On 30-May-2009, at 12:53, Mark Sapiro wrote:
LuKreme wrote:
$ bin/newlist -l en --urlhost=mailman.covisp.net -- emailhost=kreme.com hgt-school@kreme.com kreme@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-school@akane
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'.
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
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.
The underlying issue is the MailList.Create() method as called by bin/newlist validates the list name by checking that LISTNAME@DEFAULT_EMAIL_HOST is a valid email address.
So I need to create the listname aliases before the list is created?
No. the check is for 'syntactically valid', not 'deliverable'
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
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 <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 30-May-2009, at 14:55, LuKreme wrote:
I which domain part? My mm_cfg.py is very simple:
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)
-- MEGAHAL: within my penguin lies a torrid story of hate and love.
LuKreme wrote:
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.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 30-May-2009, at 15:42, Mark Sapiro wrote:
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.
-- Love seekest only self to please, To bind another to its delight Joys in another's loss of ease And builds a hell in Heaven's despite!
LuKreme wrote:
On 30-May-2009, at 15:42, Mark Sapiro wrote:
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.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
LuKreme -
Mark Sapiro