Dare I ask what the time-frame for Mailman 2.1 is? And can I add the names to my existing list, or do people need to resubscribe? (I hope it's add because I'm just now populating a list with potentially 250 subscribers).
Jason
Now that we're certain this feature is not available in Mailman (and it's still needed), what we are doing is writing a CGI form that collects the information from the user when they subscribe, and
On 28 November 2001, marina said: that
CGI will then email Mailman to start the subscription. The other information I guess we can store in MySQL or similar.
Do you think anybody else would be interested in this? If you think they might be, we'd be happy to post this to the Mailman site.
Considering that Mailman 2.1 has the ability to track real names, your hack probably won't be needed in the long term.
Greg
Mailman-Users maillist - Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users
And... I would hope the upgrade is re-designed to be as easy as the CVS (patch) upgrade(s) from 2.0.6 >> 2.0.8
On Wednesday 28 November 2001 10:19 am, you wrote:
Dare I ask what the time-frame for Mailman 2.1 is? And can I add the names to my existing list, or do people need to resubscribe? (I hope it's add because I'm just now populating a list with potentially 250 subscribers).
Jason
On 28 November 2001, marina said:
Now that we're certain this feature is not available in Mailman
(and
it's still needed), what we are doing is writing a CGI form that collects the information from the user when they subscribe, and
that
CGI will then email Mailman to start the subscription. The other information I guess we can store in MySQL or similar.
Do you think anybody else would be interested in this? If you think they might be, we'd be happy to post this to the Mailman site.
Considering that Mailman 2.1 has the ability to track real names, your hack probably won't be needed in the long term.
Greg
"C" == Camel <camel@lrllamas.com> writes:
C> And... I would hope the upgrade is re-designed to be as easy as
C> the CVS (patch) upgrade(s) from 2.0.6 >> 2.0.8There will be no patch from 2.0.x -> 2.1. The patch would be much larger than the tarball because /a lot/ has changed. But I plan for it to be relatively easy to migrate from 2.0.x -> 2.1.
-Barry
participants (3)
-
barry＠zope.com -
Camel - Jay S. Curtis -
J Barnes