From noreply at sourceforge.net  Thu Oct  2 04:01:34 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct  2 04:01:40 2003
Subject: [ mailman-Bugs-816410 ] subscription request webpage has
	inconsistant wording
Message-ID: <E1A4yP0-0007HZ-00@sc8-sf-web1.sourceforge.net>

Bugs item #816410, was opened at 2003-10-02 01:01
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=816410&group_id=103

Category: Web/CGI
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: JC Dill (jcdill)
Assigned to: Nobody/Anonymous (nobody)
Summary: subscription request webpage has inconsistant wording

Initial Comment:
In the text of the page it says:



     Or hit /Cancel and discard/ to cancel this

subscription request.



But the button itself says "Cancel subscription

request" rather than "Cancel and discard".

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=816410&group_id=103

From noreply at sourceforge.net  Fri Oct  3 11:18:56 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Oct  3 11:19:00 2003
Subject: [ mailman-Bugs-817243 ] Web member list has extra bad characters
	via email subscribe
Message-ID: <E1A5Rho-0006bG-00@sc8-sf-web3.sourceforge.net>

Bugs item #817243, was opened at 2003-10-03 11:18
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=817243&group_id=103

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Dan (ptcheezer)
Assigned to: Nobody/Anonymous (nobody)
Summary: Web member list has extra bad characters via email subscribe

Initial Comment:
When I subscribe via an email command with a 

password, then the user shows up in the memberlist 

with extra characters like:

u ' and \



The members who were subscribed using the web 

interface mass-subscription do NOT have any extra 

characters at all.



The user still gets emails from the list, but when you try 

and click on the user in the admin web interface it will 

not go to their user page (goes to the General Options 

page instead)



Here is the table row from the Mailman admin interface 

where you can see the extra characters:



<tr>

      <td><center>u'<INPUT 

name="amember@ap.org_unsub" type="CHECKBOX" 

value="off" >'</center></td>

      <td>u'<a 

href="u\'https://lists.some.org/mailman/options/hrep-

agr/amember--at--

ap.org\'">u\'amember@ap.org\'</a><br><INPUT 

name="amember@ap.org_realname" type="TEXT" 

value="" size="23" ><INPUT name="user" type="HIDDEN" 

value="amember%40ap.org" >'</td>

      <td>u'<center><INPUT 

name="amember@ap.org_mod" type="CHECKBOX" 

value="on" CHECKED ></center>'</td>

      <td><center>u'<INPUT 

name="amember@ap.org_hide" type="CHECKBOX" 

value="off" >'</center></td>

      <td><center>u'<INPUT 

name="amember@ap.org_nomail" type="CHECKBOX" 

value="off" >'</center></td>

      <td><center>u'<INPUT 

name="amember@ap.org_ack" type="CHECKBOX" 

value="off" >'</center></td>

      <td><center>u'<INPUT 

name="amember@ap.org_notmetoo" type="CHECKBOX" 

value="off" >'</center></td>

      <td><center>u'<INPUT 

name="amember@ap.org_nodupes" type="CHECKBOX" 

value="on" CHECKED >'</center></td>

      <td><center>u'<INPUT 

name="amember@ap.org_digest" type="CHECKBOX" 

value="off" >'</center></td>

      <td><center><INPUT 

name="amember@ap.org_plain" type="CHECKBOX" 

value="on" CHECKED ></center></td>

      <td>u'<center>\n<Select 

name="amember@ap.org_language">\n <option 

value="en" Selected> English (USA) 

</option>\n</Select></center>'</td>

    </tr>

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=817243&group_id=103

From noreply at sourceforge.net  Fri Oct  3 11:36:39 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Oct  3 11:36:49 2003
Subject: [ mailman-Bugs-640664 ] autowrap lines over 1000 chars
Message-ID: <E1A5Ryx-0002h1-00@sc8-sf-web1.sourceforge.net>

Bugs item #640664, was opened at 2002-11-19 12:49
Message generated for change (Comment added) made by mmutz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640664&group_id=103

Category: nntp/news
Group: 2.0.x
Status: Open
Resolution: None
Priority: 1
Submitted By: Chris Dudley (dudleyc)
Assigned to: Nobody/Anonymous (nobody)
Summary: autowrap lines over 1000 chars

Initial Comment:
NNTP has a maximum line length of 1000 chars. emails do

not have the same restriction.

Would it be possible for the script which posts emails

to the mailing list to autowrap all the emails at 1000

characters so that they would still be valid nntp

posts? Currently i'm getting a fair few error 441

returns from NNTP because some emails exceed the line

length limit.



It could wrap at the last space or hyphon before the

1000th character, or something similar.



Thanks.

----------------------------------------------------------------------

Comment By: Marc Mutz (mmutz)
Date: 2003-10-03 15:36

Message:
Logged In: YES 
user_id=82377

Mailinglist manager should _not_, I repeat: _not_ change 

autowrap or otherwise mangle messages that a SMTP server is 

not allowed to do. This breaks signed mail and for the purists: 

violates rfc2821. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640664&group_id=103

From noreply at sourceforge.net  Fri Oct  3 11:49:03 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Oct  3 11:50:35 2003
Subject: [ mailman-Bugs-803045 ] mailman breaks PGP/MIME messages
Message-ID: <E1A5SAx-00040Q-00@sc8-sf-web4.sourceforge.net>

Bugs item #803045, was opened at 2003-09-09 10:41
Message generated for change (Comment added) made by mmutz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803045&group_id=103

Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Enno Rehling (eressea)
Assigned to: Nobody/Anonymous (nobody)
Summary: mailman breaks PGP/MIME messages

Initial Comment:
When sending PGP/MIME messages to mailman, mailman 

tries to wrap the message by packaging it into its own 

message. To quote the enimgamil developers:



"The message from mailman, however, has a Content-

Type: multipart/mixed, where the signed message is 

packed into the first part of that message (there is an

additional part with some footer message). This is not 

compliant to the PGP/MIME standard, no tool will be able 

to read such a message."



I originally filed this bug with the enigmail developers, 

but agree with them that the bug is on mailman's side. 

Original bug report (including attachments of example 

mail) can be read at

http://mozdev.org/bugs/show_bug.cgi?id=4601



This is with the mailman 2.1.2-6 deian package

----------------------------------------------------------------------

Comment By: Marc Mutz (mmutz)
Date: 2003-10-03 15:49

Message:
Logged In: YES 
user_id=82377

As I see it, the mp/signed part is neatly packaged as-is into the 

mp/mixed part. That's perfectly legal. In fact, KMail detects the 

signature perfectly well (except that I don't have the key). 

 

You can safely delete this bugreport. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803045&group_id=103

From noreply at sourceforge.net  Fri Oct  3 11:54:22 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Oct  3 11:54:50 2003
Subject: [ mailman-Bugs-815297 ] Breaking signatures in message/rfc822
	attachement!
Message-ID: <E1A5SG6-0000Mm-00@sc8-sf-web3.sourceforge.net>

Bugs item #815297, was opened at 2003-09-30 17:42
Message generated for change (Comment added) made by mmutz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_id=103

Category: security/privacy
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Bernhard Reiter (ber)
Assigned to: Nobody/Anonymous (nobody)
Summary: Breaking signatures in message/rfc822 attachement!

Initial Comment:
Mailman _must_ not touch MIME-parts which are nested

more deeply in the mail. As tested with Mailman 2.1.2,

header lines will be sometimes reformatted in

message/rfc822 attachments which will break the OpenPGP

signature

(also conforming to the PGP/MIME standard) on that part.



I'm attaching a simple email with on long header.

Forward this as MIME part and sign it sending it

through Mailman,

the signature will be broken.



This is an email security affecting bug, because if people 

start believing that a *BAD* signature does not mean much,

because they get many broken by mailman, they will not

react

to a seriously manipulated email anymore!



----------------------------------------------------------------------

Comment By: Marc Mutz (mmutz)
Date: 2003-10-03 15:54

Message:
Logged In: YES 
user_id=82377

This is not limited to message/rfc822 at all: 

 

As a specific example, create a message with an attachment 

and add the header 

Content-Disposition: attachment; filename="more-than-70-chars.

txt" 

(all in a single line), then send it through a mailman-managed ml. 

Result: mailman "fixes" the message to look like 

Content-Disposition: attachment; 

\tfilename="more-than-70-chars.txt" 

 

It even does that inside a multipart/signed part, and this is 

where it breaks the signature verification. 

----------------------------------------------------------------------

Comment By: Bernhard Reiter (ber)
Date: 2003-09-30 17:46

Message:
Logged In: YES 
user_id=113859

Here is the email signed by myself and broken 

after delivery through mailman. Check the "To:" header line.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_id=103

From noreply at sourceforge.net  Mon Oct  6 09:07:58 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Oct  6 09:08:01 2003
Subject: [ mailman-Patches-818601 ] "Announcement-only" list
Message-ID: <E1A6V5i-0002of-00@sc8-sf-web3.sourceforge.net>

Patches item #818601, was opened at 2003-10-06 22:07
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_id=103

Category: Web UI
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: "Announcement-only" list

Initial Comment:
Documents say that Mailman "supports a wide range of

mailing list types, such as general discussion lists and

announce-only lists".  It's exactly true.  But some people 

wish really "announcement-only" feature.



By `Announcement-only' feature:

o Posting by e-mail is not allowed at all.  All messages

  to posting address are forwarded to owners and no other 

  users won't receive it.

o Web interface is provided so that only specified users

  ("posters") can post messages to list.



For example for `mail magazine' publishers,

`announcement-only' list is safer (Oooops! I've

approved the SPAM!) and let them be free from

moderation tasks.



Changes on codes:

o New CGI script `post'.

o New handler `Posttop' which switches messages bound to 

  list to owners (only on annnouncement-only list).

o New `announcement_only' configuration directive.

o Some modifications of templates.





Notice: By now this is buggie (both in Python and English).

    Comments and Fixes are welcome.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_id=103

From noreply at sourceforge.net  Mon Oct  6 09:31:05 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Oct  6 09:31:09 2003
Subject: [ mailman-Bugs-818612 ] adding mime type for shortcut icon
Message-ID: <E1A6VS5-0003gV-00@sc8-sf-web1.sourceforge.net>

Bugs item #818612, was opened at 2003-10-06 15:30
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=818612&group_id=103

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: adding mime type for shortcut icon

Initial Comment:
Peter Bieringer reported that many browsers don't understand the 
<link REL="SHORTCUT ICON"> tag if we don't include the appropriate 
mime type: image/x-icon. 
It's possible this is simply a misconfiguration in the web server 
(which is supposed to serve the right mime type in the 1st place) but 
anyway forcing the type is cheap enough. 
 
I'm uploading the one-liner fix. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=818612&group_id=103

From noreply at sourceforge.net  Mon Oct  6 13:52:09 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Oct  6 13:52:15 2003
Subject: [ mailman-Bugs-818752 ] Changing option via email not work
Message-ID: <E1A6ZWj-0006Ks-00@sc8-sf-web2.sourceforge.net>

Bugs item #818752, was opened at 2003-10-07 02:51
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=818752&group_id=103

Category: None
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Yuji Kitano (ykitano)
Assigned to: Nobody/Anonymous (nobody)
Summary: Changing option via email not work

Initial Comment:
Some of user options are not affected when you change 

them via an email.



eg.

When you send a command email to xxxx-request,

system returns an email stating that option is set,

but that is not set actually.



set authenticate password

set delivery off



then to see if that option is set properly



set authenticate password

set show



You can change options of ack, myposts, hide, etc via 

an email but cannot change options of delivery and 

digest.



I can reproduce this issue on Mailman 2.1.2 and 2.1.3 

on Redhat Linux.

I even tried on Mailman-Users list and got the same 

result.









----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=818752&group_id=103

From noreply at sourceforge.net  Tue Oct  7 13:28:07 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Oct  7 13:28:11 2003
Subject: [ mailman-Feature Requests-584468 ] listinfo: cache
Message-ID: <E1A6vd1-0003DZ-00@sc8-sf-web2.sourceforge.net>

Feature Requests item #584468, was opened at 2002-07-21 14:32
Message generated for change (Comment added) made by pheinlein
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=584468&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Peer Heinlein (pheinlein)
Assigned to: Nobody/Anonymous (nobody)
Summary: listinfo: cache

Initial Comment:
We`re running more than 700 lists on our  
mailinglist-server. Mailman needs between 20  
and 40 seconds to generate the public listinfo  
page.   
  
Wouldn`t it be possible to generate a  
listinfo.cache including all these necessary  
informations to speed up the process?  
  
These listinfo.cache could be valid for some  
specific time, before it is removed and  
regenerated. Or this cache-file can be  
deleted if somenbody is changing his list  
configuration.  
 
Thanks... 
 
p.heinlein@jpberlin.de 

----------------------------------------------------------------------

>Comment By: Peer Heinlein (pheinlein)
Date: 2003-10-07 19:28

Message:
Logged In: YES 
user_id=581680

I`d like to refresh my wish. With more then 1.000 lists on 
our server we really need a cached listinfo-overview. 
Building a listinfo-pages takes several seconds (as you 
can see on http://listi.jpberlin.de) and this only works 
if not too many different users try to access this page at 
the same time. 
 
I`d prefer the following model: 
 
Mailman generates a listinfo.pck or something like this, 
including all necessary information. If listinfo.pck 
doesn`t exist, Mailman generates a new one. 
 
This listinfo.pck has a lifetime after which it is deleted  
(e.g. 5 minutes). 
 
After creating or deleting a new list the listinfo.pck is 
deleted. 
 
Possible: After changing the configuration of a list 
Mailman deletes listinfo.pck which means, that the general 
lifetime cat be set up to 10/15/20 minutes, because 
everytime something SHOULD have changed, Mailman SHOULD 
have deleted listinfo.pck... :-) 
 
Isn`t that possible? That shouldn`t be too much work... 
 
Peer 
 

----------------------------------------------------------------------

Comment By: Peer Heinlein (pheinlein)
Date: 2002-08-10 09:38

Message:
Logged In: YES 
user_id=581680

Having more then 700 lists on our server we now 
have problems generating the listinfo/admin 
overview-page, because the http-timeouts are 
faster then mailman :-) 
 
Is there something planned to solve the problem? 
 
Peer 
 
 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=584468&group_id=103

From noreply at sourceforge.net  Wed Oct  8 08:23:13 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Oct  8 08:23:21 2003
Subject: [ mailman-Bugs-803729 ] LookupError: unknown encoding: X-UNKNOWN
Message-ID: <E1A7DLV-0000Qt-00@sc8-sf-web3.sourceforge.net>

Bugs item #803729, was opened at 2003-09-10 15:31
Message generated for change (Comment added) made by nemethe
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_id=103

Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Ervin N?meth (nemethe)
Assigned to: Nobody/Anonymous (nobody)
Summary: LookupError: unknown encoding: X-UNKNOWN

Initial Comment:
Our site encounters the following problem. 
mailman-2.1.2 installed from OpenBSD ports.

Traceback (most recent call last):
  File "/usr/local/mailman/cron/senddigests", line 94, in ?
    main()
  File "/usr/local/mailman/cron/senddigests", line 86,
in main
    mlist.send_digest_now()
  File "/usr/local/mailman/Mailman/Digester.py", line
60, in send_digest_now
    ToDigest.send_digests(self, mboxfp)
  File
"/usr/local/mailman/Mailman/Handlers/ToDigest.py", line
130, in send_digests
    send_i18n_digests(mlist, mboxfp)
  File
"/usr/local/mailman/Mailman/Handlers/ToDigest.py", line
303, in send_i18n_digests
    msg = scrubber(mlist, msg)
  File
"/usr/local/mailman/Mailman/Handlers/Scrubber.py", line
257, in process
    url = save_attachment(mlist, part, dir)
  File
"/usr/local/mailman/Mailman/Handlers/Scrubber.py", line
348, in save_attachment
    fnext = os.path.splitext(msg.get_filename(''))[1]
  File "/usr/local/mailman/pythonlib/email/Message.py",
line 707, in get_filename
    return unicode(newvalue[2], newvalue[0])
LookupError: unknown encoding: X-UNKNOWN

----------------------------------------------------------------------

>Comment By: Ervin N?meth (nemethe)
Date: 2003-10-08 14:23

Message:
Logged In: YES 
user_id=768522

It's quite unpleasant to recieve this mail daily. In
addition there was a local mailing list to which no mail was
delivered until digests to this list was turned off.

Last day I have upgraded to mailman 2.1.3 and the last lines
of the traceback changed:

  File "/usr/local/mailman/pythonlib/email/Message.py", line
714, in get_filename
    return unicode(newvalue[2], newvalue[0] or 'us-ascii')
LookupError: unknown encoding: X-UNKNOWN


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_id=103

From noreply at sourceforge.net  Wed Oct  8 18:47:58 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Oct  8 18:48:01 2003
Subject: [ mailman-Bugs-820322 ] Crash when global subcription change causes
	collision
Message-ID: <E1A7N66-0001nO-00@sc8-sf-web1.sourceforge.net>

Bugs item #820322, was opened at 2003-10-08 15:47
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=820322&group_id=103

Category: (un)subscribing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Rich Pasco (pasco)
Assigned to: Nobody/Anonymous (nobody)
Summary: Crash when global subcription change causes collision

Initial Comment:
I ran into this bug in MailMan version 2.1.2 today:

If you change your e-mail address "globally" (on all
lists to which you subscribe), and one of those lists
(other than the one whose options page you're working
from) already has a subscription under your new address
(as well as your old address), then MailMan will crash
(and display an exception traceback).

For example, I was working from the web-team page
http://domain.net/mailman/options/listname
as I tried to change my address globally.  This would
affect about ten lists to which my old address
subscribed, including a list called "Team" among
others.  But "Team" already had my new address among
its subscribers, so it could not accept another one. 
Rather than giving a graceful error message when it
discovered this, MailMan just crashed.

I didn't capture the exception traceback, but it should
be easy to reproduce.

     - Rich

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=820322&group_id=103

From noreply at sourceforge.net  Thu Oct  9 10:51:23 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct  9 10:53:53 2003
Subject: [ mailman-Patches-818601 ] "Announcement-only" list
Message-ID: <E1A7c8R-0005ow-00@sc8-sf-web1.sourceforge.net>

Patches item #818601, was opened at 2003-10-06 22:07
Message generated for change (Comment added) made by hatukanezumi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_id=103

Category: Web UI
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: "Announcement-only" list

Initial Comment:
Documents say that Mailman "supports a wide range of
mailing list types, such as general discussion lists and
announce-only lists".  It's exactly true.  But some people 
wish really "announcement-only" feature.

By `Announcement-only' feature:
o Posting by e-mail is not allowed at all.  All messages
  to posting address are forwarded to owners and no other 
  users won't receive it.
o Web interface is provided so that only specified users
  ("posters") can post messages to list.

For example for `mail magazine' publishers,
`announcement-only' list is safer (Oooops! I've
approved the SPAM!) and let them be free from
moderation tasks.

