Ronnie- What about having a script use the TCPGUI interface to get a ticket for the user, and then passing it back to their browser? you can keep their passwords in a hidden file someplace. I'm actually working on something similar here: authenticating users against our LDAP server, getting a ticket from listserv via TCPGUI and passing the results back. -Chris Ronnie Streff wrote: > Public may be the way I have to go. I'm new to this software, so I'm not > sure if there are reasons I shouldn't. > > I'm not wanting to bypass the login, I'm trying to automate it so that > they don't have to key it in (or even know it) themselves. They > currently log in to our members only area using a last name and a member > number, the log in for the list being different would require them to > use some brain power they don't have in excess. > > E-mail searching would be way beyond their ability. (I've been called a > moron for asking which of our 6 lists they want to be removed from when > they indicate "the list"--I'm supposed to be able to read their feeble > minds.) > > Ronnie Streff > Communications & Technology Specialist > American Medical Writers Association > 40 West Gude Drive Suite 101 > Rockville, MD 20850-1192 > 301.294.5303 / 301.294.9006 fax > [log in to unmask] > www.amwa.org > > I'LL SEE YOU IN ATLANTA > October 11-13, 2007 > AMWA's 67th Annual Conference > A Legacy of Leadership > > > -----Original Message----- > From: LISTSERV list owners' forum [mailto:[log in to unmask]] > On Behalf Of Winship > Sent: Thursday, December 07, 2006 3:44 PM > To: [log in to unmask] > Subject: Re: auto sign in from Web site > > Ronnie Streff wrote: > >> My members are technically illiterate and they may be able to write >> > but > >> they can not read instructions. I currently subscribe them from my >> database software and control their subscriptions to 6 different >> > lists. > > Since when have list subscribers read the simple instructions, in email > or on websites? > > Since you want to bybass the login I assume your archives are private. > You could make them public so there would be no need to log in, and no > password requirement (or they could search via email, which requires no > password from a subscribed address, if they could read instructions that > is.) > > I don't know if you can bypass the requirement for private lists that > there must be > 1. a subscription to the list for the address > 2. a password registered with the host site for that address > > Any reason not to save yourself a lot of trouble and just make your > archives public, so the subscribers won't have to actually read > instructions? > > Douglas Winship [log in to unmask] > -- Christopher Wilson Information Systems Coordinator ISS Enterprise Systems The George Washington University 202-994-3878 [log in to unmask]