From noreply at sourceforge.net  Sat Nov  1 19:45:47 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat Nov  1 19:45:51 2003
Subject: [ mailman-Patches-834357 ] Allow list templates for archives
Message-ID: <E1AG6NH-0003Pr-00@sc8-sf-web2.sourceforge.net>

Patches item #834357, was opened at 2003-11-02 01:45
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=834357&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Nicolas Barcet (nbarcet)
Assigned to: Nobody/Anonymous (nobody)
Summary: Allow list templates for archives

Initial Comment:
The template mechanism currently does not work in
HyperArchiver : 

It is not possible to modify specifically the template
for a given site in the archive template (placing a
list specific template in
/var/lib/Mailman/lists/<listname>/<lang>/ because of a
small bug in Mailman.Archiver.HyperHarch.

To fix it modify
/usr/lib/mailman/Mailman/Archiver/HyperArch.py, in
function quick_maketext, change line 175:

        template = Utils.maketext(templatefile,
lang=lang, raw=1)

into:

        template = Utils.maketext(templatefile,
lang=lang, raw=1, mlist=mlist)

And it works...
Nick

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

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

From noreply at sourceforge.net  Sun Nov  2 06:22:09 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Nov  2 06:22:12 2003
Subject: [ mailman-Bugs-834486 ] Uncatched ValueError in Scrubber
Message-ID: <E1AGGJ7-0003ZG-00@sc8-sf-web2.sourceforge.net>

Bugs item #834486, was opened at 2003-11-02 12:22
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=834486&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Uncatched ValueError in Scrubber

Initial Comment:

Mailman 2.1.2, python 2.2

Nov 01 20:40:04 2003 (10542) Uncaught runner exception:
Empty module name
Nov 01 20:40:04 2003 (10542) Traceback (most recent
call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py",
line 105, in _oneloop
    self._onefile(msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/Runner.py",
line 155, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File
"/usr/local/mailman/Mailman/Queue/IncomingRunner.py",
line 130, in _dispose
    more = self._dopipeline(mlist, msg, msgdata, pipeline)
  File
"/usr/local/mailman/Mailman/Queue/IncomingRunner.py",
line 153, in _dopipeline
    sys.modules[modname].process(mlist, msg, msgdata)
  File
"/usr/local/mailman/Mailman/Handlers/ToDigest.py", line
89, in process
    send_digests(mlist, 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
308, in process
    t = t.encode(charset, 'replace')
  File "/usr/lib/python2.2/encodings/__init__.py", line
51, in search_function
    mod = __import__(modname,globals(),locals(),'*')
ValueError: Empty module name

This is still uncorrected in v2_1-branch

Attached a proposed fix.



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

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

From noreply at sourceforge.net  Sun Nov  2 14:41:34 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Nov  2 14:41:38 2003
Subject: [ mailman-Patches-713522 ] Spambayes integration
Message-ID: <E1AGO6Q-0001XQ-00@sc8-sf-web4.sourceforge.net>

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

Category: list administration
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Barry A. Warsaw (bwarsaw)
Assigned to: Nobody/Anonymous (nobody)
Summary: Spambayes integration

Initial Comment:
Here's a patch I developed in Jan 2003 to integrate
Spambayes http://spambayes.sf.net into Mailman.  It's
very experimental but provide here for fun.  If people
like it I could see it becoming part of Mailman 2.2 or 3.0

You need to separately download the spambayes distutils
tarball and drop it in Mailman's misc directory.  Check
that the version value in misc/Makefile.in matches.

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

>Comment By: Simone Piunno (pioppo)
Date: 2003-11-02 20:41

Message:
Logged In: YES 
user_id=227443

Revised patch for 2.1.3+
This patch works with spambayes-1.0a6.1.tar.gz
You have to 
 1. download this file, 
 2. unpack it (will create directory spambayes-1.0a6)
 3. rename the directory from spambayes-1.0a6 to
spambayes-1.0a6.1,
 4. re-pack it (tar cvzf spambayes-1.0a6.1.tar.gz
spambayes-1.0a6.1)
 5. put the new tar file in the misc directory
 6. apply the new patch.
This revised patch includes a fix for bug #715248 (a bug in
spambayes) which spambayes people acknowledged but haven't
fixed so far.
Note also that spambayes-1.0a6 requires at least python 2.3
(1.0a7 should lower the requirement again to 2.2)
Happy filtering.

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

Comment By: Simone Piunno (pioppo)
Date: 2003-04-07 00:41

Message:
Logged In: YES 
user_id=227443

I'm attaching a safe patch solving all the problems on Barry's one. 
It must be used together with #715248 (for spambayes 1.0a2) 
see 
http://sourceforge.net/tracker/index.php?func=detail&aid=715248&group_id=61702&atid=498103 
 
There are still missing functionalities, e.g. training on false 
negatives for non-moderated lists. 
 
Now I'm working on functionality enhancements. 

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

Comment By: Simone Piunno (pioppo)
Date: 2003-04-03 22:59

Message:
Logged In: YES 
user_id=227443

I'm testing this patch on a real environment and there are 
problems, namely: 
 
1. wrong umask when creating spam.pck 
2. insuffiently defensive call to .store() 
3. creates and loads spam.pck even for lists where 
use_spambayes==0 
4. lots of these: 
 
Apr 03 22:20:33 2003 (730) Uncaught runner exception:  
Apr 03 22:20:33 2003 (730) Traceback (most recent call last): 
  File "/home/mailman21/Mailman/Queue/Runner.py", line 105, in 
_oneloop 
    self._onefile(msg, msgdata) 
  File "/home/mailman21/Mailman/Queue/Runner.py", line 155, in 
_onefile 
    keepqueued = self._dispose(mlist, msg, msgdata) 
  File "/home/mailman21/Mailman/Queue/OutgoingRunner.py", line 
69, in _dispose 
    mlist.Load() 
  File "/home/mailman21/Mailman/MailList.py", line 626, in Load 
    self._spamdb = hammie.open(path, 0) 
  File "/home/mailman21/pythonlib/spambayes/hammie.py", line 
262, in open 
    b = storage.PickledClassifier(filename) 
  File "/home/mailman21/pythonlib/spambayes/storage.py", line 
80, in __init__ 
    self.load() 
  File "/home/mailman21/pythonlib/spambayes/storage.py", line 
98, in load 
    tempbayes = pickle.load(fp) 
EOFError 
 
The attached patch is an evolution of Barry's one trying to address 
issues 1-3.  4 is still unsolved, I'm investigating. 
 
Additionally, I'd want to add an header to messages publishing 
the spambayes score, so I've added some line to SpamDetect.py 
but still without success (the header does not get appended). 

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

Comment By: Simone Piunno (pioppo)
Date: 2003-04-03 22:58

Message:
Logged In: YES 
user_id=227443

I'm testing this patch on a real environment and there are 
problems, namely: 
 
1. wrong umask when creating spam.pck 
2. insuffiently defensive call to .store() 
3. creates and loads spam.pck even for lists where 
use_spambayes==0 
4. lots of these: 
 
Apr 03 22:20:33 2003 (730) Uncaught runner exception:  
Apr 03 22:20:33 2003 (730) Traceback (most recent call last): 
  File "/home/mailman21/Mailman/Queue/Runner.py", line 105, in 
_oneloop 
    self._onefile(msg, msgdata) 
  File "/home/mailman21/Mailman/Queue/Runner.py", line 155, in 
_onefile 
    keepqueued = self._dispose(mlist, msg, msgdata) 
  File "/home/mailman21/Mailman/Queue/OutgoingRunner.py", line 
69, in _dispose 
    mlist.Load() 
  File "/home/mailman21/Mailman/MailList.py", line 626, in Load 
    self._spamdb = hammie.open(path, 0) 
  File "/home/mailman21/pythonlib/spambayes/hammie.py", line 
262, in open 
    b = storage.PickledClassifier(filename) 
  File "/home/mailman21/pythonlib/spambayes/storage.py", line 
80, in __init__ 
    self.load() 
  File "/home/mailman21/pythonlib/spambayes/storage.py", line 
98, in load 
    tempbayes = pickle.load(fp) 
EOFError 
 
The attached patch is an evolution of Barry's one trying to address 
issues 1-3.  4 is still unsolved, I'm investigating. 
 
Additionally, I'd want to add an header to messages publishing 
the spambayes score, so I've added some line to SpamDetect.py 
but still without success (the header does not get appended). 

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

Comment By: Simone Piunno (pioppo)
Date: 2003-04-01 23:49

Message:
Logged In: YES 
user_id=227443

LOL! 

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-04-01 23:19

Message:
Logged In: YES 
user_id=12800

Oh please gawds of SF, accept my burnt offering of a patch
as my supplication to your greatness.  I have Checkethed the
Holy CheckBox and Fillethed in the Holy TextBox.  Now I go
to Submitteth this Update.

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

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

From noreply at sourceforge.net  Mon Nov  3 08:14:48 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov  3 08:14:52 2003
Subject: [ mailman-Bugs-835012 ] incorrect permissions on archive index file
Message-ID: <E1AGeXg-0000jM-00@sc8-sf-web2.sourceforge.net>

Bugs item #835012, was opened at 2003-11-03 13:14
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=835012&group_id=103

Category: security/privacy
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Rohan Carly (rohanc)
Assigned to: Nobody/Anonymous (nobody)
Summary: incorrect permissions on archive index file

Initial Comment:
The index file for list archives is created with the wrong 
file permissions. I'm referring to:

mailman/archives/private/ --listname-- / index.html

All my lists have index.html set to "rw-rw-rw-" which 
seems too permissive.

I think this can be corrected by modifiying the 
Archiver.InitVars method inside the file:

   mailman/Mailman/Archiver/Archiver.py .

I just added:
   os.umask(omask)
before the line that reads:
   fp = open(indexfile, 'w')

I run Mailman 2.1.3.








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

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

From noreply at sourceforge.net  Mon Nov  3 08:50:42 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov  3 08:50:53 2003
Subject: [ mailman-Bugs-832748 ] unsubscribe_policy problem
Message-ID: <E1AGf6Q-0002UN-00@sc8-sf-web3.sourceforge.net>

Bugs item #832748, was opened at 2003-10-29 18:35
Message generated for change (Comment added) made by bwarsaw
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: Closed
>Resolution: Fixed
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.. 

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-03 08:50

Message:
Logged In: YES 
user_id=12800

Fixed by application of modified patch posted to
mailman-developers (please attached patches to the tracker
item in the future -- thanks!)


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

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

From noreply at sourceforge.net  Mon Nov  3 08:58:15 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov  3 08:58:24 2003
Subject: [ mailman-Bugs-835036 ] Bug encountered when doing global change of
	address
Message-ID: <E1AGfDj-0002Wb-00@sc8-sf-web4.sourceforge.net>

Bugs item #835036, was opened at 2003-11-03 08:58
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=835036&group_id=103

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Clyde Jones (clydec)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bug encountered when doing global change of address

Initial Comment:
I was trying to do a global change of name/address for
myself and encountered this bug.  The new address was
already a member of one of the mailing lists

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

Bug in Mailman version 2.1.2

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 "/home/usr/local/mailman/scripts/driver", line
87, in run_main
    main()
  File
"/home/usr/local/mailman/Mailman/Cgi/confirm.py", line
131, in main
    addrchange_confirm(mlist, doc, cookie)
  File
"/home/usr/local/mailman/Mailman/Cgi/confirm.py", line
492, in addrchange_confirm
    op, oldaddr, newaddr =
mlist.ProcessConfirmation(cookie)
  File "/home/usr/local/mailman/Mailman/MailList.py",
line 1113, in ProcessConfirmation
    self.ApprovedChangeMemberAddress(oldaddr, newaddr,
globally)
  File "/home/usr/local/mailman/Mailman/MailList.py",
line 1032, in ApprovedChangeMemberAddress
    self.changeMemberAddress(oldaddr, newaddr)
  File
"/home/usr/local/mailman/Mailman/OldStyleMemberships.py",
line 251, in changeMemberAddress
    password=password, language=lang)
  File
"/home/usr/local/mailman/Mailman/OldStyleMemberships.py",
line 175, in addNewMember
    raise Errors.MMAlreadyAMember, member
MMAlreadyAMember: clyde.jones@thermo.com





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

Python information:
Variable Value 
sys.version 2.2.3 (#2, Jul 17 2003, 14:48:38) [GCC
egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)]  
sys.executable /usr/bin/python  
sys.prefix /usr/local  
sys.exec_prefix /usr/local  
sys.path /usr/local  
sys.platform linux2  




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

Environment variables:
Variable Value 
HTTP_ACCEPT  image/gif, image/x-xbitmap, image/jpeg,
image/pjpeg, application/vnd.ms-powerpoint,
application/vnd.ms-excel, application/msword,
application/x-shockwave-flash, */*  
CONTENT_TYPE  application/x-www-form-urlencoded  
HTTP_REFERER 
http://www.clydec.net/mailman/confirm/jujitsu/fe77e7f88cdb236aef702757e6be57e4b9f81338
 
SERVER_SOFTWARE  Apache/1.3.22 (Unix) (Red-Hat/Linux)
PHP/4.3.3 mod_perl/1.21  
PYTHONPATH  /home/usr/local/mailman  
SCRIPT_FILENAME  /home/usr/local/mailman/cgi-bin/confirm  
SERVER_ADMIN  webmaster@clydec.net  
SCRIPT_NAME  /mailman/confirm  
SERVER_SIGNATURE  Apache/1.3.22 Server at
www.clydec.net Port 80 
REQUEST_METHOD  POST  
HTTP_HOST  www.clydec.net  
PATH_INFO  /jujitsu  
SERVER_PROTOCOL  HTTP/1.1  
QUERY_STRING   
HTTP_CACHE_CONTROL  no-cache  
REQUEST_URI  /mailman/confirm/jujitsu  
CONTENT_LENGTH  69  
HTTP_USER_AGENT  Mozilla/4.0 (compatible; MSIE 6.0;
Windows NT 5.0)  
HTTP_CONNECTION  Keep-Alive  
SERVER_NAME  www.clydec.net  
REMOTE_ADDR  209.150.103.223  
REMOTE_PORT  2500  
HTTP_ACCEPT_LANGUAGE  en-us  
PATH_TRANSLATED  /home/httpd/html/jujitsu  
SERVER_PORT  80  
GATEWAY_INTERFACE  CGI/1.1  
REMOTE_HOST  clydec2.qis.net  
HTTP_ACCEPT_ENCODING  gzip, deflate  
SERVER_ADDR  209.150.103.222  
DOCUMENT_ROOT  /home/httpd/html  



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

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

From noreply at sourceforge.net  Mon Nov  3 17:04:01 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov  3 17:04:03 2003
Subject: [ mailman-Bugs-835332 ] Stops bloat in pipermail article databases
Message-ID: <E1AGmnp-00076k-00@sc8-sf-web3.sourceforge.net>

Bugs item #835332, was opened at 2003-11-03 22:04
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=835332&group_id=103

Category: Pipermail
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Stops bloat in pipermail article databases

Initial Comment:
The standard pipermail archiving code saves the body text, 
in HTML format, of every article in the -article database of 
each archived list. This bloats the size of 
these databases. Because they are pickled data structures, 
which are loaded into memory in their entirety when 
archiving operations for a list are being handled, this bloat 
can substantially prejudice archiver performance and in the 
limit, for lists carrying heavy traffic and/or receiving large 
text postings, bring archiving to a grinding halt.

This patch changes HyperArch.py and pipermail.py so that 
the data stored in the pipermail <code>$archives/private/
<listname>/database/<period>-article</code> does not 
include the body text, in HTML format, of each article. This 
reduces the size of the -article database for each list. The 
benefits of this are most pronounced with high traffic lists 
and those to which large text postings are made. 

The patch also adds a script $prefix/bin/rb-arch which will 
remove any body text, in HTML format, from existing -
article databases; this junk HTML is no longer added when 
new articles are added to the databases but existing junk 
HTML is not deleted unless this script is run. The alternative 
is to run $prefix/bin/arch for a list.

Apply the patch from within the Mailman build directory 
using the command: 

    patch -p1 < path-to-patch-file

You use this patch at your own risk and I would appreciate 
feedback about whether it works for you if you use it or/and 
any problems you encounter with the patch.

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

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

From noreply at sourceforge.net  Tue Nov  4 12:16:56 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov  4 12:17:06 2003
Subject: [ mailman-Bugs-835870 ] list create page needs full url
Message-ID: <E1AH4nY-000514-00@sc8-sf-web2.sourceforge.net>

Bugs item #835870, was opened at 2003-11-04 12:16
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=835870&group_id=103

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Mike Alberghini (uglor)
Assigned to: Nobody/Anonymous (nobody)
Summary: list create page needs full url

Initial Comment:
If you go to the list creation page without using the
full domain name of the server, then lists created via
the page will not use the full domain of the server for
internal URL's

For example, if someone in the domain example.com wants
to create a list on mailbox.example.com, they can just
type http://mailbox/mailman/create to be sent to the
list creation page.  If they create a list from that
URL, then all mailings sent out by that list (welcome
messages, list info, password reminders) will only use
the machine name, not the full machine and domain name.
 This results in broken links for anyone outside the
domain, like http://mailbox/mailman/listinfo/testlist.

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

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

From noreply at sourceforge.net  Wed Nov  5 14:17:18 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Nov  5 14:18:22 2003
Subject: [ mailman-Bugs-835870 ] list create page needs full url
Message-ID: <E1AHT9a-0006Bw-00@sc8-sf-web4.sourceforge.net>

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

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Mike Alberghini (uglor)
Assigned to: Nobody/Anonymous (nobody)
Summary: list create page needs full url

Initial Comment:
If you go to the list creation page without using the
full domain name of the server, then lists created via
the page will not use the full domain of the server for
internal URL's

For example, if someone in the domain example.com wants
to create a list on mailbox.example.com, they can just
type http://mailbox/mailman/create to be sent to the
list creation page.  If they create a list from that
URL, then all mailings sent out by that list (welcome
messages, list info, password reminders) will only use
the machine name, not the full machine and domain name.
 This results in broken links for anyone outside the
domain, like http://mailbox/mailman/listinfo/testlist.

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

Comment By: Richard Barrett (ppsys)
Date: 2003-11-05 19:17

Message:
Logged In: YES 
user_id=75166

Mailman determines the host on which to create a list from
the Host: header inserted by the origin browser into the
HTTP request and, if that is not present, it uses the
ServerName derived from the Apache server's httpd.conf.

The problem arises because the resolver on the machine
running the browser is adding what it determines is its
local domain to the hostname entered in the URL to form an
FQDN, which it then resolves the IP number of. However, that
FQDN is not finding its way back into the Host: header of
the request.

This has a number of consequence. Typically, it will break
Apache name-based virtual hosting because just a host's name
will not match the usual full FQDN ServerName in a
VirtualHost definition on the Apache server and typically
the default host will be the target of the request which may
well not be the intended host. 

It will also likely break the MM listinfo display of
listnames by virtual host if Apache name based virtual hosts
are being used.

Mailman's computation of the host on which it should create
the list breaks for exactly the same reason. I would argue
that this is right and proper.

Any other approach leaves the server side trying to second
guess what the resolver on the machine running the browser
did to form an FQDN which led to the connection to the
server's IP number. I suggest there is not a simple
algorithm that will reliably lead to this problem being
solved in the general case, which is why the Apache code
does not do it and why Mailman should not try to do it.

The answer is for people authorised to create lists to be
sufficiently aware as to not use just the hostname but the
FQDN in the URLs they use to create lists. One way to
enforce this is to use Apache name based virtual hosts so
that access to Mailman's CGI scripts is only available if
the requesting browser delivers a FQDN in the Host: request
header.


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

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

From noreply at sourceforge.net  Mon Nov 10 13:04:05 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov 10 13:04:08 2003
Subject: [ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1
Message-ID: <E1AJGOT-0008AA-00@sc8-sf-web2.sourceforge.net>

Patches item #839386, was opened at 2003-11-10 18:04
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=839386&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Kev Green (kyrian)
Assigned to: Nobody/Anonymous (nobody)
Summary: MySQL MemberAdaptor for Mailman 2.1

Initial Comment:
A MemberAdaptor "plugin" which should allow Mailman list members 
to be loaded from a MySQL database, rather than just a Mailman 
"pickle" file.

Provided as-is, and without warranty, this "plugin" may destroy your 
server, soul, scalp, house, and life. Please use it with caution.

Kev Green, oRe Net.
http://www.orenet.co.uk/

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

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

From noreply at sourceforge.net  Mon Nov 10 13:06:36 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov 10 13:06:41 2003
Subject: [ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1
Message-ID: <E1AJGQu-0008K4-00@sc8-sf-web2.sourceforge.net>

Patches item #839386, was opened at 2003-11-10 18:04
Message generated for change (Settings changed) made by kyrian
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_id=103

>Category: configure/install
>Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Kev Green (kyrian)
Assigned to: Nobody/Anonymous (nobody)
Summary: MySQL MemberAdaptor for Mailman 2.1

Initial Comment:
A MemberAdaptor "plugin" which should allow Mailman list members 
to be loaded from a MySQL database, rather than just a Mailman 
"pickle" file.

Provided as-is, and without warranty, this "plugin" may destroy your 
server, soul, scalp, house, and life. Please use it with caution.

Kev Green, oRe Net.
http://www.orenet.co.uk/

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

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

From noreply at sourceforge.net  Mon Nov 10 13:23:51 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov 10 13:23:54 2003
Subject: [ mailman-Bugs-839419 ] feature req: mails should contain URIs of
	archived msg
Message-ID: <E1AJGhb-0003dS-00@sc8-sf-web1.sourceforge.net>

Bugs item #839419, was opened at 2003-11-10 10:23
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=839419&group_id=103

Category: mail delivery
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Justin Mason (jmason)
Assigned to: Nobody/Anonymous (nobody)
Summary: feature req: mails should contain URIs of archived msg

Initial Comment:
Hi all,

It'd be a great feature for web integration, if
outgoing messages were
to contain that message's URI in the web archives.

This would provide a nice way for each message on a
public, archived list, to have a "permanent URI" for
that message; if I come across a message I'd like to
forward, I have to do one of these:

  1. forward the entire message text, traditional style, or
  2. go to the archive URI, find current month, and
visually look for the message in question in the "by
thread" page for that month



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

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

From noreply at sourceforge.net  Mon Nov 10 13:31:07 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov 10 13:31:36 2003
Subject: [ mailman-Patches-645297 ] Add PGP support
Message-ID: <E1AJGod-0002TA-00@sc8-sf-web4.sourceforge.net>

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

Category: None
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Ben Laurie (benl)
Assigned to: Thomas Wouters (twouters)
Summary: Add PGP support

Initial Comment:
Support PGP encrypted lists using GnuPG.

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

Comment By: Justin Mason (jmason)
Date: 2003-11-10 10:31

Message:
Logged In: YES 
user_id=935

another +1 for this patch, I've been looking for this
functionality too...


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

Comment By: Thomas Wouters (twouters)
Date: 2003-03-17 14:17

Message:
Logged In: YES 
user_id=34209

I'll look at incorporating this when I look at the
SecureList patch by NAH6 (SF patch #646989, currently.)


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

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

Message:
Logged In: YES 
user_id=106549

My vote goes to a PGP whitelist and blacklist feature.
Messages signed with a key present in the whitelist could go
skip moderation, messages in the blacklist would be either
ignored or rejected, and all other messages could go through
moderation. That way, PGP signatures are not required, but
those using them would see their messages delivered quickly.
Mailman would have two keyrings, and would manage them by
specifying --keyring to gpg. PGP keys would be retreived
from a PGP key server. When moderating a message that was
signed with a key missing from the whitelist, there would be
an option named "Add key to whitelist", and an other one for
the blacklist. Keys could be added to the white/blacklist
through the web interface by specifying at least a key ID,
and mailman would ask gpg to fetch the key from mailman's
default key server.

Initially proposed in French on:
http://www.linux-quebec.org/archives/general/msg03787.html

Nicolas Marchildon

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

Comment By: David Shaw (dmshaw)
Date: 2003-01-04 11:59

Message:
Logged In: YES 
user_id=606006

Another vote of support.  I actually submitted an
enhancement request earlier today for exactly this.

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

Comment By: captain larry (captainlarry)
Date: 2002-12-23 11:37

Message:
Logged In: YES 
user_id=147905

Adding a vote of support for this patch.  Please add it as
soon as it's appropriate!  I've been waiting a long time for
this functionality and I'd hate to see the patch bitrot. :-)

Adam.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-11 19:56

Message:
Logged In: YES 
user_id=12800

I have to defer this patch until after MM2.1 since we're
about ready for the first release candidate.

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

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

From noreply at sourceforge.net  Tue Nov 11 06:14:02 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 11 06:14:06 2003
Subject: [ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1
Message-ID: <E1AJWTC-0003b7-00@sc8-sf-web2.sourceforge.net>

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

Category: configure/install
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Kev Green (kyrian)
Assigned to: Nobody/Anonymous (nobody)
Summary: MySQL MemberAdaptor for Mailman 2.1

Initial Comment:
A MemberAdaptor "plugin" which should allow Mailman list members 
to be loaded from a MySQL database, rather than just a Mailman 
"pickle" file.

Provided as-is, and without warranty, this "plugin" may destroy your 
server, soul, scalp, house, and life. Please use it with caution.

Kev Green, oRe Net.
http://www.orenet.co.uk/

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

>Comment By: Kev Green (kyrian)
Date: 2003-11-11 11:14

Message:
Logged In: YES 
user_id=99923

Bit of an oops in version 1.49, 1.50 now uploaded, which should fix it.

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

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

From noreply at sourceforge.net  Tue Nov 11 20:54:13 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 11 20:54:16 2003
Subject: [ mailman-Patches-840426 ] SpamAssassin handler for pre-tagged mail
Message-ID: <E1AJkCz-0000cT-00@sc8-sf-web2.sourceforge.net>

Patches item #840426, was opened at 2003-11-11 21:54
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=840426&group_id=103

Category: list administration
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Jeff Warnica (jeffwarnica)
Assigned to: Nobody/Anonymous (nobody)
Summary: SpamAssassin handler for pre-tagged mail

Initial Comment:
In my ISP enviroment (and many others, based on my
readings of various MTA lists) ALL incomming mail is
scanned by MailScanner, which includes Spamassassin
analysis, with the results put in the header.

Simmilar to the other SA handlers in here, this one
deals with pre-tagged mail.

To install, drop this into the $prefix/Mailman/Handlers
directory, add 'SpamAssassin' to the GLOBAL_PIPELINE in
$prefix/Mailman/Defaults.py and (optionaly) add
configuration directives to $prefix/Mailman/mm_cfg.py
(SPAMASSASSIN_DISCARD_SCORE, SPAMASSASSIN_HOLD_SCORE,
SPAMASSASSIN_MEMBER_BONUS)

Mail that is above the ..._DISCARD_SCORE is silently
thrown away; above the ..._HOLD_SCORE is held for
moderation. The ...MEMBER_BONUS subtracts that score
from the tagged score if the sender is on the list.

One could easily customize the error/warning messages
in the top of this file.

It MAY be necessary to tweek the regular expression
that actualy sucks out the score from the headers...
Uncomment my debug syslog lines to help.

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

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

From noreply at sourceforge.net  Tue Nov 11 21:08:28 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 11 21:08:31 2003
Subject: [ mailman-Patches-840432 ] Zmailer integration
Message-ID: <E1AJkQm-0003af-00@sc8-sf-web4.sourceforge.net>

Patches item #840432, was opened at 2003-11-11 22:08
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=840432&group_id=103

Category: configure/install
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jeff Warnica (jeffwarnica)
Assigned to: Nobody/Anonymous (nobody)
Summary: Zmailer integration

Initial Comment:
A patch for zmailers alias.cf file for automatic
integration of mailman lists..  No more needing to edit
the alisaes file!

Also, you need to define the MAILMAN_ROOT variable in
zmailer.conf.. Something like:

MAILMAN_ROOT=/usr/local/mailman


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

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

From noreply at sourceforge.net  Wed Nov 12 10:26:12 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Nov 12 10:26:23 2003
Subject: [ mailman-Bugs-834486 ] Uncatched ValueError in Scrubber
Message-ID: <E1AJwsm-0003fQ-00@sc8-sf-web2.sourceforge.net>

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

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Uncatched ValueError in Scrubber

Initial Comment:

Mailman 2.1.2, python 2.2

Nov 01 20:40:04 2003 (10542) Uncaught runner exception:
Empty module name
Nov 01 20:40:04 2003 (10542) Traceback (most recent
call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py",
line 105, in _oneloop
    self._onefile(msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/Runner.py",
line 155, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File
"/usr/local/mailman/Mailman/Queue/IncomingRunner.py",
line 130, in _dispose
    more = self._dopipeline(mlist, msg, msgdata, pipeline)
  File
"/usr/local/mailman/Mailman/Queue/IncomingRunner.py",
line 153, in _dopipeline
    sys.modules[modname].process(mlist, msg, msgdata)
  File
"/usr/local/mailman/Mailman/Handlers/ToDigest.py", line
89, in process
    send_digests(mlist, 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
308, in process
    t = t.encode(charset, 'replace')
  File "/usr/lib/python2.2/encodings/__init__.py", line
51, in search_function
    mod = __import__(modname,globals(),locals(),'*')
ValueError: Empty module name

This is still uncorrected in v2_1-branch

Attached a proposed fix.



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

Comment By: jared mauch (jaredmauch)
Date: 2003-11-12 10:26

Message:
Logged In: YES 
user_id=131445

I'm also seeing this error.  This patch solved my problem. 
Thanks!


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

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

From noreply at sourceforge.net  Thu Nov 13 09:10:34 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Nov 13 09:10:41 2003
Subject: [ mailman-Bugs-841445 ] config_list -i + new_member_options
Message-ID: <E1AKIB8-0004gO-00@sc8-sf-web2.sourceforge.net>

Bugs item #841445, was opened at 2003-11-13 14:10
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=841445&group_id=103

Category: command line scripts
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: r blank (roblank)
Assigned to: Nobody/Anonymous (nobody)
Summary: config_list -i + new_member_options

Initial Comment:
Hi all,
config_list -o dumps the right new_member_options,
but config_list -i does not import it right.
I get new_member_options = 0 after import.

Using mm 2.1.3 and
Python 2.1.3 (#1, Apr  9 2002, 22:27:11)
[GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-98)] on linux2

any ideas?

thnx

robert


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

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

From noreply at sourceforge.net  Fri Nov 14 04:36:36 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Nov 14 04:37:05 2003
Subject: [ mailman-Patches-670167 ] fix i18n attachment description in
	archive 
Message-ID: <E1AKaNY-00031b-00@sc8-sf-web1.sourceforge.net>

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

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: Accepted
Priority: 8
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: fix i18n attachment description in archive 

Initial Comment:
Bug-ID 669081 (Major attachment handling bug!) is
caused inaccurate handling of charset in Scrubber.py.
This is caused   by misuse of email functions (or by
bug in email package).
In Scrubber.py, attempt is made to get message charset
by part.get_charset() but it returns only None, as far
as I experimented. In this patch, message charset is
extracted from regular expression pattern in
content-type header.
This also set the charset of internally crafted message
part.
 

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

Comment By: Guillaume Rousse (guillomovitch)
Date: 2003-11-14 10:36

Message:
Logged In: YES 
user_id=144568

What is the status of this patch for mailman 2.1.3 ? 

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

Comment By: Hugh Caley (hcaley)
Date: 2003-05-30 19:23

Message:
Logged In: YES 
user_id=17460

I patched version 2.1.2 of Mail man with patch
Scrubber.py.patch.030224.txt, using "patch -p0
<Scrubber.py.patch.030224.txt".  The patch applied cleanly,
other than removing a couple of CR's at the end of the file.
 However, it doesn't seem to make a difference; messages
sent from Outlook XP with an attachment still lose their
message text.  Did I do this correctly?

Hugh_Caley@affymetrix.com

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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2003-04-22 15:00

Message:
Logged In: YES 
user_id=67709

Recently, I had a chance to get personal correspondence to
refer this patch. To quote his comment, "(it) works like a
charm!"
So, I am incrementing the priority. :^)


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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2003-02-24 05:34

Message:
Logged In: YES 
user_id=67709

Uploading revised patch to fix more error.
Sorry for the people downloaded earlier.


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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2003-02-24 02:39

Message:
Logged In: YES 
user_id=67709

update my patch to fix error reported by sumeet

  File "/list/Mailman/Handlers/Scrubber.py", line 320, in
process
    if not t.endswith('\n'):
AttributeError: 'NoneType' object has no attribute 'endswith'


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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2003-02-22 08:05

Message:
Logged In: YES 
user_id=67709

This patch for Scrubber.py now include Bug-ID #691039.
save_attachment() now returns (url, size), because in
previous code, get_paylaod() is called before calling
save_attachment() only to get the size. save_attachment()
calls get_payload() inside.
We might be able to discard the attachment if
get_payload(decode=1) fail. (TBD: return discard message and
size 0 ?)


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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2003-02-20 02:31

Message:
Logged In: YES 
user_id=67709

Increment priority because this is now a bug fix.


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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2003-02-04 07:08

Message:
Logged In: YES 
user_id=67709

I made a new patch to fix embedded multipart messages are
stripped bug. this patch is for CVS.
see
http://mail.python.org/pipermail/mailman-users/2003-February/026071.html


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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-01-20 06:13

Message:
Logged In: YES 
user_id=12800

Reopening so this issue doesn't get lost.

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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2003-01-20 05:03

Message:
Logged In: YES 
user_id=67709

We, Japanese, need additional process of stringify and
regenerate  message instance..
Internal message is in 'euc-jp' but return value of
get_content_charset() becomes 'iso-2022-jp' even though the
get_payload() returns euc-jp text.
The message and part body is converted to iso-2022-jp when
it is output to SMTP (or whatever accepts in string format).


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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-01-20 03:18

Message:
Logged In: YES 
user_id=12800

Accepted, with changes.

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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2003-01-19 01:52

Message:
Logged In: YES 
user_id=67709

Update of patch.
Please backout the first one if you have already applied.


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

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

From noreply at sourceforge.net  Sun Nov 16 08:28:45 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Nov 16 08:28:48 2003
Subject: [ mailman-Bugs-843141 ] No date in archive overview
Message-ID: <E1ALMxJ-0002QZ-00@sc8-sf-web2.sourceforge.net>

Bugs item #843141, was opened at 2003-11-16 14:28
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=843141&group_id=103

Category: Pipermail
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Bernhard Kuemel (darsie)
Assigned to: Nobody/Anonymous (nobody)
Summary: No date in archive overview

Initial Comment:
There is no date displayed for each message in the
archive overview:

http://rainbow.bksys.at/pipermail/test/2003-July/thread.html

It may be argued if that's a bug or a feature - I
prefer to see the dates.

Bernhard


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

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

From noreply at sourceforge.net  Sun Nov 16 10:59:03 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Nov 16 10:59:09 2003
Subject: [ mailman-Patches-840426 ] SpamAssassin handler for pre-tagged mail
Message-ID: <E1ALPIl-0004rZ-00@sc8-sf-web4.sourceforge.net>

Patches item #840426, was opened at 2003-11-12 01:54
Message generated for change (Comment added) made by pieterb
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=840426&group_id=103

Category: list administration
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Jeff Warnica (jeffwarnica)
Assigned to: Nobody/Anonymous (nobody)
Summary: SpamAssassin handler for pre-tagged mail

Initial Comment:
In my ISP enviroment (and many others, based on my
readings of various MTA lists) ALL incomming mail is
scanned by MailScanner, which includes Spamassassin
analysis, with the results put in the header.

Simmilar to the other SA handlers in here, this one
deals with pre-tagged mail.

To install, drop this into the $prefix/Mailman/Handlers
directory, add 'SpamAssassin' to the GLOBAL_PIPELINE in
$prefix/Mailman/Defaults.py and (optionaly) add
configuration directives to $prefix/Mailman/mm_cfg.py
(SPAMASSASSIN_DISCARD_SCORE, SPAMASSASSIN_HOLD_SCORE,
SPAMASSASSIN_MEMBER_BONUS)

Mail that is above the ..._DISCARD_SCORE is silently
thrown away; above the ..._HOLD_SCORE is held for
moderation. The ...MEMBER_BONUS subtracts that score
from the tagged score if the sender is on the list.

One could easily customize the error/warning messages
in the top of this file.

It MAY be necessary to tweek the regular expression
that actualy sucks out the score from the headers...
Uncomment my debug syslog lines to help.

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

Comment By: PieterB (pieterb)
Date: 2003-11-16 15:59

Message:
Logged In: YES 
user_id=458461

I noticed there are currently 3 patches concerning 
SpamAssassin:
534577  Add SpamAssassin filter to mail pipeline jhenstridge 
2002-03-25 Open
640518  SpamAssassin handler jparise 2002-11-18 Open
840426  SpamAssassin handler for pre-tagged mail jeffwarnica 
2003-11-11 Open

I constructed a similar handler for SpamAssassin which can 
be used
both for systems that pre-tag the messages and for systems 
that
want to use python's to tag the message using spamd/spamc.

It's behavioure can be controlled by the mm_cfg parameter
SPAMASSASSIN_USE_HEADERS. It parsers both the score and 
the symbols
(tests) from the SpamAssassin-header.

It's based on 
http://www.daa.com.au/~james/articles/mailman-
spamassassin/
and should be able to handle both kinds of 
mailman/spamassassin
integration.

It can be found at 
http://gewis.nl/~pieterb/python/SpamAssassin.py.txt

It would be great if a SpamAssassin.py will be integrated in 
Mailman
2.1.4! Can anybody commit this SpamAssassin.py and James 
his spamd.py
to the Mailman CVS?

Feedback is welcome,
Regards,

Pieter


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

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

From noreply at sourceforge.net  Thu Nov 20 04:11:43 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Nov 20 04:11:56 2003
Subject: [ mailman-Feature Requests-534234 ] Automatic RSS feed generation
Message-ID: <E1AMkql-0005Db-00@sc8-sf-web4.sourceforge.net>

Feature Requests item #534234, was opened at 2002-03-24 12:12
Message generated for change (Comment added) made by korakot
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: Korakot Chaovavanich (korakot)
Date: 2003-11-20 16:11

Message:
Logged In: YES 
user_id=25429

Another 'me too' !

After using news aggregrator for a while, it feels so
unconvenient to read mailing list.
Mailman is the most popular mailing list tool. It would
be perfect to change it once and for all here.

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

Comment By: Simon Woodside (sbwoodsi)
Date: 2003-10-22 07: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-24 02: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-08 00: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 12: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  Fri Nov 21 07:49:40 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Nov 21 07:49:44 2003
Subject: [ mailman-Bugs-846554 ] virus found in 2.1.3
Message-ID: <E1ANAjE-0008Of-00@sc8-sf-web3.sourceforge.net>

Bugs item #846554, was opened at 2003-11-21 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=846554&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: SvR Marty (svrmarty)
Assigned to: Nobody/Anonymous (nobody)
Summary: virus found in 2.1.3

Initial Comment:
Have detected a virus [HTML_IFRMEXP.GEN] via [HTTP] 
in file [mailman-2.1.3.tgz] in http traffic on 11/21/2003 
11:03:39 with an action deleted. The original download 
path was: 
http://heanet.dl.sourceforge.net/sourceforge/mailman/m
ailman-2.1.3.tgz


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

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

From noreply at sourceforge.net  Fri Nov 21 09:34:36 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Nov 21 09:34:48 2003
Subject: [ mailman-Bugs-846554 ] virus found in 2.1.3
Message-ID: <E1ANCMm-0005fN-00@sc8-sf-web1.sourceforge.net>

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

Category: None
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: SvR Marty (svrmarty)
Assigned to: Nobody/Anonymous (nobody)
Summary: virus found in 2.1.3

Initial Comment:
Have detected a virus [HTML_IFRMEXP.GEN] via [HTTP] 
in file [mailman-2.1.3.tgz] in http traffic on 11/21/2003 
11:03:39 with an action deleted. The original download 
path was: 
http://heanet.dl.sourceforge.net/sourceforge/mailman/m
ailman-2.1.3.tgz


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-21 09:34

Message:
Logged In: YES 
user_id=12800

Your virus detector is too naive.  There is a neutered
sample of a virus in the test suite, but there is no payload
in that message.  It is harmless.


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

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

From noreply at sourceforge.net  Fri Nov 21 11:18:55 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Nov 21 11:19:01 2003
Subject: [ mailman-Bugs-846681 ] confirm hash after delivery turned off does
	not work
Message-ID: <E1ANDzj-0003Ba-00@sc8-sf-web1.sourceforge.net>

Bugs item #846681, was opened at 2003-11-21 10: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=846681&group_id=103

Category: (un)subscribing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Yeah Right (jp31415926)
Assigned to: Nobody/Anonymous (nobody)
Summary: confirm hash after delivery turned off does not work

Initial Comment:
If a user's delivery is turned off because of excessive
bounces, the confirm hash emailed to the user does not
work.  Instead it report that the hash is bad or over 3
days old.


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

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

From noreply at sourceforge.net  Fri Nov 21 17:44:34 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Nov 21 17:44:44 2003
Subject: [ mailman-Bugs-846681 ] confirm hash after delivery turned off does
	not work
Message-ID: <E1ANK0w-0005FE-00@sc8-sf-web1.sourceforge.net>

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

Category: (un)subscribing
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Yeah Right (jp31415926)
Assigned to: Nobody/Anonymous (nobody)
Summary: confirm hash after delivery turned off does not work

Initial Comment:
If a user's delivery is turned off because of excessive
bounces, the confirm hash emailed to the user does not
work.  Instead it report that the hash is bad or over 3
days old.


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-21 17:44

Message:
Logged In: YES 
user_id=12800

Fixed for Mailman 2.1.4.

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

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

From noreply at sourceforge.net  Mon Nov 24 16:40:12 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov 24 16:41:46 2003
Subject: [ mailman-Bugs-766667 ] failure at mailman/subscribe/{list-name}
Message-ID: <E1AOORI-0006r4-00@sc8-sf-web3.sourceforge.net>

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

Category: (un)subscribing
Group: 2.1 (stable)
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Ivan Kurmanov (iku)
Assigned to: Nobody/Anonymous (nobody)
Summary: failure at mailman/subscribe/{list-name}

Initial Comment:
Traceback (most recent call last):
  File "/var/lib/mailman/scripts/driver", line 87, in
run_main
    main()
  File "/usr/lib/mailman/Mailman/Cgi/subscribe.py",
line 96, in main
    process_form(mlist, doc, cgidata, language)
  File "/usr/lib/mailman/Mailman/Cgi/subscribe.py",
line 176, in process_form
    mlist.AddMember(userdesc, remote)
  File "/var/lib/mailman/Mailman/MailList.py", line
831, in AddMember
    text=text, lang=lang)
  File "/var/lib/mailman/Mailman/Message.py", line 206,
in __init__
    errors='replace')
TypeError: __init__() got an unexpected keyword
argument 'errors'

This is when I entered my email address, name,
password, and clicked [subscribe].  This might be a
misconfiguration, but it would be nice to know what
exactly is wrong.

Mailman version 2.1.2


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 16:40

Message:
Logged In: YES 
user_id=12800

Looks like this is not a bug any more.


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

Comment By: Ivan Kurmanov (iku)
Date: 2003-07-15 11:03

Message:
Logged In: YES 
user_id=320488

Looks like this problem is *unstable* python problem.  In my
case fixed by installing a stable python version.



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

Comment By: Bernhard Kuemel (darsie)
Date: 2003-07-13 18:43

Message:
Logged In: YES 
user_id=559942

The debian/unstable package 2.1.2-6 fixes both bugs.

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

Comment By: Bernhard Kuemel (darsie)
Date: 2003-07-13 18:27

Message:
Logged In: YES 
user_id=559942

appearently the same bug exists for unsubscribing or
requesting a password reminder. e.g. at
http://bksys.at/mailman/listinfo/test
I'll see if there is already an update for debian/testing
that fixes the bug.

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

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

From noreply at sourceforge.net  Mon Nov 24 16:42:41 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov 24 16:42:46 2003
Subject: [ mailman-Feature Requests-843141 ] No date in archive overview
Message-ID: <E1AOOTh-0006zh-00@sc8-sf-web3.sourceforge.net>

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

>Category: None
>Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Bernhard Kuemel (darsie)
Assigned to: Nobody/Anonymous (nobody)
Summary: No date in archive overview

Initial Comment:
There is no date displayed for each message in the
archive overview:

http://rainbow.bksys.at/pipermail/test/2003-July/thread.html

It may be argued if that's a bug or a feature - I
prefer to see the dates.

Bernhard


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 16:42

Message:
Logged In: YES 
user_id=12800

This is a feature request.

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

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

From noreply at sourceforge.net  Mon Nov 24 17:54:47 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov 24 17:54:51 2003
Subject: [ mailman-Patches-848631 ] more verbose "discarded" message in
	vette log
Message-ID: <E1AOPbT-00021R-00@sc8-sf-web2.sourceforge.net>

Patches item #848631, was opened at 2003-11-24 23:54
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=848631&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: more verbose "discarded" message in vette log

Initial Comment:
Trying to understand why a message has been automatically 
discarded can be very hard: 
 
Nov 24 23:27:48 2003 (1250) Message discarded, msgid: 
<2003112423xxxx@ferrara.linux.it> 
 
There's no specified reason. 
 
The attached patch will expose a reason, e.g. 
 
Nov 24 23:27:48 2003 (1250) Message discarded, msgid: 
<2003112423xxxx@ferrara.linux.it>, reason: The message's 
content type was explicitly disallowed 
 

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

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

From noreply at sourceforge.net  Mon Nov 24 18:08:19 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov 24 18:08:28 2003
Subject: [ mailman-Bugs-841445 ] config_list -i + new_member_options
Message-ID: <E1AOPoZ-0003GL-00@sc8-sf-web3.sourceforge.net>

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

Category: command line scripts
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: r blank (roblank)
Assigned to: Nobody/Anonymous (nobody)
Summary: config_list -i + new_member_options

Initial Comment:
Hi all,
config_list -o dumps the right new_member_options,
but config_list -i does not import it right.
I get new_member_options = 0 after import.

Using mm 2.1.3 and
Python 2.1.3 (#1, Apr  9 2002, 22:27:11)
[GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-98)] on linux2

any ideas?

thnx

robert


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 18:08

Message:
Logged In: YES 
user_id=12800

Fixed for Mailman 2.1.4.


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

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

From noreply at sourceforge.net  Mon Nov 24 18:42:29 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov 24 18:42:38 2003
Subject: [ mailman-Bugs-835870 ] list create page needs full url
Message-ID: <E1AOQLd-0004Dc-00@sc8-sf-web2.sourceforge.net>

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

Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Mike Alberghini (uglor)
Assigned to: Nobody/Anonymous (nobody)
Summary: list create page needs full url

Initial Comment:
If you go to the list creation page without using the
full domain name of the server, then lists created via
the page will not use the full domain of the server for
internal URL's

For example, if someone in the domain example.com wants
to create a list on mailbox.example.com, they can just
type http://mailbox/mailman/create to be sent to the
list creation page.  If they create a list from that
URL, then all mailings sent out by that list (welcome
messages, list info, password reminders) will only use
the machine name, not the full machine and domain name.
 This results in broken links for anyone outside the
domain, like http://mailbox/mailman/listinfo/testlist.

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 18:42

Message:
Logged In: YES 
user_id=12800

Here's a thought: if VIRTUAL_HOST_OVERVIEW is true, we can
refuse to create a list in a virtual domain we don't know
anything about.  If it's false, then I agree w/ ppsys, you
need to know what you're doing.

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

Comment By: Richard Barrett (ppsys)
Date: 2003-11-05 14:17

Message:
Logged In: YES 
user_id=75166

Mailman determines the host on which to create a list from
the Host: header inserted by the origin browser into the
HTTP request and, if that is not present, it uses the
ServerName derived from the Apache server's httpd.conf.

The problem arises because the resolver on the machine
running the browser is adding what it determines is its
local domain to the hostname entered in the URL to form an
FQDN, which it then resolves the IP number of. However, that
FQDN is not finding its way back into the Host: header of
the request.

This has a number of consequence. Typically, it will break
Apache name-based virtual hosting because just a host's name
will not match the usual full FQDN ServerName in a
VirtualHost definition on the Apache server and typically
the default host will be the target of the request which may
well not be the intended host. 

It will also likely break the MM listinfo display of
listnames by virtual host if Apache name based virtual hosts
are being used.

Mailman's computation of the host on which it should create
the list breaks for exactly the same reason. I would argue
that this is right and proper.

Any other approach leaves the server side trying to second
guess what the resolver on the machine running the browser
did to form an FQDN which led to the connection to the
server's IP number. I suggest there is not a simple
algorithm that will reliably lead to this problem being
solved in the general case, which is why the Apache code
does not do it and why Mailman should not try to do it.

The answer is for people authorised to create lists to be
sufficiently aware as to not use just the hostname but the
FQDN in the URLs they use to create lists. One way to
enforce this is to use Apache name based virtual hosts so
that access to Mailman's CGI scripts is only available if
the requesting browser delivers a FQDN in the Host: request
header.


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

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

From noreply at sourceforge.net  Mon Nov 24 18:52:05 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Nov 24 18:52:10 2003
Subject: [ mailman-Bugs-835870 ] list create page needs full url
Message-ID: <E1AOQUv-0000dS-00@sc8-sf-web1.sourceforge.net>

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

Category: Web/CGI
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Mike Alberghini (uglor)
Assigned to: Nobody/Anonymous (nobody)
Summary: list create page needs full url

Initial Comment:
If you go to the list creation page without using the
full domain name of the server, then lists created via
the page will not use the full domain of the server for
internal URL's

For example, if someone in the domain example.com wants
to create a list on mailbox.example.com, they can just
type http://mailbox/mailman/create to be sent to the
list creation page.  If they create a list from that
URL, then all mailings sent out by that list (welcome
messages, list info, password reminders) will only use
the machine name, not the full machine and domain name.
 This results in broken links for anyone outside the
domain, like http://mailbox/mailman/listinfo/testlist.

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 18:52

Message:
Logged In: YES 
user_id=12800

This is what I've commited for Mailman 2.1.4.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 18:42

Message:
Logged In: YES 
user_id=12800

Here's a thought: if VIRTUAL_HOST_OVERVIEW is true, we can
refuse to create a list in a virtual domain we don't know
anything about.  If it's false, then I agree w/ ppsys, you
need to know what you're doing.

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

Comment By: Richard Barrett (ppsys)
Date: 2003-11-05 14:17

Message:
Logged In: YES 
user_id=75166

Mailman determines the host on which to create a list from
the Host: header inserted by the origin browser into the
HTTP request and, if that is not present, it uses the
ServerName derived from the Apache server's httpd.conf.

The problem arises because the resolver on the machine
running the browser is adding what it determines is its
local domain to the hostname entered in the URL to form an
FQDN, which it then resolves the IP number of. However, that
FQDN is not finding its way back into the Host: header of
the request.

This has a number of consequence. Typically, it will break
Apache name-based virtual hosting because just a host's name
will not match the usual full FQDN ServerName in a
VirtualHost definition on the Apache server and typically
the default host will be the target of the request which may
well not be the intended host. 

It will also likely break the MM listinfo display of
listnames by virtual host if Apache name based virtual hosts
are being used.

Mailman's computation of the host on which it should create
the list breaks for exactly the same reason. I would argue
that this is right and proper.

Any other approach leaves the server side trying to second
guess what the resolver on the machine running the browser
did to form an FQDN which led to the connection to the
server's IP number. I suggest there is not a simple
algorithm that will reliably lead to this problem being
solved in the general case, which is why the Apache code
does not do it and why Mailman should not try to do it.

The answer is for people authorised to create lists to be
sufficiently aware as to not use just the hostname but the
FQDN in the URLs they use to create lists. One way to
enforce this is to use Apache name based virtual hosts so
that access to Mailman's CGI scripts is only available if
the requesting browser delivers a FQDN in the Host: request
header.


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

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

From noreply at sourceforge.net  Mon Nov 24 21:10:02 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 02:54:15 2003
Subject: [ mailman-Bugs-835036 ] Bug encountered when doing global change of
	address
Message-ID: <E1AOSeQ-0001Gd-00@sc8-sf-web2.sourceforge.net>

Bugs item #835036, was opened at 2003-11-03 08:58
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=835036&group_id=103

Category: Web/CGI
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Clyde Jones (clydec)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bug encountered when doing global change of address

Initial Comment:
I was trying to do a global change of name/address for
myself and encountered this bug.  The new address was
already a member of one of the mailing lists

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

Bug in Mailman version 2.1.2

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 "/home/usr/local/mailman/scripts/driver", line
87, in run_main
    main()
  File
"/home/usr/local/mailman/Mailman/Cgi/confirm.py", line
131, in main
    addrchange_confirm(mlist, doc, cookie)
  File
"/home/usr/local/mailman/Mailman/Cgi/confirm.py", line
492, in addrchange_confirm
    op, oldaddr, newaddr =
mlist.ProcessConfirmation(cookie)
  File "/home/usr/local/mailman/Mailman/MailList.py",
line 1113, in ProcessConfirmation
    self.ApprovedChangeMemberAddress(oldaddr, newaddr,
globally)
  File "/home/usr/local/mailman/Mailman/MailList.py",
line 1032, in ApprovedChangeMemberAddress
    self.changeMemberAddress(oldaddr, newaddr)
  File
"/home/usr/local/mailman/Mailman/OldStyleMemberships.py",
line 251, in changeMemberAddress
    password=password, language=lang)
  File
"/home/usr/local/mailman/Mailman/OldStyleMemberships.py",
line 175, in addNewMember
    raise Errors.MMAlreadyAMember, member
MMAlreadyAMember: clyde.jones@thermo.com





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

Python information:
Variable Value 
sys.version 2.2.3 (#2, Jul 17 2003, 14:48:38) [GCC
egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)]  
sys.executable /usr/bin/python  
sys.prefix /usr/local  
sys.exec_prefix /usr/local  
sys.path /usr/local  
sys.platform linux2  




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

Environment variables:
Variable Value 
HTTP_ACCEPT  image/gif, image/x-xbitmap, image/jpeg,
image/pjpeg, application/vnd.ms-powerpoint,
application/vnd.ms-excel, application/msword,
application/x-shockwave-flash, */*  
CONTENT_TYPE  application/x-www-form-urlencoded  
HTTP_REFERER 
http://www.clydec.net/mailman/confirm/jujitsu/fe77e7f88cdb236aef702757e6be57e4b9f81338
 
SERVER_SOFTWARE  Apache/1.3.22 (Unix) (Red-Hat/Linux)
PHP/4.3.3 mod_perl/1.21  
PYTHONPATH  /home/usr/local/mailman  
SCRIPT_FILENAME  /home/usr/local/mailman/cgi-bin/confirm  
SERVER_ADMIN  webmaster@clydec.net  
SCRIPT_NAME  /mailman/confirm  
SERVER_SIGNATURE  Apache/1.3.22 Server at
www.clydec.net Port 80 
REQUEST_METHOD  POST  
HTTP_HOST  www.clydec.net  
PATH_INFO  /jujitsu  
SERVER_PROTOCOL  HTTP/1.1  
QUERY_STRING   
HTTP_CACHE_CONTROL  no-cache  
REQUEST_URI  /mailman/confirm/jujitsu  
CONTENT_LENGTH  69  
HTTP_USER_AGENT  Mozilla/4.0 (compatible; MSIE 6.0;
Windows NT 5.0)  
HTTP_CONNECTION  Keep-Alive  
SERVER_NAME  www.clydec.net  
REMOTE_ADDR  209.150.103.223  
REMOTE_PORT  2500  
HTTP_ACCEPT_LANGUAGE  en-us  
PATH_TRANSLATED  /home/httpd/html/jujitsu  
SERVER_PORT  80  
GATEWAY_INTERFACE  CGI/1.1  
REMOTE_HOST  clydec2.qis.net  
HTTP_ACCEPT_ENCODING  gzip, deflate  
SERVER_ADDR  209.150.103.222  
DOCUMENT_ROOT  /home/httpd/html  



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

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

Message:
Logged In: YES 
user_id=12800

Fixed for Mailman 2.1.4

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

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

From noreply at sourceforge.net  Mon Nov 24 23:41:49 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 03:00:05 2003
Subject: [ mailman-Bugs-828381 ] ASCII decoding error
Message-ID: <E1AOV1J-0006Go-00@sc8-sf-web2.sourceforge.net>

Bugs item #828381, was opened at 2003-10-22 13:53
Message generated for change (Comment added) made by bwarsaw
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: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 23:41

Message:
Logged In: YES 
user_id=12800

It was possible in older versions of Mailman to get
non-ascii characters into the email addresses.  Mailman
2.1.3 should prevent this, and removing invalid addresses as
you've done below is the way to fix older lists.

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

Comment By: Jon Stevens (latchkey)
Date: 2003-10-27 13: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  Mon Nov 24 21:19:20 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 03:02:21 2003
Subject: [ mailman-Bugs-829982 ] MakeCookie/WebAuthent fail when a user
	changes the password
Message-ID: <E1AOSnQ-0002Au-00@sc8-sf-web3.sourceforge.net>

Bugs item #829982, was opened at 2003-10-25 00:51
Message generated for change (Comment added) made by bwarsaw
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...




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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 21:19

Message:
Logged In: YES 
user_id=12800

Please provide me with a set of instructions that will
reproducibly cause the crash.  I am unable to make it happen
in my test set up.

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

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

From noreply at sourceforge.net  Mon Nov 24 23:55:21 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 03:02:52 2003
Subject: [ mailman-Bugs-825143 ] build with multiple submake jobs fails
Message-ID: <E1AOVEP-00053H-00@sc8-sf-web4.sourceforge.net>

Bugs item #825143, was opened at 2003-10-16 18:11
Message generated for change (Comment added) made by bwarsaw
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: Closed
>Resolution: Wont Fix
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.

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

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

Message:
Logged In: YES 
user_id=12800

Mailman doesn't have enough C code to justify supporting
parallel makes IMO.  Mailman doesn't do anything special
here, so if something like this does get set automatically,
it's probably because of the configure script.  I don't
think there's anything for us to do (but if you come up with
a patch you think will help your cause, feel free to attach
it here).

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

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

