[Mailman-Users] Creating a new list fails
LuKreme
kremels at kreme.com
Sat May 30 22:55:44 CEST 2009
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 at kreme.com
>> kreme at 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 at 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 at 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.
More information about the Mailman-Users
mailing list