OK, good points . . . so I'll amend my wish to say "add the OK feature to renew/confirm processing" rather than the original "instead of" phrase . . . since it is VERY much easier and simpler than the proffered "forward this message back" method. To forward the message, a subscriber must actually type in the server name and address (and be sure not to send it to the listname instead). >>> [log in to unmask] 03/12/01 03:52PM >>> On Mon, 12 Mar 2001, Kevin Parris wrote: > How about making the subscription renewal available on an "OK" method > instead of requiring the explicit 'confirm' command - have the "renewal > is due" notification message include a cookie for this purpose? I can give you three reasons: 1) if the subscriber gets it wrong, and asks listowoner for help, listowner can simply tell subscriber send CONFIRM listname to [log in to unmask] without worrying about the number, which the subscriber has probably discarded; 2) subscriber can do a CONFIRM listname at any time to reset the RENEWAL clock; 3) listowner can do the CONFIRM listname for the subscriber without having the "number" which would be required with an OK approval. Douglas