[Mailman-Developers] on the subject of fix_url, list creation with @ is non-intuitive..

Bob Puff bob at nleaudio.com
Mon Oct 18 02:43:48 CEST 2004

Hmm I guess I still don't get why "name at domain" is confusing, because that
-is- the posting address of the list!  If you want to add another field for
domain, that's fine; but I think the current behaviour makes sense.

Also, as I stated before, the web-based create should take the hostname used
as the domain name.  It currently forces one domain.


---------- Original Message -----------
From: Terri Oda <terri at zone12.com>
To: Joe Rhett <jrhett at meer.net>
Cc: mailman-developers at python.org
Sent: Sun, 17 Oct 2004 19:02:44 -0400
Subject: Re: [Mailman-Developers] on the subject of fix_url, list creation
with @ is non-intuitive..

> On Oct 11, 2004, at 11:10 PM, Joe Rhett wrote:
> > On Mon, Oct 11, 2004 at 11:47:37AM -0700, Mark Sapiro wrote:
> >> Well, the help for newlist (bin/newlist --help) is pretty clear that
> >> the notation name at domain is not the e-mail address of the list but
> >> just a way of specifying the web domain.
> >
> > Right, but it still seems counter-intuitive to me.
> I'm with Joe on this one -- just because it's a documented oddity 
> doesn't make it the right way to do things.
> Is there any particular reason we couldn't change the newlist script 
> to accept "name domain" instead of "name at domain" ?  It's just that 
> much less confusing if we don't have this thing that looks like an 
> email address but isn't.  I can't believe anyone's that attached to 
> the confusing syntax, and the increased usability seems worth the 
> small patch this'll take.
>   Terri
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers at python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
> Unsubscribe:
------- End of Original Message -------

More information about the Mailman-Developers mailing list