From noreply at sourceforge.net  Mon Nov 24 23:56:28 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 03:02:54 2003
Subject: [ mailman-Bugs-820322 ] Crash when global subcription change causes
	collision
Message-ID: <E1AOVFU-0007Vy-00@sc8-sf-web3.sourceforge.net>

Bugs item #820322, was opened at 2003-10-08 18:47
Message generated for change (Comment added) made by bwarsaw
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: Closed
>Resolution: Duplicate
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: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 23:56

Message:
Logged In: YES 
user_id=12800

This is a duplicate, and the bug has been fixed for Mailman
2.1.4

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

Comment By: Simon Harrison (simonha)
Date: 2003-10-30 06: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  Mon Nov 24 23:42:18 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 05:45:57 2003
Subject: [ mailman-Bugs-828381 ] ASCII decoding error
Message-ID: <E1AOV1m-0006Hl-00@sc8-sf-web2.sourceforge.net>

Bugs item #828381, was opened at 2003-10-22 13:53
Message generated for change (Settings changed) made by bwarsaw
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: Closed
>Resolution: Wont Fix
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: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 23:41

Message:
Logged In: YES 
user_id=12800

It was possible in older versions of Mailman to get
non-ascii characters into the email addresses.  Mailman
2.1.3 should prevent this, and removing invalid addresses as
you've done below is the way to fix older lists.

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

