Hot on the heels of the last release, I'm announcing Mailman 2.0.10 which fixes a few minor problems. See the NEWS file entries below. This is not a critical fix, although it will eliminate a confusing (but harmless) error message, and could provide better support for sites which use the qmail MTA.
As usual, I've made both full source tarballs and patches available. See
http://sourceforge.net/project/showfiles.php?group_id=103for links to download all the patches and the source tarball. If you decide to install the patches, please do read the release notes first:
http://sourceforge.net/project/shownotes.php?release_id=63042See also:
http://www.gnu.org/software/mailman
http://www.list.org
http://mailman.sf.netCheers, -Barry
2.0.10 (09-Apr-2002)
- Closed another small race condition.
- Add the RFC-2822 recommended Message-ID: header on internally
generated outgoing messages. Not all MTAs add this field if
missing (read: Qmail).
A list had subscriptions set to require both confirmation and approval. Someone initiates the subscription process through the web interface. I modified the list to only require approval. The person sent back their address confirmation, and Mailman subscribed them (without requiring approval).
I don't know if this portion of mailman has been gutted/replaced in the 2.1 development, but if it hasn't, this buglet is likely still there...
-Dale
"DN" == Dale Newfield <Dale@Newfield.org> writes:
DN> A list had subscriptions set to require both confirmation and
DN> approval. Someone initiates the subscription process through
DN> the web interface. I modified the list to only require
DN> approval. The person sent back their address confirmation,
DN> and Mailman subscribed them (without requiring approval).
DN> I don't know if this portion of mailman has been
DN> gutted/replaced in the 2.1 development, but if it hasn't, this
DN> buglet is likely still there...I doubt this has been changed in MM2.1, but I'm not sure how easy it would be to fix. A subscription request is going to be guided by the policy in place at the time the process is set in motion. Changing that policy in the middle isn't going to affect requests that have already started.
-Barry
On Fri, 19 Apr 2002, Barry A. Warsaw wrote:
A subscription request is going to be guided by the policy in place at the time the process is set in motion. Changing that policy in the middle isn't going to affect requests that have already started.
Approval was "required" both when the process started and when it completed, but it skipped asking for it. (Before Confirmation&Approval, then just Approval).
-Dale
"DN" == Dale Newfield <Dale@Newfield.org> writes:
DN> On Fri, 19 Apr 2002, Barry A. Warsaw wrote:
>> A subscription request is going to be guided by the policy in
>> place at the time the process is set in motion. Changing that
>> policy in the middle isn't going to affect requests that have
>> already started.
DN> Approval was "required" both when the process started and when
DN> it completed, but it skipped asking for it. (Before
DN> Confirmation&Approval, then just Approval).Ah yes, happens for me to. -Barry
Ah if only all bugs were so eaily fixed. Fixed in cvs. -Barry
participants (2)
-
barry＠zope.com -
Dale Newfield