Due to some personal issues I have not been able to address this problem for a while. But... I am back and still troubled. I spent yesterday attempting to implement the +BB and +EB comments to remove some of these options. No matter what I tried, it could not make it work. It just continued to display all the options. I finally realized that I would be quite happy with just the Meta Refresh tag and implement my own HTML code for subscription options. Once again I found myself unable to find the answer to this issue. I tried adding it to the top line of the SUBEDIT-MAIN file from the web interface, without success. I sent the Get command for the WWWTPL file and have toyed with putting a Meta Refresh tag in this file, but now my ignorance comes to the top. Okay... real simple question. Exactly where do I need to add a Meta Refresh tag to my WWWTPL file? Will this file accept a standard Meta Refresh tag, (like this): <meta http-equiv="Refresh" content="0; URL=http://domain.com"> ...or do I need something different??? I only want to be able to build my own form subscription options boxs on my web site, (http://nospin.com), and refresh to a page of my choice, using the WA.EXE module. Thanks for any advice... Bob Wright The NOSPIN Group At Fri, 2 Apr 1999 10:12:11 , Ben Parker wrote: >> >>My question concerns using this module. Everytime someone >>joins or quits, it takes them to the full page generated by the >>module. This confuses the new users unaccustom to all the >>features of Listserv, subsequently they sometimes fill it out >>again. Is there a sub-routine for the WA.EXE module that will >>allow us to redirect to a different page than the one generated >>by the WA.EXE module after they have clicked the Join or Quit >>button? Possibly a page existing on our web site, that says >>they have completed the task? > >The better way to do this is to edit the SUBEDIT-MAIN template in >listname.WWWTPL and have it not display various groups of options which confuse >them. You can also redirect this page to a different page of your own design, >using the "meta-refresh" technique, but you then must give up entirely on this >page, which means users cannot ever edit their own subscriber options via the >WWW interface. (they can still issue email commands to do so). >