Comment By: Jon Stevens (latchkey)
Date: 2003-10-27 13: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  Tue Nov 25 00:47:21 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 07:03:13 2003
Subject: [ mailman-Bugs-818752 ] Changing option via email not work
Message-ID: <E1AOW2j-0004Og-00@sc8-sf-web1.sourceforge.net>

Bugs item #818752, was opened at 2003-10-06 13:51
Message generated for change (Comment added) made by bwarsaw
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: Closed
>Resolution: Fixed
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.





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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-25 00:47

Message:
Logged In: YES 
user_id=12800

I've previously fixed the bug with setting delivery for
Mailman 2.1.4  AFAICT, setting digest works fine.

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

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

From noreply at sourceforge.net  Mon Nov 24 23:49:40 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 07:09:45 2003
Subject: [ mailman-Bugs-826775 ] Change URL for submit buttons
Message-ID: <E1AOV8u-0006Tq-00@sc8-sf-web2.sourceforge.net>

Bugs item #826775, was opened at 2003-10-20 07:06
Message generated for change (Comment added) made by bwarsaw
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: Closed
>Resolution: Invalid
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: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 23:49

Message:
Logged In: YES 
user_id=12800

If you set up the virtual hosting support properly, and if
you visit the pages via the right virtual host url, Mailman
should use that to form the basis of the various urls.  It
will set web_page_url when you create the list.  If this
variable isn't set right, you'll need to use bin/withlist to
fix it, as you cannot change this variable through the web.

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