Changes on codes:
o New CGI script `post'.
o New handler `Posttop' which switches messages bound to 
  list to owners (only on annnouncement-only list).
o New `announcement_only' configuration directive.
o Some modifications of templates.


Notice: By now this is buggie (both in Python and English).
    Comments and Fixes are welcome.


----------------------------------------------------------------------

>Comment By: Hatuka*nezumi (hatukanezumi)
Date: 2003-10-09 23:51

Message:
Logged In: YES 
user_id=529503

rel.0.2.

* Posttop handler now placed after Hold handler so that 
  spam discarding and auto-response are capable.

* Global pipelone processing are ommitted when:
  --------------------------------------
  SpamDetect           : [A] and [W]
  Approve              :         [W]
  ReplyBot             :         [W]
  Moderate             : [A] 
  Hold                 :
  - administrivia      : [A]
  - too many recips    : [A]
  - implicit dest.     : [A]
  - suspicious headers : [A] and not [W]
  - message size       : [A] and not [W]
  - news moderation    : [A] and not [W]
  Posttop              : (if [A], may be switched to owner
pipeline.)
  AvoidDuplicates      : [A]
  ------------------------------
  [A]: list is announcement-only.
  [W]: message is posted from Web (by `poster').

* Additional modification to templates.

* Some admin option categories are hidden.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_id=103

From noreply at sourceforge.net  Thu Oct  9 12:19:32 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct  9 12:19:36 2003
Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration
	patch
Message-ID: <E1A7dVk-00059a-00@sc8-sf-web3.sourceforge.net>

Patches item #820723, was opened at 2003-10-09 16:19
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman/pipermail/MHonArc integration patch

Initial Comment:
This patch tightly integrates the MHonArc mail-to-HTML
convertor  with Mailman and its internal pipermail
archiving code. 

The purpose of the patch is to produce a fusion of
(hopefully) the best features of pipermail and MHonArc
for handling Mailman mailing list archives.

For more detail see patch content or
http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

From noreply at sourceforge.net  Thu Oct  9 12:37:19 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct  9 12:37:25 2003
Subject: [ mailman-Feature Requests-820728 ] limit postings by count
Message-ID: <E1A7dmx-0002l6-00@sc8-sf-web1.sourceforge.net>

Feature Requests item #820728, was opened at 2003-10-09 12:37
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=820728&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jim Jewett (jimjjewett)
Assigned to: Nobody/Anonymous (nobody)
Summary: limit postings by count

Initial Comment:
Place a limit on the number of postings/day before the list 
becomes temporarily moderated.  (mlist.emergency gets 
set and EmergencyHold added to the processors.)

Ideally, there would also be a separate per-poster limit 
before the individual became temporarily moderated.

Reason:  If one (or even several) individuals sets up a 
bad .vacation responder or succumbs to a virus, the list 
may soon be swamped with junk traffic.  Better to shut it 
down than to swamp all readers.

(Why yes, I am on a pair of lists sending out new digests 
every 5 minutes because of a .vacation loop problem.  In 
this case, it would be enough to stop posts from this 
individual, but I realize that may not always be the case.)



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=820728&group_id=103

From noreply at sourceforge.net  Thu Oct  9 12:46:48 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct  9 12:49:19 2003
Subject: [ mailman-Feature Requests-820733 ] List Prefix per/user
Message-ID: <E1A7dw8-0005To-00@sc8-sf-web2.sourceforge.net>

Feature Requests item #820733, was opened at 2003-10-09 12:46
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=820733&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jim Jewett (jimjjewett)
Assigned to: Nobody/Anonymous (nobody)
Summary: List Prefix per/user

Initial Comment:
It would be nice if users could individually configure 
whether to add [LISTNAME] or [TOPIC] to the beginning 
of the subject line.  I suppose an alternate header would 
be good too, but most people who can filter on arbitrary 
headers already know how to filter the list.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=820733&group_id=103

From noreply at sourceforge.net  Fri Oct 10 13:51:54 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Oct 10 13:52:00 2003
Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration
	patch
Message-ID: <E1A81Qg-0003GK-00@sc8-sf-web4.sourceforge.net>

Patches item #820723, was opened at 2003-10-09 16:19
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman/pipermail/MHonArc integration patch

Initial Comment:
This patch tightly integrates the MHonArc mail-to-HTML
convertor  with Mailman and its internal pipermail
archiving code. 

The purpose of the patch is to produce a fusion of
(hopefully) the best features of pipermail and MHonArc
for handling Mailman mailing list archives.

For more detail see patch content or
http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html

----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2003-10-10 17:51

Message:
Logged In: YES 
user_id=75166

Under some circumstances, when a single message is passed to
MHonArc for archiving via a pipe, MHonArc may finish its
processing and exit, closing its STDIN before the Mailman
process that invoked it has finished output of the message
to the pipe. Mistakenly, the patched pipermail code treated
this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

From noreply at sourceforge.net  Tue Oct 14 01:49:47 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Oct 14 01:49:54 2003
Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration
	patch
Message-ID: <E1A9I43-0005j1-00@sc8-sf-web2.sourceforge.net>

Patches item #820723, was opened at 2003-10-09 16:19
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman/pipermail/MHonArc integration patch

Initial Comment:
This patch tightly integrates the MHonArc mail-to-HTML
convertor  with Mailman and its internal pipermail
archiving code. 

The purpose of the patch is to produce a fusion of
(hopefully) the best features of pipermail and MHonArc
for handling Mailman mailing list archives.

For more detail see patch content or
http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html

----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2003-10-14 05:49

Message:
Logged In: YES 
user_id=75166

With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself 
defined in Defaults.py is the empty string and, until this is 
changed, the option to select MHonArc instead of pipermail for 
per-list archiving is not offered on the web admin GUI.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-10 17:51

Message:
Logged In: YES 
user_id=75166

Under some circumstances, when a single message is passed to
MHonArc for archiving via a pipe, MHonArc may finish its
processing and exit, closing its STDIN before the Mailman
process that invoked it has finished output of the message
to the pipe. Mistakenly, the patched pipermail code treated
this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

From noreply at sourceforge.net  Thu Oct 16 00:23:52 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct 16 00:23:56 2003
Subject: [ mailman-Bugs-688751 ] Scrubber/attachment bug on NetBSD
Message-ID: <E1A9zg0-0001ZW-00@sc8-sf-web4.sourceforge.net>

Bugs item #688751, was opened at 2003-02-18 16:55
Message generated for change (Comment added) made by dkhelmet
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=688751&group_id=103

Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Eric Ding (ericding)
Assigned to: Nobody/Anonymous (nobody)
Summary: Scrubber/attachment bug on NetBSD

Initial Comment:
I'm using Mailman 2.1.1, and have encountered issues
with mail delivery of messages with attachments (having
to do, I think, with the recent change to use the
scrubber on such messages for digests).

