On 7/28/2005 10:09 AM, A. Ömer Köker wrote:
>  
> why don't you synchronize the user pass for ldap and listserv, have your
> 'mailing list tab' when selected actually do a login to the listserv panel
> and display that within your portal design either by css manipulation or
> better yet an iframe.  Using the iframe all interaction over the listserv
> panel would go through your portal and you can get fancy by having your
> portal access listserv panel elements with js...

By default, the LISTSERV web interface uses HTTP, rather than HTTPS, so the
password will be sent in clear text, thus exposing the user's enterprise
password to network sniffers. This would not be an acceptable solution at
many sites. It might be an acceptable solution, if and only if, the LISTSERV
web interface was configured to require the use of HTTPS.

It might be possible to use the TCPGUI interface to provide the functionality
described in the initial message in this thread. When a user logs in to the
portal, the portal server could run a script to login to the TCPGUI interface
with a LISTSERV postmaster address, issue the 'QUERY * FOR user@domain' command,
and parse the output. This may not scale well if there are many lists and/or a
high volume of other traffic on the LISTSERV server.

--
Paul Russell
Senior Systems Administrator
OIT Messaging Services Team
University of Notre Dame