Comment By: Ulrich Windl (windl)
Date: 2003-10-22 06: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 06: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  Mon Nov 24 21:10:59 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 08:46:07 2003
Subject: [ mailman-Bugs-833762 ] virus detected on file within tgz
Message-ID: <E1AOSfL-0001I3-00@sc8-sf-web2.sourceforge.net>

Bugs item #833762, was opened at 2003-10-31 12:34
Message generated for change (Comment added) made by bwarsaw
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: Closed
>Resolution: Invalid
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

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

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

Message:
Logged In: YES 
user_id=12800

Your antivirus isn't that smart.  Mailman's test suite
contains a neutered message with the nimda headers, but it
definitely does not contain any virus.

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

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

From noreply at sourceforge.net  Tue Nov 25 10:40:55 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 10:40:58 2003
Subject: [ mailman-Bugs-849036 ] fully remove product and version information
Message-ID: <E1AOfJ9-0006eP-00@sc8-sf-web3.sourceforge.net>

Bugs item #849036, was opened at 2003-11-25 16:40
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=849036&group_id=103

Category: security/privacy
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Florian Effenberger (floeff)
Assigned to: Nobody/Anonymous (nobody)
Summary: fully remove product and version information

Initial Comment:
I would like to see an option in the configuration
files to fully remove product and version information
from the CGIs and the mail headers.

