I have this problem on some of my lists.  But the added burden is that
the subs cancel if the requester does not confirm within 48 hours.
Given that many don't read mail daily, and that the potential for
delayed mail-distribution to some sites around the world is not only
possible but regular, it is unrealistic to tag a 48 hr deadline on
any sub confirmation note.  Furthermore, why put 'neophyte Grade 1's
to all this hassle, and the listowner to all the extra problem with the
dissatisfied and confused neophytes???
 
Mel
---
 
> > Here's the real rub.  For a neophyte who is just beginning to learn, sending
> > the confirmation can be an arduous task.  For a pro, NO PROBLEM.  But my
> > normal method of subscribing to lists is:
> >
> > sub xxx-l Bob Parks
> > set xxx-l digest
> >
> > But with confirmation on, I have to 'reply' to the confirmation, I get  the
> > job  output saying that I am not signed onto xxx-l so can not use set xxx-l
> > digest.  Then I get the subscription, then I  send  the  set  xxx-l  digest
> > again,  and  then get another message back....
>
> Suggestion for Eric:  It might be good if, for the sake of neophytes, the
> "CONFIRM is necessary" message would also repeat any commands that the
> user had sent and were rejected because the subscription was not yet
> complete, and spell out for user that they need to re-send those specific
> commands *after* their subscription has been fully accepted.
>
> -- Roger Burns   [log in to unmask]
>