> >-- Editing and PUTting the list header specifically. A GUI might be > >developed to enable changing most header keywords by toggling, or > >cutting/pasting addresses for Owner=, Editor=, Filter=, Notify=. > > Seems to me that this should be a feature of LISTSERV, and not of InfoMagnet. Pardon me? Does Listserv have a graphical user interface or other menu capabilities? I thought that's what *InfoMagnet* was all about. Am I mistaken? > >-- Managing error notices. Some part of the program might gather up > >notices and report daily to the list-owner, and offer a menu for actions. > >A sub-routine might collect alleged "user unknown" addresses and after X > >days (X set by the list-owner) offer actions. The list-owner would be > >alerted immediately if a first time error notice had been delayed for 7 > >days or longer. > > Obviously a LISTSERV function, since LISTSERV already does a great deal of > this list owners. I'm proposing *management* of error notices. Listserv doesn't manage them, it just sends them individually. *I* manage them. Would that I could buy some software to do that for me. Maybe somebody will develop such software. Another aspect I've just recalled is that for Subscription= By_owner, your forge method won't work since the non-listowner user isn't authorized to ADD himself. (And your scheme as it stands can't use ADD anyway.) -- Roger Burns [log in to unmask]