It is part of my security concept to NOT show anything
like that to outside users.

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

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

From noreply at sourceforge.net  Tue Nov 25 10:42:44 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 10:42:46 2003
Subject: [ mailman-Feature Requests-849039 ] How to disable lists
Message-ID: <E1AOfKu-0002Ny-00@sc8-sf-web2.sourceforge.net>

Feature Requests item #849039, was opened at 2003-11-25 15:42
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=849039&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: How to disable lists

Initial Comment:
Hi,
I want to disable lists. It should be impossible to post 
messages after disableing a list. Everything else shall 
work like before.

I thought its just to comment out the list refering lies in 
data/aliases but this dosn?t help.

I?m very appreciated for any idea, thanks.

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

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

From noreply at sourceforge.net  Tue Nov 25 11:51:12 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 11:51:18 2003
Subject: [ mailman-Bugs-825143 ] build with multiple submake jobs fails
Message-ID: <E1AOgPA-0002pw-00@sc8-sf-web3.sourceforge.net>

Bugs item #825143, was opened at 2003-10-16 15:11
Message generated for change (Comment added) made by lanclos
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: Closed
Resolution: Wont Fix
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.

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

>Comment By: Kyle Lanclos (lanclos)
Date: 2003-11-25 08:51

Message:
Logged In: YES 
user_id=888067

