Well, the main problem is not the wizard per se. The problem is that in most if not all LISTSERV list header keywords, the comma means "next value/parameter follows". So when you do something like the following (even from the manual edit window): Owner= [log in to unmask] (Joe Schlabotnik, 999-999-9999) LISTSERV internally tries to parse this as two list owners, i.e., Owner= [log in to unmask] (Joe Schlabotnik Owner= 999-999-9999) The parentheses don't have any special meaning to LISTSERV. You could just as easily define this as Owner= [log in to unmask] Joe Schlabotnik - 999-999-9999 because LISTSERV stops reading the email address at the space and treats the rest to the end of the line (or to the next comma) as a "real name" field. As has already been noted, the way to get around this is to use a different character for the separator, or (my preference) don't use a separator at all: Owner= [log in to unmask] (Joe Schlabotnik 999-999-9999) Nathan At 12:28 PM 8/24/2010 -0500, James Morrill wrote: >We don't have many owners that change their lists anyway but when someone >tries to use the wizzard we just tell them to change the comma to a hyphen >and that works. We (LISTSERV help staff) are changing them as we find them >(I don't ever use the wizzard anyway, a list owner found the comma problem >for us:-) and it's not been much of an issue here. > >-- > James Morrill office: HL 11, 785-532-4909 www-personal.ksu.edu/~james > > There can be no happiness if the things we believe in are different > from the things we do. > >On Tue, 24 Aug 2010, Listserv Manager wrote: > >>Wizard doesn't like our Owner Information >> >>We just upgraded to 16.0 from 14.4, and I didn't pick up what is probably going to turn into a major problem for us. Many of our owner lines are of the form: >> >>Owner= [log in to unmask]<mailto:[log in to unmask]> (Joe Schlabotnik, 999-999-9999) >> >>Manual edit is quite happy, but the wizard is not. The parser sees the comma, and whatever follows (in this case, 999-999-9999) becomes another owner! That is invalid, and when saving, throws an error. We have hundreds (probably over a thousand) in this format and have been that way "forever." School is about to open and lots of people are going to encounter this error- a problem for them and a public relations disaster for Listserv. Yeah, we should have picked this up earlier, but we were in a bit of a hurry to get upgraded, being so far behind. >> >>Any ideas/suggestions? Thanks in advance for your response. >>Nelson >> >>Nelson R. Pardee, Support Analyst, Information Technology and Services >>Syracuse University, CST 1-205, Syracuse, NY 13244 (315) 443-1079