Announcing Mailman 2.0 release candidate 1
Hello folks,
Okay, we're really close now! I've put together Mailman 2.0 release candidate 1 and uploaded it to SourceForge. You can grab the tarball from the file release page at
http://sourceforge.net/project/shownotes.php?release_id=14446www.list.org and www.gnu.org should be updated soon. This release contains a bunch of bug fixes and a few local security patches. The source code is essentially frozen, modulo any last minute show stopper bugs. I will probably make a pass at the documentation before the final release. Expect 2.0 final hopefully by the weekend.
Enjoy, -Barry
Hi,
I have setup Mailman for internal use, as well as, for our OpenAir.com service. Mailman is great. I had to make couple of changes in order for it to work the way I needed. Here is what I did:
I changed unsubscribe not to require a password if the body only contained the keyword "unsubscribe". Then only the sender is unsubscribed. This way it is easier for list members to unsubscribe. All our members are subscribed by our service and have no access to their passwords.
I changed subscribe to accept an Admin password when subscribing someone other than self. I have made the list open so that it does not require either Admin approval nor member confirmation. But, I did not want anyone subscribing someone else without any authority.
Questions:
- Does anyone see any major issues with what I did? Could I have done this another way?
- How do I set the "not me too" option to be set by default for each new member?
Thanks,
Boris
Boris:
Many Mailman users would be very happy to see your changes. Please consider wrapping them up cleanly and submitting them as a Sourceforge patch.
Boris Boruchovich wrote:
Hi,
I have setup Mailman for internal use, as well as, for our OpenAir.com service. Mailman is great. I had to make couple of changes in order for it to work the way I needed. Here is what I did:
I changed unsubscribe not to require a password if the body only contained the keyword "unsubscribe". Then only the sender is unsubscribed. This way it is easier for list members to unsubscribe. All our members are subscribed by our service and have no access to their passwords.
I changed subscribe to accept an Admin password when subscribing someone other than self. I have made the list open so that it does not require either Admin approval nor member confirmation. But, I did not want anyone subscribing someone else without any authority.
Questions:
- Does anyone see any major issues with what I did? Could I have done this another way?
- How do I set the "not me too" option to be set by default for each new member?
Thanks,
Boris
Mailman-Users maillist - Mailman-Users@python.org http://www.python.org/mailman/listinfo/mailman-users
At 1:29 PM -0700 10/26/00, Dan Mick wrote:
- I changed unsubscribe not to require a password if the body only contained the keyword "unsubscribe". Then only the sender is unsubscribed. This way it is easier for list members to unsubscribe. All our members are subscribed by our service and have no access to their passwords.
I like that. I really like that. that probably resolved 95% of the hassles with passwords.
-- Chuq Von Rospach - Plaidworks Consulting (mailto:chuqui@plaidworks.com) Apple Mail List Gnome (mailto:chuq@apple.com)
Be just, and fear not.
- I changed unsubscribe not to require a password if the body only contained the keyword "unsubscribe". Then only the sender is unsubscribed. This way it is easier for list members to unsubscribe. All our members are subscribed by our service and have no access to their passwords.
Tell us how to do this!!! Please!
Bob
Is there a way to filter out html garbage on text-only digest versions? I would think a simple filter that does the following would work nicely:
- Get a character. Is it a "<"? No - pass it along, repeat.
- Swallow the byte. Get another byte. Is it a ">"? If not, repeat.
- go to step 1.
...Since most all the html stuff is encased in <...>
I'd like to keep the html for the mime digests, naturally.
Bob
Hi,
I manage a list with about 160,000 members. I am using Mailman version 2.0 and I seem to be experiencing a problem when I post anything to this list. The number of files in qfiles directory keeps growing and not getting any smaller.
Here is an excerpt from the smtp log: "Nov 29 23:28:55 2000 (457) All recipients refused: (111, 'Connection refused') Nov 29 23:30:14 2000 (457) smtp for 150686 recips, completed in 1412.545 seconds"
Here is an excerpt from the qrunner log: "Nov 29 23:51:01 2000 (2960) Could not acquire qrunner lock Nov 29 23:52:01 2000 (2987) Could not acquire qrunner lock Nov 29 23:53:02 2000 (3025) Could not acquire qrunner lock Nov 29 23:54:01 2000 (3083) Could not acquire qrunner lock"
Here is an excerpt from the error log: "Nov 29 23:29:48 2000 (4735) thelist db file was corrupt, using fallback: /home/mailman/lists/thelist/config.db.last Nov 29 23:29:48 2000 (4725) thelist db file was corrupt, using fallback: /home/mailman/lists/thelist/config.db.last Nov 29 23:29:51 2000 (4720) thelist db file was corrupt, using fallback: /home/mailman/lists/thelist/config.db.last Nov 29 23:30:05 2000 (4736) thelist db file was corrupt, using fallback: /home/mailman/lists/thelist/config.db.last"
When I run check_db on "thelist" list the result state that it is fine. I am not sure of what is happening, can anyone point me in the right direction?
Thanks,
Boris
participants (5)
-
barry＠wooz.org -
Bob Puff＠NLE -
Boris Boruchovich -
Chuq Von Rospach -
Dan Mick