Enabling parallel compilation is, I agree, not worthwhile
for mailman-- however, disabling parallel compilation is,
given that the errors produced by multiple active submake
jobs are completely silent to the person building the
software. It'd be nice if mailman would just shutdown the
jobserver mode completely given that it is unnecessary.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 20:55

Message:
Logged In: YES 
user_id=12800

Mailman doesn't have enough C code to justify supporting
parallel makes IMO.  Mailman doesn't do anything special
here, so if something like this does get set automatically,
it's probably because of the configure script.  I don't
think there's anything for us to do (but if you come up with
a patch you think will help your cause, feel free to attach
it here).

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

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

From noreply at sourceforge.net  Tue Nov 25 12:06:00 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 12:06:35 2003
Subject: [ mailman-Bugs-825143 ] build with multiple submake jobs fails
Message-ID: <E1AOgdU-00069C-00@sc8-sf-web1.sourceforge.net>

Bugs item #825143, was opened at 2003-10-16 18:11
Message generated for change (Comment added) made by bwarsaw
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: Closed
Resolution: Wont Fix
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.

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-25 12:06

Message:
Logged In: YES 
user_id=12800

If you want to develop a patch, I would definitely take a
look at it.

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

Comment By: Kyle Lanclos (lanclos)
Date: 2003-11-25 11:51

