Yes, indeed this is the situation I am also in. I have an application, somewhat like SourceForge, where we embed Mailman as the list manager. The user is already logged in to the main application, and we know the user's email address, etc. So, its not very nice to have: (1) separate passwords for each mailing list, and (2) require the user to type in their identity and password for subscription, options editing, and un-subscribe requests.
I'm in the process of changing some of the Cgi scripts and making a few changes to Mailman 2.0.9 to remove these aspects for an already authenticated user.
If others are interested, I can put a patch together with the latest Mailman code.
Regards
Pankaj
-----Original Message----- From: mailman-users-admin@python.org [mailto:mailman-users-admin@python.org]On Behalf Of Jim Popovitch Sent: Wednesday, October 02, 2002 4:24 AM To: Will Yardley; mailman-users@python.org Subject: RE: [Mailman-Users] Re: Re: One Button Direct Subscription
Hi Will,
That is not entirely true. Sometimes you already have the person authenticated via another fashion (think: online banking software), and all that you want to do is have the user subscribe for banking notices by pressing one button.
-Jim P.
-----Original Message----- From: Will Yardley Sent: Wednesday, October 02, 2002 4:11 AM
Well in any event, you should confirm the subscription; otherwise anyone can subscribe anyone else to your list.
This is known as confirmed opt-in, and if you don't use a system like this, you're very likely to get booted by your ISP for spamming.
-- Will Yardley input: william < @ hq . newdream . net . >
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/