By definition,  having 2 lines saying  'Owner=X' and 'Owner=Y' is  the same as
having  one line  saying 'Owner=X,Y'.  There is  one single  piece of  code in
LISTSERV  that analyzes  keywords,  this piece  of code  does  the merging  of
multiple occurences  of the single keyword,  and nothing else in  LISTSERV can
know how it was originally specified.
 
You said that you switched to a  single line to avoid getting messages to both
addresses. For the reason I just mentioned this cannot work; the proper way is
to tell LISTSERV to send only to  the address you want, for instance by saying
'Errors-To= Owner' and 'Notify= Owner' (or  you could also key in directly the
address you want  the messages sent to). 'Owner' means  'only the first person
in the  OWNER keyword', whereas 'Owners'  means 'all the people  listed in the
OWNER  keyword'; the  default  values are  generally 'OwnerS',  so  as not  to
confuse the users in case the owner list is reordered.
 
Finally the cause of  your problem is the extra blank after  the comma in your
'Owner='  field, which  tells LISTSERV  the rest  is another  keyword. Because
keywords are interpreted in  REXX, it is not possible to  put too much "smart"
conditional code  to handle this kind  of mistakes, as this  could easily cost
you a factor of 2 or 3 in  list header processing; when you have 100 lists, it
matters a lot.
 
  Eric