Message:
Logged In: YES 
user_id=888067

Enabling parallel compilation is, I agree, not worthwhile
for mailman-- however, disabling parallel compilation is,
given that the errors produced by multiple active submake
jobs are completely silent to the person building the
software. It'd be nice if mailman would just shutdown the
jobserver mode completely given that it is unnecessary.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-24 23:55

Message:
Logged In: YES 
user_id=12800

Mailman doesn't have enough C code to justify supporting
parallel makes IMO.  Mailman doesn't do anything special
here, so if something like this does get set automatically,
it's probably because of the configure script.  I don't
think there's anything for us to do (but if you come up with
a patch you think will help your cause, feel free to attach
it here).

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

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

From noreply at sourceforge.net  Tue Nov 25 14:15:37 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 14:15:42 2003
Subject: [ mailman-Bugs-849036 ] fully remove product and version information
Message-ID: <E1AOiev-0007Dz-00@sc8-sf-web4.sourceforge.net>

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

Category: security/privacy
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Florian Effenberger (floeff)
Assigned to: Nobody/Anonymous (nobody)
Summary: fully remove product and version information

Initial Comment:
I would like to see an option in the configuration
files to fully remove product and version information
from the CGIs and the mail headers.

It is part of my security concept to NOT show anything
like that to outside users.

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

>Comment By: Florian Effenberger (floeff)
Date: 2003-11-25 20:15

Message:
Logged In: YES 
user_id=240337

No problem, it was just a suggestion :) I know views may
vary on this.

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

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

From noreply at sourceforge.net  Tue Nov 25 14:17:47 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue Nov 25 14:18:26 2003
Subject: [ mailman-Bugs-849036 ] fully remove product and version information
Message-ID: <E1AOih1-0007MV-00@sc8-sf-web4.sourceforge.net>

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

Category: security/privacy
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Florian Effenberger (floeff)
Assigned to: Nobody/Anonymous (nobody)
Summary: fully remove product and version information

Initial Comment:
I would like to see an option in the configuration
files to fully remove product and version information
from the CGIs and the mail headers.

It is part of my security concept to NOT show anything
like that to outside users.

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

>Comment By: Florian Effenberger (floeff)
Date: 2003-11-25 20:17

Message:
Logged In: YES 
user_id=240337

Ah, sorry, the comment from 2003-11-25 20:15 was meant for
another bug, please ignore it. The feature request is still
valid, though.

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

Comment By: Florian Effenberger (floeff)
Date: 2003-11-25 20:15

Message:
Logged In: YES 
user_id=240337

No problem, it was just a suggestion :) I know views may
vary on this.

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

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

From noreply at sourceforge.net  Wed Nov 26 10:33:30 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Nov 26 10:33:34 2003
Subject: [ mailman-Feature Requests-849711 ] Challenge/Response for held
	postings
Message-ID: <E1AP1fW-0006SK-00@sc8-sf-web2.sourceforge.net>

Feature Requests item #849711, was opened at 2003-11-26 16:33
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=849711&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin Schr?der (oneiros)
Assigned to: Nobody/Anonymous (nobody)
Summary: Challenge/Response for held postings

Initial Comment:
With moderated or member-only lists the lists get a
multitude of spam which the admin has to discard
manually (Listserv does this automagically). 

Mailman could discard most of the spam automatically if
it would implement a challenge/response for all
messages hold for moderator approval: Mail the sender
(usually forged) and  ask them to confirm the message
(by mail or www). If the message isn't confirmed after
24h, drop it silently and don't bother the admin.

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

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

From noreply at sourceforge.net  Fri Nov 28 11:23:43 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Nov 28 11:23:47 2003
Subject: [ mailman-Patches-850805 ] Aggressive anti email address harvesting
	measure
Message-ID: <E1APlPD-0007Cc-00@sc8-sf-web3.sourceforge.net>

Patches item #850805, was opened at 2003-11-28 16:23
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=850805&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: Aggressive anti email address harvesting measure

Initial Comment:
This patch is prompted by discussion on the mailman-
developers list won the following subject:

Re: [Mailman-Developers] bugtraq submission warning: 
email address harvesting exploit

For those with deep concerns about email address harvesting 
this patch offers a more aggressive masking of email 
addresses in Mailman mail archive files.

The patch modifes two files in the standard Mailman 
distribution: Mailman/Defaults.py and Mailman/Cgi/
private.py and can be applied using the following command 
from within the Mailman build directory:

    path -p1 < path-to-patch-file
    
It would be fairly trivial to make enabling this feature per-
list configurable rather than it being a site admin decision 
and I will enhance this patch for that purpose if people show 
an interest in it being done.

The following notes about the patch can be found in 
Defaults.py. Rather idiosyncratically most of the operational 
elements of this patch are in that file. My reasoning behind 
this decision is that if people want to fool with the regexes 
that are at the heart of this patch they can see what will be 
affected by the changes more readily if the related bits are 
in the same place.


#####
# Anti-spam email address harvesting prevention measures.
#
# These measures are to limit the ability of spam generators 
to acquire
# email address from archived material in Mailman's list 
archives.
# Implementation is via a dynamic search and replace for 
email
# addresses, appearing in files of MIME type text/html or 
text/plain, as
# those files are requested. The underlying archive file 
content as 
# generated by the archiving software remains unchanged.
#
# The implementation requires that archive files are all 
delivered by a
# modified private.py CGI script which only requires user 
authentication 
# if the list whose archive material is being requested is set 
up as a private
# list. In order to get public archives served by private.py a 
RewriteRule
# like this:
#
#     RewriteRule ^/pipermail/(.*) /mailman/private/$1 [PT]
#
# needs to be used in the Apache httpd.conf to transparently 
redirect 
# public arechive file requests.
#
# When email addresses are found, the domain part of the 
addressed is replaced
# with a string of 'x' characters. If the local part of the 
address appears to 
# have been VERP'ed then the VERP information is similarly 
obscured. This is
# a fairly brutal set of irreversible modifications to any 
email addresses in 
# the returned text and will break any mailto: links in the 
text.
#
# Th eamil address regex looks for either an '@' character 
or its HTML escaped
# version '%40' as the local-part/domain separator. You 
should set
# ARCHIVER_OBSCURES_EMAILADDRS = 0 and run bin/arch 
to rebuild existing archives 
# to prevent that feature interfering with the operation of 
these harvesting 
# prevention measures.
#
# If you decide to change the regexes then copy all of this 
stuff into
# mm_cfg.py and make the changes there.
#
#####


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

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

From noreply at sourceforge.net  Sat Nov 29 21:37:53 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat Nov 29 21:37:56 2003
Subject: [ mailman-Bugs-851416 ] No HTML quoting of address on "Subscription
	results" page
Message-ID: <E1AQHT7-0002yi-00@sc8-sf-web1.sourceforge.net>

Bugs item #851416, was opened at 2003-11-30 13:37
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=851416&group_id=103

Category: Web/CGI
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter J. R. Moulder (pjrm)
Assigned to: Nobody/Anonymous (nobody)
Summary: No HTML quoting of address on "Subscription results" page