I actually have ARCHIVE_SCRUBBER set to 0 on my system,
since I use MHonArc for archiving. Still, the scrubber
is called from ToDigest. As a result of this bug, ANY
message with an attachment is currently getting
shunted!!  :(

Here's an example stacktrace from the error log:

Feb 18 11:20:55 2003 (7122) Uncaught runner exception:
[Errno 1] Operation not permitted:
'/home/mailman/archives/private/greengrass_coordinator/attachments/20030217/d2897c2f'
Feb 18 11:20:55 2003 (7122) Traceback (most recent call
last):
  File "/home/mailman/Mailman/Queue/Runner.py", line
105, in _oneloop
    self._onefile(msg, msgdata)
  File "/home/mailman/Mailman/Queue/Runner.py", line
155, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "/home/mailman/Mailman/Queue/IncomingRunner.py",
line 130, in _dispose
    more = self._dopipeline(mlist, msg, msgdata, pipeline)
  File "/home/mailman/Mailman/Queue/IncomingRunner.py",
line 153, in _dopipeline
    sys.modules[modname].process(mlist, msg, msgdata)
  File "/home/mailman/Mailman/Handlers/ToDigest.py",
line 82, in process
    send_digests(mlist, mboxfp)
  File "/home/mailman/Mailman/Handlers/ToDigest.py",
line 123, in send_digests
    send_i18n_digests(mlist, mboxfp)
  File "/home/mailman/Mailman/Handlers/ToDigest.py",
line 295, in send_i18n_digests
    msg = scrubber(mlist, msg)
  File "/home/mailman/Mailman/Handlers/Scrubber.py",
line 219, in process
    url = save_attachment(mlist, part, dir, filter_html=0)
  File "/home/mailman/Mailman/Handlers/Scrubber.py",
line 341, in save_attachment
    makedirs(fsdir)
  File "/home/mailman/Mailman/Handlers/Scrubber.py",
line 333, in makedirs
    os.path.walk(dir, twiddle, None)
  File "/usr/pkg/lib/python2.2/posixpath.py", line 279,
in walk
    func(arg, top, names)
  File "/home/mailman/Mailman/Handlers/Scrubber.py",
line 332, in twiddle
    os.chmod(dirname, 02775)
OSError: [Errno 1] Operation not permitted:
'/home/mailman/archives/private/greengrass_coordinator/attachments/20030217/d2897c2f'

To work aorund this issue, I've currently commented out
lines  331-333 on my system.

----------------------------------------------------------------------

Comment By: Jeff Labonski (dkhelmet)
Date: 2003-10-16 04:23

Message:
Logged In: YES 
user_id=8939

I can confirm this on OpenBSD 3.3 running Mailman 2.1.3 and
Postfix 2.0.16. I get the same exact error. Perhaps I should
try reinstalling without following the setgid flag for BSD. 

Just for confirmation, after each email is sent with an
attachment, check_perms reports it doesn't have 02775
permissions. After check_perms -f is run and another email
sent, the same thing occurs, but for a different directory.
Commenting out the offending lines seems to have fixed the
problem; even the archive is correct.

I'll try recompiling in a day or two after I get some sleep.

----------------------------------------------------------------------

Comment By: Eric Ding (ericding)
Date: 2003-04-08 16:07

Message:
Logged In: YES 
user_id=302756

The only problems that check_perms reveals are all the
directories that do not have the setgid bit set. I installed
with README.BSD in mind, assuming that the setgid bit is
unnecessary.  Running check_perms -f to turn on that bit has
no effect on the behavior.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-04-07 22:37

Message:
Logged In: YES 
user_id=12800

I need more information for this one. Do you still get the
crash if you run check_perms first?  I've never seen this on
Linux and I don't have a NetBSD box available to see if
there's some platform specific problem involved.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=688751&group_id=103

From noreply at sourceforge.net  Thu Oct 16 12:35:41 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct 16 12:35:44 2003
Subject: [ mailman-Feature Requests-824944 ] Yahoogroups
Message-ID: <E1AAB6D-0000gl-00@sc8-sf-web1.sourceforge.net>

Feature Requests item #824944, was opened at 2003-10-16 16:35
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=824944&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Alex (halloalex)
Assigned to: Nobody/Anonymous (nobody)
Summary: Yahoogroups

Initial Comment:
Hi,

I consider to install Mailman on my server to host several 
communities. But unfortunately up till now Mailman is 
only designed for mailing lists. So it doesnt offer the 
possibility to upload files, etc. To be honest, I also think 
that the design of Yahoogroups is more userfriendly. Has 
anybody ever thought about to enhance Mailman, so 
that it can compete with Yahoogroups?

Greetings from Alex,
who appreciates every hint in this direction


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=824944&group_id=103

From noreply at sourceforge.net  Thu Oct 16 14:16:46 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct 16 14:16:55 2003
Subject: [ mailman-Feature Requests-824944 ] Yahoogroups
Message-ID: <E1AACg2-0005wp-00@sc8-sf-web1.sourceforge.net>

Feature Requests item #824944, was opened at 2003-10-16 12:35
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=824944&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Alex (halloalex)
Assigned to: Nobody/Anonymous (nobody)
Summary: Yahoogroups

Initial Comment:
Hi,

I consider to install Mailman on my server to host several 
communities. But unfortunately up till now Mailman is 
only designed for mailing lists. So it doesnt offer the 
possibility to upload files, etc. To be honest, I also think 
that the design of Yahoogroups is more userfriendly. Has 
anybody ever thought about to enhance Mailman, so 
that it can compete with Yahoogroups?

Greetings from Alex,
who appreciates every hint in this direction


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-10-16 14:16

Message:
Logged In: YES 
user_id=12800

Sure.  Introduce me to the VC with money burning holes in
his pockets and I think we could do something killer. :)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=824944&group_id=103

From noreply at sourceforge.net  Thu Oct 16 16:49:05 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct 16 16:49:10 2003
Subject: [ mailman-Bugs-825084 ] HyperArch.py allows empty subjects
Message-ID: <E1AAF3R-0006Gt-00@sc8-sf-web4.sourceforge.net>

Bugs item #825084, was opened at 2003-10-16 13:49
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=825084&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Kyle Lanclos (lanclos)
Assigned to: Nobody/Anonymous (nobody)
Summary: HyperArch.py allows empty subjects

Initial Comment:
Messages coming into HyperArch.py with a subject of
"Re: " (or similar) come out having no subject at all.
This is Bad(tm), because the HREF links in the HTML
archives are keyed to the subject, and if there's no
subject, there's no link.

Here's a simple fix, against the 2.1.3 source.


--- mailman-2.1.3/Mailman/Archiver/HyperArch.py     
Sun Sep 21 19:40:51 2003
+++ /opt/mailman/Mailman/Archiver/HyperArch.py Thu Oct
16 13:38:39 2003
@@ -262,6 +262,8 @@
             if result:
                 i = result.end(0)
                 self.subject = self.subject[i:]
+               if self.subject.strip() == EMPTYSTRING:
+                       self.subject = '(no subject)'
             else:
                 i = -1
         # Useful to keep around


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=825084&group_id=103

From noreply at sourceforge.net  Thu Oct 16 18:11:09 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct 16 18:11:13 2003
Subject: [ mailman-Bugs-825143 ] build with multiple submake jobs fails
Message-ID: <E1AAGKr-0000ua-00@sc8-sf-web2.sourceforge.net>

Bugs item #825143, was opened at 2003-10-16 15:11
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=825143&group_id=103

Category: configuring/installing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Kyle Lanclos (lanclos)
Assigned to: Nobody/Anonymous (nobody)
Summary: build with multiple submake jobs fails

Initial Comment:
Well, it doesn't so much fail, as it quietly screws up
many a binary. On a Solaris 9 machine with four
processors, I set:

MAKE="gmake -j4"

...and proceed to configure/build mailman. No errors.
Nothing creeps up until I try to use the binaries in
cgi-bin. Depending on the time of day, cosmic rays,
etc., several of the binaries will all end up being the
same file; for example, the "admin" wrapper will really
be another copy of the "create" wrapper. This seems to
happen with at least half of them, and the arrangement
is random each time I do it.

The solution was simple:

MAKE="gmake"

...reconfigure, rebuild, reinstall. Everything was
exactly as it should be. Somewhere in the relevant
makefile, -jN needs to be disabled.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=825143&group_id=103

From noreply at sourceforge.net  Thu Oct 16 18:11:51 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct 16 18:12:00 2003
Subject: [ mailman-Bugs-825084 ] HyperArch.py allows empty subjects
Message-ID: <E1AAGLX-0000vz-00@sc8-sf-web2.sourceforge.net>

Bugs item #825084, was opened at 2003-10-16 13:49
Message generated for change (Settings changed) made by lanclos
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=825084&group_id=103

>Category: Pipermail
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Kyle Lanclos (lanclos)
Assigned to: Nobody/Anonymous (nobody)
Summary: HyperArch.py allows empty subjects

Initial Comment:
Messages coming into HyperArch.py with a subject of
"Re: " (or similar) come out having no subject at all.
This is Bad(tm), because the HREF links in the HTML
archives are keyed to the subject, and if there's no
subject, there's no link.

Here's a simple fix, against the 2.1.3 source.


--- mailman-2.1.3/Mailman/Archiver/HyperArch.py     
Sun Sep 21 19:40:51 2003
+++ /opt/mailman/Mailman/Archiver/HyperArch.py Thu Oct
16 13:38:39 2003
@@ -262,6 +262,8 @@
             if result:
                 i = result.end(0)
                 self.subject = self.subject[i:]
+               if self.subject.strip() == EMPTYSTRING:
+                       self.subject = '(no subject)'
             else:
                 i = -1
         # Useful to keep around


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=825084&group_id=103

From noreply at sourceforge.net  Fri Oct 17 13:51:12 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Oct 17 13:51:26 2003
Subject: [ mailman-Feature Requests-824944 ] Yahoogroups
Message-ID: <E1AAYkq-0008IS-00@sc8-sf-web3.sourceforge.net>

Feature Requests item #824944, was opened at 2003-10-16 16:35
Message generated for change (Comment added) made by halloalex
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=824944&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Alex (halloalex)
Assigned to: Nobody/Anonymous (nobody)
Summary: Yahoogroups

Initial Comment:
Hi,

I consider to install Mailman on my server to host several 
communities. But unfortunately up till now Mailman is 
only designed for mailing lists. So it doesnt offer the 
possibility to upload files, etc. To be honest, I also think 
that the design of Yahoogroups is more userfriendly. Has 
anybody ever thought about to enhance Mailman, so 
that it can compete with Yahoogroups?

Greetings from Alex,
who appreciates every hint in this direction


----------------------------------------------------------------------

>Comment By: Alex (halloalex)
Date: 2003-10-17 17:51

Message:
Logged In: YES 
user_id=767295

Well, unfortunately I am just a poor student with basic 
computer knowledge and all of my websites are non-profit-
projects. So I guess I am not really helpful for you. However, 
if anyone develops something like Yahoogroups or maybe 
knows a company that already offers such a script, please 
inform me. For a stable version I would not even hesitate to 
pay - lets say- up to 350 to 400 US.

Regards,
alex

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-10-16 18:16

Message:
Logged In: YES 
user_id=12800

Sure.  Introduce me to the VC with money burning holes in
his pockets and I think we could do something killer. :)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=824944&group_id=103

From noreply at sourceforge.net  Sat Oct 18 11:05:27 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat Oct 18 11:05:32 2003
Subject: [ mailman-Patches-825997 ] sync_members traceback
Message-ID: <E1AAsdz-0007Ae-00@sc8-sf-web3.sourceforge.net>

Patches item #825997, was opened at 2003-10-18 17:05
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=825997&group_id=103

Category: command line scripts
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniel Buchmann (avalon)
Assigned to: Nobody/Anonymous (nobody)
Summary: sync_members traceback

Initial Comment:
sync_members would give a traceback when reading a file
containing foreign (non-ASCII) characters in the
"fullname" of an email address:

Traceback (most recent call last):
  File "/home/mailman/bin/sync_members", line 286, in ?
    main()
  File "/home/mailman/bin/sync_members", line 259, in main
    s = email.Utils.formataddr((name,
addr)).encode(enc, 'replace')
UnicodeError: ASCII decoding error: ordinal not in
range(128)

The patch attached fixes this, using code copied from
list_members.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=825997&group_id=103