Initial Comment:
When subscribing using the web interface (e.g.
http://lists.sourceforge.net/lists/listinfo/inkscape-devel),
the resulting "mylist Subscription results" page
includes the literal text "<jrl@host.domain>"
("Instructions are being sent to you at
<jrl@host.domain>"), whereas HTML contains no such
element.  Subscriber address ought to be html-escaped
using &lt;, &gt;, &amp;.

(Also, as mentioned in #596215, this page contains
other bad HTML such as an unterminated "<body" tag, and
a <html>...</html> element within a <BODY
...>...</body> element.)

version 2.0.9-sf.net

pjrm.

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

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

From noreply at sourceforge.net  Sat Nov 29 21:44:03 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat Nov 29 21:44:05 2003
Subject: [ mailman-Patches-851419 ] Clam AntiVirus handler for Mailman
Message-ID: <E1AQHZ5-0008JR-00@sc8-sf-web3.sourceforge.net>

Patches item #851419, was opened at 2003-11-30 02:44
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=851419&group_id=103

Category: None
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Sean Reifschneider (jafo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Clam AntiVirus handler for Mailman

Initial Comment:
Included is a Handler for passing messages through Clam
AntiVirus, and holding or discarding messages that are
determined to be viruses.    Similar to modules that
interface SpamAssassin, particularly useful with the
"discard" option enabled so that list managers don't
have to manually deal with viruses sent to their lists.

Currently, this tar file is oriented towards
installation by administrators into their existing
setups, as it's likely to be a while before this
functionality is available in the base.  For the final
release I imagine that a README.ClamAV, a section in
the main README, or simply a good set of comments for
the Defaults.py file would do the job.  I'll build
patches to support these, please provide feedback on
which mechanism is preferred.

Sean

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

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

From noreply at sourceforge.net  Sun Nov 30 02:02:11 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Nov 30 02:02:18 2003
Subject: [ mailman-Patches-850805 ] Aggressive anti email address harvesting
	measure
Message-ID: <E1AQLat-0002x9-00@sc8-sf-web4.sourceforge.net>

Patches item #850805, was opened at 2003-11-28 16:23
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&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: Aggressive anti email address harvesting measure

Initial Comment:
This patch is prompted by discussion on the mailman-
developers list won the following subject:

Re: [Mailman-Developers] bugtraq submission warning: 
email address harvesting exploit

For those with deep concerns about email address harvesting 
this patch offers a more aggressive masking of email 
addresses in Mailman mail archive files.

The patch modifes two files in the standard Mailman 
distribution: Mailman/Defaults.py and Mailman/Cgi/
private.py and can be applied using the following command 
from within the Mailman build directory:

    path -p1 < path-to-patch-file
    
It would be fairly trivial to make enabling this feature per-
list configurable rather than it being a site admin decision 
and I will enhance this patch for that purpose if people show 
an interest in it being done.

The following notes about the patch can be found in 
Defaults.py. Rather idiosyncratically most of the operational 
elements of this patch are in that file. My reasoning behind 
this decision is that if people want to fool with the regexes 
that are at the heart of this patch they can see what will be 
affected by the changes more readily if the related bits are 
in the same place.


#####
# Anti-spam email address harvesting prevention measures.
#
# These measures are to limit the ability of spam generators 
to acquire
# email address from archived material in Mailman's list 
archives.
# Implementation is via a dynamic search and replace for 
email
# addresses, appearing in files of MIME type text/html or 
text/plain, as
# those files are requested. The underlying archive file 
content as 
# generated by the archiving software remains unchanged.
#
# The implementation requires that archive files are all 
delivered by a
# modified private.py CGI script which only requires user 
authentication 
# if the list whose archive material is being requested is set 
up as a private
# list. In order to get public archives served by private.py a 
RewriteRule
# like this:
#
#     RewriteRule ^/pipermail/(.*) /mailman/private/$1 [PT]
#
# needs to be used in the Apache httpd.conf to transparently 
redirect 
# public arechive file requests.
#
# When email addresses are found, the domain part of the 
addressed is replaced
# with a string of 'x' characters. If the local part of the 
address appears to 
# have been VERP'ed then the VERP information is similarly 
obscured. This is
# a fairly brutal set of irreversible modifications to any 
email addresses in 
# the returned text and will break any mailto: links in the 
text.
#
# Th eamil address regex looks for either an '@' character 
or its HTML escaped
# version '%40' as the local-part/domain separator. You 
should set
# ARCHIVER_OBSCURES_EMAILADDRS = 0 and run bin/arch 
to rebuild existing archives 
# to prevent that feature interfering with the operation of 
these harvesting 
# prevention measures.
#
# If you decide to change the regexes then copy all of this 
stuff into
# mm_cfg.py and make the changes there.
#
#####


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

>Comment By: Richard Barrett (ppsys)
Date: 2003-11-30 07:02

Message:
Logged In: YES 
user_id=75166

As pointed out on the mailman-developers list, potential users of 
this patch should be aware that the simple approach to masking 
email addresses used by this patch will also capture and munge 
any other strings in the archive data that resemble email 
addresses. This can include mailto URLs, other URLs and Message 
ids. This side-effect may make the patch unsuitable for use with 
your system, although you also need to consider that the patch 
does not irreversibly change the source pipermail archived 
material held on the server; the changes are only made in the 
copy of the archive material sent to the requesting browser by the 
server.

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

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

From noreply at sourceforge.net  Sun Nov 30 19:13:33 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Nov 30 19:13:39 2003
Subject: [ mailman-Bugs-784700 ] 'make install' after 'make' modifies source
	tree
Message-ID: <E1AQbgz-0008TM-00@sc8-sf-web1.sourceforge.net>

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

Category: configuring/installing
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Thomas Arendsen Hein (thomas_ah)
Assigned to: Nobody/Anonymous (nobody)
Summary: 'make install' after 'make' modifies source tree

Initial Comment:
With mailman 2.1.2 './configure' and 'make' run fine,
but then I switched to the mailman user account to do
'make install'.

It tried to unpack misc/email-2.5.1.tar.gz,
misc/JapaneseCodecs-1.4.9.tar.gz and
misc/KoreanCodecs-2.0.5.tar.gz, but this failed because
the mailman user doesn't have write permission in the
source tree.

I think 'make install' shouldn't need to write to the
source tree after 'make' was done. Either this has to
be done during 'make' or to the /tmp directory.


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-30 19:13

Message:
Logged In: YES 
user_id=12800

Fixed by addition of a make variable PKGDIR

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

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

From noreply at sourceforge.net  Sun Nov 30 19:37:46 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Nov 30 19:37:54 2003
Subject: [ mailman-Bugs-849036 ] fully remove product and version information
Message-ID: <E1AQc4Q-0001rc-00@sc8-sf-web4.sourceforge.net>

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

Category: security/privacy
Group: 2.1 (stable)
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Florian Effenberger (floeff)
Assigned to: Nobody/Anonymous (nobody)
Summary: fully remove product and version information

Initial Comment:
I would like to see an option in the configuration
files to fully remove product and version information
from the CGIs and the mail headers.

It is part of my security concept to NOT show anything
like that to outside users.

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-30 19:37

Message:
Logged In: YES 
user_id=12800

You'll have to hack the source to do this.  I don't plan on
making this a configuration variable.

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

Comment By: Florian Effenberger (floeff)
Date: 2003-11-25 14:17

Message:
Logged In: YES 
user_id=240337

Ah, sorry, the comment from 2003-11-25 20:15 was meant for
another bug, please ignore it. The feature request is still
valid, though.

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

Comment By: Florian Effenberger (floeff)
Date: 2003-11-25 14:15

Message:
Logged In: YES 
user_id=240337

No problem, it was just a suggestion :) I know views may
vary on this.

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

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

From noreply at sourceforge.net  Sun Nov 30 19:54:23 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Nov 30 19:54:44 2003
Subject: [ mailman-Bugs-833384 ] wrong moderator password shouldn't silently
	discard message
Message-ID: <E1AQcKV-0002Xk-00@sc8-sf-web4.sourceforge.net>

Bugs item #833384, was opened at 2003-10-30 17:05
Message generated for change (Comment added) made by bwarsaw
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: Closed
>Resolution: Fixed
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.)


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-30 19:54

Message:
Logged In: YES 
user_id=12800

Fixed for 2.1.4


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

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

From noreply at sourceforge.net  Sun Nov 30 20:03:54 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Nov 30 20:04:19 2003
Subject: [ mailman-Bugs-835012 ] incorrect permissions on archive index file
Message-ID: <E1AQcTi-00078q-00@sc8-sf-web3.sourceforge.net>

Bugs item #835012, was opened at 2003-11-03 08:14
Message generated for change (Settings changed) made by bwarsaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=835012&group_id=103

Category: security/privacy
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Rohan Carly (rohanc)
Assigned to: Nobody/Anonymous (nobody)
Summary: incorrect permissions on archive index file

Initial Comment:
The index file for list archives is created with the wrong 
file permissions. I'm referring to:

mailman/archives/private/ --listname-- / index.html

All my lists have index.html set to "rw-rw-rw-" which 
seems too permissive.

I think this can be corrected by modifiying the 
Archiver.InitVars method inside the file:

   mailman/Mailman/Archiver/Archiver.py .

I just added:
   os.umask(omask)
before the line that reads:
   fp = open(indexfile, 'w')

I run Mailman 2.1.3.








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

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

From noreply at sourceforge.net  Sun Nov 30 20:23:00 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Nov 30 20:23:07 2003
Subject: [ mailman-Bugs-816410 ] subscription request webpage has
	inconsistant wording
Message-ID: <E1AQcmC-0003MT-00@sc8-sf-web2.sourceforge.net>

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

Category: Web/CGI
>Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
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  Sun Nov 30 20:43:31 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Nov 30 20:43:57 2003
Subject: [ mailman-Bugs-834486 ] Uncatched ValueError in Scrubber
Message-ID: <E1AQd63-0004CT-00@sc8-sf-web4.sourceforge.net>

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

Category: None
>Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Uncatched ValueError in Scrubber

Initial Comment:

Mailman 2.1.2, python 2.2

Nov 01 20:40:04 2003 (10542) Uncaught runner exception:
Empty module name
Nov 01 20:40:04 2003 (10542) Traceback (most recent
call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py",
line 105, in _oneloop
    self._onefile(msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/Runner.py",
line 155, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File
"/usr/local/mailman/Mailman/Queue/IncomingRunner.py",
line 130, in _dispose
    more = self._dopipeline(mlist, msg, msgdata, pipeline)
  File
"/usr/local/mailman/Mailman/Queue/IncomingRunner.py",
line 153, in _dopipeline
    sys.modules[modname].process(mlist, msg, msgdata)
  File
"/usr/local/mailman/Mailman/Handlers/ToDigest.py", line
89, in process
    send_digests(mlist, 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
308, in process
    t = t.encode(charset, 'replace')
  File "/usr/lib/python2.2/encodings/__init__.py", line
51, in search_function
    mod = __import__(modname,globals(),locals(),'*')
ValueError: Empty module name

This is still uncorrected in v2_1-branch

Attached a proposed fix.



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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-11-30 20:43

Message:
Logged In: YES 
user_id=12800

Thanks, applied!

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

Comment By: jared mauch (jaredmauch)
Date: 2003-11-12 10:26

Message:
Logged In: YES 
user_id=131445

I'm also seeing this error.  This patch solved my problem. 
Thanks!


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

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