From noreply at sourceforge.net  Sun Oct 19 17:13:03 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Oct 19 17:13:35 2003
Subject: [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi
Message-ID: <E1ABKrH-0005Ek-00@sc8-sf-web4.sourceforge.net>

Patches item #444884, was opened at 2001-07-26 18:27
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103

Category: Unofficial 2.0 patch
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 3
Submitted By: Richard Barrett (ppsys)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: Integration of Mailman & htdig for archi

Initial Comment:
This patch is applicable to Mailman 2.0.6 release that 
has had search enhancement patch 444879 patch 
installed - if your Defaults.py has the 
ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE 
in it then you've got that patch.

It replaces earlier patches 401670 and 402423 and is 
mainly to correct some problems arising from fixes 
introduced into Mailman by bug fix releases since the 
402423 patch. 

This patch integrates htdig with Mailman and provides:

1. per list search facility with a search form on the 
list's TOC page.

2. maintenance of privacy of private archives which 
requires the user to establish their credentials via 
the normal private archive access before any access 
via htdig is allowed.
   
3. a common base URL for both public and private 
archive access via htsearch results so that htdig 
indices are unaffected by changingan archive from 
private to public and vice versa. All access to 
archives via htdig is controlled by a new wrapped cgi-
bin script called htdig.py.
   
4. a new cron activated script and extra crontab entry 
which runs htdig regularly to maintain the per list 
search indices.
   
5. automatic creation, deletion and maintenance of 
htdig configuration files and such. Beyond installing 
htdig and telling Mailman where it is via mm_cfg you 
do not have to do any other setup. Well not quite you 
do have to set up a single per installation symlink to 
allow htdig to find the automatically generated per 
list htdig configuration files.

You probably want to run this patch as follows:

cd <mailman 2.0.6 untarred and unzipped directory>
patch -p1 < <this patch file>  

----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2003-10-19 21:13

Message:
Logged In: YES 
user_id=75166

htdig-2.1.3-0.3.patch.gz add minor private archive security
improvements to the patch for MM 2.1.3

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-09-30 20:14

Message:
Logged In: YES 
user_id=75166

htdig-2.1.3-0.1.patch is a MM 2.1.3 compatible version of
the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-06-06 17:47

Message:
Logged In: YES 
user_id=75166

last comment should have read: 

htdig-2.1.2-0.4.patch.gz corrects an error in 2 scripts, 
mmsearch.py and remote_mmsearch, which caused an 
exception if list archives were being accessed via HTTPS and 
a search was performed.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-06-06 17:45

Message:
Logged In: YES 
user_id=75166

htdig-2.1.2-0.3.patch.gz corrects an error in 2 scripts, 
mmsearch.py and remote_mmsearch, which caused an 
exception if list archives were being accessed via HTTPS and 
a search was performed.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-05-01 19:00

Message:
Logged In: YES 
user_id=75166

htdig-2.1.2-0.3.patch.gz adds some minor performance 
improvement in template handling in MM 2.1.2

You should consider also applying this bug-fis patch:

[ 730769 ] template access hierarchy is broken

http://sourceforge.net/tracker/index.php?
func=detail&aid=730769&group_id=103&atid=100103

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-04-28 15:44

Message:
Logged In: YES 
user_id=75166

htdig-2.1.2-0.2.patch.gz corrects error in file uploaded as 
htdig-2.1.2-0.1.patch.gz. Sorry for any inconvenience.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-04-28 14:46

Message:
Logged In: YES 
user_id=75166

htdig-2.1.2-0.1.patch.gz is a revised version for MM 2.1.2 
compatibility.

It also incoporates a previosuly unpublished change to 
overcome a potential problem with htdig excluced urls - see 
the INSTALL.htdig-mm file for more information

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-03-21 18:29

Message:
Logged In: YES 
user_id=75166

htdig-2.1.1-0.4.patch.gz fixes a problem with mmsearch 
handling multi-page search results from htsearch.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-03-21 17:54

Message:
Logged In: YES 
user_id=75166

htdig-2.1.1-0.3.patch.gz fixes a fault when mmsearch.py is 
rasing an excpetion because it has had a problem running 
htsearch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-03-20 14:10

Message:
Logged In: YES 
user_id=75166

htdig-2.1.1-0.2.patch.gz close a security exploit which allows 
leakage of information held in htdig's per-list search indexes 
to users not authorized to view private list archives.

Read file INSTALL.htdig-mm installed by this patch for details 
and instructions for upgrading MM installations using earlier 
versions of this patch



----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-02-10 15:50

Message:
Logged In: YES 
user_id=75166

htdig-2.1.1-0.1.patch.gz introduces no functional change but 
applies without offset warnings to MM 2.1.1

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-02-05 18:12

Message:
Logged In: YES 
user_id=75166

It seems it is possible, if this patch is installed, for a list's 
htdig conf file and the list specific htdig index db files to be 
read directly through the web interface for list archives. 

Even if this patch isn't installed it seems a list's pipermail.pck 
file can also be read directly through the web interface for list 
archives.

This seems to be true for accesses via /pipermail for public 
lists and via /mailman/private for private lists.

The problem does not occur for htdig search results 
accessed via /mailman/htdig as the htdig.py script is more 
protective than private.py

Broadly speaking the data affected is availble to a user in 
normal operation which is why I do not consider the issue to 
be a security breach as such.

Adding the following RewriteRule to Apache's httpd.conf 
prevents the situation, assuming you got the RewriteEngine 
On:

RewriteRule ^(/pipermail/.*)/(pipermail.pck|htdig/[^/]*)$ 
$1/index.html [F]

RewriteRule ^(/mailman/private/.*)/(pipermail.pck|htdig/[^/]*)$ 
$1/index.htm
l [F]

You could, of course, substitute an R flag for the F flag on the 
RewriteRules and be more hacker friendly.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-22 14:20

Message:
Logged In: YES 
user_id=75166

htdig-2.1-0.3.patch corrects yet another bug in htdig.py. Hope 
that all of them!

Stops use of obsolete config variable DEFAULT_HOST in 
several files.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-15 20:18

Message:
Logged In: YES 
user_id=75166

htdig-2.1-0.2.patch corrects a bug in htdig.py and deals with 
an adverse interaction between htdig.py and a bug in 
$prefix/scripts/driver (see #668685 for a patch to fix this).

It also improves the content type and security handling by 
htdig.py for MM 2.1 version of patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-15 20:14

Message:
Logged In: YES 
user_id=75166

Uploaded wrong file mailer-2.0.13-0.4.patch on last attempt.

Should have been htdig-2.0.13-0.4.patch which improves the 
content type and security handling by htdig.py for MM 2.0.13 
version of patch.

Please ignore mailer-2.0.13-0.4.patch file

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-15 20:09

Message:
Logged In: YES 
user_id=75166

mailer-2.0.13-0.4.patch improves the content type and 
security handling by htdig.py for MM 2.0.13 version of patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-02 16:07

Message:
Logged In: YES 
user_id=75166

htdig-2.1-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-11 11:48

Message:
Logged In: YES 
user_id=75166

htdig-2.1b6-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1b6

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-04 10:53

Message:
Logged In: YES 
user_id=75166

htdig-2.0.13-0.3.patch corrects a minor typo in text appearing 
in the list TOC after the patch is applied.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-11-27 10:24

Message:
Logged In: YES 
user_id=75166

htdig-2.1b5-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1b5

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-10-30 11:43

Message:
Logged In: YES 
user_id=75166

htdig-2.1b4-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1b4

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-10-14 11:50

Message:
Logged In: YES 
user_id=75166

htdig-2.1b3-0.3.patch removes use of the file() function, used 
instead of the open() function, in three cron scripts added by 
the patch. Use of the file() function created an unnecessary 
dependency on Python 2.2

----------------------------------------------------------------------

Comment By: Colin Mackinlay (cmackinlay)
Date: 2002-10-12 16:51

Message:
Logged In: YES 
user_id=624179

Got a workaround!

The line referred to in the traceback:
 file(rundig_run_file, 'w').close()
is used to create a 'rundig_last_run' file of lenght 0 bytes
Creating this manually (or copying it) means the line isn't 
called and everything seems to work.

Either file() is not a valid function call or my python is broken - 
I'm not literate enough in python to know the answer though! 

----------------------------------------------------------------------

Comment By: Colin Mackinlay (cmackinlay)
Date: 2002-10-06 14:18

Message:
Logged In: YES 
user_id=624179

Just rebuilt MM as 2.1b3 with htdig.
Upgraded lists which had htdig before work fine
New lists give the obvious error:
  Unable to read word database file
  Did you run htmerge?
Running the cronjob doesn't fix as it used to, message is:
  Output from command /usr/bin/python -
S /usr/local/mailman/cron/nightly_htdig ..

Traceback (most recent call last):
  File "/usr/local/mailman/cron/nightly_htdig", line 153, in ?
    main()
  File "/usr/local/mailman/cron/nightly_htdig", line 118, in main
    file(rundig_run_file, 'w').close()
NameError: global name 'file' is not defined

The archive/htdig folder only contains the xx.conf file, but no 
db.xx files

If I copy in db.xx files from another list then the problem goes 
away (except I've now got an invalid set of references!)

Is this my elementary error or is it more sinister?!


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-15 11:02

Message:
Logged In: YES 
user_id=75166

htdig-2.1b3-0.2.patch corrects a dumb syntax error in htdig-
2.1b3-0.1.patch which will typically show up as logged errors 
in the operation of the ArchRunner qrunner at line 721 of 
HyperArch.py

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-14 16:51

Message:
Logged In: YES 
user_id=75166

htdig-2.1b3-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1b3

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-08 16:33

Message:
Logged In: YES 
user_id=12800

I've sent Richard some comments off-line about this patch.

Meta comments: the 2.0.x patches can't be officially
supported, but I'm going to create an unofficial patches
page off the wiki for where the 2.0 patches can be migrated.

I think this patch set is too big for MM2.1, but if it's
cleaned up as per my private message, let's re-evaluate it
for MM2.2 (or 3.0).

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-05 10:11

Message:
Logged In: YES 
user_id=75166

htdig-2.0.13-0.2.patch just adds a GPL notice to the patch


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-01 16:35

Message:
Logged In: YES 
user_id=75166

htdig-2.1b2-0.1.patch is a revised version of the patch 
that is compatible with MM 2.1b2

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-07-30 11:25

Message:
Logged In: YES 
user_id=75166

htdig-2.0.13-0.1.patch is purely cosmetic to get no mumble 
application to MM 2.0.13

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-07-25 15:07

Message:
Logged In: YES 
user_id=75166

Do not use htdig-2.0.12-0.1.patch there is an error in it.
Use htdig-2.0.12-0.2.patch instead

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-07-25 14:10

Message:
Logged In: YES 
user_id=75166

htdig-2.0.12-0.1.patch is a revised version of the patch that 
applies without complaint to MM 2.0.12.

It also add a facility for adding site wide htdig configuration 
attributes to all list specific htdig configuration files. 



----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-05-23 09:59

Message:
Logged In: YES 
user_id=75166

htdig-2.0.11-0.1.patch is a revised version of the patch that 
is compatible with MM 2.0.11

This version removes an incompatibility with Python 2.2 
which caused warning messages to be generated when any 
of the family cron/nightly_htdig scripts were run.

Some guidance on file access permissions for some htdig 
database files needed by rundig have been added to 
installation notes.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-04-19 10:59

Message:
Logged In: YES 
user_id=75166

htdig-2.0.10-0.1.patch is a revised version of the patch 
that is compatible with MM 2.0.10

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-04-08 17:46

Message:
Logged In: YES 
user_id=75166

htdig-2.0.9-0.1.patch is a revised version of the patch 
that is compatible with MM 2.0.9

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-03-06 16:22

Message:
Logged In: YES 
user_id=75166

htdig-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in 
mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002

Known deficiency is that the non-English versions of files under $build/templates still contain text in English 
and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in 
files under $build/messages remain to be done.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-12-17 16:56

Message:
Logged In: YES 
user_id=75166

htdig-2.1cvs-20011217.patch is a revised version of the 
patch that is compatible with the code published in mailman 
CVS on sourceforge as 11:50 GMT 17 Dec 2001

The only known deficiency is that the non-English versions 
of files under $build/templates still contain text in 
English and need translations I cannot do. Also the 
necessary pygettext activity and subsequent translations in 
files under $build/messages remain to be done.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-12-13 16:58

Message:
Logged In: YES 
user_id=75166

htdig-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in 
mailman-2.1a3.tgz on sourceforge.

The only known deficiency is that the non-English versions of files under $build/templates still contain text 
in English and need translations I cannot do. Also the necessary pygettext activity and subsequent 
translations in files under $build/messages remain to be done. 

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-28 17:33

Message:
Logged In: YES 
user_id=75166

The htdig-2.0.8-0.1.patch version of the patch resolves a problem that can arise with htdig indexing if the 
web_page_url for a list uses other than the http addressing (some folks want to use https). While specified 
as for MM 2.0.8 the revised patch should work OK with 2.0.7, 2.0.6 and probably back as far as 2.0.3. If 
you do not have the requirement for using other than http addressing in you lists web_page_urls it probably 
isn't worth the trouble of upgrading to this patch level.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-28 11:08

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-27 12:00

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to Mm 2.0.7

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-09 11:54

Message:
Logged In: YES 
user_id=75166

The htdig-2.0.6-03.patch version of the patch makes some 
previously hard-coded things configurable and enhances the 
capability to run the htdig searches and indexing on a 
different machine to the one delivering Mailman and 
Mailman's web UI.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103

From noreply at sourceforge.net  Mon Oct 20 07:06:24 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Oct 20 07:06:27 2003
Subject: [ mailman-Bugs-826775 ] Chnage URL for submit buttons
Message-ID: <E1ABXrk-00008E-00@sc8-sf-web4.sourceforge.net>

Bugs item #826775, was opened at 2003-10-20 13:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=826775&group_id=103

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Ulrich Windl (windl)
Assigned to: Nobody/Anonymous (nobody)
Summary: Chnage URL for submit buttons

Initial Comment:
I have a special configuration, where the CGI scripts
have problems:
the hostname is like "host.domain.org" with two
ethernet interfaces, each having its own name like
"host-a.domain.org" and "host-b.domain.org". I also
have an alias like "mailman.domain.org" that is
intended to be used as virtual host for the CGI interface.
However not every URL in the CGI pages are correct. At
the moment, I cannot submit administrative changes,
because the SUBMIT button uses "host.domain.org" (which
has no address record associated with).
It also seems that access via the virtual host name
does not display the mailing lists being configured.
Where are the places I should look at to change URLs?
I think the submit buttons should have an URL...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=826775&group_id=103

From noreply at sourceforge.net  Tue Oct 21 13:08:01 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Oct 21 13:08:05 2003
Subject: [ mailman-Feature Requests-827651 ] genaliases should use temporary
	aliases-file
Message-ID: <E1ABzzF-0001EY-00@sc8-sf-web1.sourceforge.net>

Feature Requests item #827651, was opened at 2003-10-21 19:08
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=827651&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 6
Submitted By: Peer Heinlein (pheinlein)
Assigned to: Nobody/Anonymous (nobody)
Summary: genaliases should use temporary aliases-file

Initial Comment:
 
We have so many lists, that rebuilding the aliases-file takes 
more 10 to 20 mintues. -Very long. 
 
genaliases calls postupdate after every list, so that aliases.db 
ist empty at the beginning and grows from list to list. 
 
In this time my MTA Postfix bounces messages, because he 
isn`t able to find  proper aliases for some lists, because 
genaliases has thrown everything away. 
 
It would be MUCH better, if genaliases would call postupdate 
after finishing ALL the lists. That would save a lot of time and 
this would resolve the problem, that the MTA has to be 
stopped when genaliases is started, because aliases.db 
contains all the lists just untill genaliases has finished his job 
and aliases is totally rebuild. 
 
Peer 
 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=827651&group_id=103

From noreply at sourceforge.net  Tue Oct 21 13:09:13 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Oct 21 13:10:09 2003
Subject: [ mailman-Feature Requests-827651 ] genaliases shouldn`t call
	postmap after every list
Message-ID: <E1AC00P-0001I5-00@sc8-sf-web1.sourceforge.net>

Feature Requests item #827651, was opened at 2003-10-21 19:08
Message generated for change (Settings changed) made by pheinlein
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=827651&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 6
Submitted By: Peer Heinlein (pheinlein)
Assigned to: Nobody/Anonymous (nobody)
>Summary: genaliases shouldn`t call postmap after every list

Initial Comment:
 
We have so many lists, that rebuilding the aliases-file takes 
more 10 to 20 mintues. -Very long. 
 
genaliases calls postupdate after every list, so that aliases.db 
ist empty at the beginning and grows from list to list. 
 
In this time my MTA Postfix bounces messages, because he 
isn`t able to find  proper aliases for some lists, because 
genaliases has thrown everything away. 
 
It would be MUCH better, if genaliases would call postupdate 
after finishing ALL the lists. That would save a lot of time and 
this would resolve the problem, that the MTA has to be 
stopped when genaliases is started, because aliases.db 
contains all the lists just untill genaliases has finished his job 
and aliases is totally rebuild. 
 
Peer 
 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=827651&group_id=103

From noreply at sourceforge.net  Tue Oct 21 13:37:01 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Oct 21 13:37:04 2003
Subject: [ mailman-Feature Requests-584468 ] listinfo: cache
Message-ID: <E1AC0RJ-0002Kd-00@sc8-sf-web3.sourceforge.net>

Feature Requests item #584468, was opened at 2002-07-21 14:32
Message generated for change (Comment added) made by pheinlein
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=584468&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
>Priority: 9
Submitted By: Peer Heinlein (pheinlein)
Assigned to: Nobody/Anonymous (nobody)
Summary: listinfo: cache

Initial Comment:
We`re running more than 700 lists on our  
mailinglist-server. Mailman needs between 20  
and 40 seconds to generate the public listinfo  
page.   
  
Wouldn`t it be possible to generate a  
listinfo.cache including all these necessary  
informations to speed up the process?  
  
These listinfo.cache could be valid for some  
specific time, before it is removed and  
regenerated. Or this cache-file can be  
deleted if somenbody is changing his list  
configuration.  
 
Thanks... 
 
p.heinlein@jpberlin.de 

----------------------------------------------------------------------

>Comment By: Peer Heinlein (pheinlein)
Date: 2003-10-21 19:37

Message:
Logged In: YES 
user_id=581680

I have to post again my problem. And it is REALLY a problem. 
 
Generating the listinfo-pages takes much time and Mailman uses 
more then 74 MByte of memory. We need so much memory in our 
server just for beeing able to generate the listinfo page even if five 
or six users try to access the listinfo-page at the same time. 
 
I can`t set up a server with 2 GByte of memory just for a listinfo 
overview page. 
 
And, anyway, it takes TO MUCH time.  
 
I don`t know how to programm python, but I can`t imagin that it 
should be so hard to integrate a caching mechnism. 
 
If this problem will not be solved in the near future, we have to stop 
using mailman, because Mailman isn`t enough designed to perform 
even on big mailingliste-server. :-(((((((( 
 
PLEASE! 
 
 

----------------------------------------------------------------------

Comment By: Peer Heinlein (pheinlein)
Date: 2003-10-07 19:28

Message:
Logged In: YES 
user_id=581680

I`d like to refresh my wish. With more then 1.000 lists on 
our server we really need a cached listinfo-overview. 
Building a listinfo-pages takes several seconds (as you 
can see on http://listi.jpberlin.de) and this only works 
if not too many different users try to access this page at 
the same time. 
 
I`d prefer the following model: 
 
Mailman generates a listinfo.pck or something like this, 
including all necessary information. If listinfo.pck 
doesn`t exist, Mailman generates a new one. 
 
This listinfo.pck has a lifetime after which it is deleted  
(e.g. 5 minutes). 
 
After creating or deleting a new list the listinfo.pck is 
deleted. 
 
Possible: After changing the configuration of a list 
Mailman deletes listinfo.pck which means, that the general 
lifetime cat be set up to 10/15/20 minutes, because 
everytime something SHOULD have changed, Mailman SHOULD 
have deleted listinfo.pck... :-) 
 
Isn`t that possible? That shouldn`t be too much work... 
 
Peer 
 

----------------------------------------------------------------------

Comment By: Peer Heinlein (pheinlein)
Date: 2002-08-10 09:38

Message:
Logged In: YES 
user_id=581680

Having more then 700 lists on our server we now 
have problems generating the listinfo/admin 
overview-page, because the http-timeouts are 
faster then mailman :-) 
 
Is there something planned to solve the problem? 
 
Peer 
 
 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=584468&group_id=103

From noreply at sourceforge.net  Tue Oct 21 20:01:52 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Oct 21 20:02:09 2003
Subject: [ mailman-Feature Requests-534234 ] Automatic RSS feed generation
Message-ID: <E1AC6Rk-00045q-00@sc8-sf-web2.sourceforge.net>

Feature Requests item #534234, was opened at 2002-03-24 05:12
Message generated for change (Comment added) made by sbwoodsi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=534234&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Rob Lanphier (robla)
Assigned to: Nobody/Anonymous (nobody)
Summary: Automatic RSS feed generation

Initial Comment:
It would be really great to have an automatic RSS feed
as a result of using Mailman archiving.

More info on RSS:
http://purl.org/rss/1.0/
http://directory.google.com/Top/Reference/Libraries/Library_and_Information_Science/Technical_Services/Cataloguing/Metadata/Resource_Description_Framework_-_RDF/Applications/RSS/

RSS Validator:
http://aggregator.userland.com/validator

----------------------------------------------------------------------

Comment By: Simon Woodside (sbwoodsi)
Date: 2003-10-22 00:01

Message:
Logged In: YES 
user_id=54239

Just to add a "me too" !!! This would be very, very useful
for my site, http://openict.net where I use mailman as the
discussion group system. Having RSS feeds would allow me to
create a nifty list of "most recent posts" to each group on
the web, without having to get into some kind of
webforum-style system instead. I much prefer to use mailman.

----------------------------------------------------------------------

Comment By: A.M. Kuchling (akuchling)
Date: 2002-12-23 19:22

Message:
Logged In: YES 
user_id=11375

Patch #657951 adds an RSS summary to mailing lists.






----------------------------------------------------------------------

Comment By: captain larry (captainlarry)
Date: 2002-08-07 17:02

Message:
Logged In: YES 
user_id=147905

If it's useful a friend and I have recently hacked on a <a
href="http://taint.org/mmrss/">Perl script</a> which
generates RSS feeds by scraping the Mailman archives.  We
made some (I think) significant improvements over the
original which are documented in <a
href="http://www.spack.org/index.cgi/MailmanHelp">our
version</a> of the script.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-05-03 05:21

Message:
Logged In: YES 
user_id=12800

Care to submit a patch?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=534234&group_id=103

From noreply at sourceforge.net  Wed Oct 22 06:35:39 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Oct 22 06:36:11 2003
Subject: [ mailman-Bugs-826775 ] Change URL for submit buttons
Message-ID: <E1ACGL5-0000i9-00@sc8-sf-web1.sourceforge.net>

Bugs item #826775, was opened at 2003-10-20 13:06
Message generated for change (Comment added) made by windl
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=826775&group_id=103

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Ulrich Windl (windl)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Change URL for submit buttons

Initial Comment:
I have a special configuration, where the CGI scripts
have problems:
the hostname is like "host.domain.org" with two
ethernet interfaces, each having its own name like
"host-a.domain.org" and "host-b.domain.org". I also
have an alias like "mailman.domain.org" that is
intended to be used as virtual host for the CGI interface.
However not every URL in the CGI pages are correct. At
the moment, I cannot submit administrative changes,
because the SUBMIT button uses "host.domain.org" (which
has no address record associated with).
It also seems that access via the virtual host name
does not display the mailing lists being configured.
Where are the places I should look at to change URLs?
I think the submit buttons should have an URL...

----------------------------------------------------------------------

>Comment By: Ulrich Windl (windl)
Date: 2003-10-22 12:35

Message:
Logged In: YES 
user_id=181779

I found out that re-creating the mailing list auto-magically
fixed the issue. That's good. However it's not quite clear
which config variable gets misused to form the submit URL;
is it the NNTP host?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=826775&group_id=103

From noreply at sourceforge.net  Wed Oct 22 06:36:52 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Oct 22 06:37:01 2003
Subject: [ mailman-Bugs-826775 ] Change URL for submit buttons
Message-ID: <E1ACGMG-0000lx-00@sc8-sf-web1.sourceforge.net>

Bugs item #826775, was opened at 2003-10-20 13:06
Message generated for change (Comment added) made by windl
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=826775&group_id=103

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Ulrich Windl (windl)
Assigned to: Nobody/Anonymous (nobody)
Summary: Change URL for submit buttons

Initial Comment:
I have a special configuration, where the CGI scripts
have problems:
the hostname is like "host.domain.org" with two
ethernet interfaces, each having its own name like
"host-a.domain.org" and "host-b.domain.org". I also
have an alias like "mailman.domain.org" that is
intended to be used as virtual host for the CGI interface.
However not every URL in the CGI pages are correct. At
the moment, I cannot submit administrative changes,
because the SUBMIT button uses "host.domain.org" (which
has no address record associated with).
It also seems that access via the virtual host name
does not display the mailing lists being configured.
Where are the places I should look at to change URLs?
I think the submit buttons should have an URL...

----------------------------------------------------------------------

>Comment By: Ulrich Windl (windl)
Date: 2003-10-22 12:36

Message:
Logged In: YES 
user_id=181779

I found out that re-creating the mailing list auto-magically
fixed the issue. That's good. However it's not quite clear
which config variable gets misused to form the submit URL;
is it the NNTP host?

----------------------------------------------------------------------

Comment By: Ulrich Windl (windl)
Date: 2003-10-22 12:35

Message:
Logged In: YES 
user_id=181779

I found out that re-creating the mailing list auto-magically
fixed the issue. That's good. However it's not quite clear
which config variable gets misused to form the submit URL;
is it the NNTP host?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=826775&group_id=103

From noreply at sourceforge.net  Wed Oct 22 10:32:21 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Oct 22 10:32:39 2003
Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration
	patch
Message-ID: <E1ACK29-0004mO-00@sc8-sf-web3.sourceforge.net>

Patches item #820723, was opened at 2003-10-09 16:19
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman/pipermail/MHonArc integration patch

Initial Comment:
This patch tightly integrates the MHonArc mail-to-HTML
convertor  with Mailman and its internal pipermail
archiving code. 

The purpose of the patch is to produce a fusion of
(hopefully) the best features of pipermail and MHonArc
for handling Mailman mailing list archives.

For more detail see patch content or
http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html

----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2003-10-22 14:32

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.3-0.6.patch better supports the use of MHonArc
-saveresources option. Also fixes minor HTML syntax error in
mhonarc.mrc and author.mrc that affected generated date and
author index pages.


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-14 05:49

Message:
Logged In: YES 
user_id=75166

With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself 
defined in Defaults.py is the empty string and, until this is 
changed, the option to select MHonArc instead of pipermail for 
per-list archiving is not offered on the web admin GUI.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-10 17:51

Message:
Logged In: YES 
user_id=75166

Under some circumstances, when a single message is passed to
MHonArc for archiving via a pipe, MHonArc may finish its
processing and exit, closing its STDIN before the Mailman
process that invoked it has finished output of the message
to the pipe. Mistakenly, the patched pipermail code treated
this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

From noreply at sourceforge.net  Wed Oct 22 10:55:13 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Oct 22 10:55:55 2003
Subject: [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi
Message-ID: <E1ACKOH-0003P1-00@sc8-sf-web1.sourceforge.net>

Patches item #444884, was opened at 2001-07-26 18:27
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103

Category: Unofficial 2.0 patch
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 3
Submitted By: Richard Barrett (ppsys)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: Integration of Mailman & htdig for archi

Initial Comment:
This patch is applicable to Mailman 2.0.6 release that 
has had search enhancement patch 444879 patch 
installed - if your Defaults.py has the 
ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE 
in it then you've got that patch.

It replaces earlier patches 401670 and 402423 and is 
mainly to correct some problems arising from fixes 
introduced into Mailman by bug fix releases since the 
402423 patch. 

This patch integrates htdig with Mailman and provides:

1. per list search facility with a search form on the 
list's TOC page.

2. maintenance of privacy of private archives which 
requires the user to establish their credentials via 
the normal private archive access before any access 
via htdig is allowed.
   
3. a common base URL for both public and private 
archive access via htsearch results so that htdig 
indices are unaffected by changingan archive from 
private to public and vice versa. All access to 
archives via htdig is controlled by a new wrapped cgi-
bin script called htdig.py.
   
4. a new cron activated script and extra crontab entry 
which runs htdig regularly to maintain the per list 
search indices.
   
5. automatic creation, deletion and maintenance of 
htdig configuration files and such. Beyond installing 
htdig and telling Mailman where it is via mm_cfg you 
do not have to do any other setup. Well not quite you 
do have to set up a single per installation symlink to 
allow htdig to find the automatically generated per 
list htdig configuration files.

You probably want to run this patch as follows:

cd <mailman 2.0.6 untarred and unzipped directory>
patch -p1 < <this patch file>  

----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2003-10-22 14:55

Message:
Logged In: YES 
user_id=75166

htdig-2.1.3-0.4.patch provides minor improvements in
handling of HTTP request handled by htidg.py which lead to
the user receiving an authentication challenge.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-19 21:13

Message:
Logged In: YES 
user_id=75166

htdig-2.1.3-0.3.patch.gz add minor private archive security
improvements to the patch for MM 2.1.3

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-09-30 20:14

Message:
Logged In: YES 
user_id=75166

htdig-2.1.3-0.1.patch is a MM 2.1.3 compatible version of
the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-06-06 17:47

Message:
Logged In: YES 
user_id=75166

last comment should have read: 

htdig-2.1.2-0.4.patch.gz corrects an error in 2 scripts, 
mmsearch.py and remote_mmsearch, which caused an 
exception if list archives were being accessed via HTTPS and 
a search was performed.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-06-06 17:45

Message:
Logged In: YES 
user_id=75166

htdig-2.1.2-0.3.patch.gz corrects an error in 2 scripts, 
mmsearch.py and remote_mmsearch, which caused an 
exception if list archives were being accessed via HTTPS and 
a search was performed.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-05-01 19:00

Message:
Logged In: YES 
user_id=75166

htdig-2.1.2-0.3.patch.gz adds some minor performance 
improvement in template handling in MM 2.1.2

You should consider also applying this bug-fis patch:

[ 730769 ] template access hierarchy is broken

http://sourceforge.net/tracker/index.php?
func=detail&aid=730769&group_id=103&atid=100103

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-04-28 15:44

Message:
Logged In: YES 
user_id=75166

htdig-2.1.2-0.2.patch.gz corrects error in file uploaded as 
htdig-2.1.2-0.1.patch.gz. Sorry for any inconvenience.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-04-28 14:46

Message:
Logged In: YES 
user_id=75166

htdig-2.1.2-0.1.patch.gz is a revised version for MM 2.1.2 
compatibility.

It also incoporates a previosuly unpublished change to 
overcome a potential problem with htdig excluced urls - see 
the INSTALL.htdig-mm file for more information

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-03-21 18:29

Message:
Logged In: YES 
user_id=75166

htdig-2.1.1-0.4.patch.gz fixes a problem with mmsearch 
handling multi-page search results from htsearch.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-03-21 17:54

Message:
Logged In: YES 
user_id=75166

htdig-2.1.1-0.3.patch.gz fixes a fault when mmsearch.py is 
rasing an excpetion because it has had a problem running 
htsearch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-03-20 14:10

Message:
Logged In: YES 
user_id=75166

htdig-2.1.1-0.2.patch.gz close a security exploit which allows 
leakage of information held in htdig's per-list search indexes 
to users not authorized to view private list archives.

Read file INSTALL.htdig-mm installed by this patch for details 
and instructions for upgrading MM installations using earlier 
versions of this patch



----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-02-10 15:50

Message:
Logged In: YES 
user_id=75166

htdig-2.1.1-0.1.patch.gz introduces no functional change but 
applies without offset warnings to MM 2.1.1

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-02-05 18:12

Message:
Logged In: YES 
user_id=75166

It seems it is possible, if this patch is installed, for a list's 
htdig conf file and the list specific htdig index db files to be 
read directly through the web interface for list archives. 

Even if this patch isn't installed it seems a list's pipermail.pck 
file can also be read directly through the web interface for list 
archives.

This seems to be true for accesses via /pipermail for public 
lists and via /mailman/private for private lists.

The problem does not occur for htdig search results 
accessed via /mailman/htdig as the htdig.py script is more 
protective than private.py

Broadly speaking the data affected is availble to a user in 
normal operation which is why I do not consider the issue to 
be a security breach as such.

Adding the following RewriteRule to Apache's httpd.conf 
prevents the situation, assuming you got the RewriteEngine 
On:

RewriteRule ^(/pipermail/.*)/(pipermail.pck|htdig/[^/]*)$ 
$1/index.html [F]

RewriteRule ^(/mailman/private/.*)/(pipermail.pck|htdig/[^/]*)$ 
$1/index.htm
l [F]

You could, of course, substitute an R flag for the F flag on the 
RewriteRules and be more hacker friendly.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-22 14:20

Message:
Logged In: YES 
user_id=75166

htdig-2.1-0.3.patch corrects yet another bug in htdig.py. Hope 
that all of them!

Stops use of obsolete config variable DEFAULT_HOST in 
several files.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-15 20:18

Message:
Logged In: YES 
user_id=75166

htdig-2.1-0.2.patch corrects a bug in htdig.py and deals with 
an adverse interaction between htdig.py and a bug in 
$prefix/scripts/driver (see #668685 for a patch to fix this).

It also improves the content type and security handling by 
htdig.py for MM 2.1 version of patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-15 20:14

Message:
Logged In: YES 
user_id=75166

Uploaded wrong file mailer-2.0.13-0.4.patch on last attempt.

Should have been htdig-2.0.13-0.4.patch which improves the 
content type and security handling by htdig.py for MM 2.0.13 
version of patch.

Please ignore mailer-2.0.13-0.4.patch file

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-15 20:09

Message:
Logged In: YES 
user_id=75166

mailer-2.0.13-0.4.patch improves the content type and 
security handling by htdig.py for MM 2.0.13 version of patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-02 16:07

Message:
Logged In: YES 
user_id=75166

htdig-2.1-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-11 11:48

Message:
Logged In: YES 
user_id=75166

htdig-2.1b6-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1b6

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-04 10:53

Message:
Logged In: YES 
user_id=75166

htdig-2.0.13-0.3.patch corrects a minor typo in text appearing 
in the list TOC after the patch is applied.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-11-27 10:24

Message:
Logged In: YES 
user_id=75166

htdig-2.1b5-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1b5

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-10-30 11:43

Message:
Logged In: YES 
user_id=75166

htdig-2.1b4-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1b4

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-10-14 11:50

Message:
Logged In: YES 
user_id=75166

htdig-2.1b3-0.3.patch removes use of the file() function, used 
instead of the open() function, in three cron scripts added by 
the patch. Use of the file() function created an unnecessary 
dependency on Python 2.2

----------------------------------------------------------------------

Comment By: Colin Mackinlay (cmackinlay)
Date: 2002-10-12 16:51

Message:
Logged In: YES 
user_id=624179

Got a workaround!

The line referred to in the traceback:
 file(rundig_run_file, 'w').close()
is used to create a 'rundig_last_run' file of lenght 0 bytes
Creating this manually (or copying it) means the line isn't 
called and everything seems to work.

Either file() is not a valid function call or my python is broken - 
I'm not literate enough in python to know the answer though! 

----------------------------------------------------------------------

Comment By: Colin Mackinlay (cmackinlay)
Date: 2002-10-06 14:18

Message:
Logged In: YES 
user_id=624179

Just rebuilt MM as 2.1b3 with htdig.
Upgraded lists which had htdig before work fine
New lists give the obvious error:
  Unable to read word database file
  Did you run htmerge?
Running the cronjob doesn't fix as it used to, message is:
  Output from command /usr/bin/python -
S /usr/local/mailman/cron/nightly_htdig ..

Traceback (most recent call last):
  File "/usr/local/mailman/cron/nightly_htdig", line 153, in ?
    main()
  File "/usr/local/mailman/cron/nightly_htdig", line 118, in main
    file(rundig_run_file, 'w').close()
NameError: global name 'file' is not defined

The archive/htdig folder only contains the xx.conf file, but no 
db.xx files

If I copy in db.xx files from another list then the problem goes 
away (except I've now got an invalid set of references!)

Is this my elementary error or is it more sinister?!


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-15 11:02

Message:
Logged In: YES 
user_id=75166

htdig-2.1b3-0.2.patch corrects a dumb syntax error in htdig-
2.1b3-0.1.patch which will typically show up as logged errors 
in the operation of the ArchRunner qrunner at line 721 of 
HyperArch.py

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-14 16:51

Message:
Logged In: YES 
user_id=75166

htdig-2.1b3-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1b3

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-08 16:33

Message:
Logged In: YES 
user_id=12800

I've sent Richard some comments off-line about this patch.

Meta comments: the 2.0.x patches can't be officially
supported, but I'm going to create an unofficial patches
page off the wiki for where the 2.0 patches can be migrated.

I think this patch set is too big for MM2.1, but if it's
cleaned up as per my private message, let's re-evaluate it
for MM2.2 (or 3.0).

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-05 10:11

Message:
Logged In: YES 
user_id=75166

htdig-2.0.13-0.2.patch just adds a GPL notice to the patch


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-01 16:35

Message:
Logged In: YES 
user_id=75166

htdig-2.1b2-0.1.patch is a revised version of the patch 
that is compatible with MM 2.1b2

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-07-30 11:25

Message:
Logged In: YES 
user_id=75166

htdig-2.0.13-0.1.patch is purely cosmetic to get no mumble 
application to MM 2.0.13

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-07-25 15:07

Message:
Logged In: YES 
user_id=75166

Do not use htdig-2.0.12-0.1.patch there is an error in it.
Use htdig-2.0.12-0.2.patch instead

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-07-25 14:10

Message:
Logged In: YES 
user_id=75166

htdig-2.0.12-0.1.patch is a revised version of the patch that 
applies without complaint to MM 2.0.12.

It also add a facility for adding site wide htdig configuration 
attributes to all list specific htdig configuration files. 



----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-05-23 09:59

Message:
Logged In: YES 
user_id=75166

htdig-2.0.11-0.1.patch is a revised version of the patch that 
is compatible with MM 2.0.11

This version removes an incompatibility with Python 2.2 
which caused warning messages to be generated when any 
of the family cron/nightly_htdig scripts were run.

Some guidance on file access permissions for some htdig 
database files needed by rundig have been added to 
installation notes.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-04-19 10:59

Message:
Logged In: YES 
user_id=75166

htdig-2.0.10-0.1.patch is a revised version of the patch 
that is compatible with MM 2.0.10

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-04-08 17:46

Message:
Logged In: YES 
user_id=75166

htdig-2.0.9-0.1.patch is a revised version of the patch 
that is compatible with MM 2.0.9

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-03-06 16:22

Message:
Logged In: YES 
user_id=75166

htdig-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in 
mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002

Known deficiency is that the non-English versions of files under $build/templates still contain text in English 
and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in 
files under $build/messages remain to be done.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-12-17 16:56

Message:
Logged In: YES 
user_id=75166

htdig-2.1cvs-20011217.patch is a revised version of the 
patch that is compatible with the code published in mailman 
CVS on sourceforge as 11:50 GMT 17 Dec 2001

The only known deficiency is that the non-English versions 
of files under $build/templates still contain text in 
English and need translations I cannot do. Also the 
necessary pygettext activity and subsequent translations in 
files under $build/messages remain to be done.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-12-13 16:58

Message:
Logged In: YES 
user_id=75166

htdig-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in 
mailman-2.1a3.tgz on sourceforge.

The only known deficiency is that the non-English versions of files under $build/templates still contain text 
in English and need translations I cannot do. Also the necessary pygettext activity and subsequent 
translations in files under $build/messages remain to be done. 

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-28 17:33

Message:
Logged In: YES 
user_id=75166

The htdig-2.0.8-0.1.patch version of the patch resolves a problem that can arise with htdig indexing if the 
web_page_url for a list uses other than the http addressing (some folks want to use https). While specified 
as for MM 2.0.8 the revised patch should work OK with 2.0.7, 2.0.6 and probably back as far as 2.0.3. If 
you do not have the requirement for using other than http addressing in you lists web_page_urls it probably 
isn't worth the trouble of upgrading to this patch level.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-28 11:08

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-27 12:00

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to Mm 2.0.7

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-09 11:54

Message:
Logged In: YES 
user_id=75166

The htdig-2.0.6-03.patch version of the patch makes some 
previously hard-coded things configurable and enhances the 
capability to run the htdig searches and indexing on a 
different machine to the one delivering Mailman and 
Mailman's web UI.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103

From noreply at sourceforge.net  Wed Oct 22 13:41:09 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Oct 22 13:41:22 2003
Subject: [ mailman-Feature Requests-761484 ] Allow alternate email addresses
Message-ID: <E1ACMyr-0004k5-00@sc8-sf-web1.sourceforge.net>

Feature Requests item #761484, was opened at 2003-06-26 17:00
Message generated for change (Comment added) made by edgimar
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=761484&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Pug Bainter (phelim_gervase)
Assigned to: Nobody/Anonymous (nobody)
Summary: Allow alternate email addresses

Initial Comment:
Allow users to specify alternate email addresses that
they may post from. For example:

pug.bainter@pug.net would like to allow pug@pug.net as
well as pug.bainter@stardock.pug.net to be able to post
to the restricted lists that he's subscribed to.

----------------------------------------------------------------------

Comment By: Mark Edgington (edgimar)
Date: 2003-10-22 12:41

Message:
Logged In: YES 
user_id=227839

Yes, this would be an excellent feature.  Perhaps it could be done by grouping together distinct email addresses by some unique group identifier/name.  In other words, say I have a list-user joesmith@abcd.com, then this user might have a group ID associated with it of 1234.  Now, if I want, I can assign new list-user entries (i.e. jsmitty@defg.com) to this same group ID.  Then, all entries associated with a particular group ID could be administered (by the user) from the same webpage (some entries might want the nomail flag set, others not, etc.) -- it could be a miniature version of what the admin sees when administering users, but only showing entries of a particular group ID.
Also, this makes it easy when a user wants to unsubscribe from the list.  All of his/her entries can be deleted at once with an option that removes all entries associated with a certain group ID.  So, on the user-admin page, you'd want to distinguish between "remove an alternate email address from user profile" and "remove user profile" (which would remove all associated email addresses).

There are various other ways this grouping concept could be expanded for other purposes.  For example, there could be an administration page where profile-classes could be defined (which contain settings that apply to the user-profiles which are assigned to this profile-class).  Now every user-profile which has been set to belong to such-and-such a profile-class inherits/assumes the current settings of the profile-class.

(talk about a long-winded comment... :)


----------------------------------------------------------------------

Comment By: Pug Bainter (phelim_gervase)
Date: 2003-06-26 17:05

Message:
Logged In: YES 
user_id=484284

It would also be beneficial to allow a user or list to
recognize subdomains as acceptable email addresses for the user.

As above, pug.bainter@stardock.pug.net would be the same as
pug.bainter@pug.net.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=761484&group_id=103

From noreply at sourceforge.net  Wed Oct 22 13:53:35 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Oct 22 13:53:38 2003
Subject: [ mailman-Bugs-828381 ] ASCII decoding error
Message-ID: <E1ACNAt-0008V0-00@sc8-sf-web3.sourceforge.net>

Bugs item #828381, was opened at 2003-10-22 13:53
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=828381&group_id=103

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Benjamin Reed (rangerrick)
Assigned to: Nobody/Anonymous (nobody)
Summary: ASCII decoding error

Initial Comment:
I get the following when trying to hit the "members"
page on a mailing list we have.  If you need more
information for debugging or similar, let me know.

Traceback (most recent call last):
  File "/var/mailman/scripts/driver", line 87, in run_main
    main()
  File "/var/mailman/Mailman/Cgi/admin.py", line 192,
in main
    show_results(mlist, doc, category, subcat, cgidata)
  File "/var/mailman/Mailman/Cgi/admin.py", line 491,
in show_results
    form.AddItem(membership_options(mlist, subcat,
cgidata, doc, form))
  File "/var/mailman/Mailman/Cgi/admin.py", line 799,
in membership_options
    all = [_m.encode() for _m in mlist.getMembers()]
UnicodeError: ASCII decoding error: ordinal not in
range(128)

Python information:

Variable	Value
sys.version	2.2.2 (#1, Feb 24 2003, 19:13:11) [GCC
3.2.2 20030222 (Red Hat Linux 3.2.2-4)]
sys.executable	/usr/bin/python
sys.prefix	/usr
sys.exec_prefix	/usr
sys.path	/usr
sys.platform	linux2



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=828381&group_id=103

From noreply at sourceforge.net  Wed Oct 22 18:54:03 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Oct 22 18:55:03 2003
Subject: [ mailman-Feature Requests-828564 ] per-user "Reply-To:"
	configuration
Message-ID: <E1ACRrf-0007oB-00@sc8-sf-web2.sourceforge.net>

Feature Requests item #828564, was opened at 2003-10-22 22:54
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=828564&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jorge Bernal (koke)
Assigned to: Nobody/Anonymous (nobody)
Summary: per-user "Reply-To:" configuration

Initial Comment:
In order to prevent the periodic flame about
"Reply-To-harmful" and "Reply-To-is-good", it would be
a great feature if any user could choose if he/she
wants the "Reply-To" header to be modified or not

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=828564&group_id=103

From noreply at sourceforge.net  Wed Oct 22 19:54:58 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Oct 22 19:56:13 2003
Subject: [ mailman-Patches-573505 ] usenet threading improvements
Message-ID: <E1ACSoc-00070h-00@sc8-sf-web1.sourceforge.net>

Patches item #573505, was opened at 2002-06-25 07:59
Message generated for change (Comment added) made by mundaun
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103

Category: mail delivery
Group: Mailman 2.0.x
Status: Open
Resolution: None
Priority: 1
Submitted By: Mark Weaver (mdw21)
Assigned to: Nobody/Anonymous (nobody)
Summary: usenet threading improvements

Initial Comment:
Basically message-id munging for all messages.

Might be 
better as an option?  This helps with threading in usenet gating, as 
what happens is this:

someone sends a mail with message-
id foo@bar.com
gating replaces the message-id with 
mailman.123.456.list@list.com
list member replies via mail, 
"in-reply-to" header is set to the foo@bar.com
now when the 
message is gated it can't thread because in-reply-to: (which is 
translated into references:) is wrong.

Solution is to munge 
all message-ids.  Doesn't really do any harm AFAICT.

----------------------------------------------------------------------

Comment By: Michael Stucki (mundaun)
Date: 2003-10-23 01:54

Message:
Logged In: YES 
user_id=751974

Hello, 
 
we had exactly the same problem. However we run mailman 
2.1.2 where things seem to have changed, so I am now writing 
down the required steps for more recent releases... 
 
I had to copy the munging code from 
Mailman/Queue/NewsRunner.py to 
Mailman/Handlers/CookHeaders.py: 
 
block 1: 
=== 
# Matches our Mailman crafted Message-IDs.  See 
Utils.unique_message_id() 
mcre = re.compile(r""" 
    <mailman.                                     # match the prefix 
    \d+.                                          # serial number 
    \d+.                                          # time in seconds since epoch 
    \d+.                                          # pid 
    (?P<listname>[^@]+)                           # list's internal_name() 
    @                                             # localpart@dom.ain 
    (?P<hostname>[^>]+)                           # list's host_name 
    >                                             # trailer 
    """, re.VERBOSE) 
=== 
 
block 2: 
=== 
    hackmsgid = 1 
    if msgid: 
        mo = mcre.search(msgid) 
        if mo: 
            lname, hname = mo.group('listname', 'hostname') 
            if lname == mlist.internal_name() and hname == 
mlist.host_name: 
                hackmsgid = 0 
    if hackmsgid: 
        del msg['message-id'] 
        msg['Message-ID'] = Utils.unique_message_id(mlist) 
 
=== 
 
After that, my biggest problem was that I applied the changes 
but mailman didn't follow them. I finally recognised that I had to 
restart the qrunner daemon (which wasn't there in older 
releases). 
 
Hope this helps 
- michael 

----------------------------------------------------------------------

Comment By: Nicolas Marchildon (elecnix)
Date: 2003-01-16 06:11

Message:
Logged In: YES 
user_id=106549

I solved the problem by adding the munging code to
DeliverToList, in HandlerAPI.py, right before the message is
sent in the delivery pipeline, and removed it from
ToUsenet.py and CookHeaders.py. This way, the Message-ID
header is calculated only once, and used for all the steps
of the pipeline.

Nicolas Marchildon

----------------------------------------------------------------------

Comment By: Nicolas Marchildon (elecnix)
Date: 2003-01-16 05:21

Message:
Logged In: YES 
user_id=106549

The submitted patch does not do what it should to. The calls
to time.time() will not return the same thing as in
ToUsenet.py. I don't know much about the internals of
Mailman, and not much either about Python, so I don't really
know where to store the "correct" message ID so that it is
generated once, and used in both places.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103

From noreply at sourceforge.net  Thu Oct 23 06:30:08 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct 23 06:36:10 2003
Subject: [ mailman-Patches-828811 ] Reduced listinfo and admin CGI process
	size
Message-ID: <E1ACcjI-0002mU-00@sc8-sf-web4.sourceforge.net>

Patches item #828811, was opened at 2003-10-23 10:30
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=828811&group_id=103

Category: Web UI
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Reduced listinfo and admin CGI process size

Initial Comment:
When the CGI scripts listinfo.py and admin.py are
generating an overview page listing all the advertised
mailing lists, they accumulate in memory a MailingList
object for every mailing list to appear on the page.
For sites with a large number of lists this can lead to
the CGI process becoming quite large.

This patch changes the behaviour so that what is
accumulated in memory by the scripts is only the
information about each list that is necessary to
generate the overview page. This should reduce the
maximum size reached by the CGI process during their
execution.

This patch can be applied by running the following
command with either $build or $prefix as the current
directory, that is, you can apply the patch in the
build directory before running ./configure and make
install or to the installed system:

patch -p1 < path-to-patch-file

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=828811&group_id=103

From noreply at sourceforge.net  Thu Oct 23 11:39:53 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct 23 11:40:02 2003
Subject: [ mailman-Patches-828811 ] Reduced listinfo and admin CGI process
	size
Message-ID: <E1AChZ3-0003A9-00@sc8-sf-web1.sourceforge.net>

Patches item #828811, was opened at 2003-10-23 06:30
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=828811&group_id=103

Category: Web UI
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Reduced listinfo and admin CGI process size

Initial Comment:
When the CGI scripts listinfo.py and admin.py are
generating an overview page listing all the advertised
mailing lists, they accumulate in memory a MailingList
object for every mailing list to appear on the page.
For sites with a large number of lists this can lead to
the CGI process becoming quite large.

This patch changes the behaviour so that what is
accumulated in memory by the scripts is only the
information about each list that is necessary to
generate the overview page. This should reduce the
maximum size reached by the CGI process during their
execution.

This patch can be applied by running the following
command with either $build or $prefix as the current
directory, that is, you can apply the patch in the
build directory before running ./configure and make
install or to the installed system:

patch -p1 < path-to-patch-file

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-10-23 11:39

Message:
Logged In: YES 
user_id=12800

I haven't looked at the patch, but +1 on the idea.  Thanks!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=828811&group_id=103

From noreply at sourceforge.net  Thu Oct 23 13:18:54 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct 23 13:19:15 2003
Subject: [ mailman-Patches-746728 ] ssl support for list administration
Message-ID: <E1ACj6s-0001b3-00@sc8-sf-web2.sourceforge.net>

Patches item #746728, was opened at 2003-05-31 22:27
Message generated for change (Comment added) made by pheinlein
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=746728&group_id=103

Category: list administration
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: matze (indygena)
Assigned to: Nobody/Anonymous (nobody)
Summary: ssl support for list administration

Initial Comment:
adds ssl support for the administration interface. via
the boolean configuration parameter
DEFAULT_ADMIN_USE_SSL can be defined that the list
administration interface is accessed oven a ssl
encrypted connection

----------------------------------------------------------------------

>Comment By: Peer Heinlein (pheinlein)
Date: 2003-10-23 19:18

Message:
Logged In: YES 
user_id=581680

It work`s well and should be included into the normal Mailman as 
soon as possible. 
 
But it would be better, if Mailman produces a HTTP 301 redirect to 
https, if the admin login page is accessed via http instead of https. 
 
That would take care of having no admin password transferred to 
mailman without using an encrypted connection. 
 
And -- this patch should procude a similar 301-redirect if 
/mailman/create ist accessed via http. :-) 
 
 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=746728&group_id=103

From noreply at sourceforge.net  Fri Oct 24 09:03:53 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Oct 24 09:04:08 2003
Subject: [ mailman-Feature Requests-829568 ] No effect after editing
	templates
Message-ID: <E1AD1bd-0007rF-00@sc8-sf-web1.sourceforge.net>

Feature Requests item #829568, was opened at 2003-10-24 13:03
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=829568&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: b_user (b_user)
Assigned to: Nobody/Anonymous (nobody)
Summary: No effect after editing templates

Initial Comment:
Hi,

I?m a little bit confused. When editing for example the 
listinfo.html template I see the changing on my mailman 
webinterface.
But when I change any template of the ones which 
illustrate the mails, there is no visible effect on it. Even 
when I reload mailman, reboot the computer or create a 
new list after editing the templates there is nothing 
changed in the presentation of mailman.

I?m very appreciate for any helpful answers.
I want to make the look&feel of my local mailman 
installation more handsome for my purpose.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=829568&group_id=103

From noreply at sourceforge.net  Sat Oct 25 00:51:55 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat Oct 25 00:52:04 2003
Subject: [ mailman-Bugs-829982 ] MakeCookie/WebAuthent fail when a user
	changes the password
Message-ID: <E1ADGP5-0006I0-00@sc8-sf-web2.sourceforge.net>

Bugs item #829982, was opened at 2003-10-24 23:51
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=829982&group_id=103

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Pablo Chamorro C. (pchamorro)
Assigned to: Nobody/Anonymous (nobody)
Summary: MakeCookie/WebAuthent fail when a user changes the password

Initial Comment:
I just created a new list and I suscribed some users,
but when a user changes his password Mailman shows this
sad message:

Bug in Mailman version 2.1.3

We're sorry, we hit a bug! ....

Traceback:

Traceback (most recent call last):
  File "/var/mailman/scripts/driver", line 87, in run_main
    main()
  File "/var/mailman/Mailman/Cgi/private.py", line 120,
in main
    password, username):
  File "/var/mailman/Mailman/SecurityManager.py", line
219, in WebAuthenticate
    print self.MakeCookie(ac, user)
  File "/var/mailman/Mailman/SecurityManager.py", line
228, in MakeCookie
    raise ValueError
ValueError

I could reproduce this error in other server and with
others lists and users.  I was trying under RH 9.0. 
Please help me...




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=829982&group_id=103

From noreply at sourceforge.net  Sat Oct 25 00:59:05 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat Oct 25 00:59:36 2003
Subject: [ mailman-Bugs-829982 ] MakeCookie/WebAuthent fail when a user
	changes the password
Message-ID: <E1ADGW1-0006Sh-00@sc8-sf-web2.sourceforge.net>

Bugs item #829982, was opened at 2003-10-24 23:51
Message generated for change (Settings changed) made by pchamorro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=829982&group_id=103

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
>Priority: 9
Submitted By: Pablo Chamorro C. (pchamorro)
Assigned to: Nobody/Anonymous (nobody)
Summary: MakeCookie/WebAuthent fail when a user changes the password

Initial Comment:
I just created a new list and I suscribed some users,
but when a user changes his password Mailman shows this
sad message:

Bug in Mailman version 2.1.3

We're sorry, we hit a bug! ....

Traceback:

Traceback (most recent call last):
  File "/var/mailman/scripts/driver", line 87, in run_main
    main()
  File "/var/mailman/Mailman/Cgi/private.py", line 120,
in main
    password, username):
  File "/var/mailman/Mailman/SecurityManager.py", line
219, in WebAuthenticate
    print self.MakeCookie(ac, user)
  File "/var/mailman/Mailman/SecurityManager.py", line
228, in MakeCookie
    raise ValueError
ValueError

I could reproduce this error in other server and with
others lists and users.  I was trying under RH 9.0. 
Please help me...




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=829982&group_id=103

From noreply at sourceforge.net  Mon Oct 27 00:17:07 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Oct 27 00:17:33 2003
Subject: [ mailman-Patches-694902 ] Fix MIME digest attachment
Message-ID: <E1ADzkZ-0005im-00@sc8-sf-web3.sourceforge.net>

Patches item #694902, was opened at 2003-02-28 08:02
Message generated for change (Comment added) made by mrjc
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=694902&group_id=103

Category: mail delivery
Group: Mailman 2.1
Status: Closed
Resolution: Accepted
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix MIME digest attachment

Initial Comment:
ToDigest.py in Mailman 2.1.1 was improved in handling
plain text digest but there was a side effect in MIME
digest.
We should now use copy of Message instance because the
original is scrubbed afterwards.


----------------------------------------------------------------------

Comment By: Martin RJ. Cleaver (mrjc)
Date: 2003-10-27 05:17

Message:
Logged In: YES 
user_id=50125

did this make 2.1.3?

I'm still getting this: 
http://cp1.myhostdns.org/pipermail/webmasters_mbssrc.com/
2003-October/000025.html whenever my users post HTML 
messages.

Thanks, M. 

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-04-11 02:48

Message:
Logged In: YES 
user_id=12800

The patch looks good, so I'm closing this in anticipation
that testing will work out.

I'm with tkikuchi though, I can't see how this patch could
possibly evoke dwighternest's bug.


----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2003-04-09 01:29

Message:
Logged In: YES 
user_id=67709

This patch is only 3 lines. Please check if your
Handlers/ToDigest.py was properly patched. I can't see
anything related to this patch from your traceback log.


----------------------------------------------------------------------

Comment By: Dwight Ernest (dwighternest)
Date: 2003-04-09 01:17

Message:
Logged In: YES 
user_id=740960

After I applied this patch, I started to receive uncaught
exceptions leading to 100% of my postings being shunted.

Apr 08 10:03:57 2003 (20895) Uncaught runner exception:
'module' object has no attribute 'process'
Apr 08 10:03:57 2003 (20895) Traceback (most recent call last):
  File "/var/mailman/Mailman/Queue/Runner.py", line 105, in
_oneloop
    self._onefile(msg, msgdata)
  File "/var/mailman/Mailman/Queue/Runner.py", line 155, in
_onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "/var/mailman/Mailman/Queue/VirginRunner.py", line
38, in _dispose
    return IncomingRunner._dispose(self, mlist, msg, msgdata)
  File "/var/mailman/Mailman/Queue/IncomingRunner.py", line
130, in _dispose
    more = self._dopipeline(mlist, msg, msgdata, pipeline)
  File "/var/mailman/Mailman/Queue/IncomingRunner.py", line
153, in _dopipeline
    sys.modules[modname].process(mlist, msg, msgdata)
AttributeError: 'module' object has no attribute 'process'

Apr 08 10:03:57 2003 (20895) SHUNTING:
1049803236.489061+24037ff46bd58f849bf9a9646db1dd90bb863d2c



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=694902&group_id=103

From noreply at sourceforge.net  Mon Oct 27 05:51:50 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Oct 27 05:51:53 2003
Subject: [ mailman-Feature Requests-830905 ] Custom authentification option
Message-ID: <E1AE4yU-0003pV-00@sc8-sf-web1.sourceforge.net>

Feature Requests item #830905, was opened at 2003-10-27 11:51
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=830905&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Miha Lampret (mlampret)
Assigned to: Nobody/Anonymous (nobody)
Summary: Custom authentification option

Initial Comment:
It wuld be nice if we could use external program for checking 
passwords when logging in to admin area..

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=830905&group_id=103

From noreply at sourceforge.net  Mon Oct 27 13:53:51 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Oct 27 13:53:58 2003
Subject: [ mailman-Bugs-828381 ] ASCII decoding error
Message-ID: <E1AECUx-0004WS-00@sc8-sf-web4.sourceforge.net>

Bugs item #828381, was opened at 2003-10-22 10:53
Message generated for change (Comment added) made by latchkey
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=828381&group_id=103

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Benjamin Reed (rangerrick)
Assigned to: Nobody/Anonymous (nobody)
Summary: ASCII decoding error

Initial Comment:
I get the following when trying to hit the "members"
page on a mailing list we have.  If you need more
information for debugging or similar, let me know.

Traceback (most recent call last):
  File "/var/mailman/scripts/driver", line 87, in run_main
    main()
  File "/var/mailman/Mailman/Cgi/admin.py", line 192,
in main
    show_results(mlist, doc, category, subcat, cgidata)
  File "/var/mailman/Mailman/Cgi/admin.py", line 491,
in show_results
    form.AddItem(membership_options(mlist, subcat,
cgidata, doc, form))
  File "/var/mailman/Mailman/Cgi/admin.py", line 799,
in membership_options
    all = [_m.encode() for _m in mlist.getMembers()]
UnicodeError: ASCII decoding error: ordinal not in
range(128)

Python information:

Variable	Value
sys.version	2.2.2 (#1, Feb 24 2003, 19:13:11) [GCC
3.2.2 20030222 (Red Hat Linux 3.2.2-4)]
sys.executable	/usr/bin/python
sys.prefix	/usr
sys.exec_prefix	/usr
sys.path	/usr
sys.platform	linux2



----------------------------------------------------------------------

Comment By: Jon Stevens (latchkey)
Date: 2003-10-27 10:53

Message:
Logged In: YES 
user_id=234781

I recently posted this on the developer mailing list...no
response...=(

------ Forwarded Message
From: Jon Scott Stevens
Date: Tue, 21 Oct 2003 15:22:56 -0700
To: <mailman-developers@python.org>
Subject: [Mailman-Developers] Bug in mailman 2.1.3

Hello everyone.

I just got the stack trace below from one of my list
admins...not sure how
he screwed things up...but I figured I would let you
know...based on the
traceback, it seems that he somehow got a strange character
into the list of
members...

[share] 3:16pm ~ > ./bin/check_db -v sfindie-fence
List: sfindie-fence
   /usr/local/mailman/lists/sfindie-fence/config.pck: okay
   /usr/local/mailman/lists/sfindie-fence/config.pck.last: okay
   /usr/local/mailman/lists/sfindie-fence/config.db: okay
   /usr/local/mailman/lists/sfindie-fence/config.db.last: okay

[share] 3:17pm ~ > ./bin/list_members -u sfindie-fence
            [no output]
[share] 3:18pm ~ > ./bin/list_members -i sfindie-fence
?knights_bishop@yahooooooo.com
[share] 3:18pm ~ > ./bin/list_members -i sfindie-fence > bad.txt
[share] 3:19pm ~ > ./bin/remove_members -f bad.txt sfindie-fence

Yup...removing that address solved the problem.

Note: this list admin only has access to the web interface.
So, somehow he
was able to send corrupt data to the server which caused
this problem.
Probably not a good thing. =)

---------------------------------------------------------------------------

Bug in Mailman version 2.1.3

We're sorry, we hit a bug!

If you would like to help us identify the problem, please
email a copy of
this page to the webmaster for this site with a description
of what
happened. Thanks!
Traceback:

Traceback (most recent call last):
  File "/usr/local/mailman/scripts/driver", line 87, in run_main
    main()
  File "/usr/local/mailman/Mailman/Cgi/admin.py", line 192,
in main
    show_results(mlist, doc, category, subcat, cgidata)
  File "/usr/local/mailman/Mailman/Cgi/admin.py", line 491,
in show_results
    form.AddItem(membership_options(mlist, subcat, cgidata,
doc, form))
  File "/usr/local/mailman/Mailman/Cgi/admin.py", line 799, in
membership_options
    all = [_m.encode() for _m in mlist.getMembers()]
UnicodeError: ASCII decoding error: ordinal not in range(128)


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=828381&group_id=103

From noreply at sourceforge.net  Wed Oct 29 05:39:38 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Oct 29 05:39:43 2003
Subject: [ mailman-Patches-818601 ] "Announcement-only" (read only) list
Message-ID: <E1AEnjm-0001r7-00@sc8-sf-web1.sourceforge.net>

Patches item #818601, was opened at 2003-10-06 22:07
Message generated for change (Comment added) made by hatukanezumi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_id=103

Category: Web UI
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
>Summary: "Announcement-only" (read only) list

Initial Comment:
Documents say that Mailman "supports a wide range of
mailing list types, such as general discussion lists and
announce-only lists".  It's exactly true.  But some people 
wish really "announcement-only" feature.

By `Announcement-only' feature:
o Posting by e-mail is not allowed at all.  All messages
  to posting address are forwarded to owners and no other 
  users won't receive it.
o Web interface is provided so that only specified users
  ("posters") can post messages to list.

For example for `mail magazine' publishers,
`announcement-only' list is safer (Oooops! I've
approved the SPAM!) and let them be free from
moderation tasks.

Changes on codes:
o New CGI script `post'.
o New handler `Posttop' which switches messages bound to 
  list to owners (only on annnouncement-only list).
o New `announcement_only' configuration directive.
o Some modifications of templates.


Notice: By now this is buggie (both in Python and English).
    Comments and Fixes are welcome.


----------------------------------------------------------------------

>Comment By: Hatuka*nezumi (hatukanezumi)
Date: 2003-10-29 19:39

Message:
Logged In: YES 
user_id=529503

rel.1.0.

o Confusing "announcement-only" has been changed to "read-only".
o New admin category.


----------------------------------------------------------------------

Comment By: Hatuka*nezumi (hatukanezumi)
Date: 2003-10-09 23:51

Message:
Logged In: YES 
user_id=529503

rel.0.2.

* Posttop handler now placed after Hold handler so that 
  spam discarding and auto-response are capable.

* Global pipelone processing are ommitted when:
  --------------------------------------
  SpamDetect           : [A] and [W]
  Approve              :         [W]
  ReplyBot             :         [W]
  Moderate             : [A] 
  Hold                 :
  - administrivia      : [A]
  - too many recips    : [A]
  - implicit dest.     : [A]
  - suspicious headers : [A] and not [W]
  - message size       : [A] and not [W]
  - news moderation    : [A] and not [W]
  Posttop              : (if [A], may be switched to owner
pipeline.)
  AvoidDuplicates      : [A]
  ------------------------------
  [A]: list is announcement-only.
  [W]: message is posted from Web (by `poster').

* Additional modification to templates.

* Some admin option categories are hidden.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_id=103

From noreply at sourceforge.net  Wed Oct 29 18:35:34 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Oct 29 18:36:27 2003
Subject: [ mailman-Bugs-832748 ] unsubscribe_policy problem
Message-ID: <E1AEzqg-0000M9-00@sc8-sf-web2.sourceforge.net>

Bugs item #832748, was opened at 2003-10-30 01:35
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=832748&group_id=103

Category: (un)subscribing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Pasi Sj?holm (tigeli)
Assigned to: Nobody/Anonymous (nobody)
Summary: unsubscribe_policy problem

Initial Comment:
User is able to unsubscribe even unsubscribe_policy is
true.

Go to listinfo page of some list and write a
email-address to:

"To unsubscribe from Tietoliikenne, get a password
reminder, or change your subscription options enter
your subscription email address:"

after that hit the "unsubscribe or edit
options"-button. New page opens and hit the unsubscribe
button... bang confirmation mail goes to user and he
can really unsubscribe.. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=832748&group_id=103

From noreply at sourceforge.net  Thu Oct 30 06:39:49 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct 30 06:40:13 2003
Subject: [ mailman-Bugs-820322 ] Crash when global subcription change causes
	collision
Message-ID: <E1AFB9Z-0006Lt-00@sc8-sf-web3.sourceforge.net>

Bugs item #820322, was opened at 2003-10-08 22:47
Message generated for change (Comment added) made by simonha
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=820322&group_id=103

Category: (un)subscribing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Rich Pasco (pasco)
Assigned to: Nobody/Anonymous (nobody)
Summary: Crash when global subcription change causes collision

Initial Comment:
I ran into this bug in MailMan version 2.1.2 today:

If you change your e-mail address "globally" (on all
lists to which you subscribe), and one of those lists
(other than the one whose options page you're working
from) already has a subscription under your new address
(as well as your old address), then MailMan will crash
(and display an exception traceback).

For example, I was working from the web-team page
http://domain.net/mailman/options/listname
as I tried to change my address globally.  This would
affect about ten lists to which my old address
subscribed, including a list called "Team" among
others.  But "Team" already had my new address among
its subscribers, so it could not accept another one. 
Rather than giving a graceful error message when it
discovered this, MailMan just crashed.

I didn't capture the exception traceback, but it should
be easy to reproduce.

     - Rich

----------------------------------------------------------------------

Comment By: Simon Harrison (simonha)
Date: 2003-10-30 11:39

Message:
Logged In: YES 
user_id=898088

I have experience the same problem, here is our traceback:

Traceback:

Traceback (most recent call last):
  File "/usr/local/mailman-2.1.2/scripts/driver", line 87, in 
run_main
    main()
  File "/usr/local/mailman-2.1.2/Mailman/Cgi/confirm.py", line 
131, in main
    addrchange_confirm(mlist, doc, cookie)
  File "/usr/local/mailman-2.1.2/Mailman/Cgi/confirm.py", line 
492, in addrchange_confirm
    op, oldaddr, newaddr = mlist.ProcessConfirmation(cookie)
  File "/usr/local/mailman-2.1.2/Mailman/MailList.py", line 1113, 
in ProcessConfirmation
    self.ApprovedChangeMemberAddress(oldaddr, newaddr, 
globally)
  File "/usr/local/mailman-2.1.2/Mailman/MailList.py", line 1048, 
in ApprovedChangeMemberAddress
    mlist.changeMemberAddress(oldaddr, newaddr)
  File "/usr/local/mailman-2.1.2/Mailman/OldStyleMemberships.
py", line 251, in changeMemberAddress
    password=xxxxxxxx, language=lang)
  File "/usr/local/mailman-2.1.2/Mailman/OldStyleMemberships.
py", line 175, in addNewMember
    raise Errors.MMAlreadyAMember, member
MMAlreadyAMember: oneofourusers@ourorganisation.org.uk

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=820322&group_id=103

From noreply at sourceforge.net  Thu Oct 30 17:05:20 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Oct 30 17:06:29 2003
Subject: [ mailman-Bugs-833384 ] wrong moderator password shouldn't silently
	discard message
Message-ID: <E1AFKuu-0006Hl-00@sc8-sf-web3.sourceforge.net>

Bugs item #833384, was opened at 2003-10-30 17:05
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=833384&group_id=103

Category: None
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Ken Olum (kdolum)
Assigned to: Nobody/Anonymous (nobody)
Summary: wrong moderator password shouldn't silently discard message

Initial Comment:
If you reply to the approval required message and give
an approved: line, but mistype the password, the
pending message is silently discarded.  I think that's
a scary misfeature.  I think in this case it should
reject your confirmation mail with an error saying that
the password is wrong, since obviously you're
attempting to get the message approved.  Otherwise, you
never know that the message has been discarded except
that you don't see it appear on the list, and then it
is too late to recover it.

It would also be nice for the site password to be
usable for message approval.  (Now you see how I
discovered the problem above.)


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=833384&group_id=103

From noreply at sourceforge.net  Fri Oct 31 12:34:12 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Oct 31 12:34:16 2003
Subject: [ mailman-Bugs-833762 ] virus detected on file within tgz
Message-ID: <E1AFdA4-0004z5-00@sc8-sf-web3.sourceforge.net>

Bugs item #833762, was opened at 2003-10-31 17:34
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=833762&group_id=103

Category: configuring/installing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Gabriel Zorrilla (gabrielz1)
Assigned to: Nobody/Anonymous (nobody)
Summary: virus detected on file within tgz

Initial Comment:
Hi, After downloading the file my antivirus popped up 
saying that it found Exploit/iFrame under file nimda.txt

Best regards

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=833762&group_id=103