From claw@kanga.nu  Sun Dec  1 00:55:48 2002
From: claw@kanga.nu (J C Lawrence)
Date: Sat, 30 Nov 2002 16:55:48 -0800
Subject: [Mailman-Developers] [ mailman-Patches-644129 ] Edit held message
	header/body 
In-Reply-To: Message from noreply@sourceforge.net 
	<E18H2na-0005hA-00@sc8-sf-web3.sourceforge.net> 
References: <E18H2na-0005hA-00@sc8-sf-web3.sourceforge.net> 
Message-ID: <18729.1038704148@kanga.nu>

On Wed, 27 Nov 2002 06:04:18 -0800 
noreply  <noreply@sourceforge.net> wrote:

> Patches item #644129, was opened at 2002-11-26 09:44 You can respond
> by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_id=103

...

> Initial Comment: Here is my preliminary (brute force) patch to allow
> full editing of headers and bodies of messages being held for approval
> in Mailman 2.1 (as of beta 5).  I have released versions of this for
> 1.x and 2.0.x but wanted to wait until 2.1 was fairly stable before
> releasing this one.

...

>> Comment By: Barry A. Warsaw (bwarsaw)
> Date: 2002-11-27 09:04

> Message: Logged In: YES user_id=12800

> I'm moving this to the 2.2/3.0 group since we're in feature freeze for
> 2.1

Given the age of the patch (it goes all the way back to the 1.x days),
is this really such an unknown quantity that it has to shoved out to
post 2.1?

-- 
J C Lawrence                
---------(*)                Satan, oscillate my metallic sonatas. 
claw@kanga.nu               He lived as a devil, eh?		  
http://www.kanga.nu/~claw/  Evil is a name of a foeman, as I live.


From claw@kanga.nu  Sun Dec  1 00:59:08 2002
From: claw@kanga.nu (J C Lawrence)
Date: Sat, 30 Nov 2002 16:59:08 -0800
Subject: [Mailman-Developers] [ mailman-Patches-644129 ] Edit held message
	header/body 
In-Reply-To: Message from J C Lawrence <claw@kanga.nu> 
   of "Sat, 30 Nov 2002 16:55:48 PST." <18729.1038704148@kanga.nu> 
References: <E18H2na-0005hA-00@sc8-sf-web3.sourceforge.net>
	<18729.1038704148@kanga.nu> 
Message-ID: <18803.1038704348@kanga.nu>

On Sat, 30 Nov 2002 16:55:48 -0800 
J C Lawrence <J> wrote:

> Given the age of the patch (it goes all the way back to the 1.x days),
> is this really such an unknown quantity that it has to shoved out to
> post 2.1?

Just saw the proposed schedule.  Please ignore this.

-- 
J C Lawrence                
---------(*)                Satan, oscillate my metallic sonatas. 
claw@kanga.nu               He lived as a devil, eh?		  
http://www.kanga.nu/~claw/  Evil is a name of a foeman, as I live.


From noreply@sourceforge.net  Sun Dec  1 02:17:08 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Sat, 30 Nov 2002 18:17:08 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-646279 ] UTF8 problem with MS Exchange/MM2.1b4
Message-ID: <E18IJfQ-0004dD-00@sc8-sf-web4.sourceforge.net>

Bugs item #646279, was opened at 2002-12-01 02:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=646279&group_id=103

Category: mail delivery
Group: 2.1 alpha
Status: Open
Resolution: None
Priority: 5
Submitted By: PieterB (pieterb)
Assigned to: Nobody/Anonymous (nobody)
Summary: UTF8 problem with MS Exchange/MM2.1b4

Initial Comment:
<pre>
Hi,

I have a problem with UTF8-encoded e-mails from a 
Microsoft Exchange
2000 server which are sent to a Mailman 2.1b4 
mailinglist server.
Exchange uses "utf8" characterset, so that the users 
will get an
extra "attachement" with every mailinglist message 
(charset "utf-8"
is used for the body, and charset "us-ascii" is used for 
the signature
of the mailinglist).

An example of the headers and body is included, below.

Is there a way to change the filtering in Mailman, so that 
these messages
are converted to a more common charset, such as: us-
ascii or iso-8859-1 

For more information see:
http://www.microsoft.com/exchange/techinfo/tips/Mail_utf
8.asp
(Mailbox Tip: Allow Non-UTF-8 Mail Clients To View 
Messages Sent
from Exchange).  I tried to get the Exchange server 
changed, but
didn't get any response of the local administrator. ;(

Regards,

Pieter


8<--------------------------------------------

X-MimeOLE: Produced By Microsoft Exchange 
V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----
_=_NextPart_001_01C29496.DF565EF8"
Date: Mon, 25 Nov 2002 16:25:23 +0100
X-MS-TNEF-Correlator: 
<D5DF62311578B6438DC9703240E4FC6F179F4B@foo.
bar>
Thread-Topic: foo.bar
Thread-Index: 
AcKUlojItUqNGxBLS1mNvYY31kEXygAACufy
X-Content-Filtered-By: Mailman/MimeDel 2.1b4
X-Mailman-Version: 2.1b4

This is a multi-part message in MIME format.

------_=_NextPart_001_01C29496.DF565EF8
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

  [base64 attachement removed]

------_=_NextPart_001_01C29496.DF565EF8
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

--
footer of the mailinglist

------_=_NextPart_001_01C29496.DF565EF8--




</pre>

See: <a href="http://mail.python.org/pipermail/mailman-
developers/2002-
November/014048.html">http://mail.python.org/pipermail/
mailman-developers/2002-November/014048.html</a>

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

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

From fil@rezo.net  Sun Dec  1 10:33:42 2002
From: fil@rezo.net (Fil)
Date: Sun, 1 Dec 2002 11:33:42 +0100
Subject: [Mailman-Developers] sorry, this unicode bug is still here
Message-ID: <20021201103342.GA31566@rezo.net>


With the current cvs; it happens when I try to subscribe from the web page.
And a similar traceback appears when the daily admin reminder tries to send
email...

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><
Bug in Mailman version 2.1b5+

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/subscribe.py", line 94, in main
    process_form(mlist, doc, cgidata, language)
  File "/usr/local/mailman/Mailman/Cgi/subscribe.py", line 176, in
process_form
    mlist.AddMember(userdesc, remote)
  File "/usr/local/mailman/Mailman/MailList.py", line 832, in AddMember
    self.HoldSubscription(email, name, password, digest, lang)
  File "/usr/local/mailman/Mailman/ListAdmin.py", line 418, in
HoldSubscription
    self.preferred_language)
  File "/usr/local/mailman/Mailman/Message.py", line 203, in __init__
    self['Subject'] = Header(subject, charset, header_name='Subject')
  File "/usr/local/mailman/pythonlib/email/Header.py", line 164, in __init__
    self.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append
    ustr = unicode(s, incodec)
UnicodeError: ASCII decoding error: ordinal not in range(128)



Python information:

Variable Value
sys.version 2.1.3 (#1, Apr 20 2002, 10:14:34) [GCC 2.95.4 20011002 (Debian
prerelease)]
sys.executable /usr/bin/python
sys.prefix /usr
sys.exec_prefix /usr
sys.path /usr
sys.platform linux2

Environment variables:

Variable Value
DOCUMENT_ROOT /var/www/listes.rezo.net
SERVER_ADDR 80.67.170.17
HTTP_ACCEPT_ENCODING gzip, deflate, compress;q=0.9
CONTENT_LENGTH 31
CONTENT_TYPE application/x-www-form-urlencoded
PATH_TRANSLATED /var/www/listes.rezo.net/test
REMOTE_ADDR 62.212.98.121
GATEWAY_INTERFACE CGI/1.1
UNIQUE_ID PenkgFBDqhEAAFKeSQw
HTTP_ACCEPT_LANGUAGE en-us, en;q=0.50
HTTP_KEEP_ALIVE 300
SERVER_PORT 80
HTTP_CONNECTION keep-alive
HTTP_USER_AGENT Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1)
Gecko/20021104 Chimera/0.6
HTTP_ACCEPT
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1
REQUEST_URI /mailman/subscribe/test
QUERY_STRING
SCRIPT_FILENAME /home/mailman/cgi-bin/subscribe
SCRIPT_URL /mailman/subscribe/test
HTTP_HOST listes.rezo.net
REQUEST_METHOD POST
SERVER_SIGNATURE
SCRIPT_URI http://listes.rezo.net/mailman/subscribe/test
SCRIPT_NAME /mailman/subscribe
SERVER_ADMIN fil@rezo.net
SERVER_SOFTWARE Apache/1.3.26 (Unix) Debian GNU/Linux mod_fastcgi/2.2.12
mod_perl/1.26 PHP/4.2.3
PYTHONPATH /usr/local/mailman
PATH_INFO /test
HTTP_REFERER http://listes.rezo.net/mailman/listinfo/test
SERVER_NAME listes.rezo.net
REMOTE_PORT 28833
SERVER_PROTOCOL HTTP/1.1


-- Fil


From noreply@sourceforge.net  Sun Dec  1 19:17:31 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Sun, 01 Dec 2002 11:17:31 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-646568 ] Admin interface link on listinfo page
Message-ID: <E18IZat-0000zg-00@sc8-sf-web1.sourceforge.net>

Bugs item #646568, was opened at 2002-12-01 13:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=646568&group_id=103

Category: Web/CGI
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: David Gibbs (midrangeman)
Assigned to: Nobody/Anonymous (nobody)
Summary: Admin interface link on listinfo page

Initial Comment:
I installed MM 2.1b5 and copied the data files for a few 
test lists to the 'lists' dirctory.  I then ran update -f to 
update the data files to the new version.

When I go to the list info page for one of the lists, the 
link to the administrative interface is still pointing to the 
original (production) web interface link.

Example:

Production version of MM's web interface: 
http://lists.midrange.com/cgi-bin/listinfo/testlist

Beta version of MM's web interface:
http://lists.midrange.com/mailman2/listinfo/testlist

However, on this listinfo page, the admin link points to 
http://lists.midrange.com/cgi-bin/admin/testlist

I have changed the DEFAULT_URL_PATTERN to 
be 'http://%s/mailman2/', so I would expect the links to 
have the correct url.

Additionally, when I go directly to the test list admin 
page 
(http://lists.midrange.com/mailman2/admin/testlist), all 
the links on this page also point to old cgi-bin url.



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

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

From noreply@sourceforge.net  Sun Dec  1 19:19:42 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Sun, 01 Dec 2002 11:19:42 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-646571 ] config_list: UnboundLocalError
Message-ID: <E18IZd0-0000Ts-00@sc8-sf-web2.sourceforge.net>

Bugs item #646571, was opened at 2002-12-01 13:19
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=646571&group_id=103

Category: command line scripts
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: David Gibbs (midrangeman)
Assigned to: Nobody/Anonymous (nobody)
Summary: config_list: UnboundLocalError

Initial Comment:
[mailman@linux work]$ ../bin/config_list -o beta-
testers.cfg beta-testers
Traceback (most recent call last):
  File "../bin/config_list", line 327, in ?
    main()
  File "../bin/config_list", line 320, in main
    do_output(listname, outfile)
  File "../bin/config_list", line 122, in do_output
    if closep:
UnboundLocalError: local variable 'closep' referenced 
before assignment

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

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

From noreply@sourceforge.net  Sun Dec  1 20:24:25 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Sun, 01 Dec 2002 12:24:25 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-646596 ] wrong install path
Message-ID: <E18Iadd-00028T-00@sc8-sf-web2.sourceforge.net>

Bugs item #646596, was opened at 2002-12-01 20:24
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=646596&group_id=103

Category: configuring/installing
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthias Klose (doko)
Assigned to: Nobody/Anonymous (nobody)
Summary: wrong install path

Initial Comment:
./usr/lib/mailman/pythonlib
[...]
./usr/lib/mailman/pythonlib/japanese
./usr/lib/mailman/pythonlib/japanese/__init__.py
[...]
./usr/lib/mailman/pythonlib/lib/python2.2
./usr/lib/mailman/pythonlib/lib/python2.2/site-packages
./usr/lib/mailman/pythonlib/lib/python2.2/site-packages/japanese.pth

the last one is at least not found, because it's
installed in mailman's prefix, not in python's prefix


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

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

From noreply@sourceforge.net  Sun Dec  1 20:26:47 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Sun, 01 Dec 2002 12:26:47 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-646598 ] build machine != install machine
Message-ID: <E18Iafv-0002EW-00@sc8-sf-web2.sourceforge.net>

Bugs item #646598, was opened at 2002-12-01 20:26
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=646598&group_id=103

Category: configuring/installing
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthias Klose (doko)
Assigned to: Nobody/Anonymous (nobody)
Summary: build machine != install machine

Initial Comment:
when building packages on a machine, the machine name
is encoded in Defaults.py. Not sure, what the "correct"
solution is, but IMO it would be better to set the name
in mm_cfg.py.


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

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

From noreply@sourceforge.net  Mon Dec  2 00:29:24 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Sun, 01 Dec 2002 16:29:24 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-646722 ] Robots needed in individual msgs
Message-ID: <E18IeSi-0003U1-00@sc8-sf-web3.sourceforge.net>

Bugs item #646722, was opened at 2002-12-01 17:29
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=646722&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Joe R. Doupnik (jdoupnik)
Assigned to: Nobody/Anonymous (nobody)
Summary: Robots needed in individual msgs

Initial Comment:
Mailman 2.1b5. Archive summary web pages have
Robot shoo-away META tags, but the individual
messages do not. They should be labelded the
same way, for the same reasons. They are exposed
to plunder in publically visible archives.
 Similarly, I wish we had a control to force
authentication before aggregates are downloaded.
I have removed the wide open "download the whole
thing" givaway, but the individual (month, *.txt ) files
are vulnerable. Changing this behavior is too difficult
for a non-Python expert. I have also removed the
web based list creation/removal cgi-bin scripts
and associated web page material. The security model
is set for exploitation first, protection second.
 Joe D.

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

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

From barry@python.org  Mon Dec  2 04:56:34 2002
From: barry@python.org (Barry A. Warsaw)
Date: Sun, 1 Dec 2002 23:56:34 -0500
Subject: [Mailman-Developers] Howto submit patches?
References: <E18HUt8-0001HB-00@gandalf.math.uni-mannheim.de>
Message-ID: <15850.59394.113569.682706@gargle.gargle.HOWL>


>>>>> "MJ" == Matthias Juchem <lists@konfido.de> writes:

    MJ> I'm wondering how I should submit a patch.

    MJ> There is a patch manager on sf.net, but apparently without
    MJ> possibily to add a patch, at least for people who are not
    MJ> registered for the project.

    MJ> So is sending them to mailman-developers@python.org the best
    MJ> way?

It's not a great way, because it will be way to easy for it to get
lost in my inbox.  This is doubly true for a new feature patch, since
I'll undoubtably defer it until after MM2.1 final.

You don't have to be registered for the Mailman project to post
patches, you just have to be a registered user on SF.  This is
essential because I may need to contact you with questions or
comments, and that's not possible with anonymous patches or bug
reports.

If registering with SF is too much of a burden, then the next best
thing is to get some existing mailman-developers member to submit your
patch for you.

-Barry

From barry@python.org  Mon Dec  2 05:26:42 2002
From: barry@python.org (Barry A. Warsaw)
Date: Mon, 2 Dec 2002 00:26:42 -0500
Subject: [Mailman-Developers] Uncaught bounce notification
References: <20021129215937.GE3803@merlins.org>
Message-ID: <15850.61202.318489.680461@gargle.gargle.HOWL>


>>>>> "MM" == Marc MERLIN <marc_news@merlins.org> writes:

    MM> So, unless I'm missing something, if you use VERP, you should
    MM> be able to process any bounce from a subscriber.

Right.

    MM> Is it desirable for mailman to pass on a VERP bounce coming
    MM> from a held message notification sent to a non subscriber?

No.

    MM> Would it make sense for mailman if it receives a bounce that
    MM> is obviously verped and that there is no such member, to just
    MM> drop it silently (maybe with a log entry)?

Yes.  Actually, in a patch I worked out over the weekend (and one of
many I hope to check in in the morning), I log and drop any recoginzed
bounce that yielded a non-member address.  That seems like the most
reasonable behavior.  The current forwarding was mostly for debugging
purposes, but I think it's just more annoying than useful.

-Barry

From barry@python.org  Mon Dec  2 05:40:29 2002
From: barry@python.org (Barry A. Warsaw)
Date: Mon, 2 Dec 2002 00:40:29 -0500
Subject: [Mailman-Developers] [ mailman-Patches-644129 ] Edit held message
	header/body 
References: <E18H2na-0005hA-00@sc8-sf-web3.sourceforge.net>
	<18729.1038704148@kanga.nu>
Message-ID: <15850.62029.574001.554932@gargle.gargle.HOWL>


>>>>> "JCL" == J C Lawrence <claw@kanga.nu> writes:

    JCL> Given the age of the patch (it goes all the way back to the
    JCL> 1.x days), is this really such an unknown quantity that it
    JCL> has to shoved out to post 2.1?

If there's any hope of getting 2.1 out by the end of the year, yes.
It sucks, but such is life.  The schedule will be tight as it is.

-Barry

From barry@python.org  Mon Dec  2 05:42:27 2002
From: barry@python.org (Barry A. Warsaw)
Date: Mon, 2 Dec 2002 00:42:27 -0500
Subject: [Mailman-Developers] [ mailman-Patches-644129 ] Edit held message
	header/body 
References: <E18H2na-0005hA-00@sc8-sf-web3.sourceforge.net>
	<18729.1038704148@kanga.nu>
	<18803.1038704348@kanga.nu>
Message-ID: <15850.62147.931172.750128@gargle.gargle.HOWL>


>>>>> "JCL" == J C Lawrence <claw@kanga.nu> writes:

    >> Given the age of the patch (it goes all the way back to the 1.x
    >> days), is this really such an unknown quantity that it has to
    >> shoved out to post 2.1?

    JCL> Just saw the proposed schedule.  Please ignore this.

Oops, just saw this.  Please excuse my snippy late-night-catching-up-on-email
-after-a-long-drive-on-a-busted-up-knee remark. ;)

-Barry

From noreply@sourceforge.net  Mon Dec  2 11:27:41 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 03:27:41 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-646884 ] HyperArch.py multibyte charset
Message-ID: <E18Iojl-0000Gp-00@sc8-sf-web2.sourceforge.net>

Patches item #646884, was opened at 2002-12-02 11:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646884&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: HyperArch.py multibyte charset

Initial Comment:
HyperArch.py in 2.1b5 use Utils.uquote() for
CGIescape() and html_quote() but it does not take
language argument. This  is no good for multilbyte
charset because characters are escaped in separate 8bit
bytes which results in mojibake.
We should rather use Utils.uncanonstr() to honor the
legal characters within the multibyte charset.
This patch fixes other minor bugs in the current code.


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

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

From noreply@sourceforge.net  Mon Dec  2 13:58:58 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 05:58:58 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-637494 ] typo in README.SENDMAIL (CVS 2.4)
Message-ID: <E18Ir6A-0005dJ-00@sc8-sf-web2.sourceforge.net>

Bugs item #637494, was opened at 2002-11-12 19:49
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637494&group_id=103

Category: documentation
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Matthias Andree (m-a)
Assigned to: Nobody/Anonymous (nobody)
Summary: typo in README.SENDMAIL (CVS 2.4)

Initial Comment:
The README.SENDMAIL section on INTEGRATION has a typo:

...such that Sendmail will automatically recognize and
delivery

I presume it must be without the "y" in "delivery".

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-02 08:58

Message:
Logged In: YES 
user_id=12800

Fixed thanks.

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

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

From noreply@sourceforge.net  Mon Dec  2 16:03:17 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:03:17 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-644294 ] Uncaught runner
	exception
Message-ID: <E18It2T-00034F-00@sc8-sf-web2.sourceforge.net>

Bugs item #644294, was opened at 2002-11-26 14:22
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Terry Grace (tgrace)
Assigned to: Nobody/Anonymous (nobody)
Summary: Uncaught runner exception

Initial Comment:
Getting these repeatedly:

Nov 26 14:17:11 2002 (327) Uncaught runner exception: 
Article instance has no attribute '_mlist'
Nov 26 14:17:11 2002 (327) Traceback (most recent call 
last):
  File "/opt/mailman/Mailman/Queue/Runner.py", line 
105, in _oneloop
    self._onefile(msg, msgdata)
  File "/opt/mailman/Mailman/Queue/Runner.py", line 
154, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "/opt/mailman/Mailman/Queue/ArchRunner.py", 
line 73, in _dispose
    mlist.ArchiveMail(msg)
  File "/opt/mailman/Mailman/Archiver/Archiver.py", line 
207, in ArchiveMail
    h.close()
  File "/opt/mailman/Mailman/Archiver/pipermail.py", line 
303, in close
    self.update_dirty_archives()
  File "/opt/mailman/Mailman/Archiver/pipermail.py", line 
517, in update_dirty_archives
    self.update_archive(i)
  File "/opt/mailman/Mailman/Archiver/HyperArch.py", 
line 1058, in update_archive
    self.__super_update_archive(archive)
  File "/opt/mailman/Mailman/Archiver/pipermail.py", line 
425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/opt/mailman/Mailman/Archiver/pipermail.py", line 
485, in _update_thread_index
    self.update_article(arcdir, a1, L[0], L[2])
  File "/opt/mailman/Mailman/Archiver/HyperArch.py", 
line 1223, in update_article
    f.write(article.as_html())
  File "/opt/mailman/Mailman/Archiver/HyperArch.py", 
line 407, in as_html
    d['listurl'] = self._mlist.GetScriptURL('listinfo', 
absolute=1)
AttributeError: Article instance has no attribute '_mlist'


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

Comment By: Terry Grace (tgrace)
Date: 2002-11-26 20:40

Message:
Logged In: YES 
user_id=87771

Archives broken too. After restarting the deamons, only the 
first article posted gets archived.

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

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

From noreply@sourceforge.net  Mon Dec  2 16:04:19 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:04:19 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-635542 ] Uncaught
	MMNoSuchUserError
Message-ID: <E18It3T-00037q-00@sc8-sf-web2.sourceforge.net>

Bugs item #635542, was opened at 2002-11-08 10:38
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_id=103

Category: (un)subscribing
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Stonewall Ballard (stoneyb)
Assigned to: Nobody/Anonymous (nobody)
Summary: Uncaught MMNoSuchUserError

Initial Comment:
I found an unsubscribe confirmation message in the
shunt directory. The error log suggests that someone
used both the web and the reply to unsubscribe, but
when the email confirmation arrived, he was already
gone and qrunner faulted.

I'm running a CVS build about a week old.

Here's the traceback:

Nov 08 05:29:33 2002 (23820) Uncaught runner exception: 
Nov 08 05:29:33 2002 (23820) 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 154, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File
"/usr/local/mailman/Mailman/Queue/CommandRunner.py",
line 199, in _dispose
    res.process()
  File
"/usr/local/mailman/Mailman/Queue/CommandRunner.py",
line 93, in process
    stop = self.do_command(cmd, args)
  File
"/usr/local/mailman/Mailman/Queue/CommandRunner.py",
line 117, in do_command
    return self.do_command(cmd, args)
  File
"/usr/local/mailman/Mailman/Queue/CommandRunner.py",
line 119, in do_command
    return handler.process(self, args)
  File
"/usr/local/mailman/Mailman/Commands/cmd_confirm.py",
line 44, in process
    results = mlist.ProcessConfirmation(cookie, res.msg)
  File "/usr/local/mailman/Mailman/MailList.py", line
1107, in ProcessConfirmation
    self.ApprovedDeleteMember(addr, whence=whence)
  File "/usr/local/mailman/Mailman/MailList.py", line
936, in ApprovedDeleteMember
    raise Errors.MMNoSuchUserError
MMNoSuchUserError


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

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

From noreply@sourceforge.net  Mon Dec  2 16:06:02 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:06:02 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-643547 ] Update portuguese translation
Message-ID: <E18It58-0003Fb-00@sc8-sf-web2.sourceforge.net>

Patches item #643547, was opened at 2002-11-25 08:37
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643547&group_id=103

Category: internationalization
Group: Mailman 2.1
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Christian Reis (kiko_async)
Assigned to: Nobody/Anonymous (nobody)
Summary: Update portuguese translation

Initial Comment:
I've done a quick lookover the portuguese translation
and I have a number of small fixes and unfuzzys to be
added. This fixes mostly the listinfo page, which is
the page my users actually hit the most, and there are
some other assorted fixes (typos non-existant words etc).

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

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

From noreply@sourceforge.net  Mon Dec  2 16:06:26 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:06:26 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-643556 ] Update to portuguese listinfo template
Message-ID: <E18It5W-0003HL-00@sc8-sf-web2.sourceforge.net>

Patches item #643556, was opened at 2002-11-25 08:43
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643556&group_id=103

Category: internationalization
Group: Mailman 2.1
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Christian Reis (kiko_async)
Assigned to: Nobody/Anonymous (nobody)
Summary: Update to portuguese listinfo template

Initial Comment:
This is the second half of the quick fixups I've done
to the pt_BR translation. I've only hacked the listinfo
template so far because it's the only thing that's been
really bothering me.

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

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

From noreply@sourceforge.net  Mon Dec  2 16:07:25 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:07:25 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-646989 ] NAH6 Secure List patch: GPG plugin
Message-ID: <E18It6T-0006Hj-00@sc8-sf-web3.sourceforge.net>

Patches item #646989, was opened at 2002-12-02 11:07
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646989&group_id=103

Category: list administration
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Rop Gonggrijp (rop)
Assigned to: Nobody/Anonymous (nobody)
Summary: NAH6 Secure List patch: GPG plugin

Initial Comment:
"NAH6 Secure List" is a patch for Mailman 2.1b5 that 
adds GPG functionality. It is built around a key-scheme 
that allows an admin to create an encrypted list for 
which even the server operator doesn't have access to 
the messages.

Only the public key for the list is given to the server, so 
it can perform 'emergency encryption' in case someone 
forgets, and all users get the public and private key for 
the list.


We think we've done a decent job of describing the new 
functionality from server-operator, list-admin and list-
member points of view. There's also a technical 
document for those familiar with the Mailman code. 
Please have a look at:

http://www.nah6.com/products/secure-list/

and follow the links from there


We feel more people need this, and we'd really like it to 
be part of the Mailman distribution at some point...


Kind Regards,

Rop Gonggrijp
Joshua Eichen


Please forgive mangling the Mailman logo on the site: if 
y'all don't like it or think it's over the top we'll use 
something else....

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

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

From noreply@sourceforge.net  Mon Dec  2 16:07:29 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:07:29 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-637410 ] autorespond_requests &quot;w/discard&quot; ignored
Message-ID: <E18It6X-0003Jo-00@sc8-sf-web2.sourceforge.net>

Bugs item #637410, was opened at 2002-11-12 16:58
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637410&group_id=103

Category: mail delivery
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Donn Cave (donnc)
Assigned to: Nobody/Anonymous (nobody)
Summary: autorespond_requests &quot;w/discard&quot; ignored

Initial Comment:
Gui/Autoresponse.py makes a distinction between 
autorespond_requests == 1 or == 2, but that's implemented in 
the MailCommandHandler.py module, which is unreferenced in b3 
and gone in b4.  CommandRunner._dispose could check for this 
after it calls Replybot.process(), I think.  Or if the feature 
was intentionally left out, it could be left out of the web 
interface too.

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

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

From noreply@sourceforge.net  Mon Dec  2 16:07:51 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:07:51 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-621597 ] list creation ignores DEFAULT_EMAIL_HOST
Message-ID: <E18It6t-0003KO-00@sc8-sf-web2.sourceforge.net>

Bugs item #621597, was opened at 2002-10-10 18:06
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621597&group_id=103

Category: None
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: list creation ignores DEFAULT_EMAIL_HOST

Initial Comment:
If I set DEFAULT_EMAIL_HOST in mm_cfg.py, its value is 
ignored when creating a new list.  It's pretty easy to see 
why: MailList.InitVars uses DEFAULT_HOST_NAME.  But 
the two are only equal as long as mm_cfg.py is not used.

If DEFAULT_HOST_NAME and DEFAULT_EMAIL_HOST 
are really supposed to be the same, perhaps 
DEFAULT_HOST_NAME should not be set in Defaults.py -- 
rather, any code that looks at DEFAULT_EMAIL_HOST 
should check to see if DEFAULT_HOST_NAME happens to 
be defined in mm_cfg, and use it if so.  Or something like 
that.

I'm happy to supply a patch if someone agrees that this is a 
bug.

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

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

From noreply@sourceforge.net  Mon Dec  2 16:08:26 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:08:26 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-644773 ] &quot;description&quot; doesn't get encoded
Message-ID: <E18It7S-0003Lb-00@sc8-sf-web2.sourceforge.net>

Bugs item #644773, was opened at 2002-11-27 10:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644773&group_id=103

Category: None
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Sven Anderson (tuttle)
Assigned to: Nobody/Anonymous (nobody)
Summary: &quot;description&quot; doesn't get encoded

Initial Comment:
Mailman 2.1b5

The "description" option is being used for both the web-
pages and the Reply-To: header.

If there are non-ASCII characters in it, it won't be 
encoded, so that there are unencoded non-ASCII 
characters in the mail header.



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

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

From noreply@sourceforge.net  Mon Dec  2 16:09:35 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:09:35 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-540978 ] List-* header multiline split bug
Message-ID: <E18It8Z-0003Oq-00@sc8-sf-web2.sourceforge.net>

Bugs item #540978, was opened at 2002-04-08 08:56
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=540978&group_id=103

Category: mail delivery
Group: 2.1 beta
>Status: Closed
>Resolution: Out of Date
Priority: 7
Submitted By: Markus Mandalka (mandalka)
Assigned to: Nobody/Anonymous (nobody)
Summary: List-* header multiline split bug

Initial Comment:
I have a list 
antiatomforum@lists.kommunikationssystem.de and others 
with long names.

It seems that mailman can not handle with such long 
names, because in the subscribe-mail (which you have 
to answer to be in the list) the first columns are 
some things from the header (unsubscribe: 
xxx@lists.xxx and so on).

Whith names like atest@lists.kommunikationssystem.de 
it works.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-23 17:38

Message:
Logged In: YES 
user_id=12800

Changing the summary

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

Comment By: Nobody/Anonymous (nobody)
Date: 2002-08-15 00:37

Message:
Logged In: NO 

I just installed mailman and can confirm this bug as well.  
When the list address + hostname is too long (in my case 
the listname was north-texas-stovebolters-
club@stovebolt.stovebolt.com -- 52 characters total) the 
headers overflow into the body of the message.  The "break 
point" was at the List Subscribe line:
*******************
This is header:

List-Subscribe: 
<http://stovebolt.stovebolt.com/mailman/listinfo/north-
texas-stovebolters-club>,
(total of 94 characters before the split)
*******************
This is body

	<mailto:north-texas-stovebolters-club-
request@stovebolt.stovebolt.com?subject=subscribe>
List-Unsubscribe: 
<http://stovebolt.stovebolt.com/mailman/listinfo/north-
texas-stovebolters-club>,

	<mailto:north-texas-stovebolters-club-
request@stovebolt.stovebolt.com?subject=unsubscribe>
List-Archive: 
<http://stovebolt.stovebolt.com/pipermail/north-texas-
stovebolters-club>
List-Help: <mailto:north-texas-stovebolters-club-
request@stovebolt.stovebolt.com?subject=help>
Sender: north-texas-stovebolters-club-
bounces@stovebolt.stovebolt.com
Errors-To: north-texas-stovebolters-club-
bounces@stovebolt.stovebolt.com
************************
This is the initial text of the message that was posted.

I'm sure that I'll be there. :-)

****************************
It looks like there's a line break or line limit that's causing 
the problem.  Perhaps it's line 33:
MAXLINELEN = 78

The first line that breaks (in my case) is a line that has 94 
characters in the first part, none of which can be separated 
(no spaces or line breaks, just continuous text.)

The very next line drops to the body.

I believe giuans is correct that the problem is in the wrap 
section of the code, because the break occurs immediately 
after a comma, which, if I'm understanding the code 
correctly, is inserted by the program after an overlength 
line occurs, to split the line at 78 (or as close to that as it 
can get.)

I think the correct fix would be to add the "h" portion 
subsequent to the split so that each line in the header 
would have the required semi-colon to indicate that it's 
header.  If the MTA sees a line with no semicolon, it's going 
to think that it's body text, not header.

*****************
Present code:
if len(h) + 2 + len(v) > 78:
            v = CONTINUATION.join(v.split(', '))
        msg[h] = v

******************
Possible fix
if len(h) + 2 + len(v) > 78:
            v=CONTINUATION.join(h + v.split(','))
        msg[h] = v

or something like that.  (I haven't worked with php, so I'm 
not familiar with its functions and syntax.)  The idea is to 
split a line like this:

Line exceeds 78 characters?
h+v,
h+ rest of v

HTH.

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

Comment By: Jean Millerat (drsigmund)
Date: 2002-07-04 04:13

Message:
Logged In: YES 
user_id=70686

I have reached the same bug with mailing list adresses such as
<11 characters>@<30 characters> whereas <8 characters>@<30
characters> works properly. The effect of this bug is that
the headers of the subcription annoucement or any further
email from the list are "mangled" as was said on
[mailman-developers]. As an example when one of the List-*
header line is too long, it is broken in two parts (and the
second part is indented). Since then, Outlook (and I suppose
other email clients) think this second part of the broken
header line is the beginning of the body of the message.
Therefore the remaining headers are sent as part of the body
of the message !

I think this bug does not only occur with too long email
adresses but may occur with too long header lines whichever
line it is (even with the Subject line especially when this
subject line is very long because of quoted-printable
characters). See [mailman-developers] for the description of
maybe the same bug, in mails dealing with headers being
"mangled".

My current workarounds :
- using short mailing list names.
- and not sending quoted-printable characters within subject
lines.

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

Comment By: Giovanni Lopedote (giuans)
Date: 2002-05-02 10:27

Message:
Logged In: YES 
user_id=531451

I've found it. A fast fix for is to comment lines 149-150 
in Mailman/Handlers:/CookHeaders.py:

--- CookHeaders.py      2002-05-02 14:51:36.000000000 +0200
+++ CookHeaders.py.new  2002-05-02 16:12:09.000000000 +0200
@@ -146,8 +146,8 @@
         # Wrap these lines if they are too long.  78 
character width probably
         # shouldn't be hardcoded, but is at least 
text-MUA friendly.  The
         # adding of 2 is for the colon-space separator.
-        if len(h) + 2 + len(v) > 78:
-            v = CONTINUATION.join(v.split(', '))
+#        if len(h) + 2 + len(v) > 78:
+#            v = CONTINUATION.join(v.split(', '))
         msg[h] = v
     # Always delete List-Archive header, but only add it 
back if the list is
     # actually archiving

Tested with Mailman 2.1b1, Source Mage GNU/Linux 2.4.18, 
Postfix 1.1.7.
I know there should be a better way, but I'm not a Python 
programmer at all. :)


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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-04-11 18:03

Message:
Logged In: YES 
user_id=12800

I've confirmed this bug, but don't have a fix for it right now.

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

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

From noreply@sourceforge.net  Mon Dec  2 16:11:20 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:11:20 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-642996 ] can't send Plain Digest w/multipart msg.
Message-ID: <E18ItAG-0003TS-00@sc8-sf-web2.sourceforge.net>

Bugs item #642996, was opened at 2002-11-24 02:42
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642996&group_id=103

Category: mail delivery
Group: 2.1 beta
Status: Open
>Resolution: Works For Me
Priority: 7
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: can't send Plain Digest w/multipart msg.

Initial Comment:
cron/senddigests and cgi-bin/admin/digest
can't send plain digest when multipart
message(s) are contained.

Note: Attached file will solve this
problem for only cron/senddigests, but
not for cgi.


Traceback:

admin(17454):
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
admin(17454): [----- Mailman Version: 2.1b5 -----]
admin(17454): [----- Traceback ------]
admin(17454): Traceback (most recent call last):
admin(17454):   File
"/usr/local/mail/mailman/scripts/driver", line 87, in
run_main
admin(17454):     main()
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Cgi/admin.py", line
169, in main
admin(17454):     change_options(mlist, category,
subcat, cgidata, doc)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Cgi/admin.py", line
1229, in change_options
admin(17454):     gui.handleForm(mlist, category,
subcat, cgidata, doc)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Gui/GUIBase.py", line
169, in handleForm
admin(17454):     self._setValue(mlist, property, val,
doc)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Gui/Digest.py", line
148, in _setValue
admin(17454):     status = mlist.send_digest_now()
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Digester.py", line 60,
in send_digest_now
admin(17454):     ToDigest.send_digests(self, mboxfp)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py",
line 130, in send_digests
admin(17454):     send_i18n_digests(mlist, mboxfp)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py",
line 301, in send_i18n_digests
admin(17454):     g(msg, unixfrom=0)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 100, in flatten
admin(17454):     self._write(msg)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 128, in _write
admin(17454):     self._dispatch(msg)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 154, in _dispatch
admin(17454):     meth(msg)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 212, in _handle_text
admin(17454):     raise TypeError, 'string payload
expected: %s' % type(payload)
admin(17454): TypeError: string payload expected: <type
'list'>


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-02 11:11

Message:
Logged In: YES 
user_id=12800

I tried some examples but couldn't get this to reproduce. 
Can you send me an example message which, when sent through
the plain text digest, causes it to barf like this?  IOW,
can you upload a reproducible test case?

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

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

From noreply@sourceforge.net  Mon Dec  2 16:14:00 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:14:00 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-229568 ] Pipermail won't resolve author names of
 aol.com addresses
Message-ID: <E18ItCq-0003ZW-00@sc8-sf-web2.sourceforge.net>

Bugs item #229568, was opened at 2001-01-20 22:53
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Closed
>Resolution: Out of Date
Priority: 7
Submitted By: Aharon Varady (aharon)
Assigned to: Nobody/Anonymous (nobody)
Summary: Pipermail won't resolve author names of aol.com addresses

Initial Comment:
Pipermail does not resolve the "author" of emails sent from aol.com. Instead, Pipermail gives the email address of the listserve.

For example: "John" <user@aol.com>
is resolved by pipermail as:  listname@foo.com
and not as John.

This bug only occurs for users of aol.com addresses.

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

Comment By: Terri Oda (spot)
Date: 2002-07-02 16:00

Message:
Logged In: YES 
user_id=110886

Whoops.  Diffed the wrong thing.  That's what happens when I 
try to patch code but haven't slept in a few days.  This 
actually works better:

180c180
<       if e is not None:
---
>       if e is not None and self.email == "":


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

Comment By: Terri Oda (spot)
Date: 2002-07-01 14:03

Message:
Logged In: YES 
user_id=110886

The problem is that it defaults to using the reply-to address if 
it's set, and this isn't what we want when the reply-to is 
always being set by the list.   

Take a careful look at the rest of your archives and you'll 
probably note that *everyone's* email address is showing up 
as listname@foo.com.  It's a nice anti-spam feature, perhaps, 
but probably not what you want. 

Here's a quick fix for pipermail.py:

180c180
<       if e is not None:
---
>       if e is not None and self.email is None:

This just changes it so that it defaults to the From: address 
(when it's set) rather than the Reply-to address.  

If there's some particular reason to take the Reply-To over the 
From, I can make something which actually checks to see if 
the reply-to is being set by the list, but this should solve your 
problem for the moment.

 Terri


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

Comment By: Ava Jarvis (katanalynx)
Date: 2002-06-10 22:14

Message:
Logged In: YES 
user_id=561110

This bug -- for version 2.0.11 at least -- seems to occur
when 'from' only contains the email address. 

There's some code in pipermail.py (version 2.0.11), line 177: 

<excerpt>
        # Figure out the e-mail address and poster's name
        self.author, self.email = message.getaddr('From')
        e = message.getheader('Reply-To')
        if e is not None:
            self.email = e
        self.email = strip_separators(self.email)
        self.author = strip_separators(self.author)

        if self.author == "":
            self.author = self.email
</excerpt>

If reply-to is set, then it is always taken as the author's
email address.  However, some lists set the reply-to field
to be, for instance, the list address.... and you can guess
what happens 
next when there is no name comment/author.



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

Comment By: Nobody/Anonymous (nobody)
Date: 2002-06-06 12:09

Message:
Logged In: NO 

This comment doesn't directly address the case you report,
but it might be related so I thought it worthwhile to submit.

I see you are using MM2.0.9.
I saw a similar problem with MM2.1b1, which was fixed in
MM2.1b2.
The problem then was that an address with a name "comment"
would be displayed in the archive as the list name, whereas
an address with a name comment would be displayed (properly)
with the name.  Example:

"John Doe" jdoe@whereever.com   displayed as "John Doe"
whereas
jdoe@whereever.com  displayed as the list name.

In your comment, you use an example with a name comment of
"John", but
in the example you provided there is no name comment field,
so perhaps my statements here do apply.

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

Comment By: Aharon Varady (aharon)
Date: 2002-06-05 21:37

Message:
Logged In: YES 
user_id=139355

Well, this remains (and has always been) a problem for my
lists. I have never had a user posting with an aol.com
address that this hasn't been the case with. 

Currently my solution is to replace the wrong address shown
(philly_ambient@phobos.serve.com) with a generic or balnk mark.

Here is the html source of a typical email from our
pipermail archive, and below it the source email with headers.

-------------------------------------------------------------
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
 <head>
   <title> [Philly_ambient] tool!
   </title>
   <link REL="Index" HREF="index.html" >
   <link REL="made"
HREF="mailto:philly_ambient%40phobos.serve.com">
   <meta NAME="robots" CONTENT="index,nofollow">
   
   <link REL="Previous" 
href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/002904.html">
   <link REL="Next" 
href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/002911.html">

 <style TYPE="text/css"><!-- A:link {text-decoration:none}
A:visited {text-decoration:none} --></style></head>
 <body BGCOLOR="#cccccc"><font face="Arial,Helvetica"
size=-1><ul>
   <h4>[Philly_ambient] tool!</h4>Posted by <b>.   .  . .. .
 .   .</b> on <i>Mon Jun  3 23:17:02 2002</i>
    <p></font><table cellpadding=3><tr><td bgcolor=#FFFFFF
width="475"><font face="geneva,courier"><tt> 
<!--beginarticle-->
<pre>hey all
a friend can get me some free tickets to see TOOL on monday
august 12 at 
sovereign bank arena in trenton. i know mondays suck, but oh
well. is anyone 
here into going?  if so, contact me privately.  i know it's
not ambient, but 
neither is some of what we discuss here :)
let me know asap, please

gina


</pre>
<!--endarticle-->
    </tt></font></td></tr></table><font
face="Arial,Helvetica" size=-1>
     <p>
        <!--threads--><!-- robots content="noindex" -->
        <li> Previous message: <a
href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/002904.html">[Philly_ambient]
Noise Deafinitions and playlist
</a></li>
        <li> Next message: <a
href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/002911.html">[Philly_ambient]
Do you hear what I hear? (re: noise deaf)

</a></li>
         <li> <b>Messages sorted by:</b>
              <a
href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/date.html#2907">[
date ]</a>
              <a
href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/thread.html#2907">[
thread ]</a>
              <a
href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/subject.html#2907">[
subject ]</a>
              <a
href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/author.html#2907">[
author ]</a>

         </li><!-- /robots --> 
</body></html>
---------------------------------------------------------------------

Here is the original email with headers:

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

>From - Tue Jun 04 01:16:56 2002
X-UIDL: m;n!!9'f!!a2E"!3;D"!
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Return-Path: <philly_ambient-admin@phobos.serve.com>
Delivered-To: aharon@phobos.serve.com
Received: from phobos.serve.com (localhost.localdomain
[127.0.0.1])
	by phobos.serve.com (Postfix) with ESMTP
	id 6BC4D52D2B; Mon,  3 Jun 2002 23:17:06 -0400 (EDT)
Delivered-To: philly_ambient@phobos.serve.com
Received: from imo-r06.mx.aol.com (imo-r06.mx.aol.com
[152.163.225.102])
	by phobos.serve.com (Postfix) with ESMTP id 6F82F52D1D
	for <philly_ambient@phobos.serve.com>; Mon,  3 Jun 2002
23:16:46 -0400 (EDT)
Received: from Mistsojorn@aol.com
	by imo-r06.mx.aol.com (mail_out_v32.5.) id p.d4.184e63f9 (17378)
	 for <philly_ambient@phobos.serve.com>; Mon, 3 Jun 2002
23:14:35 -0400 (EDT)
From: Mistsojorn@aol.com
Message-ID: <d4.184e63f9.2a2d8a9b@aol.com>
To: philly_ambient@phobos.serve.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 4.0 for Mac - Post-GM sub 66
Subject: [Philly_ambient] tool!
Sender: philly_ambient-admin@phobos.serve.com
Errors-To: philly_ambient-admin@phobos.serve.com
X-BeenThere: philly_ambient@phobos.serve.com
X-Mailman-Version: 2.0.9
Precedence: bulk
Reply-To: philly_ambient@phobos.serve.com
List-Help:
<mailto:philly_ambient-request@phobos.serve.com?subject=help>
List-Post: <mailto:philly_ambient@phobos.serve.com>
List-Subscribe:
<http://phobos.serve.com/mailman/listinfo/philly_ambient>,
	<mailto:philly_ambient-request@phobos.serve.com?subject=subscribe>
List-Id: a discussion list relevant to Philadelphia Ambient
and Experimental Psychedelic Music Enthusiasts
<philly_ambient.phobos.serve.com>
List-Unsubscribe:
<http://phobos.serve.com/mailman/listinfo/philly_ambient>,
	<mailto:philly_ambient-request@phobos.serve.com?subject=unsubscribe>
List-Archive:
<http://phobos.serve.com/pipermail/philly_ambient/>
X-Original-Date: Mon, 3 Jun 2002 23:14:35 EDT
Date: Mon, 3 Jun 2002 23:14:35 EDT
X-UIDL: m;n!!9'f!!a2E"!3;D"!

hey all
a friend can get me some free tickets to see TOOL on monday
august 12 at 
sovereign bank arena in trenton. i know mondays suck, but oh
well. is anyone 
here into going?  if so, contact me privately.  i know it's
not ambient, but 
neither is some of what we discuss here :)
let me know asap, please

gina
_______________________________________________
Philly_ambient mailing list
Philly_ambient@phobos.serve.com
Subscribe, Unsubscribe, Edit Options at:
http://phobos.serve.com/mailman/listinfo/philly_ambient

a PAC(MaN) List
http://simpletone.com

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


I don't know why pipermail would treat my aol subscribers
different either. But it is.

Aharon



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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-04-28 21:11

Message:
Logged In: YES 
user_id=12800

Bizarre.  I've never seen this, and I can't see any reason
why Pipermail would treat aol.com addresses any different.

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

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

From noreply@sourceforge.net  Mon Dec  2 16:15:35 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:15:35 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-644005 ] sync_members: problems with u umlaut
Message-ID: <E18ItEN-0003dd-00@sc8-sf-web2.sourceforge.net>

Bugs item #644005, was opened at 2002-11-26 04:57
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644005&group_id=103

Category: command line scripts
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Matthias Klose (doko)
Assigned to: Nobody/Anonymous (nobody)
Summary: sync_members: problems with u umlaut

Initial Comment:
Running sync_members -n,

I get this error, when a member with an umlaut-u in
it's real name gets removed.

Traceback (most recent call last):
  File "/usr/sbin/sync_members", line 283, in ?
    main()
  File "/usr/sbin/sync_members", line 275, in main
    print _('Removed: <%(addr)30s> %(name)s')
UnicodeError: ASCII encoding error: ordinal not in
range(128)

Changing the ü in the web-frontend to ue, and then
running again sync_members "fixes" the problem.


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-02 11:15

Message:
Logged In: YES 
user_id=12800

The same problem affects list_members.  I think I've fixed
them both by coercing the unicode text to a byte string in
the default encoding.  That's about the only way to know
what encoding is going to be used by stdout, AFAICT. 

Please check and if this isn't sufficient, we'll have to
think of something else.

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

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

From noreply@sourceforge.net  Mon Dec  2 16:12:25 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:12:25 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color
Message-ID: <E18ItBJ-0003Vl-00@sc8-sf-web2.sourceforge.net>

Bugs item #635462, was opened at 2002-11-08 07:13
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103

Category: Web/CGI
Group: 2.1 beta
Status: Open
>Resolution: Wont Fix
>Priority: 4
Submitted By: Marcin Orlowski (carl-os)
Assigned to: Nobody/Anonymous (nobody)
Summary: Admin pages HTML does not set TEXT color

Initial Comment:
Mailman admin pages believe that TEXT color is always
black and does not set it to, hoping nobody changes the
defaults. And this is false assumption ;-) For testing
purposes my defaults are black bg color and yellow
text. And since admin pages sets bg to white it now
exposes yellow fonts on white background here. Kinda
unreadable. Solution -> fix template/css/whatever to
set up text color to black.

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-02 11:12

Message:
Logged In: YES 
user_id=12800

There's no official css support yet.  I won't fix this for
MM2.1 unless someone can provide a really clean patch.

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

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

From noreply@sourceforge.net  Mon Dec  2 16:12:46 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:12:46 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-642996 ] can't send Plain Digest w/multipart msg.
Message-ID: <E18ItBe-0003WK-00@sc8-sf-web2.sourceforge.net>

Bugs item #642996, was opened at 2002-11-24 02:42
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642996&group_id=103

Category: mail delivery
Group: 2.1 beta
Status: Open
Resolution: Works For Me
>Priority: 4
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: can't send Plain Digest w/multipart msg.

Initial Comment:
cron/senddigests and cgi-bin/admin/digest
can't send plain digest when multipart
message(s) are contained.

Note: Attached file will solve this
problem for only cron/senddigests, but
not for cgi.


Traceback:

admin(17454):
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
admin(17454): [----- Mailman Version: 2.1b5 -----]
admin(17454): [----- Traceback ------]
admin(17454): Traceback (most recent call last):
admin(17454):   File
"/usr/local/mail/mailman/scripts/driver", line 87, in
run_main
admin(17454):     main()
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Cgi/admin.py", line
169, in main
admin(17454):     change_options(mlist, category,
subcat, cgidata, doc)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Cgi/admin.py", line
1229, in change_options
admin(17454):     gui.handleForm(mlist, category,
subcat, cgidata, doc)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Gui/GUIBase.py", line
169, in handleForm
admin(17454):     self._setValue(mlist, property, val,
doc)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Gui/Digest.py", line
148, in _setValue
admin(17454):     status = mlist.send_digest_now()
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Digester.py", line 60,
in send_digest_now
admin(17454):     ToDigest.send_digests(self, mboxfp)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py",
line 130, in send_digests
admin(17454):     send_i18n_digests(mlist, mboxfp)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py",
line 301, in send_i18n_digests
admin(17454):     g(msg, unixfrom=0)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 100, in flatten
admin(17454):     self._write(msg)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 128, in _write
admin(17454):     self._dispatch(msg)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 154, in _dispatch
admin(17454):     meth(msg)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 212, in _handle_text
admin(17454):     raise TypeError, 'string payload
expected: %s' % type(payload)
admin(17454): TypeError: string payload expected: <type
'list'>


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

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

Message:
Logged In: YES 
user_id=12800

I tried some examples but couldn't get this to reproduce. 
Can you send me an example message which, when sent through
the plain text digest, causes it to barf like this?  IOW,
can you upload a reproducible test case?

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

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

From noreply@sourceforge.net  Mon Dec  2 16:23:59 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:23:59 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-640374 ] 2.1b4 Mailman bug
Message-ID: <E18ItMV-00040P-00@sc8-sf-web1.sourceforge.net>

Bugs item #640374, was opened at 2002-11-18 17:57
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640374&group_id=103

Category: Web/CGI
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Paul Marshall (paulmarshll)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.1b4 Mailman bug

Initial Comment:
When I try to access some of my lists via the web 
interface to moderate them I receive this error message:

Traceback (most recent call last):
  File "/var/mailman/scripts/driver", line 87, in run_main
    main()
  File "/var/mailman/Mailman/Cgi/admindb.py", line 227, 
in main
    show_pending_unsubs(mlist, form)
  File "/var/mailman/Mailman/Cgi/admindb.py", line 332, 
in show_pending_unsubs
    fullname = Utils.uncanonstr(mlist.getMemberName
(addr), lang)
  File "/var/mailman/Mailman/OldStyleMemberships.py", 
line 128, in getMemberName
    self.__assertIsMember(member)
  File "/var/mailman/Mailman/OldStyleMemberships.py", 
line 113, in __assertIsMember
    raise Errors.NotAMemberError, member
NotAMemberError: capeterson28@hotmail.com

This is only a problem for some of my lists.  Some lists I 
can log into and moderate successfully from the Web.

I am running Mailman 2.1b4 on RedHat Linux 7.3.

Let me know if you need more information.
Thanks for your help.

Paul Marshall

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

Comment By: Paul Marshall (paulmarshll)
Date: 2002-11-19 14:27

Message:
Logged In: YES 
user_id=582441

I recently upgraded to Mailman 2.1b5, however I still receive 
this error when I try to log into some of the lists.

Thanks. Paul.

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

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

From noreply@sourceforge.net  Mon Dec  2 16:24:33 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:24:33 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-612174 ] subscribe_policy + ALLOW_OPEN_SUBSCRIBE
Message-ID: <E18ItN3-00043K-00@sc8-sf-web1.sourceforge.net>

Bugs item #612174, was opened at 2002-09-20 11:42
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612174&group_id=103

Category: command line scripts
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Jay Luker (lbjay)
Assigned to: Nobody/Anonymous (nobody)
Summary: subscribe_policy + ALLOW_OPEN_SUBSCRIBE

Initial Comment:
There is a flaw somewhere in the logic that alters the 
value of subscribe_policy based on the value of 
mm_cfg.ALLOW_OPEN_SUBSCRIBE. 
 
I have ALLOW_OPEN_SUBSCRIBE = 0. When I attempt 
to set subscribe_policy = 1 via the config_list script, 
subscribe_policy is always set to 2. 

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

Comment By: Jay Luker (lbjay)
Date: 2002-09-20 12:02

Message:
Logged In: YES 
user_id=51347

OK, I was just able to track this down further. The problem (I 
think) lies in Gui/Privacy.py. _setValue states: 
 
"For subscribe_policy when ALLOW_OPEN_SUBSCRIBE is 
true, we need to add one to the value because the page didn't 
present an open list as an option." 
 
... but then the subsequent code actually adds one to the 
value if ALLOW_OPEN_SUBSCRIBE is untrue. 
 

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

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

From noreply@sourceforge.net  Mon Dec  2 16:26:08 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:26:08 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-610570 ] RFC 2369 URL is broken
Message-ID: <E18ItOa-00048Q-00@sc8-sf-web1.sourceforge.net>

Bugs item #610570, was opened at 2002-09-17 10:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610570&group_id=103

Category: documentation
Group: 2.1 beta
>Status: Closed
>Resolution: Out of Date
Priority: 7
Submitted By: Nick Arnett (narnett)
Assigned to: Nobody/Anonymous (nobody)
Summary: RFC 2369 URL is broken

Initial Comment:
Paths to RFCs have changed.  The correct one for 
2369 is now 
http://www.faqs.org/rfcs/rfc2369.html

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-02 11:26

Message:
Logged In: YES 
user_id=12800

I think this is out of date, since all references in 2.1b5+
cvs point to this location.   Or do you know of a place I'm
missing?

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

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

From noreply@sourceforge.net  Mon Dec  2 16:25:12 2002
From: noreply@sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 08:25:12 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-419992 ] bin/arch messed up existing web archive
Message-ID: <E18ItNg-00045q-00@sc8-sf-web1.sourceforge.net>

Bugs item #419992, was opened at 2001-04-29 14:24
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=419992&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Bernhard Reiter (ber)
Assigned to: Nobody/Anonymous (nobody)
Summary: bin/arch messed up existing web archive

Initial Comment:
When running arch and webpages still exists, the web
archive is messed up. This is quite confusing.
A warning should be printed if arch is started on a
list where there is already stuff in the web archive.
Optionally it could delete the files is is regenerating
first.

Details: arch seems to attach each mail again to the
.txt monthly archive files here and then build the
web archive out of this. No wonder that the mail I
deleted is still in after the process....

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

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

Message:
Logged In: YES 
user_id=12800

I (finally) fixed this by giving bin/arch a --wipe argument

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

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

From noreply at sourceforge.net  Mon Dec  2 18:38:57 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 10:38:57 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-647083 ] compress dies w/ MemoryError
Message-ID: <E18IvT7-0001lN-00@sc8-sf-web1.sourceforge.net>

Patches item #647083, was opened at 2002-12-02 10:38
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=647083&group_id=103

Category: command line scripts
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: John-Mark Gurney (jmg)
Assigned to: Nobody/Anonymous (nobody)
Summary: compress dies w/ MemoryError

Initial Comment:
If you have a large mailing list, it is very easy to
quickly exhast memory in many conditions.  nightly_gzip
script tries to load the entire file into memory before
compressing it, not only is this terribly ineffecient,
it also means you are limited to file sizes that can
fit in memory.  Some machines also further restrict how
much memory each process can access at a time.  If that
limit is 512megs, and you have a 400+meg file, compress
will die.

Solution:  read/write the file in blocks.

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

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

From noreply at sourceforge.net  Mon Dec  2 18:53:45 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 10:53:45 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-647083 ] compress dies w/ MemoryError
Message-ID: <E18IvhR-0002Sq-00@sc8-sf-web1.sourceforge.net>

Patches item #647083, was opened at 2002-12-02 13:38
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=647083&group_id=103

Category: command line scripts
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: John-Mark Gurney (jmg)
Assigned to: Nobody/Anonymous (nobody)
Summary: compress dies w/ MemoryError

Initial Comment:
If you have a large mailing list, it is very easy to
quickly exhast memory in many conditions.  nightly_gzip
script tries to load the entire file into memory before
compressing it, not only is this terribly ineffecient,
it also means you are limited to file sizes that can
fit in memory.  Some machines also further restrict how
much memory each process can access at a time.  If that
limit is 512megs, and you have a 400+meg file, compress
will die.

Solution:  read/write the file in blocks.

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

Comment By: Bryan Fullerton (fehwalker)
Date: 2002-12-02 13:53

Message:
Logged In: YES 
user_id=660772

would it make more sense to do this with zlib routines on a
stream than with gzip on blocks?


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

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

From noreply at sourceforge.net  Mon Dec  2 19:08:40 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 11:08:40 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-647102 ] MemoryError when generating indexes
Message-ID: <E18Ivvs-0005T8-00@sc8-sf-web3.sourceforge.net>

Bugs item #647102, was opened at 2002-12-02 11:08
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=647102&group_id=103

Category: Pipermail
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: John-Mark Gurney (jmg)
Assigned to: Nobody/Anonymous (nobody)
Summary: MemoryError when generating indexes

Initial Comment:
Vernier Networks has a relatively small/medium mailing
list archive (only ~238megs) that can not be
regenerated in 512megs of memory.  (Once the machine
needs a reboot, this will increase to 1gig.)   It dies
with a MemoryError supplied below:
Updating index files for archive [2002-May]
Traceback (most recent call last):
  File "/home/mailman/bin/arch", line 129, in ?
    main()
  File "/home/mailman/bin/arch", line 119, in main
    archiver.close()
  File "/home/mailman/Mailman/Archiver/pipermail.py",
line 304, in close
    self.update_dirty_archives()
  File "/home/mailman/Mailman/Archiver/HyperArch.py",
line 934, in update_dirty_archives
    self.__super_update_dirty_archives()
  File "/home/mailman/Mailman/Archiver/pipermail.py",
line 513, in update_dirty_archives
    self.update_archive(i)
  File "/home/mailman/Mailman/Archiver/HyperArch.py",
line 937, in update_archive
    self.__super_update_archive(archive)
  File "/home/mailman/Mailman/Archiver/pipermail.py",
line 417, in update_archive
    self.__set_parameters(archive)
  File "/home/mailman/Mailman/Archiver/pipermail.py",
line 332, in __set_parameters
    firstdate = self.database.firstdate(archive)
  File
"/home/mailman/Mailman/Archiver/HyperDatabase.py", line
207, in firstdate
    self.__openIndices(archive)
  File
"/home/mailman/Mailman/Archiver/HyperDatabase.py", line
238, in __openIndices
    self.__closeIndices()
  File
"/home/mailman/Mailman/Archiver/HyperDatabase.py", line
259, in __closeIndices
    index.close() 
  File
"/home/mailman/Mailman/Archiver/HyperDatabase.py", line
186, in close
    fp.write(marshal.dumps(self.dict))
MemoryError

and I also have an IOError on a lock file.

I will be looking at it, but since I do not know
Pipermail, I won't progress very far.

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

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

From webperson at now.org  Mon Dec  2 22:20:43 2002
From: webperson at now.org (NOW Website Coordinator)
Date: Mon, 02 Dec 2002 14:20:43 -0800
Subject: [Mailman-Developers] "Site list is missing"
Message-ID: <4.3.2.7.2.20021202141613.00ca8b30@now.org>

I can't find this answer in the archives, or in the scripts.  The first 
time that 2.1 (right now I'm using 2.1b5) would send out password 
reminders, it failed with this message:

Your "cron" job on now
/usr/local/bin/python -S /usr/local/mailman/cron/mailpasswds
produced the following output:
Site list is missing: mailman

When I look at the mailpasswds script, I find the section it came from:

# This is the list that all the reminders will look like they come from,
     # but with the host name coerced to the virtual host we're processing.
     try:
         sitelist = MailList.MailList(mm_cfg.MAILMAN_SITE_LIST, lock=0)
     except Errors.MMUnknownListError:
         # Do it this way for I18n's _()
         sitelistname = mm_cfg.MAILMAN_SITE_LIST
         print >> sys.stderr, _('Site list is missing: %(sitelistname)s')
         syslog('error', 'Site list is missing: %s', mm_cfg.MAILMAN_SITE_LIST)
         sys.exit(1)


but I'm not sure what exactly the problem is.  Is there something in 
mm_cfg.py I should set?

Thanks in advance.

By the way, this worked for 2.0.

Also: 2.1b5 fixed my earlier problem of not being able to see the 
members!  Thanks.


Sarah Stapleton-Gray
--------------------------------------------
Web Site Coordinator
National Organization for Women
http://www.now.org



From noreply at sourceforge.net  Mon Dec  2 23:56:55 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 15:56:55 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-647102 ] MemoryError when generating indexes
Message-ID: <E18J0Qp-0004GC-00@sc8-sf-web2.sourceforge.net>

Bugs item #647102, was opened at 2002-12-02 11:08
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=647102&group_id=103

Category: Pipermail
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: John-Mark Gurney (jmg)
Assigned to: Nobody/Anonymous (nobody)
Summary: MemoryError when generating indexes

Initial Comment:
Vernier Networks has a relatively small/medium mailing
list archive (only ~238megs) that can not be
regenerated in 512megs of memory.  (Once the machine
needs a reboot, this will increase to 1gig.)   It dies
with a MemoryError supplied below:
Updating index files for archive [2002-May]
Traceback (most recent call last):
  File "/home/mailman/bin/arch", line 129, in ?
    main()
  File "/home/mailman/bin/arch", line 119, in main
    archiver.close()
  File "/home/mailman/Mailman/Archiver/pipermail.py",
line 304, in close
    self.update_dirty_archives()
  File "/home/mailman/Mailman/Archiver/HyperArch.py",
line 934, in update_dirty_archives
    self.__super_update_dirty_archives()
  File "/home/mailman/Mailman/Archiver/pipermail.py",
line 513, in update_dirty_archives
    self.update_archive(i)
  File "/home/mailman/Mailman/Archiver/HyperArch.py",
line 937, in update_archive
    self.__super_update_archive(archive)
  File "/home/mailman/Mailman/Archiver/pipermail.py",
line 417, in update_archive
    self.__set_parameters(archive)
  File "/home/mailman/Mailman/Archiver/pipermail.py",
line 332, in __set_parameters
    firstdate = self.database.firstdate(archive)
  File
"/home/mailman/Mailman/Archiver/HyperDatabase.py", line
207, in firstdate
    self.__openIndices(archive)
  File
"/home/mailman/Mailman/Archiver/HyperDatabase.py", line
238, in __openIndices
    self.__closeIndices()
  File
"/home/mailman/Mailman/Archiver/HyperDatabase.py", line
259, in __closeIndices
    index.close() 
  File
"/home/mailman/Mailman/Archiver/HyperDatabase.py", line
186, in close
    fp.write(marshal.dumps(self.dict))
MemoryError

and I also have an IOError on a lock file.

I will be looking at it, but since I do not know
Pipermail, I won't progress very far.

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

>Comment By: John-Mark Gurney (jmg)
Date: 2002-12-02 15:56

Message:
Logged In: YES 
user_id=27410

Found that in pipermail.T.processUnixMailbox, it will read
in ALL articles w/ their bodies attached.  I have fixed
pipermail.Article to use an instance of a new class I wrote
for body.  The class will emulate a simple sequence and an
interator object and just store the offsets to the lines,
and reread the lines as necessary.  I'm waiting the nightly
run to see how things will go.

The patches currently work for small archives.

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

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

From noreply at sourceforge.net  Tue Dec  3 00:22:19 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 16:22:19 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-647083 ] compress dies w/ MemoryError
Message-ID: <E18J0pP-000283-00@sc8-sf-web3.sourceforge.net>

Patches item #647083, was opened at 2002-12-02 10:38
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=647083&group_id=103

Category: command line scripts
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: John-Mark Gurney (jmg)
Assigned to: Nobody/Anonymous (nobody)
Summary: compress dies w/ MemoryError

Initial Comment:
If you have a large mailing list, it is very easy to
quickly exhast memory in many conditions.  nightly_gzip
script tries to load the entire file into memory before
compressing it, not only is this terribly ineffecient,
it also means you are limited to file sizes that can
fit in memory.  Some machines also further restrict how
much memory each process can access at a time.  If that
limit is 512megs, and you have a 400+meg file, compress
will die.

Solution:  read/write the file in blocks.

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

>Comment By: John-Mark Gurney (jmg)
Date: 2002-12-02 16:22

Message:
Logged In: YES 
user_id=27410

Well, from the looks of it, it is best to use the gzip
module if we want to be able to use gunzip (cmd line) to
uncompress the file.  zlib only provides for compression
objects, and doesn't say if the output is compatible for
direct input to the gunzip program.

I also went with the easiest modification, least source
modifications.

Now that I'm thinking about it, it might of been implemented
as a call to writelines(xreadlines()) w/o having to use my
own while loop resulting in even less modification of the
code.  The only problem is that this may produce very long
lines for binary code.  Also, this requires more scanning
for the new lines, while the block while does not have to
scan the input.

To bad write doesn't support file objects to copy in a block
manner. so the code could simply be:
outfp.write(infp)

P.S.  I forgot to mention in the body that this work is
supported by Vernier Networks, Inc.

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

Comment By: Bryan Fullerton (fehwalker)
Date: 2002-12-02 10:53

Message:
Logged In: YES 
user_id=660772

would it make more sense to do this with zlib routines on a
stream than with gzip on blocks?


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

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

From sb.list at sb.org  Tue Dec  3 00:32:37 2002
From: sb.list at sb.org (Stonewall Ballard)
Date: Mon, 02 Dec 2002 19:32:37 -0500
Subject: [Mailman-Developers] "Site list is missing"
In-Reply-To: <4.3.2.7.2.20021202141613.00ca8b30@now.org>
Message-ID: <BA1165D5.50E8C%sb.list@sb.org>

You need to have a mailing list named "mailman". The INSTALL file says:

    - Create a "site-wide" mailing list.  This is the one that
      password reminders will appear to come from.  Usually this
      should be the "mailman" mailing list, but if you need to change
      this, be sure to change the MAILMAN_SITE_LIST variable in
      mm_cfg.py (see below).

          % bin/newlist mailman

      Follow the prompts, and see the README file for more
      information.

    - You should then subscribe yourself to the mailman list.

 - Stoney

On 12/2/02 5:20 PM, "NOW Website Coordinator" <webperson@now.org> wrote:

> I can't find this answer in the archives, or in the scripts.  The first
> time that 2.1 (right now I'm using 2.1b5) would send out password
> reminders, it failed with this message:
> 
> Your "cron" job on now
> /usr/local/bin/python -S /usr/local/mailman/cron/mailpasswds
> produced the following output:
> Site list is missing: mailman
> 
> When I look at the mailpasswds script, I find the section it came from:
> 
> # This is the list that all the reminders will look like they come from,
>    # but with the host name coerced to the virtual host we're processing.
>    try:
>        sitelist = MailList.MailList(mm_cfg.MAILMAN_SITE_LIST, lock=0)
>    except Errors.MMUnknownListError:
>        # Do it this way for I18n's _()
>        sitelistname = mm_cfg.MAILMAN_SITE_LIST
>        print >> sys.stderr, _('Site list is missing: %(sitelistname)s')
>        syslog('error', 'Site list is missing: %s', mm_cfg.MAILMAN_SITE_LIST)
>        sys.exit(1)
> 
> 
> but I'm not sure what exactly the problem is.  Is there something in
> mm_cfg.py I should set?
> 
> Thanks in advance.
> 
> By the way, this worked for 2.0.
> 
> Also: 2.1b5 fixed my earlier problem of not being able to see the
> members!  Thanks.
> 
> 
> Sarah Stapleton-Gray
> --------------------------------------------
> Web Site Coordinator
> National Organization for Women
> http://www.now.org
> 
> 
> 
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers@python.org
> http://mail.python.org/mailman/listinfo/mailman-developers


From rb at islandnet.com  Tue Dec  3 02:15:10 2002
From: rb at islandnet.com (Ron Brogden)
Date: Mon, 2 Dec 2002 18:15:10 -0800
Subject: [Mailman-Developers] unicode / archive problem revisited
Message-ID: <E18J2ag-000LVF-00@mail.islandnet.com>

Howdy.  I am currently running 2.1b5 of Mailman and am trying to sort out an 
issue with archiving that has crept up.  

The problem has been mentioned previously from what I can tell but no 
resolution seems to have been mentioned.

What the problem is that list archives (for reasons I won't bore you with) 
have a number of SPAM message in them with all sorts of random encoding types 
and other mangled garbage.  What happens is that when the archiver gets to 
the point of writing the archive, the encoding type test generates an error 
and the whole archiving process grinds to a crashing halt.  These are busy 
lists and the mbox archive takes a very long time to parse and there just is 
not enough time in the day to search for the offending message, chop it out 
and wait another 45 minutes or more until the archives are regenerated to hit 
the next garbled header, etc.  This will also continue to be a problem if any 
future SPAM messages sneak in via forged headers, etc.

The issue appears to be with: 

/usr/local/mailman/Mailman/Archiver/HyperArch.py 

Traceback (most recent call last):
  File "./bin/arch", line 173, in ?
    main()
  File "./bin/arch", line 163, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in 
update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1058, in 
update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 423, in 
update_archive
    self._update_simple_index(hdr, archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 444, in 
_update_simple_index
    self.write_index_entry(article)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 980, in 
write_index_entry
    subject = self.get_header("subject", article)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1007, in 
get_header
    return unicode(result, article.charset)
TypeError: unicode() argument 2 must be string, not None

What I want is the archiver to default to english if it cannot figure out the 
encoding so that at least the archiver will not die.  

So two questions:

What is a valid encoding type to pass as default to the unicode call?  
Secondly, is there any danger in changing the fallback option to always use a 
specific charset?  I'd rather have gibberish than a process that dies.

Basically, around line 1007 in 
"/usr/local/mailman/Mailman/Archiver/HyperArch.py" I want to change:

 if isinstance(result, types.UnicodeType):
            return result
 try:
            return unicode(result, article.charset)

to

 if isinstance(result, types.UnicodeType):
            return result
 try:
            return unicode(result, "some string") # never fail!

Thanks for any suggestions.

Cheers

From wildfire at progsoc.uts.edu.au  Tue Dec  3 04:21:49 2002
From: wildfire at progsoc.uts.edu.au (Anand Kumria)
Date: Tue, 3 Dec 2002 15:21:49 +1100
Subject: [Mailman-Developers] MHonArc integration
In-Reply-To: <3DE5CAA6.60109@nsc.com>
References: <3DE5CAA6.60109@nsc.com>
Message-ID: <20021203042149.GE13758@yeenoghu.progsoc.uts.edu.au>

On Wed, Nov 27, 2002 at 11:49:58PM -0800, Prakash Subramanian wrote:
> I am trying to use a simple method to include MHonArc archiver enabled 
> with monthly archive functionality.  I found your script that does, but 
> I am not sure how to use it.

Hi Prakash,

Actually you aren't the first person to mention that to me. I think you
are probably the 10th or so; and since that is a double digit it is time
to write some docs.

> I tried replacing ~mailman/Mailman/Archiver/HyperArch.py with your 
> MHonArc.py but it gives the following error message.
> 
> ~mailman/bin/arch mylist
> Traceback (most recent call last):
>  File "/usr/local/mailman/bin/arch", line 43, in ?
>    from Mailman.Archiver.HyperArch import HyperArchive, Article
> ImportError: cannot import name Article

You don't actually want to do that instead you want to replace the
import directive. MHonArc doesn't imlpement the Article class -- I
haven't looked at it in detail to see if it is required.

> The method Article is been used by various script and I am not able to 
> get rid of this .
> 
> Please advice on how to use your script.

Well, nowl  that MHonArc is managing the archiving I've been using it
rather than the interface mailman provides. If you take a look at 
<URL: http://www.progsoc.org/~wildfire/code/>, that is the latest
version of the code and some setup instructions.

You may also find the set_list_pass script useful too.

> 
> Another question,  why
> 

I didn't find the pipermail archiving very appealing; I tried shell
scripts and they were a bit fragile. So I nutted this out over a number
of train trips to/from work.

Regards,
Anand

-- 
 `` We are shaped by our thoughts, we become what we think.
 When the mind is pure, joy follows like a shadow that never
 leaves. '' -- Buddha, The Dhammapada

From noreply at sourceforge.net  Tue Dec  3 07:43:11 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon, 02 Dec 2002 23:43:11 -0800
Subject: [Mailman-Developers] 
 [ mailman-Feature Requests-581103 ] do not moderate mails from nntp-groups
Message-ID: <E18J7i3-00055Z-00@sc8-sf-web3.sourceforge.net>

Feature Requests item #581103, was opened at 2002-07-13 20:35
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=581103&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Markus Mandalka (mandalka)
Assigned to: Nobody/Anonymous (nobody)
Summary: do not moderate mails from nntp-groups

Initial Comment:
i wish to have an setting for the nntp-gateway that
allows posting the nntp-articles without moderating on
lists, that need confirmation for member-postings.

The moderation should only be for the emails sendet to
the list, not for nntp-postings.

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

Comment By: Philip Lowman (plowman)
Date: 2002-12-03 07:43

Message:
Logged In: YES 
user_id=78148

I've also been looking for this feature to be added, i'm
kinda upset it hasn't been assigned to anyone :(  This is a
good idea!  I don't care who posts on the NNTP side of
things, reflecting that to the list is fine.  I am worried
about spammers on the email side of things and there is no
way to add everyone who would post to the newsgroup to the
explicit allow list.  This is not good :)... luckily I
haven't been spammed... yet

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

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

From noreply at sourceforge.net  Tue Dec  3 17:36:31 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue, 03 Dec 2002 09:36:31 -0800
Subject: [Mailman-Developers] [ mailman-Patches-644810 ] Sendmail mailer in
	Python
Message-ID: <E18JGyF-00018A-00@sc8-sf-web4.sourceforge.net>

Patches item #644810, was opened at 2002-11-27 16:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103

Category: mail delivery
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Sendmail mailer in Python

Initial Comment:
This patch provide a Python implementation (with C 
wrapper) of a Sendmail mailer, if Sendmail is your MTA 
of choice, which removes the necessity of maintining an 
aliases database on your Mailman server. All subject to 
a bunch of conditions most prominent of which is that 
the server has to be pretty much dedicated to MM.

This patch draws on an original contribution by David 
Champion <dgc@uchicago.edu> which is included in 
the contrib directory of the Mailman 2.1b distribution as 
mm-handler.

See the README.SENDMAIL.mailer installed by this 
patch for differences between this and David's Perl 
original and more information of what you are getting into 
if you use this patch.

Versions of the patch for MM 2.0.13 and MM 2.1b5 are 
available.

This patch requires patch 644797 to be installed before 
it.

In the MM build directory say: 

patch -p1 < patch-filename 

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

>Comment By: Richard Barrett (ppsys)
Date: 2002-12-03 17:36

Message:
Logged In: YES 
user_id=75166

Fix for permissions related exceptions being generated by the 
subprocess spawned by mm_mailer script.

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

Comment By: Richard Barrett (ppsys)
Date: 2002-11-27 16:29

Message:
Logged In: YES 
user_id=75166

version for MM 2.1b5

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

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

From noreply at sourceforge.net  Tue Dec  3 17:37:36 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue, 03 Dec 2002 09:37:36 -0800
Subject: [Mailman-Developers] [ mailman-Patches-644810 ] Sendmail mailer in
	Python
Message-ID: <E18JGzI-0001Ar-00@sc8-sf-web4.sourceforge.net>

Patches item #644810, was opened at 2002-11-27 16:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103

Category: mail delivery
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Sendmail mailer in Python

Initial Comment:
This patch provide a Python implementation (with C 
wrapper) of a Sendmail mailer, if Sendmail is your MTA 
of choice, which removes the necessity of maintining an 
aliases database on your Mailman server. All subject to 
a bunch of conditions most prominent of which is that 
the server has to be pretty much dedicated to MM.

This patch draws on an original contribution by David 
Champion <dgc@uchicago.edu> which is included in 
the contrib directory of the Mailman 2.1b distribution as 
mm-handler.

See the README.SENDMAIL.mailer installed by this 
patch for differences between this and David's Perl 
original and more information of what you are getting into 
if you use this patch.

Versions of the patch for MM 2.0.13 and MM 2.1b5 are 
available.

This patch requires patch 644797 to be installed before 
it.

In the MM build directory say: 

patch -p1 < patch-filename 

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

>Comment By: Richard Barrett (ppsys)
Date: 2002-12-03 17:37

Message:
Logged In: YES 
user_id=75166

Fix for permissions related exceptions being generated by the 
subprocess spawned by mm_mailer script

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

Comment By: Richard Barrett (ppsys)
Date: 2002-12-03 17:36

Message:
Logged In: YES 
user_id=75166

Fix for permissions related exceptions being generated by the 
subprocess spawned by mm_mailer script.

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

Comment By: Richard Barrett (ppsys)
Date: 2002-11-27 16:29

Message:
Logged In: YES 
user_id=75166

version for MM 2.1b5

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

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

From rb at islandnet.com  Wed Dec  4 01:30:06 2002
From: rb at islandnet.com (Ron Brogden)
Date: Tue, 3 Dec 2002 17:30:06 -0800
Subject: [Mailman-Developers] unicode / archive problem followup (scrubber.py
	too)
Message-ID: <E18JOMb-000ISb-00@mail.islandnet.com>

Howdy.  Since no one replied with any suggestions for me I decided to take a 
chance with a crude little hack to deal with the archiver getting confused 
when the unicode type returned was "None".  This also brought up a bug with 
the attachment handling code in the archiver though which again, I have done 
a crude hack to but which I want to make sure I haven't done a big no no.

First off, the specific changes:

In HyperArchive.py the following lines were munged to always return the 
following charset if none could be discerned:

450:            return unicode(subj, "iso-8859-1")
1010:            return unicode(result, "iso-8859-1") 

This got me past the initial error but this led to a new error to with dates 
and attachement folders.  

The sanity checking is not too bright for the folder name selection and so 
what happens is that if the date cannot be culled from the message due to a 
logic problem (it falls through in a funny way), the net result is that the 
archiver dies instead of either just picking a date or tossing the 
attachment. Since I am not totally clear on what all the date efffects, I 
chickened out and just assumed that there would always be a date in the 
received header which probably isn't wise but is better than it is now.

In Scrubber.py around line 80:

def calculate_attachments_dir(mlist, msg, msgdata):
    # Calculate the directory that attachments for this message will go
    # under.  To avoid inode limitations, the scheme will be:
    # archives/private/<listname>/attachments/YYYYMMDD/<msgid-hash>/<files>
    # Start by calculating the date-based and msgid-hash components.
    msgdate = msg.get('Date')
    if msgdate is None:
        now = time.gmtime(msgdata.get('received_time', time.time()))
    else:
        now = parsedate(msgdate)

This a problem since it appears that parsedate() is not guaranteed to return 
something useful and so again, the archiver was dying.  To get around this I 
had to add the following catchall afterwards:

    if now is None:
        now = time.gmtime(msgdata.get('received_time', time.time()))

So two questions.  First, is the above a reasonable thing to do (i.e. am I 
introducing anything nasty by doing this)?  Secondly, I don't want 
attachments archived at all - how do how do you disable this behaviour?

Thanks for any suggestions or feedback.

Cheers,

Ron

From novembre+dated+1039410247.6d79a7 at ournature.org  Wed Dec  4 05:26:30 2002
From: novembre+dated+1039410247.6d79a7 at ournature.org (Jinhyok Heo)
Date: Wed, 04 Dec 2002 14:26:30 +0900
Subject: [Mailman-Developers] Archiving problem in current CVS.
Message-ID: <microsoft-free.3ou1hu73sp.fsf@ournature.org>

I got two problems and one feature request.

Fist, if I try to regenerate archive of a list with Current CVS
mailman(using bin/arch), characters of the archives are currupted,
unlike incoming mails. Can you give it a glance?

And, I've set "ARCHIVE_HTML_SANITIZER = 3" in my mm_cfg.py, but it
doesn't work. Incoming mails are archived as if set with
"ARCHIVE_HTML_SANITIZER = 1".

Why don't we have such a ARCHIVE_HTML_SANITIZER option that leaves
html parts inline and doesn't html-escape. It can be really dangerous
but, in a small reliable group, such an option can be quite useful.
Nowadays there are many free webmail services which they send html
mails only and archives become quite ugly.

-- 
| Jinhyok Heo (novembre @ ournature.org || http://ournature.org/~novembre/)
|--------------------------------------------------------------------------
| "We are still reaching for the sky. In the developed countries people
|  are coming back down, saying, `It's empty up there.'" --- a Ladakhi monk



From noreply at sourceforge.net  Wed Dec  4 10:53:16 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed, 04 Dec 2002 02:53:16 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi
Message-ID: <E18JX9Y-0006um-00@sc8-sf-web1.sourceforge.net>

Patches item #444884, was opened at 2001-07-26 18:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103

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

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

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

This patch integrates htdig with Mailman and provides:

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

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

You probably want to run this patch as follows:

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=624179

Got a workaround!

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

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

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

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

Message:
Logged In: YES 
user_id=624179

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

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

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

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

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


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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=12800

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

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

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

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

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

Message:
Logged In: YES 
user_id=75166

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


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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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



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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.8

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

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

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to Mm 2.0.7

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

From noreply at sourceforge.net  Wed Dec  4 13:52:10 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed, 04 Dec 2002 05:52:10 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-646571 ] config_list: UnboundLocalError
Message-ID: <E18JZwg-0003mB-00@sc8-sf-web2.sourceforge.net>

Bugs item #646571, was opened at 2002-12-01 14:19
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=646571&group_id=103

Category: command line scripts
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: David Gibbs (midrangeman)
Assigned to: Nobody/Anonymous (nobody)
Summary: config_list: UnboundLocalError

Initial Comment:
[mailman@linux work]$ ../bin/config_list -o beta-
testers.cfg beta-testers
Traceback (most recent call last):
  File "../bin/config_list", line 327, in ?
    main()
  File "../bin/config_list", line 320, in main
    do_output(listname, outfile)
  File "../bin/config_list", line 122, in do_output
    if closep:
UnboundLocalError: local variable 'closep' referenced 
before assignment

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

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

From barry at python.org  Wed Dec  4 14:08:05 2002
From: barry at python.org (Barry A. Warsaw)
Date: Wed, 4 Dec 2002 09:08:05 -0500
Subject: [Mailman-Developers] unicode / archive problem revisited
References: <E18J2ag-000LVF-00@mail.islandnet.com>
Message-ID: <15854.3141.928144.215628@gargle.gargle.HOWL>


>>>>> "RB" == Ron Brogden <rb@islandnet.com> writes:

    RB> Howdy.  I am currently running 2.1b5 of Mailman and am trying
    RB> to sort out an issue with archiving that has crept up.

    RB> The problem has been mentioned previously from what I can tell
    RB> but no resolution seems to have been mentioned.

    RB> What the problem is that list archives (for reasons I won't
    RB> bore you with) have a number of SPAM message in them with all
    RB> sorts of random encoding types and other mangled garbage.
    RB> What happens is that when the archiver gets to the point of
    RB> writing the archive, the encoding type test generates an error
    RB> and the whole archiving process grinds to a crashing halt.
    RB> These are busy lists and the mbox archive takes a very long
    RB> time to parse and there just is not enough time in the day to
    RB> search for the offending message, chop it out and wait another
    RB> 45 minutes or more until the archives are regenerated to hit
    RB> the next garbled header, etc.  This will also continue to be a
    RB> problem if any future SPAM messages sneak in via forged
    RB> headers, etc.

Could you send me a sample of an offending message, as an attachment?
Better yet, file a bug report with SourceForge and upload (don't
paste!) that same on the bug report.

Thanks,
-Barry

From gward at mems-exchange.org  Wed Dec  4 16:24:04 2002
From: gward at mems-exchange.org (Greg Ward)
Date: Wed, 4 Dec 2002 11:24:04 -0500
Subject: [Mailman-Developers] bin/arch traceback
Message-ID: <20021204162404.GA12277@cthulhu.gerg.ca>

A few weeks back (http://mail.python.org/pipermail/mailman-developers/
2002-November/013960.html), Andrew Clark reported a traceback from
bin/arch on some lists some of the time.  I've just hit the same bug
(our tracebacks are identical):

$ ./bin/arch <listname>
[...churn, churn, churn...]
#04077 <mailman.4063.1039018365.21495.mems-talk@memsnet.org>
Updating index files for archive [2001-July]
  Date
  Subject
  Author
  Thread
Computing threaded index
Updating HTML for article 8892
Updating HTML for article 8893
Updating HTML for article 8894
Updating HTML for article 8895
Updating HTML for article 8896
Updating HTML for article 8897
Updating HTML for article 8898
Updating HTML for article 8899
Updating HTML for article 8891
Updating HTML for article 8900
Updating HTML for article 8901
Updating HTML for article 8902
Updating HTML for article 8903
Updating HTML for article 8904
Updating HTML for article 5007
Traceback (most recent call last):
  File "./bin/arch", line 173, in ?
    main()
  File "./bin/arch", line 163, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_d
irty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_
archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_a
rchive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_
thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_
article
    f.write(article.as_html())
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html
    d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1)
AttributeError: Article instance has no attribute '_mlist'

Andrew said that renaming away the existing HTML archive did the trick
-- I'll do that, but I don't like making the archives for this list
unavailable even for a few minutes.  (It takes a while to generate the
whole archive, which goes back to 1994.)  Or should I "cvs up" instead,
ie. has this bug been fixed?

Thanks --

        Greg
-- 
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org

From barry at python.org  Wed Dec  4 16:28:35 2002
From: barry at python.org (Barry A. Warsaw)
Date: Wed, 4 Dec 2002 11:28:35 -0500
Subject: [Mailman-Developers] bin/arch traceback
References: <20021204162404.GA12277@cthulhu.gerg.ca>
Message-ID: <15854.11571.315728.288468@gargle.gargle.HOWL>


>>>>> "GW" == Greg Ward <gward@mems-exchange.org> writes:

    GW> Andrew said that renaming away the existing HTML archive did
    GW> the trick -- I'll do that, but I don't like making the
    GW> archives for this list unavailable even for a few minutes.
    GW> (It takes a while to generate the whole archive, which goes
    GW> back to 1994.)  Or should I "cvs up" instead, ie. has this bug
    GW> been fixed?

Greg, I believe this bug is fixed in cvs, so I'd recommend cvs
up'ing.  However, if any new messages arrived while you were running
2.1b4 then you should also run b4b5-archfix after up'ing.

If, after all that you still get this exception, I wanna know about
it.

-Barry

From gward at mems-exchange.org  Wed Dec  4 16:31:34 2002
From: gward at mems-exchange.org (Greg Ward)
Date: Wed, 4 Dec 2002 11:31:34 -0500
Subject: [Mailman-Developers] Re: bin/arch traceback
In-Reply-To: <20021204162404.GA12277@cthulhu.gerg.ca>
References: <20021204162404.GA12277@cthulhu.gerg.ca>
Message-ID: <20021204163134.GA12309@cthulhu.gerg.ca>

On 04 December 2002, I said:
> Andrew said that renaming away the existing HTML archive did the trick
> -- I'll do that, but I don't like making the archives for this list
> unavailable even for a few minutes.

Arrghh!  I did this and now bin/arch goes a lot farther, but it still
crashes eventually:

[...]
Updating HTML for article 4073
Updating HTML for article 4074
Updating HTML for article 4076
Pickling archive state into /usr/local/mailman/archives/private/mems-talk/pipermail.pck
Traceback (most recent call last):
  File "./bin/arch", line 173, in ?
    main()
  File "./bin/arch", line 161, in main
    archiver.processUnixMailbox(fp, start, end)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 557, in processUnixMailbox
    a = self._makeArticle(m, self.sequence)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 619, in _makeArticle
    mlist=self.maillist)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 261, in __init__
    self.check_header_charsets(charset)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 350, in check_header_charsets
    author, a_charset = self.decode_charset(self.author)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 379, in decode_charset
    h = make_header(pairs, 99999)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 123, in make_header
    h.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append
    ustr = unicode(s, incodec)
LookupError: unknown encoding

I presume this is some Asian encoding that's not *supposed* to appear in
an English-language list, but does.  Grumble.  I'll see if I can figure
out the offending message.

        Greg
-- 
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org

From gward at mems-exchange.org  Wed Dec  4 16:36:36 2002
From: gward at mems-exchange.org (Greg Ward)
Date: Wed, 4 Dec 2002 11:36:36 -0500
Subject: [Mailman-Developers] Re: bin/arch traceback
In-Reply-To: <20021204163134.GA12309@cthulhu.gerg.ca>
References: <20021204162404.GA12277@cthulhu.gerg.ca>
	<20021204163134.GA12309@cthulhu.gerg.ca>
Message-ID: <20021204163636.GB12309@cthulhu.gerg.ca>

On 04 December 2002, I said:
> [...]
> Updating HTML for article 4073
> Updating HTML for article 4074
> Updating HTML for article 4076
> Pickling archive state into /usr/local/mailman/archives/private/mems-talk/pipermail.pck
> Traceback (most recent call last):
>   File "./bin/arch", line 173, in ?
>     main()
[...]
>   File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append
>     ustr = unicode(s, incodec)
> LookupError: unknown encoding
> 
> I presume this is some Asian encoding that's not *supposed* to appear in
> an English-language list, but does.

Yep.  Here's the start of message #4077:

"""
>From mswang@princeton.com.tw Fri Dec 17 06:33:22 1999
To: mems@isi.edu
Subject:   request info. on GDSII                           
From:   "Tina Wang" <mswang@princeton.com.tw>            
Date: Fri Dec 17 06:33:22 1999
Status: O
Content-Length: 1330
Lines: 45

This is a multi-part message in MIME format.

------=_NextPart_000_001A_01BF489B.AB8341E0
Content-Type: text/plain;
        charset="big5"                       <<< I don't think so
Content-Transfer-Encoding: quoted-printable

Dear MEMES Discussion Group,
[...]
"""

Obviously that first message part is *not* encoded with big5, but you
try telling Mailman that.  Sigh.  I'll try editing the offending message
and seeing how far arch gets this time.

Oh yeah, should I be filing bug reports?

        Greg
-- 
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org

From barry at python.org  Wed Dec  4 16:37:30 2002
From: barry at python.org (Barry A. Warsaw)
Date: Wed, 4 Dec 2002 11:37:30 -0500
Subject: [Mailman-Developers] Re: bin/arch traceback
References: <20021204162404.GA12277@cthulhu.gerg.ca>
	<20021204163134.GA12309@cthulhu.gerg.ca>
Message-ID: <15854.12106.74106.523661@gargle.gargle.HOWL>


>>>>> "GW" == Greg Ward <gward@mems-exchange.org> writes:

    GW> I presume this is some Asian encoding that's not *supposed* to
    GW> appear in an English-language list, but does.  Grumble.  I'll
    GW> see if I can figure out the offending message.

Some one else reported this, but I'm still waiting for an example so I
can reproduce the bug.  If you find it, please send it (or better yet,
add it to a SF bug report).

Thanks!
-Barry

From barry at python.org  Wed Dec  4 16:42:16 2002
From: barry at python.org (Barry A. Warsaw)
Date: Wed, 4 Dec 2002 11:42:16 -0500
Subject: [Mailman-Developers] Re: bin/arch traceback
References: <20021204162404.GA12277@cthulhu.gerg.ca>
	<20021204163134.GA12309@cthulhu.gerg.ca>
	<20021204163636.GB12309@cthulhu.gerg.ca>
Message-ID: <15854.12392.880733.385745@gargle.gargle.HOWL>


>>>>> "GW" == Greg Ward <gward@mems-exchange.org> writes:

    GW> Oh yeah, should I be filing bug reports?

Yes, please!

Be sure to set the group to Mailman 2.1beta.
-Barry

From gward at mems-exchange.org  Wed Dec  4 20:23:24 2002
From: gward at mems-exchange.org (Greg Ward)
Date: Wed, 4 Dec 2002 15:23:24 -0500
Subject: [Mailman-Developers] bin/arch traceback
In-Reply-To: <15854.11571.315728.288468@gargle.gargle.HOWL>
References: <20021204162404.GA12277@cthulhu.gerg.ca>
	<15854.11571.315728.288468@gargle.gargle.HOWL>
Message-ID: <20021204202324.GA300@cthulhu.gerg.ca>

On 04 December 2002, Barry A. Warsaw said:
> Greg, I believe this bug is fixed in cvs, so I'd recommend cvs
> up'ing.  However, if any new messages arrived while you were running
> 2.1b4 then you should also run b4b5-archfix after up'ing.

The list in question never ran under 2.1b4 -- I got nervous about all
the problems people were having with the archiver, so didn't upgrade it
until 2.1b5 was out.  And, just for the heck of it, I did re-run
b4b5-archfix -- no point though, since the grep for '_mlist' turned up
nothing.

> If, after all that you still get this exception, I wanna know about
> it.

Yes, I'm still getting it with the current CVS code.  It comes in
exactly the same place in the execution of bin/arch, and the traceback
is basically identical -- mainly line number differences, and your
recent patch to Mailman/Archiver/HyperArch.py.

Here's are arch's death throes:

[...]
Updating HTML for article 8903
Updating HTML for article 8904
Updating HTML for article 5007
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1247, in update_article
    f.write(article.as_html())
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 411, in as_html
    emailurl = self._mlist.GetListEmail()
AttributeError: Article instance has no attribute '_mlist'

-- 
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org

From noreply at sourceforge.net  Wed Dec  4 20:51:31 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed, 04 Dec 2002 12:51:31 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-648604 ] Crash from "article file missing" error
Message-ID: <E18JgUV-0002VN-00@sc8-sf-web1.sourceforge.net>

Bugs item #648604, was opened at 2002-12-04 15:51
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=648604&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: Crash from "article file missing" error

Initial Comment:
If I playfully delete the HTML version of a message and then re-run bin/arch, it crashes:

$ rm -f archives/private/mems-talk/2001-July/005007.html

$ /bin/arch mems-talk
#00000 <E15QYR8-0006UV-00@ute.cnri.reston.va.us>
figuring article archives
2001-July
Updating index files for archive [2001-July]
  Date
  Subject
  Author
  Thread
Computing threaded index
Updating HTML for article 8891
Updating HTML for article 8899
Updating HTML for article 8900
Updating HTML for article 8901
Updating HTML for article 8902
Updating HTML for article 8903
Updating HTML for article 8904
Updating HTML for article 5007
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1238, in update_article
    self.message(_("article file %s is missing!")
TypeError: format requires a mapping

To my embarassment, I can't make this simple %s work at all!  Must be some funky I18N thing.  If I remove the _() from the format string, it works.



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

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

From noreply at sourceforge.net  Wed Dec  4 20:51:38 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed, 04 Dec 2002 12:51:38 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-648605 ] Crash from "article file missing" error
Message-ID: <E18JgUc-0002VX-00@sc8-sf-web1.sourceforge.net>

Bugs item #648605, was opened at 2002-12-04 15:51
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=648605&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: Crash from "article file missing" error

Initial Comment:
If I playfully delete the HTML version of a message and then re-run bin/arch, it crashes:

$ rm -f archives/private/mems-talk/2001-July/005007.html

$ /bin/arch mems-talk
#00000 <E15QYR8-0006UV-00@ute.cnri.reston.va.us>
figuring article archives
2001-July
Updating index files for archive [2001-July]
  Date
  Subject
  Author
  Thread
Computing threaded index
Updating HTML for article 8891
Updating HTML for article 8899
Updating HTML for article 8900
Updating HTML for article 8901
Updating HTML for article 8902
Updating HTML for article 8903
Updating HTML for article 8904
Updating HTML for article 5007
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1238, in update_article
    self.message(_("article file %s is missing!")
TypeError: format requires a mapping

To my embarassment, I can't make this simple %s work at all!  Must be some funky I18N thing.  If I remove the _() from the format string, it works.



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

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

From noreply at sourceforge.net  Wed Dec  4 20:52:30 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed, 04 Dec 2002 12:52:30 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-648605 ] Crash from "article file missing" error
Message-ID: <E18JgVS-0002WK-00@sc8-sf-web1.sourceforge.net>

Bugs item #648605, was opened at 2002-12-04 15:51
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=648605&group_id=103

Category: None
Group: None
>Status: Deleted
>Resolution: Invalid
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Crash from "article file missing" error

Initial Comment:
If I playfully delete the HTML version of a message and then re-run bin/arch, it crashes:

$ rm -f archives/private/mems-talk/2001-July/005007.html

$ /bin/arch mems-talk
#00000 <E15QYR8-0006UV-00@ute.cnri.reston.va.us>
figuring article archives
2001-July
Updating index files for archive [2001-July]
  Date
  Subject
  Author
  Thread
Computing threaded index
Updating HTML for article 8891
Updating HTML for article 8899
Updating HTML for article 8900
Updating HTML for article 8901
Updating HTML for article 8902
Updating HTML for article 8903
Updating HTML for article 8904
Updating HTML for article 5007
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1238, in update_article
    self.message(_("article file %s is missing!")
TypeError: format requires a mapping

To my embarassment, I can't make this simple %s work at all!  Must be some funky I18N thing.  If I remove the _() from the format string, it works.



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

>Comment By: Greg Ward (gward)
Date: 2002-12-04 15:52

Message:
Logged In: YES 
user_id=14422

oops, duplicate bug

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

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

From noreply at sourceforge.net  Wed Dec  4 20:52:45 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed, 04 Dec 2002 12:52:45 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-648604 ] Crash from "article file missing" error
Message-ID: <E18JgVh-0002WQ-00@sc8-sf-web1.sourceforge.net>

Bugs item #648604, was opened at 2002-12-04 15:51
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=648604&group_id=103

Category: None
>Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Crash from "article file missing" error

Initial Comment:
If I playfully delete the HTML version of a message and then re-run bin/arch, it crashes:

$ rm -f archives/private/mems-talk/2001-July/005007.html

$ /bin/arch mems-talk
#00000 <E15QYR8-0006UV-00@ute.cnri.reston.va.us>
figuring article archives
2001-July
Updating index files for archive [2001-July]
  Date
  Subject
  Author
  Thread
Computing threaded index
Updating HTML for article 8891
Updating HTML for article 8899
Updating HTML for article 8900
Updating HTML for article 8901
Updating HTML for article 8902
Updating HTML for article 8903
Updating HTML for article 8904
Updating HTML for article 5007
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1238, in update_article
    self.message(_("article file %s is missing!")
TypeError: format requires a mapping

To my embarassment, I can't make this simple %s work at all!  Must be some funky I18N thing.  If I remove the _() from the format string, it works.



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

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

From noreply at sourceforge.net  Wed Dec  4 20:54:27 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed, 04 Dec 2002 12:54:27 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-648607 ] bin/arch crash: '_mlist' still missing
Message-ID: <E18JgXL-0002Xo-00@sc8-sf-web1.sourceforge.net>

Bugs item #648607, was opened at 2002-12-04 15:54
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=648607&group_id=103

Category: Pipermail
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: bin/arch crash: '_mlist' still missing

Initial Comment:
Even with the latest CVS, bin/arch still sometimes crashes with an AttributeError from '_mlist'.  Here's my traceback:

Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1247, in update_article
    f.write(article.as_html())
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 411, in as_html
    emailurl = self._mlist.GetListEmail()
AttributeError: Article instance has no attribute '_mlist'


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

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

From noreply at sourceforge.net  Wed Dec  4 22:42:04 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed, 04 Dec 2002 14:42:04 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-648607 ] bin/arch crash: '_mlist' still missing
Message-ID: <E18JiDU-0003Oc-00@sc8-sf-web3.sourceforge.net>

Bugs item #648607, was opened at 2002-12-04 15:54
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=648607&group_id=103

Category: Pipermail
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
>Assigned to: Barry A. Warsaw (bwarsaw)
Summary: bin/arch crash: '_mlist' still missing

Initial Comment:
Even with the latest CVS, bin/arch still sometimes crashes with an AttributeError from '_mlist'.  Here's my traceback:

Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1247, in update_article
    f.write(article.as_html())
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 411, in as_html
    emailurl = self._mlist.GetListEmail()
AttributeError: Article instance has no attribute '_mlist'


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

>Comment By: Greg Ward (gward)
Date: 2002-12-04 17:42

Message:
Logged In: YES 
user_id=14422

Patch attached.  Barry, you're gonna kick yourself.


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

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

From noreply at sourceforge.net  Wed Dec  4 22:43:56 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed, 04 Dec 2002 14:43:56 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-648607 ] bin/arch crash: '_mlist' still missing
Message-ID: <E18JiFI-0008FN-00@sc8-sf-web2.sourceforge.net>

Bugs item #648607, was opened at 2002-12-04 15:54
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=648607&group_id=103

Category: Pipermail
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: bin/arch crash: '_mlist' still missing

Initial Comment:
Even with the latest CVS, bin/arch still sometimes crashes with an AttributeError from '_mlist'.  Here's my traceback:

Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1247, in update_article
    f.write(article.as_html())
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 411, in as_html
    emailurl = self._mlist.GetListEmail()
AttributeError: Article instance has no attribute '_mlist'


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-04 17:43

Message:
Logged In: YES 
user_id=12800

Ouch!  My ass!  

Thanks Greg, I'll apply this later tonight.


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

Comment By: Greg Ward (gward)
Date: 2002-12-04 17:42

Message:
Logged In: YES 
user_id=14422

Patch attached.  Barry, you're gonna kick yourself.


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

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

From gward at mems-exchange.org  Wed Dec  4 23:05:39 2002
From: gward at mems-exchange.org (Greg Ward)
Date: Wed, 4 Dec 2002 18:05:39 -0500
Subject: [Mailman-Developers] bin/arch traceback
In-Reply-To: <20021204202324.GA300@cthulhu.gerg.ca>
References: <20021204162404.GA12277@cthulhu.gerg.ca>
	<15854.11571.315728.288468@gargle.gargle.HOWL>
	<20021204202324.GA300@cthulhu.gerg.ca>
Message-ID: <20021204230539.GA25147@cthulhu.gerg.ca>

On 04 December 2002, I said:
> Yes, I'm still getting it with the current CVS code.  It comes in
> exactly the same place in the execution of bin/arch, and the traceback
> is basically identical -- mainly line number differences, and your
> recent patch to Mailman/Archiver/HyperArch.py.

Found the problem and uploaded a patch to my bug report.
Article.setListIfUnset() was, umm, completely broken.

In related news, bin/arch bloated up to 200 MB of RAM trying to rebuild
this archive before I killed it.  Ouch!  I thought that had been fixed
too.

        Greg

From chuqui at plaidworks.com  Thu Dec  5 03:58:06 2002
From: chuqui at plaidworks.com (Chuq Von Rospach)
Date: Wed, 4 Dec 2002 19:58:06 -0800
Subject: [Mailman-Developers] not quite about mailman -- AOL data losses.
Message-ID: <C2A4F8FC-0805-11D7-9439-0003934516A8@plaidworks.com>

not quite on topic, but for list managers....

I finally have some real numbers on AOL silently eating email. A list 
member just came back from 2 weeks of vacation to find 1/3 of the 
digests sent during that time missing, never delivered. And all were 
accepted from my site by AOL, and I never saw any bounces.

More data here, but I've noticed the aol problems have gotten worse in 
the last couple of weeks. Six or seven of my list members have 
complained about missing messages, where before, I was getting one 
here, one there.

ugh. AOL seems to be imploding, or something. But this isn't good.

<http://www.plaidworks.com/chuqui/blog/000118.html#000118>

a semi RFE for mailman: one of my AOL users asked if we could number 
messages going out. I think under some circumstances, that might not be 
a bad idea. Not just for unreliable feeds, but for things like seed 
lists or other lists where reliablility is crucial... But not for 
2.1....



-- 
Chuq Von Rospach, Architech
chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/

But I can hear the sound
Of slamming doors and folding chairs
And that's a sound they'll never know


From satyap at satya.virtualave.net  Thu Dec  5 05:12:10 2002
From: satyap at satya.virtualave.net (Satya)
Date: Wed, 4 Dec 2002 21:12:10 -0800 (PST)
Subject: [Mailman-Developers] not quite about mailman -- AOL data losses.
In-Reply-To: <C2A4F8FC-0805-11D7-9439-0003934516A8@plaidworks.com>
Message-ID: <Pine.LNX.4.21.0212042102180.22588-100000@gort.cjb.net>

On Dec 4, 2002 at 19:58, Chuq Von Rospach wrote:

>a semi RFE for mailman: one of my AOL users asked if we could number 

What's RFE, again?

>messages going out. I think under some circumstances, that might not be 
>a bad idea. Not just for unreliable feeds, but for things like seed 
>lists or other lists where reliablility is crucial... But not for 
>2.1....

No, not for 2.1 :-P

What is a seed list?

Hmm, you could throw in YA X-header, call it X-MailmanSN, and have it
contain yyyymmdd or the output from time().

-- 
Satya. <URL:http://satya.virtualave.net/> I need a job!
Perl, Apache, Linux, C. http://www-scf.usc.edu/~phanse/resume.pdf
As I said before, I never repeat myself.


From chuqui at plaidworks.com  Thu Dec  5 05:16:02 2002
From: chuqui at plaidworks.com (Chuq Von Rospach)
Date: Wed, 4 Dec 2002 21:16:02 -0800
Subject: [Mailman-Developers] not quite about mailman -- AOL data losses.
In-Reply-To: <Pine.LNX.4.21.0212042102180.22588-100000@gort.cjb.net>
Message-ID: <A5B60502-0810-11D7-9439-0003934516A8@plaidworks.com>


On Wednesday, December 4, 2002, at 09:12  PM, Satya wrote:

> On Dec 4, 2002 at 19:58, Chuq Von Rospach wrote:
>
>> a semi RFE for mailman: one of my AOL users asked if we could number
>
> What's RFE, again?

sorry. Request for Enhancement.

(it's a feature, not a bug... giggle)

> What is a seed list?

there are some lists that people use, like software developers working 
with their beta sites, where guarantee of reception is a good thing. 
seed lists is a variation of that (at least, that's what we call them)

> Hmm, you could throw in YA X-header, call it X-MailmanSN, and have it
> contain yyyymmdd or the output from time().

tough for AOL, though. it throws out a lot of that stuff. The AOL 
person suggested putting it in the subject line flag area (as in 
[Mailman-Developers:113]), which is as good as anything.


>
> -- 
> Satya. <URL:http://satya.virtualave.net/> I need a job!
> Perl, Apache, Linux, C. http://www-scf.usc.edu/~phanse/resume.pdf
> As I said before, I never repeat myself.
>
>
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers@python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
>
-- 
Chuq Von Rospach, Architech
chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/

The Cliff's Notes Cliff's Notes on Hamlet:
     And they all died happily ever after


From spacey-mailman at lenin.nu  Thu Dec  5 05:21:37 2002
From: spacey-mailman at lenin.nu (Peter C. Norton)
Date: Wed, 4 Dec 2002 21:21:37 -0800
Subject: [Mailman-Developers] not quite about mailman -- AOL data losses.
In-Reply-To: <A5B60502-0810-11D7-9439-0003934516A8@plaidworks.com>
References: <Pine.LNX.4.21.0212042102180.22588-100000@gort.cjb.net>
	<A5B60502-0810-11D7-9439-0003934516A8@plaidworks.com>
Message-ID: <20021205052137.GB1603@lenin.nu>

On Wed, Dec 04, 2002 at 09:16:02PM -0800, Chuq Von Rospach wrote:
> >Hmm, you could throw in YA X-header, call it X-MailmanSN, and have it
> >contain yyyymmdd or the output from time().
> 
> tough for AOL, though. it throws out a lot of that stuff. The AOL 
> person suggested putting it in the subject line flag area (as in 
> [Mailman-Developers:113]), which is as good as anything.

ezmlm throws the message id into the envelope sender as part of the
VERP - or as part of the crypto hash that is in the VERP.  I forget
which.  That's something that even AOL can't screw with.

-Peter

-- 
The 5 year plan:
In five years we'll make up another plan.
Or just re-use this one.

From barry at python.org  Thu Dec  5 05:47:03 2002
From: barry at python.org (Barry A. Warsaw)
Date: Thu, 5 Dec 2002 00:47:03 -0500
Subject: [Mailman-Developers] not quite about mailman -- AOL data losses.
References: <C2A4F8FC-0805-11D7-9439-0003934516A8@plaidworks.com>
Message-ID: <15854.59479.84870.715485@gargle.gargle.HOWL>


>>>>> "CVR" == Chuq Von Rospach <chuqui@plaidworks.com> writes:

    CVR> a semi RFE for mailman: one of my AOL users asked if we could
    CVR> number messages going out. I think under some circumstances,
    CVR> that might not be a bad idea. Not just for unreliable feeds,
    CVR> but for things like seed lists or other lists where
    CVR> reliablility is crucial... But not for 2.1....

There's a patch on SF to do something like this IIRC.  Perhaps from
Tokio Kikuchi?  I deferred it so it's probably in the 2.2/3.0 group,
but I'm too tired right now to search for it.

-Barry

From noreply at sourceforge.net  Thu Dec  5 05:52:07 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed, 04 Dec 2002 21:52:07 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-648607 ] bin/arch crash: '_mlist' still missing
Message-ID: <E18Jovf-0002IC-00@sc8-sf-web1.sourceforge.net>

Bugs item #648607, was opened at 2002-12-04 15:54
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=648607&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: bin/arch crash: '_mlist' still missing

Initial Comment:
Even with the latest CVS, bin/arch still sometimes crashes with an AttributeError from '_mlist'.  Here's my traceback:

Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1247, in update_article
    f.write(article.as_html())
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 411, in as_html
    emailurl = self._mlist.GetListEmail()
AttributeError: Article instance has no attribute '_mlist'


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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-04 17:43

Message:
Logged In: YES 
user_id=12800

Ouch!  My ass!  

Thanks Greg, I'll apply this later tonight.


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

Comment By: Greg Ward (gward)
Date: 2002-12-04 17:42

Message:
Logged In: YES 
user_id=14422

Patch attached.  Barry, you're gonna kick yourself.


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

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

From noreply at sourceforge.net  Thu Dec  5 05:53:34 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed, 04 Dec 2002 21:53:34 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-648604 ] Crash from "article file missing" error
Message-ID: <E18Jox4-0005O8-00@sc8-sf-web4.sourceforge.net>

Bugs item #648604, was opened at 2002-12-04 15:51
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=648604&group_id=103

Category: None
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Crash from "article file missing" error

Initial Comment:
If I playfully delete the HTML version of a message and then re-run bin/arch, it crashes:

$ rm -f archives/private/mems-talk/2001-July/005007.html

$ /bin/arch mems-talk
#00000 <E15QYR8-0006UV-00@ute.cnri.reston.va.us>
figuring article archives
2001-July
Updating index files for archive [2001-July]
  Date
  Subject
  Author
  Thread
Computing threaded index
Updating HTML for article 8891
Updating HTML for article 8899
Updating HTML for article 8900
Updating HTML for article 8901
Updating HTML for article 8902
Updating HTML for article 8903
Updating HTML for article 8904
Updating HTML for article 5007
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1238, in update_article
    self.message(_("article file %s is missing!")
TypeError: format requires a mapping

To my embarassment, I can't make this simple %s work at all!  Must be some funky I18N thing.  If I remove the _() from the format string, it works.



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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-05 00:53

Message:
Logged In: YES 
user_id=12800

It's an i18n thing.  Strings wrapped in _() can't have bare
%s's, they have to be %(name)s substitutions.

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

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

From tkikuchi at is.kochi-u.ac.jp  Thu Dec  5 06:02:27 2002
From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi)
Date: Thu, 05 Dec 2002 15:02:27 +0900
Subject: [Mailman-Developers] not quite about mailman -- AOL data losses.
References: <C2A4F8FC-0805-11D7-9439-0003934516A8@plaidworks.com>
	<15854.59479.84870.715485@gargle.gargle.HOWL>
Message-ID: <3DEEEBF3.5080500@is.kochi-u.ac.jp>


>     CVR> a semi RFE for mailman: one of my AOL users asked if we could
>     CVR> number messages going out. I think under some circumstances,
>     CVR> that might not be a bad idea. Not just for unreliable feeds,
>     CVR> but for things like seed lists or other lists where
>     CVR> reliablility is crucial... But not for 2.1....
> 
> There's a patch on SF to do something like this IIRC.  Perhaps from
> Tokio Kikuchi?  I deferred it so it's probably in the 2.2/3.0 group,
> but I'm too tired right now to search for it.

Yes, it (the patch) is out there for a few month now.
http://sourceforge.net/tracker/index.php?func=detail&aid=601117&group_id=103&atid=300103

You may need to adjust a bit by hand for the latest cvs.
I will try to update if I have time.

-- 
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/


From noreply at sourceforge.net  Thu Dec  5 06:04:59 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed, 04 Dec 2002 22:04:59 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-648604 ] Crash from "article file missing" error
Message-ID: <E18Jp87-0005eA-00@sc8-sf-web4.sourceforge.net>

Bugs item #648604, was opened at 2002-12-04 15:51
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=648604&group_id=103

Category: None
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Crash from "article file missing" error

Initial Comment:
If I playfully delete the HTML version of a message and then re-run bin/arch, it crashes:

$ rm -f archives/private/mems-talk/2001-July/005007.html

$ /bin/arch mems-talk
#00000 <E15QYR8-0006UV-00@ute.cnri.reston.va.us>
figuring article archives
2001-July
Updating index files for archive [2001-July]
  Date
  Subject
  Author
  Thread
Computing threaded index
Updating HTML for article 8891
Updating HTML for article 8899
Updating HTML for article 8900
Updating HTML for article 8901
Updating HTML for article 8902
Updating HTML for article 8903
Updating HTML for article 8904
Updating HTML for article 5007
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1238, in update_article
    self.message(_("article file %s is missing!")
TypeError: format requires a mapping

To my embarassment, I can't make this simple %s work at all!  Must be some funky I18N thing.  If I remove the _() from the format string, it works.



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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-05 00:53

Message:
Logged In: YES 
user_id=12800

It's an i18n thing.  Strings wrapped in _() can't have bare
%s's, they have to be %(name)s substitutions.

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

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

From noreply at sourceforge.net  Thu Dec  5 15:21:07 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu, 05 Dec 2002 07:21:07 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-649007 ] arch: LookupError: unknown encoding
Message-ID: <E18JxoJ-00031o-00@sc8-sf-web2.sourceforge.net>

Bugs item #649007, was opened at 2002-12-05 10:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649007&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: arch: LookupError: unknown encoding

Initial Comment:
bin/arch is crashing with the following traceback:

Updating HTML for article 27
Pickling archive state into /usr/local/mailman/archives/private/mems-talk/pipermail.pck
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 174, in main
    archiver.processUnixMailbox(fp, start, end)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 557, in processUnixMailbox
    a = self._makeArticle(m, self.sequence)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 630, in _makeArticle
    mlist=self.maillist)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 261, in __init__
    self.check_header_charsets(charset)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 354, in check_header_charsets
    author, a_charset = self.decode_charset(self.author)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 383, in decode_charset
    h = make_header(pairs, 99999)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 123, in make_header
    h.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append
    ustr = unicode(s, incodec)
LookupError: unknown encoding: gb2312

Oddly, it appears that the message causing the problem has no mention of gb2312 -- there are some bogus MIME headers in the body that mention big5, though.

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

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

From noreply at sourceforge.net  Thu Dec  5 15:29:18 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu, 05 Dec 2002 07:29:18 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-649011 ] arch crashes with custom
	mbox
Message-ID: <E18JxwD-00080f-00@sc8-sf-web3.sourceforge.net>

Bugs item #649011, was opened at 2002-12-05 10:29
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649011&group_id=103

Category: None
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: arch crashes with custom mbox

Initial Comment:
If I run bin/arch with a custom mbox file, it appears to still use the standard mbox file for something -- because it crashes if I have removed the standard mbox:

$ rm archives/private/mems-talk.mbox/mems-talk.mbox
$ ./bin/arch mems-talk archives/private/mems-talk.mbox/mems-talk.mbox.reduced
[...]
Computing threaded index
Updating HTML for article 4
Updating HTML for article 15
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 305, in close
    self.write_TOC()
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1048, in write_TOC
    toc.write(self.html_TOC())
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 705, in html_TOC
    d = {"listname": mlist.real_name,
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 103, in sizeof
    size = os.path.getsize(filename)
  File "/www/plat/python2.2.2/lib/python2.2/posixpath.py", line 139, in getsize
    st = os.stat(filename)
OSError: [Errno 2] No such file or directory: '/usr/local/mailman/archives/private/mems-talk.mbox/mems-talk.mbox'


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

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

From noreply at sourceforge.net  Thu Dec  5 15:29:31 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu, 05 Dec 2002 07:29:31 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-649007 ] arch: LookupError: unknown encoding
Message-ID: <E18JxwR-00081L-00@sc8-sf-web3.sourceforge.net>

Bugs item #649007, was opened at 2002-12-05 10:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649007&group_id=103

Category: None
>Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: arch: LookupError: unknown encoding

Initial Comment:
bin/arch is crashing with the following traceback:

Updating HTML for article 27
Pickling archive state into /usr/local/mailman/archives/private/mems-talk/pipermail.pck
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 174, in main
    archiver.processUnixMailbox(fp, start, end)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 557, in processUnixMailbox
    a = self._makeArticle(m, self.sequence)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 630, in _makeArticle
    mlist=self.maillist)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 261, in __init__
    self.check_header_charsets(charset)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 354, in check_header_charsets
    author, a_charset = self.decode_charset(self.author)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 383, in decode_charset
    h = make_header(pairs, 99999)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 123, in make_header
    h.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append
    ustr = unicode(s, incodec)
LookupError: unknown encoding: gb2312

Oddly, it appears that the message causing the problem has no mention of gb2312 -- there are some bogus MIME headers in the body that mention big5, though.

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

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

From noreply at sourceforge.net  Thu Dec  5 15:33:18 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu, 05 Dec 2002 07:33:18 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-649007 ] arch: LookupError: unknown encoding
Message-ID: <E18Jy06-0008A5-00@sc8-sf-web3.sourceforge.net>

Bugs item #649007, was opened at 2002-12-05 10:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649007&group_id=103

Category: None
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: arch: LookupError: unknown encoding

Initial Comment:
bin/arch is crashing with the following traceback:

Updating HTML for article 27
Pickling archive state into /usr/local/mailman/archives/private/mems-talk/pipermail.pck
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 174, in main
    archiver.processUnixMailbox(fp, start, end)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 557, in processUnixMailbox
    a = self._makeArticle(m, self.sequence)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 630, in _makeArticle
    mlist=self.maillist)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 261, in __init__
    self.check_header_charsets(charset)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 354, in check_header_charsets
    author, a_charset = self.decode_charset(self.author)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 383, in decode_charset
    h = make_header(pairs, 99999)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 123, in make_header
    h.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append
    ustr = unicode(s, incodec)
LookupError: unknown encoding: gb2312

Oddly, it appears that the message causing the problem has no mention of gb2312 -- there are some bogus MIME headers in the body that mention big5, though.

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

>Comment By: Greg Ward (gward)
Date: 2002-12-05 10:33

Message:
Logged In: YES 
user_id=14422

Ahh!  Ignore my last paragraph: the offending message yesterday was one with "big5" mentioned in a MIME header.  The one causing problems today has 1) gb2312 in the Subject and 2) binary junk in a footer supplied by yahoo.com.cn.


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

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

From noreply at sourceforge.net  Thu Dec  5 15:35:56 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu, 05 Dec 2002 07:35:56 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-649007 ] bin/arch crash: unknown encoding
Message-ID: <E18Jy2e-0008G4-00@sc8-sf-web3.sourceforge.net>

Bugs item #649007, was opened at 2002-12-05 10:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649007&group_id=103

Category: None
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
>Summary: bin/arch crash: unknown encoding

Initial Comment:
bin/arch is crashing with the following traceback:

Updating HTML for article 27
Pickling archive state into /usr/local/mailman/archives/private/mems-talk/pipermail.pck
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 174, in main
    archiver.processUnixMailbox(fp, start, end)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 557, in processUnixMailbox
    a = self._makeArticle(m, self.sequence)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 630, in _makeArticle
    mlist=self.maillist)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 261, in __init__
    self.check_header_charsets(charset)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 354, in check_header_charsets
    author, a_charset = self.decode_charset(self.author)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 383, in decode_charset
    h = make_header(pairs, 99999)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 123, in make_header
    h.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append
    ustr = unicode(s, incodec)
LookupError: unknown encoding: gb2312

Oddly, it appears that the message causing the problem has no mention of gb2312 -- there are some bogus MIME headers in the body that mention big5, though.

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

Comment By: Greg Ward (gward)
Date: 2002-12-05 10:33

Message:
Logged In: YES 
user_id=14422

Ahh!  Ignore my last paragraph: the offending message yesterday was one with "big5" mentioned in a MIME header.  The one causing problems today has 1) gb2312 in the Subject and 2) binary junk in a footer supplied by yahoo.com.cn.


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

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

From noreply at sourceforge.net  Thu Dec  5 15:49:01 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu, 05 Dec 2002 07:49:01 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-649007 ] bin/arch crash: unknown encoding
Message-ID: <E18JyFJ-0000Kt-00@sc8-sf-web3.sourceforge.net>

Bugs item #649007, was opened at 2002-12-05 10:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649007&group_id=103

Category: None
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: bin/arch crash: unknown encoding

Initial Comment:
bin/arch is crashing with the following traceback:

Updating HTML for article 27
Pickling archive state into /usr/local/mailman/archives/private/mems-talk/pipermail.pck
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 174, in main
    archiver.processUnixMailbox(fp, start, end)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 557, in processUnixMailbox
    a = self._makeArticle(m, self.sequence)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 630, in _makeArticle
    mlist=self.maillist)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 261, in __init__
    self.check_header_charsets(charset)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 354, in check_header_charsets
    author, a_charset = self.decode_charset(self.author)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 383, in decode_charset
    h = make_header(pairs, 99999)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 123, in make_header
    h.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append
    ustr = unicode(s, incodec)
LookupError: unknown encoding: gb2312

Oddly, it appears that the message causing the problem has no mention of gb2312 -- there are some bogus MIME headers in the body that mention big5, though.

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

>Comment By: Greg Ward (gward)
Date: 2002-12-05 10:49

Message:
Logged In: YES 
user_id=14422

Another easy fix, I think -- uploading patch.

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

Comment By: Greg Ward (gward)
Date: 2002-12-05 10:33

Message:
Logged In: YES 
user_id=14422

Ahh!  Ignore my last paragraph: the offending message yesterday was one with "big5" mentioned in a MIME header.  The one causing problems today has 1) gb2312 in the Subject and 2) binary junk in a footer supplied by yahoo.com.cn.


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

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

From noreply at sourceforge.net  Thu Dec  5 15:56:43 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu, 05 Dec 2002 07:56:43 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-649037 ] Attachments not working.
Message-ID: <E18JyMl-000575-00@sc8-sf-web1.sourceforge.net>

Bugs item #649037, was opened at 2002-12-05 15:56
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649037&group_id=103

Category: Pipermail
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Patrick Finnerty (finnertyp)
Assigned to: Nobody/Anonymous (nobody)
Summary: Attachments not working.

Initial Comment:
Platform: TRU64 v5.1a

I'm using Mailman v2.1b5 and have noticed the following problem when archiving attached files.

MS-Excel documents are not getting properly archived. Well, the file that is posted appears unharmed in the ...archive/<list>/attachments/... directory on the server, but it isn't available as an attachment from the posted message. A few lines are garbage are there instead.

MS Word, Powerpoint, PDF files are OK from what I've tested although I've found a similar problem to above with a Word document when using 'arch' on an existing mailbox.

Ie, arch creates the html pages OK and extracts the attachments OK, but a Word document isn't available from the message. 

- Pat.

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

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

From noreply at sourceforge.net  Thu Dec  5 18:59:57 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu, 05 Dec 2002 10:59:57 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-649112 ] "#" in mail address confuses mailman
Message-ID: <E18K1E5-0004Iq-00@sc8-sf-web1.sourceforge.net>

Bugs item #649112, was opened at 2002-12-05 19:59
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649112&group_id=103

Category: Web/CGI
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Fredrik Lundh (effbot)
Assigned to: Nobody/Anonymous (nobody)
Summary: "#" in mail address confuses mailman

Initial Comment:
someone recently managed to subscribe himself to
the python.org image-sig mailing list, using an add-
ress looking a bit like this one:

    prefix#user@some.com

unfortunately, the web interface doesn't escape the
"#" character, so the web pages for this user cannot
be accessed:

    http://mail.python.org/mailman/options/image-
sig/prefix#user--at--some.com

(the browser strips off the "#" and everything after
it before sending the URL to mailman...).

I'm not sure what version python.org is running,
but I suspect that the Barry person might be able
to figure that out.

cheers /F


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

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

From satyap at satya.virtualave.net  Thu Dec  5 20:34:28 2002
From: satyap at satya.virtualave.net (Satya)
Date: Thu, 5 Dec 2002 12:34:28 -0800 (PST)
Subject: [Mailman-Developers] not quite about mailman -- AOL data losses.
In-Reply-To: <A5B60502-0810-11D7-9439-0003934516A8@plaidworks.com>
Message-ID: <Pine.LNX.4.21.0212051229570.26749-100000@gort.cjb.net>

On Dec 4, 2002 at 21:16, Chuq Von Rospach wrote:

[X-headers]
>tough for AOL, though. it throws out a lot of that stuff. The AOL 

Sheesh, if they're not going to do email like everyone else, they're
not part of the internet. I mean, pulling out headers, come on?
Dropping email silently, when *not* blackholed? ::gibbers::

>person suggested putting it in the subject line flag area (as in 
>[Mailman-Developers:113]), which is as good as anything.

Okay, but that bloats the subject line more, and will get flames from
people who filter on "[listname]" instead of "List-Id:.*listname".
Whatever. As long as you don't mess with List-Id, I don't care :-\.

How about adding a line just after the headers, in the body, saying
"message x of y"? Or in the footer or wherever Mailman inserts stuff.

-- 
Satya. <URL:http://satya.virtualave.net/> I need a job!
Perl, Apache, Linux, C. http://www-scf.usc.edu/~phanse/resume.pdf
WWW: World Wide Wait


From barry at python.org  Thu Dec  5 20:41:22 2002
From: barry at python.org (Barry A. Warsaw)
Date: Thu, 5 Dec 2002 15:41:22 -0500
Subject: [Mailman-Developers] not quite about mailman -- AOL data losses.
References: <A5B60502-0810-11D7-9439-0003934516A8@plaidworks.com>
	<Pine.LNX.4.21.0212051229570.26749-100000@gort.cjb.net>
Message-ID: <15855.47602.394837.937996@gargle.gargle.HOWL>


>>>>> "S" == Satya  <satyap@satya.virtualave.net> writes:

    S> How about adding a line just after the headers, in the body,
    S> saying "message x of y"? Or in the footer or wherever Mailman
    S> inserts stuff.

That wouldn't be too hard to wedge in.  I have some thoughts about how
to do more personalization from data driven from a database, so
post-2.1 I'll upload some thoughts on that.

-Barry

From noreply at sourceforge.net  Thu Dec  5 21:15:30 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu, 05 Dec 2002 13:15:30 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-649158 ] unwanted space
	(cosmetic)
Message-ID: <E18K3LG-0001M7-00@sc8-sf-web1.sourceforge.net>

Bugs item #649158, was opened at 2002-12-05 22:15
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649158&group_id=103

Category: Web/CGI
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: unwanted space (cosmetic)

Initial Comment:
The attached patch removes a single space from a string.
The space is between a word and a semi-colon, which is 
bad (at least in italian).


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

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

From claw at kanga.nu  Thu Dec  5 22:26:54 2002
From: claw at kanga.nu (J C Lawrence)
Date: Thu, 05 Dec 2002 14:26:54 -0800
Subject: [Mailman-Developers] not quite about mailman -- AOL data losses. 
In-Reply-To: Message from Satya <satyap@satya.virtualave.net> 
	<Pine.LNX.4.21.0212042102180.22588-100000@gort.cjb.net> 
References: <Pine.LNX.4.21.0212042102180.22588-100000@gort.cjb.net> 
Message-ID: <26637.1039127214@kanga.nu>

On Wed, 4 Dec 2002 21:12:10 -0800 (PST) 
satyap  <Satya> wrote:

> Hmm, you could throw in YA X-header, call it X-MailmanSN, and have it
> contain yyyymmdd or the output from time().

Given either Postfix or Exim, this would be fairly easy to add at a
system level filter.

-- 
J C Lawrence                
---------(*)                Satan, oscillate my metallic sonatas. 
claw@kanga.nu               He lived as a devil, eh?		  
http://www.kanga.nu/~claw/  Evil is a name of a foeman, as I live.


From noreply at sourceforge.net  Fri Dec  6 07:29:20 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu, 05 Dec 2002 23:29:20 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-621689 ] Subscribe requests dropped from admin db
Message-ID: <E18KCvI-0004lx-00@sc8-sf-web3.sourceforge.net>

Bugs item #621689, was opened at 2002-10-10 20:10
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_id=103

Category: (un)subscribing
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 7
Submitted By: Mark Dadgar (mdadgar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Subscribe requests dropped from admin db

Initial Comment:
Occasionally, subscribe requests (via the web page) to a list that 
requires moderator approval for subscriptions never make it to the 
admin db for that list.  They are listed in the subscribe log file, but 
never show up on the admin db page.

Log file entries look like this:

Oct 10 18:43:43 2002 (31168) eventmasters: pending   
XXXXXX.swfla.rr.com

But the admin db page for the list shows no outstanding issues.

I have verified that there was an actual subscription request 
behind this log entry.

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

>Comment By: Mark Dadgar (mdadgar)
Date: 2002-12-05 23:29

Message:
Logged In: YES 
user_id=598228

Ok, I verified that it's still a problem under 2.1b5 with the htdig and 
indexing patches.

It's a real drag, too.  :(

Please let me know if you need more debug info.

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

Comment By: Mark Dadgar (mdadgar)
Date: 2002-11-21 22:08

Message:
Logged In: YES 
user_id=598228

Unfortunately, it's still occurring under 2.1b4.  

I'll check it under 2.1b5 as soon as the patches for htdig integration are 
released, as I need those to implement.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-10-22 07:11

Message:
Logged In: YES 
user_id=12800

I'm going to defer this one until 2.1b4 goes out.  I've
fixed some related bugs in cvs, so hopefully this will be
fixed in the new version.

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

Comment By: Mark Dadgar (mdadgar)
Date: 2002-10-20 10:14

Message:
Logged In: YES 
user_id=598228

Sorry - I'm running 2.1b3.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-10-20 08:48

Message:
Logged In: YES 
user_id=12800

What version of Mailman are you using.  It's import to know
the exact version, i.e. 2.1beta3, or if you're running from
cvs.  A lot of these problems have been fixed in cvs, which
will soon be released as 2.1 beta 4.

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

Comment By: Mark Dadgar (mdadgar)
Date: 2002-10-10 21:29

Message:
Logged In: YES 
user_id=598228

I just verified, by cat'ing pending.pck, that the appropriate changes 
seem to be in there.  But the web interface never picks them up.

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

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

From michael.kallas at web.de  Fri Dec  6 08:29:55 2002
From: michael.kallas at web.de (Michael Kallas)
Date: Fri, 6 Dec 2002 09:29:55 +0100
Subject: [Mailman-Developers] Legal trouble in Germany
Message-ID: <200212060829.gB68TtX26258@mailgate5.cinetic.de>

Hi,

This has been considered illegal by the Landgericht Berlin:
> Mailing list subscription confirmation notice for mailing list
> Mailman-Users
>=20
> We have received a request from [IP address] for subscription of your
> email address, "michael.kallas@web.de", to the
> mailman-users@python.org mailing list.
[...]
This court decided (search Google for "16 O 515/02") that it is considered=

to be "unwanted advertisement" (UCE, SPAM) if a businessman gets a mail
in which he is asked whether he wants to be subscribed to a newsletter.
It would be the task of the newsletter administrator to prove that the=20
other person really =5Fwanted=5F to subscribe.
Similar rights could be used for private persons, so this affects indeed a=
ll
mailing lists / newsletters.

Should this judgement be shared by other german courts, newsletter admins
using mailman or any similar software would have to fear a wave of
dissuasions.

Best regards
Michael Kallas
--=20
All thoughts are free, Who can ever guess them=3F
Die Gedanken sind frei, Wer kann sie erraten=3F

=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F
Angst vor Viren=3F Nicht bei WEB.DE FreeMail. Hier k=F6nnen Sie jeden
Dateianhang auf Viren pr=FCfen. http://freemail.web.de/features/=3Fmc=3D021157


From sb.list at sb.org  Fri Dec  6 14:14:58 2002
From: sb.list at sb.org (Stonewall Ballard)
Date: Fri, 06 Dec 2002 09:14:58 -0500
Subject: [Mailman-Developers] Legal trouble in Germany
In-Reply-To: <200212060829.gB68TtX26258@mailgate5.cinetic.de>
Message-ID: <BA161B12.51AC8%sb.list@sb.org>

Sometimes law gets away from reality.

So how would someone confirm a subscription if it's illegal to email them
before they confirm it?

 - Stoney

On 12/6/02 3:29 AM, "Michael Kallas" <michael.kallas@web.de> wrote:

> Hi,
> 
> This has been considered illegal by the Landgericht Berlin:
>> Mailing list subscription confirmation notice for mailing list
>> Mailman-Users
>> 
>> We have received a request from [IP address] for subscription of your
>> email address, "michael.kallas@web.de", to the
>> mailman-users@python.org mailing list.
> [...]
> This court decided (search Google for "16 O 515/02") that it is considered
> to be "unwanted advertisement" (UCE, SPAM) if a businessman gets a mail
> in which he is asked whether he wants to be subscribed to a newsletter.
> It would be the task of the newsletter administrator to prove that the
> other person really _wanted_ to subscribe.
> Similar rights could be used for private persons, so this affects indeed all
> mailing lists / newsletters.
> 
> Should this judgement be shared by other german courts, newsletter admins
> using mailman or any similar software would have to fear a wave of
> dissuasions.
> 
> Best regards
> Michael Kallas


From bigdog at dogpound.vnet.net  Fri Dec  6 17:10:28 2002
From: bigdog at dogpound.vnet.net (Matthew Davis)
Date: Fri, 6 Dec 2002 12:10:28 -0500
Subject: [Mailman-Developers] Legal trouble in Germany
In-Reply-To: <200212060829.gB68TtX26258@mailgate5.cinetic.de>;
	from michael.kallas@web.de on Fri, Dec 06, 2002 at 09:29:55AM +0100
References: <200212060829.gB68TtX26258@mailgate5.cinetic.de>
Message-ID: <20021206121028.A13625@dogpound.vnet.net>

* Michael Kallas (michael.kallas@web.de) wrote:
> This has been considered illegal by the Landgericht Berlin:
> > Mailing list subscription confirmation notice for mailing list
> > Mailman-Users
> > 
> > We have received a request from [IP address] for subscription of your
> > email address, "michael.kallas@web.de", to the
> > mailman-users@python.org mailing list.
> [...]
> This court decided (search Google for "16 O 515/02") that it is considered
> to be "unwanted advertisement" (UCE, SPAM) if a businessman gets a mail
> in which he is asked whether he wants to be subscribed to a newsletter.
> It would be the task of the newsletter administrator to prove that the 
> other person really _wanted_ to subscribe.
> Similar rights could be used for private persons, so this affects indeed all
> mailing lists / newsletters.


So turn off the confirmation so you assume if the user clicks the subscribe, they _want_ to be subscribed.

----------------------------------------------
| Matthew Davis /\ http://dogpound.vnet.net/ |
|--------------------------------------------|
| Friday, December 06, 2002 / 12:09PM      |
----------------------------------------------
Futuristic: It only runs on the next-generation supercomputer.

From kiko at async.com.br  Fri Dec  6 14:22:48 2002
From: kiko at async.com.br (Christian Reis)
Date: Fri, 6 Dec 2002 12:22:48 -0200
Subject: [Mailman-Developers] [mailman@async.com.br: cron:
	/usr/local/bin/python -S /home/mailman/cron/senddigests]
Message-ID: <20021206122248.F11879@blackjesus.async.com.br>


A set of bugs bit me today. Basically, the steps to get to this point
were:

- I created a mailing list.
- I did *not* add the aliases.
- I subscribed myself using the mail interface (digest off)
- I received the confirmation email. When using the HTML link to confirm
  (since the aliases were not added yet, and I realized it), I got the
  error below. 
  
- When confirming it via reply (just after adding the aliases) I now
  always get the the invalid confirmation string message.

The HTML error:

    Bug in Mailman version 2.1b5

    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/mailman/scripts/driver", line 87, in run_main
        main()
      File "/home/mailman/Mailman/Cgi/confirm.py", line 110, in main
        subscription_confirm(mlist, doc, cookie, cgidata)
      File "/home/mailman/Mailman/Cgi/confirm.py", line 326, in
    subscription_confirm
        op, addr, pw, digest, lang = mlist.ProcessConfirmation(
      File "/home/mailman/Mailman/MailList.py", line 1080, in
    ProcessConfirmation
        self.ApprovedAddMember(userdesc)
      File "/home/mailman/Mailman/MailList.py", line 889, in
    ApprovedAddMember
        digest, text)
      File "/home/mailman/Mailman/Deliverer.py", line 69, in
    SendSubscribeAck
        text, pluser)
      File "/home/mailman/Mailman/Message.py", line 203, in __init__
        self['Subject'] = Header(subject, charset, header_name='Subject')
      File "/home/mailman/pythonlib/email/Header.py", line 164, in __init__
        self.append(s, charset)
      File "/home/mailman/pythonlib/email/Header.py", line 230, in append
        ustr = unicode(s, incodec)
    UnicodeError: ASCII decoding error: ordinal not in range(128)



    Python information:

    Variable Value
    sys.version 2.1.1 (#6, Jun 26 2002, 10:03:21) [GCC egcs-2.91.66
    19990314/Linux (egcs-1.1.2 release)]
    sys.executable /usr/local/bin/python
    sys.prefix /usr/local
    sys.exec_prefix /usr/local
    sys.path /usr/local
    sys.platform linux2

    Environment variables:

    Variable Value
    DOCUMENT_ROOT /mondo/htdocs/async
    SERVER_ADDR 200.206.134.238
    HTTP_ACCEPT_ENCODING gzip, deflate, compress;q=0.9
    REMOTE_HOST 200-158-184-99.dsl.telesp.net.br
    CONTENT_TYPE application/x-www-form-urlencoded
    PATH_TRANSLATED /mondo/htdocs/async/consave-d
    REMOTE_ADDR 200.158.184.99
    SERVER_SOFTWARE Apache/1.3.27 (Unix) mod_filter/1.1 mod_ssl/2.8.12
    OpenSSL/0.9.6g PHP/4.2.2
    GATEWAY_INTERFACE CGI/1.1
    HTTP_COOKIE SITESERVER=ID=e58326c5509211ccd3008d3f52cc9967;
    spam+admin=2802000000691053ef3d732800000063663562336334316435363833663662353233613665646233393932343462363338333333313735
    HTTP_ACCEPT_LANGUAGE en-us, en;q=0.50
    REMOTE_PORT 36399
    SERVER_PORT 80
    HTTP_CONNECTION keep-alive
    HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2)
    Gecko/20021126
    HTTP_ACCEPT_CHARSET ISO-8859-1, utf-8;q=0.66, *;q=0.66
    HTTP_ACCEPT
    text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1
    REQUEST_URI /mailman/confirm/consave-d
    QUERY_STRING
    SERVER_PROTOCOL HTTP/1.1
    HTTP_KEEP_ALIVE 300
    HTTP_HOST www.async.com.br
    REQUEST_METHOD POST
    SERVER_SIGNATURE
    Apache/1.3.27 Server at www.async.com.br Port 80
    SCRIPT_NAME /mailman/confirm
    SERVER_ADMIN kiko@async.com.br
    SCRIPT_FILENAME /home/mailman/cgi-bin/confirm
    CONTENT_LENGTH 128
    PYTHONPATH /home/mailman
    PATH_INFO /consave-d
    HTTP_REFERER
    http://www.async.com.br/mailman/confirm/consave-d/988bb60b8d7b00155f487b645b887492ff4a041f
    SERVER_NAME www.async.com.br 

This one came in through email to me right now:

----- Forwarded message from GNU Mailman user <mailman@async.com.br> -----

Date: Fri, 6 Dec 2002 12:00:06 -0200
From: GNU Mailman user <mailman@async.com.br>
To: mailman@async.com.br
Subject: cron: /usr/local/bin/python -S /home/mailman/cron/senddigests

Traceback (most recent call last):
  File "/home/mailman/cron/senddigests", line 94, in ?
    main()
  File "/home/mailman/cron/senddigests", line 86, in main
    mlist.send_digest_now()
  File "/home/mailman/Mailman/Digester.py", line 60, in send_digest_now
    ToDigest.send_digests(self, mboxfp)
  File "/home/mailman/Mailman/Handlers/ToDigest.py", line 128, in send_digests
    send_i18n_digests(mlist, mboxfp)
  File "/home/mailman/Mailman/Handlers/ToDigest.py", line 141, in send_i18n_digests
    digestid = _('%(realname)s Digest, Vol %(volume)d, Issue %(issue)d')
  File "/home/mailman/Mailman/i18n.py", line 78, in _
    return _translation.gettext(s) % dict
ValueError: unsupported format character ',' (0x2c) at index 18

----- End forwarded message -----

Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL

From philb at philb.us  Sat Dec  7 06:21:07 2002
From: philb at philb.us (Phil Barnett)
Date: Sat, 7 Dec 2002 01:21:07 -0500
Subject: [Mailman-Developers] Legal trouble in Germany
In-Reply-To: <20021206121028.A13625@dogpound.vnet.net>
References: <200212060829.gB68TtX26258@mailgate5.cinetic.de>
	<20021206121028.A13625@dogpound.vnet.net>
Message-ID: <200212070121.07995.philb@philb.us>

On Friday 06 December 2002 12:10 pm, Matthew Davis wrote:
> * Michael Kallas (michael.kallas@web.de) wrote:
> > This has been considered illegal by the Landgericht Berlin:
> > > Mailing list subscription confirmation notice for mailing list
> > > Mailman-Users
> > >
> > > We have received a request from [IP address] for subscription of yo=
ur
> > > email address, "michael.kallas@web.de", to the
> > > mailman-users@python.org mailing list.
> >
> > [...]
> > This court decided (search Google for "16 O 515/02") that it is
> > considered to be "unwanted advertisement" (UCE, SPAM) if a businessma=
n
> > gets a mail in which he is asked whether he wants to be subscribed to=
 a
> > newsletter. It would be the task of the newsletter administrator to p=
rove
> > that the other person really _wanted_ to subscribe.
> > Similar rights could be used for private persons, so this affects ind=
eed
> > all mailing lists / newsletters.
>
> So turn off the confirmation so you assume if the user clicks the
> subscribe, they _want_ to be subscribed.

So, how do you then prove that it was them and not someone else?

--=20

"Suppose you were an idiot . . . . And suppose you were a member of Congr=
ess .=20
=2E . . but I repeat myself."...Mark Twain

From noreply at sourceforge.net  Sat Dec  7 07:25:36 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri, 06 Dec 2002 23:25:36 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-649158 ] unwanted space
	(cosmetic)
Message-ID: <E18KZLE-0007U7-00@sc8-sf-web4.sourceforge.net>

Bugs item #649158, was opened at 2002-12-05 16:15
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649158&group_id=103

Category: Web/CGI
Group: 2.1 beta
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: unwanted space (cosmetic)

Initial Comment:
The attached patch removes a single space from a string.
The space is between a word and a semi-colon, which is 
bad (at least in italian).


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

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

From noreply at sourceforge.net  Sat Dec  7 07:36:20 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri, 06 Dec 2002 23:36:20 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-649011 ] arch crashes with custom
	mbox
Message-ID: <E18KZVc-0003nL-00@sc8-sf-web1.sourceforge.net>

Bugs item #649011, was opened at 2002-12-05 10:29
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649011&group_id=103

Category: None
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: arch crashes with custom mbox

Initial Comment:
If I run bin/arch with a custom mbox file, it appears to still use the standard mbox file for something -- because it crashes if I have removed the standard mbox:

$ rm archives/private/mems-talk.mbox/mems-talk.mbox
$ ./bin/arch mems-talk archives/private/mems-talk.mbox/mems-talk.mbox.reduced
[...]
Computing threaded index
Updating HTML for article 4
Updating HTML for article 15
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 305, in close
    self.write_TOC()
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1048, in write_TOC
    toc.write(self.html_TOC())
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 705, in html_TOC
    d = {"listname": mlist.real_name,
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 103, in sizeof
    size = os.path.getsize(filename)
  File "/www/plat/python2.2.2/lib/python2.2/posixpath.py", line 139, in getsize
    st = os.stat(filename)
OSError: [Errno 2] No such file or directory: '/usr/local/mailman/archives/private/mems-talk.mbox/mems-talk.mbox'


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 02:36

Message:
Logged In: YES 
user_id=12800

Cheezy fix checked in.  We just catch ENOENT around the
getsize() call and return "size not available" in that case.
 It's too much of a pain to weave the explicit mbox fie name
from bin/arch to html_TOC.


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

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

From noreply at sourceforge.net  Sat Dec  7 07:42:40 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri, 06 Dec 2002 23:42:40 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-649007 ] bin/arch crash: unknown encoding
Message-ID: <E18KZbk-0000bu-00@sc8-sf-web3.sourceforge.net>

Bugs item #649007, was opened at 2002-12-05 10:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649007&group_id=103

>Category: Pipermail
Group: 2.1 beta
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: bin/arch crash: unknown encoding

Initial Comment:
bin/arch is crashing with the following traceback:

Updating HTML for article 27
Pickling archive state into /usr/local/mailman/archives/private/mems-talk/pipermail.pck
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 174, in main
    archiver.processUnixMailbox(fp, start, end)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 557, in processUnixMailbox
    a = self._makeArticle(m, self.sequence)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 630, in _makeArticle
    mlist=self.maillist)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 261, in __init__
    self.check_header_charsets(charset)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 354, in check_header_charsets
    author, a_charset = self.decode_charset(self.author)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 383, in decode_charset
    h = make_header(pairs, 99999)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 123, in make_header
    h.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append
    ustr = unicode(s, incodec)
LookupError: unknown encoding: gb2312

Oddly, it appears that the message causing the problem has no mention of gb2312 -- there are some bogus MIME headers in the body that mention big5, though.

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

Comment By: Greg Ward (gward)
Date: 2002-12-05 10:49

Message:
Logged In: YES 
user_id=14422

Another easy fix, I think -- uploading patch.

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

Comment By: Greg Ward (gward)
Date: 2002-12-05 10:33

Message:
Logged In: YES 
user_id=14422

Ahh!  Ignore my last paragraph: the offending message yesterday was one with "big5" mentioned in a MIME header.  The one causing problems today has 1) gb2312 in the Subject and 2) binary junk in a footer supplied by yahoo.com.cn.


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

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

From noreply at sourceforge.net  Sat Dec  7 08:08:13 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 00:08:13 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-649037 ] Attachments not working.
Message-ID: <E18Ka0T-0000p5-00@sc8-sf-web2.sourceforge.net>

Bugs item #649037, was opened at 2002-12-05 10:56
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649037&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Patrick Finnerty (finnertyp)
Assigned to: Nobody/Anonymous (nobody)
Summary: Attachments not working.

Initial Comment:
Platform: TRU64 v5.1a

I'm using Mailman v2.1b5 and have noticed the following problem when archiving attached files.

MS-Excel documents are not getting properly archived. Well, the file that is posted appears unharmed in the ...archive/<list>/attachments/... directory on the server, but it isn't available as an attachment from the posted message. A few lines are garbage are there instead.

MS Word, Powerpoint, PDF files are OK from what I've tested although I've found a similar problem to above with a Word document when using 'arch' on an existing mailbox.

Ie, arch creates the html pages OK and extracts the attachments OK, but a Word document isn't available from the message. 

- Pat.

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 03:08

Message:
Logged In: YES 
user_id=12800

I think the problem you're seeing is that with Excel
spreadsheets, your browser is displaying the binary data to
you instead of offering to save it to disk, as it does for
Powerpoint files.

Here's the problem: we don't trust the file extension on
attachments, but instead, we look the Content-Type up in
Python's mimetypes module to find the file extension that we
use when saving the attachment to a file. 
application/vnd.ms-excel are reversed mapped to .xlb
extension but your browser probably doesn't know what to do
with .xlb

I think there's little Mailman can do here.  I suggest
right-clicking on the link to save it to a file.

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

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

From liam at routt.net  Sat Dec  7 07:43:20 2002
From: liam at routt.net (Liam Routt)
Date: Sat, 7 Dec 2002 18:43:20 +1100
Subject: [Mailman-Developers] Unable to install 2.1b5 on RedHat 7.3
Message-ID: <20021207074320.GA30458@routt.net>

I'm new to the list (although I've been using 2.0x for a while now).

I'm trying to install 2.1b5 on a RedHat 7.3 system, and having no luck. 
Some pertinent info:

RedHat 7.3 i386
Comes with python 1.5.2 installed
also installed python2 (python 2.2)
Have qmail installed in place of sendmail (although sendmail rpm is in 
place)

The error I'm getting is one I have seen mention of before in the 
archives:

Compiling /home/mailman/Mailman/versions.py ...
Traceback (most recent call last):
  File "bin/update", line 44, in ?
    import paths
  File "bin/paths.py", line 55, in ?
    import japanese
ImportError: No module named japanese

The solution was supposed to have to do with setting the permissions 
pythonlib and its contents, I believe. I fiddled around trying to make 
sure that was being done, but noticed that pythonlib was empty.

That ends up being the actual problem I'm having. The packages which are 
supposed to be in pythonlib are not put there. The reason is buried back 
in the earlier part of the installation (and I don't have the output to 
hand at the moment). In short, the misc/Makefile.in (where the packages 
are to be installed and the permissons set correctly) is unable to 
recognize my python installation.

At first I was leaving things as they installed on my machine, with python 
1.5.2 in the path as "python" and using the --with-python directive to 
point to "python2". When I worked out what was going wrong I mv'd python 
out of the way and put a link to "python2" from "python" and tried again, 
but it had the same effect (ie it was unable to recognize the python 2.2 
installation). After that I put python 1.5.2 back where it belonged and 
tried the installation without the --with-python, and that had the same 
results.

What I recall is that it was looking for a particular file (a config file 
of some sort) in a directory that does exist. The file is not there, 
although a lot of other python packages and files are.

Things to consider:

1. The failure did not halt the install, although it did make it 
impossible for it to complete. But the relevant messages were *way* back, 
and probably meaningless to a non-technical person, at a guess.

2. How should mailman recognize this python 2.2 installation as used in 
RedHat 7.3 (and earlier, at least). Without removing my older python 
(which there are a lot of apparent dependencies on) and installing from 
the src, I can't see any other way to get python 2.2 easily installed.

3. Any suggestions what I should try?

Take care,

Liam
--
Liam Routt                                               liam@routt.net
Darcsyde Productions                     http://www.routt.net/Caligari/

        -- still waiting for the Absolute Destiny Apocalypse --

From barry at python.org  Sat Dec  7 14:45:42 2002
From: barry at python.org (Barry A. Warsaw)
Date: Sat, 7 Dec 2002 09:45:42 -0500
Subject: [Mailman-Developers] bin/arch traceback
References: <20021204162404.GA12277@cthulhu.gerg.ca>
	<15854.11571.315728.288468@gargle.gargle.HOWL>
	<20021204202324.GA300@cthulhu.gerg.ca>
	<20021204230539.GA25147@cthulhu.gerg.ca>
Message-ID: <15858.2454.498238.296323@gargle.gargle.HOWL>


>>>>> "GW" == Greg Ward <gward@mems-exchange.org> writes:

    GW> In related news, bin/arch bloated up to 200 MB of RAM trying
    GW> to rebuild this archive before I killed it.  Ouch!  I thought
    GW> that had been fixed too.

That's not surprising, since pipermail keeps everything in memory as
it's building the archive.  Which is why bin/arch has the --start and
--end options, so you can build an archive in chunks.

-Barry

From barry at python.org  Sat Dec  7 15:05:34 2002
From: barry at python.org (Barry A. Warsaw)
Date: Sat, 7 Dec 2002 10:05:34 -0500
Subject: [Mailman-Developers] Archiving problem in current CVS.
References: <microsoft-free.3ou1hu73sp.fsf@ournature.org>
Message-ID: <15858.3646.391548.803104@gargle.gargle.HOWL>


>>>>> "JH" == Jinhyok Heo
>>>>> <novembre+dated+1039410247.6d79a7@ournature.org> writes:

    JH> I got two problems and one feature request.

    JH> Fist, if I try to regenerate archive of a list with Current
    JH> CVS mailman(using bin/arch), characters of the archives are
    JH> currupted, unlike incoming mails. Can you give it a glance?

There may still be problems w/i18n in the archiver, but I'll need a
lot more information than that to investigate your problem.  Best
would be a bug report on SF, with an uploaded sample message.

(I'm still catching up on list traffic.)

    JH> And, I've set "ARCHIVE_HTML_SANITIZER = 3" in my mm_cfg.py,
    JH> but it doesn't work. Incoming mails are archived as if set
    JH> with "ARCHIVE_HTML_SANITIZER = 1".

Did you run "mailmanctl restart"?  Remember that any change to
mm_cfg.py requires a restart for it to take effect.  I just tried it
and ARCHIVE_HTML_SANITIZER=3 works for me.

    JH> Why don't we have such a ARCHIVE_HTML_SANITIZER option that
    JH> leaves html parts inline and doesn't html-escape.

There's a comment says that reminds me that it was difficult to code
that option given the current architecture of Pipermail.
Unfortunately, I don't remember the details.

-Barry

From noreply at sourceforge.net  Sat Dec  7 16:27:27 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 08:27:27 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-646884 ] HyperArch.py multibyte charset
Message-ID: <E18Khnb-0003mM-00@sc8-sf-web4.sourceforge.net>

Patches item #646884, was opened at 2002-12-02 06:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646884&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: HyperArch.py multibyte charset

Initial Comment:
HyperArch.py in 2.1b5 use Utils.uquote() for
CGIescape() and html_quote() but it does not take
language argument. This  is no good for multilbyte
charset because characters are escaped in separate 8bit
bytes which results in mojibake.
We should rather use Utils.uncanonstr() to honor the
legal characters within the multibyte charset.
This patch fixes other minor bugs in the current code.


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 11:27

Message:
Logged In: YES 
user_id=12800

Here's a new version of the patch that applies cleanly to
current cvs.  I'm not sure I'm testing it well enough, so
could you take a look?


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

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

From barry at python.org  Sat Dec  7 16:29:53 2002
From: barry at python.org (Barry A. Warsaw)
Date: Sat, 7 Dec 2002 11:29:53 -0500
Subject: [Mailman-Developers] Patch # 646884
Message-ID: <15858.8705.464930.370504@gargle.gargle.HOWL>


Tokio Kikuchi posted patch #646884 to fix some mojibake problems with
the archiver (ooh, I just love throwing that term around :).

I worked out a cleaner patch w.r.t. today's cvs and uploaded it

http://sf.net/tracker/index.php?func=detail&aid=646884&group_id=103&atid=300103

I'm not sure I'm testing it thoroughly, so I'd appreciate another set
of eyes.  Should I apply this patch?

Thanks,
-Barry

From noreply at sourceforge.net  Sat Dec  7 16:33:20 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 08:33:20 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-616674 ] bin/arch not processing mbox import corr
Message-ID: <E18KhtI-0004pr-00@sc8-sf-web3.sourceforge.net>

Bugs item #616674, was opened at 2002-09-30 13:43
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=616674&group_id=103

Category: command line scripts
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 7
Submitted By: fuzzy (fuzzynco)
Assigned to: Nobody/Anonymous (nobody)
Summary: bin/arch not processing mbox import corr

Initial Comment:
I needed to import an archive from yahoo!groups. a 
list formerly on Y!G is now on my server with 
MM2.1b3. After creating the mbox file with a perl 
script na dtesting it with pine (to make sure all the 
email is acuallu there), I tried to import it
using arch. there are a few thousand emails in the file, 
but arch only finds 2? I posted to the mm users 
mailing list and got a reply from Larry Weeks, said to 
send him a copy of the file, and he tested it with 
bin/arch from 2.0.6 and it works as expected. 
since the mbox file is readable by pine, shouldn't arch
handle it correctly?

email me if i can provide any thing that would help 
diagnose the problem.

thanks...
fuzzy@pooh.asarian.org


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 11:33

Message:
Logged In: YES 
user_id=12800

arch only handles mbox files in "Unix mbox format".  Such
files delineate messages with a single line containing "From
" -- that's "F R O M space" at the front of the line.  There
can be stricter criteria on what follows that header, but
that's the gist of it.  Maybe your individual files don't
have the right separator.

You can try running bin/cleanarch on the file to see if it's
close.  Use --dry-run to just examine the file.

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

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

From noreply at sourceforge.net  Sat Dec  7 17:10:23 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 09:10:23 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-646884 ] HyperArch.py multibyte charset
Message-ID: <E18KiT9-0001Qs-00@sc8-sf-web1.sourceforge.net>

Patches item #646884, was opened at 2002-12-02 12:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646884&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: HyperArch.py multibyte charset

Initial Comment:
HyperArch.py in 2.1b5 use Utils.uquote() for
CGIescape() and html_quote() but it does not take
language argument. This  is no good for multilbyte
charset because characters are escaped in separate 8bit
bytes which results in mojibake.
We should rather use Utils.uncanonstr() to honor the
legal characters within the multibyte charset.
This patch fixes other minor bugs in the current code.


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

Comment By: Martin v. Löwis (loewis)
Date: 2002-12-07 18:10

Message:
Logged In: YES 
user_id=21627

Tokio, can you please explain the problem in more detail?
Utils.uquote will always return 7bit strings only,
potentially with nested HTML character references. Why could
this cause a problem in a multi-byte encoding? Can you refer
to a page that looks incorrectly because of that?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 17:27

Message:
Logged In: YES 
user_id=12800

Here's a new version of the patch that applies cleanly to
current cvs.  I'm not sure I'm testing it well enough, so
could you take a look?


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

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

From noreply at sourceforge.net  Sat Dec  7 19:11:08 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 11:11:08 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-650147 ] archived with bad dates / out of range
Message-ID: <E18KkM0-0005HI-00@sc8-sf-web1.sourceforge.net>

Bugs item #650147, was opened at 2002-12-07 14:11
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=650147&group_id=103

Category: Pipermail
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Mentor Cana (mcana)
Assigned to: Nobody/Anonymous (nobody)
Summary: archived with bad dates / out of range

Initial Comment:
Here is one of these messages with a bad date that 
when archived gets archived with the date of the archive 
task. So, when rebuilding archives it is archived wrongly.

Example: the message attached should be archived 
with a date of "Apr 9 2000" and instead gets archived 
with today's data if rebuild today.


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

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

From noreply at sourceforge.net  Sat Dec  7 22:32:13 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 14:32:13 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-643231 ] Last archived date is incorrect
Message-ID: <E18KnUb-0006On-00@sc8-sf-web3.sourceforge.net>

Bugs item #643231, was opened at 2002-11-24 15:57
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643231&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Terry Grace (tgrace)
Assigned to: Nobody/Anonymous (nobody)
Summary: Last archived date is incorrect

Initial Comment:
The last archived date/time is incorrect. Time appears to 
be GMT, not local time (e.g. ahead 5 hrs for sites in 
EST)

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

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

From noreply at sourceforge.net  Sat Dec  7 23:02:56 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 15:02:56 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-646598 ] build machine != install machine
Message-ID: <E18KnyK-0006HF-00@sc8-sf-web4.sourceforge.net>

Bugs item #646598, was opened at 2002-12-01 15:26
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=646598&group_id=103

Category: configuring/installing
Group: 2.1 beta
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Matthias Klose (doko)
Assigned to: Nobody/Anonymous (nobody)
Summary: build machine != install machine

Initial Comment:
when building packages on a machine, the machine name
is encoded in Defaults.py. Not sure, what the "correct"
solution is, but IMO it would be better to set the name
in mm_cfg.py.


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:02

Message:
Logged In: YES 
user_id=12800

mm_cfg.py is off-limits for Mailman to touch -- it's purely
for site customizations.  Between manually editing mm_cfg.py
in its final destination and the configure switches
--with-mailhost and --with-urlhost, I think there are plenty
of acceptable ways to configure this.

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

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

From noreply at sourceforge.net  Sat Dec  7 23:08:55 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 15:08:55 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-646596 ] wrong install path
Message-ID: <E18Ko47-0003kK-00@sc8-sf-web1.sourceforge.net>

Bugs item #646596, was opened at 2002-12-01 15:24
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=646596&group_id=103

Category: configuring/installing
Group: 2.1 beta
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Matthias Klose (doko)
Assigned to: Nobody/Anonymous (nobody)
Summary: wrong install path

Initial Comment:
./usr/lib/mailman/pythonlib
[...]
./usr/lib/mailman/pythonlib/japanese
./usr/lib/mailman/pythonlib/japanese/__init__.py
[...]
./usr/lib/mailman/pythonlib/lib/python2.2
./usr/lib/mailman/pythonlib/lib/python2.2/site-packages
./usr/lib/mailman/pythonlib/lib/python2.2/site-packages/japanese.pth

the last one is at least not found, because it's
installed in mailman's prefix, not in python's prefix


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:08

Message:
Logged In: YES 
user_id=12800

It's a little ugly but I don't think it matters much to
Mailman's operation, so I don't intend to fix it, at least
not for MM2.1

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

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

From noreply at sourceforge.net  Sat Dec  7 23:09:54 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 15:09:54 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-650147 ] archived with bad dates / out of range
Message-ID: <E18Ko54-0003lh-00@sc8-sf-web1.sourceforge.net>

Bugs item #650147, was opened at 2002-12-07 14:11
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=650147&group_id=103

Category: Pipermail
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Mentor Cana (mcana)
Assigned to: Nobody/Anonymous (nobody)
Summary: archived with bad dates / out of range

Initial Comment:
Here is one of these messages with a bad date that 
when archived gets archived with the date of the archive 
task. So, when rebuilding archives it is archived wrongly.

Example: the message attached should be archived 
with a date of "Apr 9 2000" and instead gets archived 
with today's data if rebuild today.


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:09

Message:
Logged In: YES 
user_id=12800

Mentor, there's no attached file.  Did you forget to check
the checkbox?

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

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

From noreply at sourceforge.net  Sat Dec  7 23:11:06 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 15:11:06 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-650147 ] archived with bad dates / out of range
Message-ID: <E18Ko6E-0003oC-00@sc8-sf-web1.sourceforge.net>

Bugs item #650147, was opened at 2002-12-07 14:11
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=650147&group_id=103

Category: Pipermail
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Mentor Cana (mcana)
Assigned to: Nobody/Anonymous (nobody)
Summary: archived with bad dates / out of range

Initial Comment:
Here is one of these messages with a bad date that 
when archived gets archived with the date of the archive 
task. So, when rebuilding archives it is archived wrongly.

Example: the message attached should be archived 
with a date of "Apr 9 2000" and instead gets archived 
with today's data if rebuild today.


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:11

Message:
Logged In: YES 
user_id=12800

Oops, is this supposed to be the file you sent to me separately?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:09

Message:
Logged In: YES 
user_id=12800

Mentor, there's no attached file.  Did you forget to check
the checkbox?

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

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

From noreply at sourceforge.net  Sat Dec  7 23:13:38 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 15:13:38 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-650147 ] archived with bad dates / out of range
Message-ID: <E18Ko8g-0006X4-00@sc8-sf-web4.sourceforge.net>

Bugs item #650147, was opened at 2002-12-07 14:11
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=650147&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Mentor Cana (mcana)
Assigned to: Nobody/Anonymous (nobody)
Summary: archived with bad dates / out of range

Initial Comment:
Here is one of these messages with a bad date that 
when archived gets archived with the date of the archive 
task. So, when rebuilding archives it is archived wrongly.

Example: the message attached should be archived 
with a date of "Apr 9 2000" and instead gets archived 
with today's data if rebuild today.


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:13

Message:
Logged In: YES 
user_id=12800

Actually, sorry, if this /is/ the file you sent to me then
Mailman is doing the right thing.  The Date header in that
message has a year of 100, which is totally bogus.  Mailman
has no other way to archive the file except by using the
received date, so it's doing the correct thing.  

I think this is one of several messages you've sent me that
has broken date headers.  Maybe your mail server needs fixing?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:11

Message:
Logged In: YES 
user_id=12800

Oops, is this supposed to be the file you sent to me separately?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:09

Message:
Logged In: YES 
user_id=12800

Mentor, there's no attached file.  Did you forget to check
the checkbox?

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

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

From noreply at sourceforge.net  Sat Dec  7 23:24:23 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 15:24:23 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-650147 ] archived with bad dates / out of range
Message-ID: <E18KoJ5-00049y-00@sc8-sf-web1.sourceforge.net>

Bugs item #650147, was opened at 2002-12-07 14:11
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=650147&group_id=103

Category: Pipermail
Group: 2.1 beta
Status: Closed
Resolution: Wont Fix
Priority: 5
Submitted By: Mentor Cana (mcana)
Assigned to: Nobody/Anonymous (nobody)
Summary: archived with bad dates / out of range

Initial Comment:
Here is one of these messages with a bad date that 
when archived gets archived with the date of the archive 
task. So, when rebuilding archives it is archived wrongly.

Example: the message attached should be archived 
with a date of "Apr 9 2000" and instead gets archived 
with today's data if rebuild today.


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

Comment By: Carson Gaspar (cgaspar)
Date: 2002-12-07 18:24

Message:
Logged In: YES 
user_id=664506

There is an alternative that makes mailman "Do the Right 
Thing". Have mailman add an X-Mailman-Archived-Date 
header to the message if the Date header is missing or 
mangled (or perhaps optionally always). Then have the 
archiver use this header if the Date header is bogus (or 
always if you want to ignore the message date entirely).

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:13

Message:
Logged In: YES 
user_id=12800

Actually, sorry, if this /is/ the file you sent to me then
Mailman is doing the right thing.  The Date header in that
message has a year of 100, which is totally bogus.  Mailman
has no other way to archive the file except by using the
received date, so it's doing the correct thing.  

I think this is one of several messages you've sent me that
has broken date headers.  Maybe your mail server needs fixing?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:11

Message:
Logged In: YES 
user_id=12800

Oops, is this supposed to be the file you sent to me separately?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:09

Message:
Logged In: YES 
user_id=12800

Mentor, there's no attached file.  Did you forget to check
the checkbox?

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

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

From noreply at sourceforge.net  Sun Dec  8 01:19:49 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 17:19:49 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-646884 ] HyperArch.py multibyte charset
Message-ID: <E18Kq6n-0002c8-00@sc8-sf-web3.sourceforge.net>

Patches item #646884, was opened at 2002-12-02 11:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646884&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: HyperArch.py multibyte charset

Initial Comment:
HyperArch.py in 2.1b5 use Utils.uquote() for
CGIescape() and html_quote() but it does not take
language argument. This  is no good for multilbyte
charset because characters are escaped in separate 8bit
bytes which results in mojibake.
We should rather use Utils.uncanonstr() to honor the
legal characters within the multibyte charset.
This patch fixes other minor bugs in the current code.


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

>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-08 01:19

Message:
Logged In: YES 
user_id=67709

Thanks Barry. The patch was successfully applied and things
are worklng better. (a new i18n problem in date format, though)


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

Comment By: Martin v. Löwis (loewis)
Date: 2002-12-07 17:10

Message:
Logged In: YES 
user_id=21627

Tokio, can you please explain the problem in more detail?
Utils.uquote will always return 7bit strings only,
potentially with nested HTML character references. Why could
this cause a problem in a multi-byte encoding? Can you refer
to a page that looks incorrectly because of that?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 16:27

Message:
Logged In: YES 
user_id=12800

Here's a new version of the patch that applies cleanly to
current cvs.  I'm not sure I'm testing it well enough, so
could you take a look?


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

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

From noreply at sourceforge.net  Sun Dec  8 01:51:06 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 17:51:06 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-646884 ] HyperArch.py multibyte charset
Message-ID: <E18Kqb4-0001mc-00@sc8-sf-web4.sourceforge.net>

Patches item #646884, was opened at 2002-12-02 11:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646884&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: HyperArch.py multibyte charset

Initial Comment:
HyperArch.py in 2.1b5 use Utils.uquote() for
CGIescape() and html_quote() but it does not take
language argument. This  is no good for multilbyte
charset because characters are escaped in separate 8bit
bytes which results in mojibake.
We should rather use Utils.uncanonstr() to honor the
legal characters within the multibyte charset.
This patch fixes other minor bugs in the current code.


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

>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-08 01:51

Message:
Logged In: YES 
user_id=67709

I think I have to generate new translation regarding the
date format problem. Sorry.


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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-08 01:19

Message:
Logged In: YES 
user_id=67709

Thanks Barry. The patch was successfully applied and things
are worklng better. (a new i18n problem in date format, though)


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

Comment By: Martin v. Löwis (loewis)
Date: 2002-12-07 17:10

Message:
Logged In: YES 
user_id=21627

Tokio, can you please explain the problem in more detail?
Utils.uquote will always return 7bit strings only,
potentially with nested HTML character references. Why could
this cause a problem in a multi-byte encoding? Can you refer
to a page that looks incorrectly because of that?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 16:27

Message:
Logged In: YES 
user_id=12800

Here's a new version of the patch that applies cleanly to
current cvs.  I'm not sure I'm testing it well enough, so
could you take a look?


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

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

From noreply at sourceforge.net  Sun Dec  8 02:07:48 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 18:07:48 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-650147 ] archived with bad dates / out of range
Message-ID: <E18KqrE-0008Ce-00@sc8-sf-web1.sourceforge.net>

Bugs item #650147, was opened at 2002-12-07 14:11
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=650147&group_id=103

Category: Pipermail
Group: 2.1 beta
Status: Closed
Resolution: Wont Fix
Priority: 5
Submitted By: Mentor Cana (mcana)
Assigned to: Nobody/Anonymous (nobody)
Summary: archived with bad dates / out of range

Initial Comment:
Here is one of these messages with a bad date that 
when archived gets archived with the date of the archive 
task. So, when rebuilding archives it is archived wrongly.

Example: the message attached should be archived 
with a date of "Apr 9 2000" and instead gets archived 
with today's data if rebuild today.


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 21:07

Message:
Logged In: YES 
user_id=12800

Actually, Mailman adds an X-List-Received-Header, but it
looks like pipermail doesn't use it.  Dang, I thought it
did.  Will make it so.  Thanks.


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

Comment By: Carson Gaspar (cgaspar)
Date: 2002-12-07 18:24

Message:
Logged In: YES 
user_id=664506

There is an alternative that makes mailman "Do the Right 
Thing". Have mailman add an X-Mailman-Archived-Date 
header to the message if the Date header is missing or 
mangled (or perhaps optionally always). Then have the 
archiver use this header if the Date header is bogus (or 
always if you want to ignore the message date entirely).

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:13

Message:
Logged In: YES 
user_id=12800

Actually, sorry, if this /is/ the file you sent to me then
Mailman is doing the right thing.  The Date header in that
message has a year of 100, which is totally bogus.  Mailman
has no other way to archive the file except by using the
received date, so it's doing the correct thing.  

I think this is one of several messages you've sent me that
has broken date headers.  Maybe your mail server needs fixing?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:11

Message:
Logged In: YES 
user_id=12800

Oops, is this supposed to be the file you sent to me separately?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 18:09

Message:
Logged In: YES 
user_id=12800

Mentor, there's no attached file.  Did you forget to check
the checkbox?

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

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

From noreply at sourceforge.net  Sun Dec  8 04:13:45 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 20:13:45 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-646884 ] HyperArch.py multibyte charset
Message-ID: <E18Ksp7-0006VB-00@sc8-sf-web3.sourceforge.net>

Patches item #646884, was opened at 2002-12-02 06:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646884&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: HyperArch.py multibyte charset

Initial Comment:
HyperArch.py in 2.1b5 use Utils.uquote() for
CGIescape() and html_quote() but it does not take
language argument. This  is no good for multilbyte
charset because characters are escaped in separate 8bit
bytes which results in mojibake.
We should rather use Utils.uncanonstr() to honor the
legal characters within the multibyte charset.
This patch fixes other minor bugs in the current code.


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 23:13

Message:
Logged In: YES 
user_id=12800

Tokio, do you have an answer for Martin's question?  If this
solves a real problem w/ Japanese, I'm happy to apply it,
but it would be good to have a sample or test case that
fails without it.

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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-07 20:51

Message:
Logged In: YES 
user_id=67709

I think I have to generate new translation regarding the
date format problem. Sorry.


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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-07 20:19

Message:
Logged In: YES 
user_id=67709

Thanks Barry. The patch was successfully applied and things
are worklng better. (a new i18n problem in date format, though)


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

Comment By: Martin v. Löwis (loewis)
Date: 2002-12-07 12:10

Message:
Logged In: YES 
user_id=21627

Tokio, can you please explain the problem in more detail?
Utils.uquote will always return 7bit strings only,
potentially with nested HTML character references. Why could
this cause a problem in a multi-byte encoding? Can you refer
to a page that looks incorrectly because of that?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 11:27

Message:
Logged In: YES 
user_id=12800

Here's a new version of the patch that applies cleanly to
current cvs.  I'm not sure I'm testing it well enough, so
could you take a look?


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

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

From noreply at sourceforge.net  Sun Dec  8 04:19:45 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sat, 07 Dec 2002 20:19:45 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-646884 ] HyperArch.py multibyte charset
Message-ID: <E18Ksuv-0002QJ-00@sc8-sf-web1.sourceforge.net>

Patches item #646884, was opened at 2002-12-02 06:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646884&group_id=103

Category: Pipermail
Group: Mailman 2.1
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: HyperArch.py multibyte charset

Initial Comment:
HyperArch.py in 2.1b5 use Utils.uquote() for
CGIescape() and html_quote() but it does not take
language argument. This  is no good for multilbyte
charset because characters are escaped in separate 8bit
bytes which results in mojibake.
We should rather use Utils.uncanonstr() to honor the
legal characters within the multibyte charset.
This patch fixes other minor bugs in the current code.


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 23:19

Message:
Logged In: YES 
user_id=12800

Never mind, I saw your follow up in mailman-i18n.  That's
good enough for me, so I'll apply the patch.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 23:13

Message:
Logged In: YES 
user_id=12800

Tokio, do you have an answer for Martin's question?  If this
solves a real problem w/ Japanese, I'm happy to apply it,
but it would be good to have a sample or test case that
fails without it.

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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-07 20:51

Message:
Logged In: YES 
user_id=67709

I think I have to generate new translation regarding the
date format problem. Sorry.


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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-07 20:19

Message:
Logged In: YES 
user_id=67709

Thanks Barry. The patch was successfully applied and things
are worklng better. (a new i18n problem in date format, though)


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

Comment By: Martin v. Löwis (loewis)
Date: 2002-12-07 12:10

Message:
Logged In: YES 
user_id=21627

Tokio, can you please explain the problem in more detail?
Utils.uquote will always return 7bit strings only,
potentially with nested HTML character references. Why could
this cause a problem in a multi-byte encoding? Can you refer
to a page that looks incorrectly because of that?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 11:27

Message:
Logged In: YES 
user_id=12800

Here's a new version of the patch that applies cleanly to
current cvs.  I'm not sure I'm testing it well enough, so
could you take a look?


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

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

From noreply at sourceforge.net  Sun Dec  8 15:10:55 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun, 08 Dec 2002 07:10:55 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-646568 ] Admin interface link on listinfo page
Message-ID: <E18L355-0005pM-00@sc8-sf-web3.sourceforge.net>

Bugs item #646568, was opened at 2002-12-01 14:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=646568&group_id=103

Category: Web/CGI
Group: 2.1 beta
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: David Gibbs (midrangeman)
Assigned to: Nobody/Anonymous (nobody)
Summary: Admin interface link on listinfo page

Initial Comment:
I installed MM 2.1b5 and copied the data files for a few 
test lists to the 'lists' dirctory.  I then ran update -f to 
update the data files to the new version.

When I go to the list info page for one of the lists, the 
link to the administrative interface is still pointing to the 
original (production) web interface link.

Example:

Production version of MM's web interface: 
http://lists.midrange.com/cgi-bin/listinfo/testlist

Beta version of MM's web interface:
http://lists.midrange.com/mailman2/listinfo/testlist

However, on this listinfo page, the admin link points to 
http://lists.midrange.com/cgi-bin/admin/testlist

I have changed the DEFAULT_URL_PATTERN to 
be 'http://%s/mailman2/', so I would expect the links to 
have the correct url.

Additionally, when I go directly to the test list admin 
page 
(http://lists.midrange.com/mailman2/admin/testlist), all 
the links on this page also point to old cgi-bin url.



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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-08 10:10

Message:
Logged In: YES 
user_id=12800

You need to run fix_url.py.  Do bin/fix_url.py --help or
read the UPGRADING document.

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

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

From noreply at sourceforge.net  Sun Dec  8 15:12:46 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun, 08 Dec 2002 07:12:46 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-645906 ] User supplied HTML with % kills index.ht
Message-ID: <E18L36s-0002WR-00@sc8-sf-web1.sourceforge.net>

Bugs item #645906, was opened at 2002-11-29 19:52
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645906&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Closed
Resolution: None
Priority: 5
Submitted By: Joe R. Doupnik (jdoupnik)
Assigned to: Nobody/Anonymous (nobody)
Summary: User supplied HTML with % kills index.ht

Initial Comment:
Mailman 2.1b5. Edit archtoc.html or listinfo.html,
include table with phrase width=100% and find
that the list's archive overall index.html page is
unformed (present but the various MM items
are left as bare %(foobar)s style).
 After wasting a whole day on this the problem
boils down to that percent sign in user-supplied
HTML. It kills the high level index.html file. We
don''t know about this until a full list archive
operation is performed,  because at the end
the code creates the new index.html from
the template files. Ugh.
  Likely some parser deep in the system is
overreacting to the percent symbol. Needs
fixing.

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-08 10:12

Message:
Logged In: YES 
user_id=12800

archtoc.html and listinfo.html are templates (as implied by
their being in the templates/xx directory :) which means
Python substitutions are performed on the text.  Python
substitutions treat % as a special character so to get a
literal % in the text you need to use %%

E.g. change that to "width=100%%" and you'll be fine.

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

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

From david at midrange.com  Sun Dec  8 16:08:14 2002
From: david at midrange.com (David Gibbs)
Date: Sun, 08 Dec 2002 10:08:14 -0600
Subject: [Mailman-Developers] Reply to munging not using correct host?
Message-ID: <5.2.0.9.2.20021208095808.02d15e78@linux.midrange.com>

I'm not sure if this is a configuration problem or code problem.

I've got my list server to virtual host. ... the two domains are 
'midrange.com' and 'lists.fallingrock.net' ... I'm using Mailman 2.1b5 on 
lists.fallingrock.net.

I sent a message to a test list and it got sent out properly ... but the 
reply-to munging isn't set to the correct host.

All the 'List-*' headers have the correct host, and I do have the 
'host_name' config variable for the list set to 'lists.fallingrock.net', 
but the reply-to, sender, and errors-to headers are set to 'midrange.com'.

I have the reply_goes_to_list set to "this list", first_strip_reply_to set 
to yes, and reply_to_address set to blank.

I did run the fix_url script against the beta testers list.

Any ideas?

david

>Return-Path: <beta-testers-bounces@lists.fallingrock.net>
>Received: from linux.midrange.com (localhost [127.0.0.1])
>         by linux.midrange.com (8.11.6/8.11.6) with ESMTP id gB8FtTa02925;
>         Sun, 8 Dec 2002 09:55:29 -0600
>Received: from GRYFFINDOR.midrange.com (gryffindor.midrange.com
>         [192.168.1.100])
>         by linux.midrange.com (8.11.6/8.11.6) with ESMTP id gB8FtLi02900
>         for <beta-testers@lists.fallingrock.net>;
>         Sun, 8 Dec 2002 09:55:21 -0600
>Message-Id: <5.2.0.9.2.20021208095147.02ccf150@linux.midrange.com>
>X-Sender: david@linux.midrange.com (Unverified)
>X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
>Date: Sun, 08 Dec 2002 09:55:17 -0600
>To: beta-testers@lists.fallingrock.net
>From: David Gibbs <david@midrange.com>
>Subject: Re: [beta-testers] Up for another round?
>In-Reply-To: <5.2.0.9.2.20021208094537.02c70330@linux.midrange.com>
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"; format=flowed
>X-MailScanner: Found to be clean
>X-BeenThere: beta-testers@lists.fallingrock.net
>X-Mailman-Version: 2.1b5
>Precedence: list
>Reply-To: New Feature Beta Testers <beta-testers@midrange.com>
>List-Id: New Feature Beta Testers <beta-testers.lists.fallingrock.net>
>List-Unsubscribe: 
><http://lists.fallingrock.net/mailman2/listinfo/beta-testers>,
> 
><mailto:beta-testers-request@lists.fallingrock.net?subject=unsubscribe>
>List-Archive: <http://lists.fallingrock.net/mailman2/private/beta-testers>
>List-Post: <mailto:beta-testers@lists.fallingrock.net>
>List-Help: <mailto:beta-testers-request@lists.fallingrock.net?subject=help>
>List-Subscribe: <http://lists.fallingrock.net/mailman2/listinfo/beta-testers>,
>         <mailto:beta-testers-request@lists.fallingrock.net?subject=subscribe>
>Sender: beta-testers-bounces@midrange.com
>Errors-To: beta-testers-bounces@midrange.com

--
| Internet: david@midrange.com
| WWW: http://david.fallingrock.net
| AIM: MidrangeMan
|
| We're not in the middle of nowhere...
|   we're on the outskirts of everywhere!
|			- DMRoth (adapted)









From noreply at sourceforge.net  Sun Dec  8 16:50:53 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun, 08 Dec 2002 08:50:53 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-593728 ] Traceback rebuilding
	archive
Message-ID: <E18L4dp-0007T0-00@sc8-sf-web2.sourceforge.net>

Bugs item #593728, was opened at 2002-08-11 20:46
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Open
Resolution: None
Priority: 5
Submitted By: Stefan Divjak (stdivjak)
Assigned to: Nobody/Anonymous (nobody)
Summary: Traceback rebuilding archive

Initial Comment:
Witn Mailman 2.1b3, rebuilding a pipermail archive using  
$ bin/arch listname  
runs fine for 2 lists, but on the third one gives the  
following traceback:  
 
[...]  
Updating HTML for article 52 
Updating HTML for article 53 
Schreibe Archivzustand in Datei 
/home/mailman/archives/private/humor/pipermail.pck 
Traceback (most recent call last): 
  File "bin/arch", line 160, in ? 
    main() 
  File "bin/arch", line 148, in main 
    archiver.processUnixMailbox(fp, Article, start, end) 
  File "/home/mailman/Mailman/Archiver/pipermail.py", 
line 545, in processUnixMailbox 
    m = mbox.next() 
  File "/usr/local/lib/python2.2/mailbox.py", line 34, in 
next 
    return self.factory(_Subfile(self.fp, start, stop)) 
  File "/home/mailman/Mailman/Mailbox.py", line 69, in 
scrubber 
    return mailbox.scrub(msg) 
  File "/home/mailman/Mailman/Mailbox.py", line 89, in 
scrub 
    return self._scrubber(self._mlist, msg) 
  File "/home/mailman/Mailman/Handlers/Scrubber.py", 
line 159, in process 
    part.set_payload(_("""\ 
  File "/home/mailman/Mailman/i18n.py", line 76, in _ 
    return _translation.gettext(s) % dict 
UnicodeError: ASCII decoding error: ordinal not in 
range(128) 

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-09-13 21:47

Message:
Logged In: YES 
user_id=12800

I'm moving the bug report to pending since I haven't seen an
update.  I suspect this is fixed in current cvs.

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

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

Message:
Logged In: YES 
user_id=12800

Can you upload the .mbox file for the list you're
regenerating?  If not (perhaps because it's proprietary
information), can you make it available for me to look at
privately?


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

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

From noreply at sourceforge.net  Sun Dec  8 16:58:06 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun, 08 Dec 2002 08:58:06 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-593728 ] Traceback rebuilding
	archive
Message-ID: <E18L4ko-0006Fd-00@sc8-sf-web4.sourceforge.net>

Bugs item #593728, was opened at 2002-08-11 20:46
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103

Category: Pipermail
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Stefan Divjak (stdivjak)
Assigned to: Nobody/Anonymous (nobody)
Summary: Traceback rebuilding archive

Initial Comment:
Witn Mailman 2.1b3, rebuilding a pipermail archive using  
$ bin/arch listname  
runs fine for 2 lists, but on the third one gives the  
following traceback:  
 
[...]  
Updating HTML for article 52 
Updating HTML for article 53 
Schreibe Archivzustand in Datei 
/home/mailman/archives/private/humor/pipermail.pck 
Traceback (most recent call last): 
  File "bin/arch", line 160, in ? 
    main() 
  File "bin/arch", line 148, in main 
    archiver.processUnixMailbox(fp, Article, start, end) 
  File "/home/mailman/Mailman/Archiver/pipermail.py", 
line 545, in processUnixMailbox 
    m = mbox.next() 
  File "/usr/local/lib/python2.2/mailbox.py", line 34, in 
next 
    return self.factory(_Subfile(self.fp, start, stop)) 
  File "/home/mailman/Mailman/Mailbox.py", line 69, in 
scrubber 
    return mailbox.scrub(msg) 
  File "/home/mailman/Mailman/Mailbox.py", line 89, in 
scrub 
    return self._scrubber(self._mlist, msg) 
  File "/home/mailman/Mailman/Handlers/Scrubber.py", 
line 159, in process 
    part.set_payload(_("""\ 
  File "/home/mailman/Mailman/i18n.py", line 76, in _ 
    return _translation.gettext(s) % dict 
UnicodeError: ASCII decoding error: ordinal not in 
range(128) 

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

>Comment By: Stefan Divjak (stdivjak)
Date: 2002-12-08 18:58

Message:
Logged In: YES 
user_id=483131

Sorry for the long delay. I fiddled around with the 19MB 
mbox file, and cut out the part which causes this error 
(refer to the attached file).

The traceback also appeared using 2.1b5.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-09-13 21:47

Message:
Logged In: YES 
user_id=12800

I'm moving the bug report to pending since I haven't seen an
update.  I suspect this is fixed in current cvs.

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

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

Message:
Logged In: YES 
user_id=12800

Can you upload the .mbox file for the list you're
regenerating?  If not (perhaps because it's proprietary
information), can you make it available for me to look at
privately?


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

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

From noreply at sourceforge.net  Sun Dec  8 18:11:29 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun, 08 Dec 2002 10:11:29 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-593728 ] Traceback rebuilding
	archive
Message-ID: <E18L5tp-0002a9-00@sc8-sf-web3.sourceforge.net>

Bugs item #593728, was opened at 2002-08-11 20:46
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103

Category: Pipermail
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Stefan Divjak (stdivjak)
Assigned to: Nobody/Anonymous (nobody)
Summary: Traceback rebuilding archive

Initial Comment:
Witn Mailman 2.1b3, rebuilding a pipermail archive using  
$ bin/arch listname  
runs fine for 2 lists, but on the third one gives the  
following traceback:  
 
[...]  
Updating HTML for article 52 
Updating HTML for article 53 
Schreibe Archivzustand in Datei 
/home/mailman/archives/private/humor/pipermail.pck 
Traceback (most recent call last): 
  File "bin/arch", line 160, in ? 
    main() 
  File "bin/arch", line 148, in main 
    archiver.processUnixMailbox(fp, Article, start, end) 
  File "/home/mailman/Mailman/Archiver/pipermail.py", 
line 545, in processUnixMailbox 
    m = mbox.next() 
  File "/usr/local/lib/python2.2/mailbox.py", line 34, in 
next 
    return self.factory(_Subfile(self.fp, start, stop)) 
  File "/home/mailman/Mailman/Mailbox.py", line 69, in 
scrubber 
    return mailbox.scrub(msg) 
  File "/home/mailman/Mailman/Mailbox.py", line 89, in 
scrub 
    return self._scrubber(self._mlist, msg) 
  File "/home/mailman/Mailman/Handlers/Scrubber.py", 
line 159, in process 
    part.set_payload(_("""\ 
  File "/home/mailman/Mailman/i18n.py", line 76, in _ 
    return _translation.gettext(s) % dict 
UnicodeError: ASCII decoding error: ordinal not in 
range(128) 

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

>Comment By: Stefan Divjak (stdivjak)
Date: 2002-12-08 20:11

Message:
Logged In: YES 
user_id=483131

Just tried to rebuild the other archives: 4 of 21 mbox-files 
can't be rebuilt. There are two kinds of tracebacks:

* "ASCII decoding error" (see above)
* "Lookup error: unknown encoding"

I'll send the archive causing the second kind of traceback 
to Barry, hence it contains somewhat internal information.

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

Comment By: Stefan Divjak (stdivjak)
Date: 2002-12-08 18:58

Message:
Logged In: YES 
user_id=483131

Sorry for the long delay. I fiddled around with the 19MB 
mbox file, and cut out the part which causes this error 
(refer to the attached file).

The traceback also appeared using 2.1b5.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-09-13 21:47

Message:
Logged In: YES 
user_id=12800

I'm moving the bug report to pending since I haven't seen an
update.  I suspect this is fixed in current cvs.

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

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

Message:
Logged In: YES 
user_id=12800

Can you upload the .mbox file for the list you're
regenerating?  If not (perhaps because it's proprietary
information), can you make it available for me to look at
privately?


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

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

From noreply at sourceforge.net  Sun Dec  8 21:34:20 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun, 08 Dec 2002 13:34:20 -0800
Subject: [Mailman-Developers] 
 [ mailman-Feature Requests-650567 ] The plus (+) in email addresses
Message-ID: <E18L948-00074i-00@sc8-sf-web4.sourceforge.net>

Feature Requests item #650567, was opened at 2002-12-08 16:34
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=650567&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: James O'Kane (jo2y)
Assigned to: Nobody/Anonymous (nobody)
Summary: The plus (+) in email addresses

Initial Comment:
Could an option be added to treat:
foo@example.com
foo+@example.com
as the same address? I'm told the + is in the RFC, but
I haven't found it yet. I know of a few sites that auto
add the + at the end of outgoing emails. (cmu.edu and
pitt.edu for example).
It would be nice if foo+filter@example.com could be
treated as foo@example.com as well.

thanks


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

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

From noreply at sourceforge.net  Mon Dec  9 00:28:34 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun, 08 Dec 2002 16:28:34 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-645421 ] Remove all Makefiles on make distclean
Message-ID: <E18LBmk-0001JV-00@sc8-sf-web1.sourceforge.net>

Patches item #645421, was opened at 2002-11-28 21:50
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645421&group_id=103

Category: configure/install
>Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthias Juchem (brightice)
Assigned to: Nobody/Anonymous (nobody)
Summary: Remove all Makefiles on make distclean

Initial Comment:
mailman/messages/Makefile and 
mailman/tests/*/Makefile do not get cleaned up when
doing a 'make distclean'.

This should patch fix it.

Tested like this: 'configure --some-options; make
distclean'; seems to work


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

>Comment By: Matthias Juchem (brightice)
Date: 2002-12-09 01:28

Message:
Logged In: YES 
user_id=60479

Stupid me, patch is for 2.1, not for 2.2/3.0.

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

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

From noreply at sourceforge.net  Mon Dec  9 00:29:17 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun, 08 Dec 2002 16:29:17 -0800
Subject: [Mailman-Developers] 
 [ mailman-Patches-645422 ] $prefix hardcoded in qmail-to-mailman.py
Message-ID: <E18LBnR-0001L2-00@sc8-sf-web1.sourceforge.net>

Patches item #645422, was opened at 2002-11-28 21:52
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645422&group_id=103

Category: mail delivery
>Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthias Juchem (brightice)
Assigned to: Nobody/Anonymous (nobody)
Summary: $prefix hardcoded in qmail-to-mailman.py

Initial Comment:
This patch replaces the hardcoded $prefix in
contrib/qmail-to-mailman.py  with @prefix@, which is
replaced with $prefix during configure.

Tested, works for me.

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

>Comment By: Matthias Juchem (brightice)
Date: 2002-12-09 01:29

Message:
Logged In: YES 
user_id=60479

Stupid me, patch is for 2.1, not for 2.2/3.0.

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

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

From noreply at sourceforge.net  Mon Dec  9 04:26:36 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun, 08 Dec 2002 20:26:36 -0800
Subject: [Mailman-Developers] [ mailman-Bugs-593728 ] Traceback rebuilding
	archive
Message-ID: <E18LFV6-0000hl-00@sc8-sf-web4.sourceforge.net>

Bugs item #593728, was opened at 2002-08-11 14:46
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Stefan Divjak (stdivjak)
Assigned to: Nobody/Anonymous (nobody)
Summary: Traceback rebuilding archive

Initial Comment:
Witn Mailman 2.1b3, rebuilding a pipermail archive using  
$ bin/arch listname  
runs fine for 2 lists, but on the third one gives the  
following traceback:  
 
[...]  
Updating HTML for article 52 
Updating HTML for article 53 
Schreibe Archivzustand in Datei 
/home/mailman/archives/private/humor/pipermail.pck 
Traceback (most recent call last): 
  File "bin/arch", line 160, in ? 
    main() 
  File "bin/arch", line 148, in main 
    archiver.processUnixMailbox(fp, Article, start, end) 
  File "/home/mailman/Mailman/Archiver/pipermail.py", 
line 545, in processUnixMailbox 
    m = mbox.next() 
  File "/usr/local/lib/python2.2/mailbox.py", line 34, in 
next 
    return self.factory(_Subfile(self.fp, start, stop)) 
  File "/home/mailman/Mailman/Mailbox.py", line 69, in 
scrubber 
    return mailbox.scrub(msg) 
  File "/home/mailman/Mailman/Mailbox.py", line 89, in 
scrub 
    return self._scrubber(self._mlist, msg) 
  File "/home/mailman/Mailman/Handlers/Scrubber.py", 
line 159, in process 
    part.set_payload(_("""\ 
  File "/home/mailman/Mailman/i18n.py", line 76, in _ 
    return _translation.gettext(s) % dict 
UnicodeError: ASCII decoding error: ordinal not in 
range(128) 

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-08 23:26

Message:
Logged In: YES 
user_id=12800

Thanks Stefan, 

I got your mbox file, which appeared to contain one message.
 That message has an unknown charset in its RFC 2047 Subject
header.  Mailman cvs seems to handle this file just fine, so
I'm closing this as fixed in 2.1b5+

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

Comment By: Stefan Divjak (stdivjak)
Date: 2002-12-08 13:11

Message:
Logged In: YES 
user_id=483131

Just tried to rebuild the other archives: 4 of 21 mbox-files 
can't be rebuilt. There are two kinds of tracebacks:

* "ASCII decoding error" (see above)
* "Lookup error: unknown encoding"

I'll send the archive causing the second kind of traceback 
to Barry, hence it contains somewhat internal information.

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

Comment By: Stefan Divjak (stdivjak)
Date: 2002-12-08 11:58

Message:
Logged In: YES 
user_id=483131

Sorry for the long delay. I fiddled around with the 19MB 
mbox file, and cut out the part which causes this error 
(refer to the attached file).

The traceback also appeared using 2.1b5.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-09-13 15:47

Message:
Logged In: YES 
user_id=12800

I'm moving the bug report to pending since I haven't seen an
update.  I suspect this is fixed in current cvs.

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

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

Message:
Logged In: YES 
user_id=12800

Can you upload the .mbox file for the list you're
regenerating?  If not (perhaps because it's proprietary
information), can you make it available for me to look at
privately?


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

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

From noreply at sourceforge.net  Mon Dec  9 05:58:28 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun, 08 Dec 2002 21:58:28 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-644950 ] membership pages shows wrong subset
Message-ID: <E18LGw0-0003vJ-00@sc8-sf-web2.sourceforge.net>

Bugs item #644950, was opened at 2002-11-27 16:09
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644950&group_id=103

Category: Web/CGI
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Matthias Klose (doko)
Assigned to: Nobody/Anonymous (nobody)
Summary: membership pages shows wrong subset

Initial Comment:
When first entering the membership admin tab, and the
members of the list are displayed letterwise, I see the
letter A bold/higlighted, but the member starting with
"Z" are displayed.

Selecting the subset again by selecting "A" shows the
correct meber subset starting with "A".


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-09 00:58

Message:
Logged In: YES 
user_id=12800

Fixed, thanks.

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

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

From noreply at sourceforge.net  Mon Dec  9 06:23:41 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun, 08 Dec 2002 22:23:41 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-650711 ] add_members fails with specific address
Message-ID: <E18LHKP-0004VH-00@sc8-sf-web2.sourceforge.net>

Bugs item #650711, was opened at 2002-12-09 06:23
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=650711&group_id=103

Category: command line scripts
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Cabel Sasser (cabelsa)
Assigned to: Nobody/Anonymous (nobody)
Summary: add_members fails with specific address

Initial Comment:
I am migrating from one list system to another, and in
the process of doing so I'm importing tens of thousands
of addresses using the command-line add_members utility.

Bug:

add_members reproducibly crashes when it gets to the
following obviously invalid e-mail address in the text
file I'm importing from:

----@---.---

Here is the error message:

[...]
Traceback (most recent call last):
  File "/usr/local/mailman/bin/add_members", line 297, in ?
    main()
  File "/usr/local/mailman/bin/add_members", line 274,
in main
    addall(mlist, nmembers, 0, send_welcome_msg, s)
  File "/usr/local/mailman/bin/add_members", line 173,
in addall
    except MMHostileAddress:
NameError: global name 'MMHostileAddress' is not defined

If I remove the above dash-tastic address, the
add_members import succeeds.

I hope this helps! Mailman totally rocks! :)


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

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

From noreply at sourceforge.net  Mon Dec  9 06:24:19 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun, 08 Dec 2002 22:24:19 -0800
Subject: [Mailman-Developers] 
 [ mailman-Bugs-650711 ] add_members fails with specific address
Message-ID: <E18LHL1-0003Gp-00@sc8-sf-web4.sourceforge.net>

Bugs item #650711, was opened at 2002-12-09 06:23
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=650711&group_id=103

Category: command line scripts
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Cabel Sasser (cabelsa)
Assigned to: Nobody/Anonymous (nobody)
Summary: add_members fails with specific address

Initial Comment:
I am migrating from one list system to another, and in
the process of doing so I'm importing tens of thousands
of addresses using the command-line add_members utility.

Bug:

add_members reproducibly crashes when it gets to the
following obviously invalid e-mail address in the text
file I'm importing from:

----@---.---

Here is the error message:

[...]
Traceback (most recent call last):
  File "/usr/local/mailman/bin/add_members", line 297, in ?
    main()
  File "/usr/local/mailman/bin/add_members", line 274,
in main
    addall(mlist, nmembers, 0, send_welcome_msg, s)
  File "/usr/local/mailman/bin/add_members", line 173,
in addall
    except MMHostileAddress:
NameError: global name 'MMHostileAddress' is not defined

If I remove the above dash-tastic address, the
add_members import succeeds.

I hope this helps! Mailman totally rocks! :)


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

>Comment By: Cabel Sasser (cabelsa)
Date: 2002-12-09 06:24

Message:
Logged In: YES 
user_id=665207

BTW, this is 2.0b5. Sorry for not mentioning that above.

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

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

From liam at routt.net  Mon Dec  9 17:54:48 2002
From: liam at routt.net (Liam Routt)
Date: Mon Dec  9 01:57:32 2002
Subject: [Mailman-Developers] Unable to install 2.1b5 on RedHat 7.3
In-Reply-To: <20021207074320.GA30458@routt.net>
References: <20021207074320.GA30458@routt.net>
Message-ID: <20021209065448.GF14995@routt.net>

Not a whole lot of help from the list. But I have answered my own problem:


Liam Routt wrote:
> The error I'm getting is one I have seen mention of before in the 
> archives:
> 
> Compiling /home/mailman/Mailman/versions.py ...
> Traceback (most recent call last):
>   File "bin/update", line 44, in ?
>     import paths
>   File "bin/paths.py", line 55, in ?
>     import japanese
> ImportError: No module named japanese

The answer was in README.LINUX, of course: install python2-devel. Worked 
fine after that.

> Things to consider:
> 
> 1. The failure did not halt the install, although it did make it 
> impossible for it to complete. But the relevant messages were *way* back, 
> and probably meaningless to a non-technical person, at a guess.

I still think that the failure should stop the install, rather than 
allowing it to merrily continue without having installed everything it 
needed, only to be brought up short with the above message.

Take care,

Liam
--
Liam Routt                                               liam@routt.net
Darcsyde Productions                     http://www.routt.net/Caligari/

        -- still waiting for the Absolute Destiny Apocalypse --

From michael.kallas at web.de  Mon Dec  9 10:17:50 2002
From: michael.kallas at web.de (Michael Kallas)
Date: Mon Dec  9 04:18:24 2002
Subject: [Mailman-Developers] Re: Legal trouble in Germany
Message-ID: <200212090917.gB99HoX13517@mailgate5.cinetic.de>

Hi,

On Saturday, 7 Dec 2002 01:21:07 -0500
Phil Barnett <philb@philb.us> wrote:
> On Friday 06 December 2002 12:10 pm, Matthew Davis wrote:
>> So turn off the confirmation so you assume if the user clicks the
>> subscribe, they _want_ to be subscribed.
This definitely is no solution as that was already the assumption
for sending the confirmation email.
>So, how do you then prove that it was them and not someone else?
According to this court, you would have to write an email
instead of being able to sign up via web.
But we all know that it's no problem to fake email addresses.
Therefore this is a "chicken and egg" situation that
could only be solved by reliable identification of the
subscriber :-(
I don't have any solution at hand but just wanted to inform
so that maybe something can be done about it.

Best wishes
Michael
-- 
All thoughts are free, Who can ever guess them?
Die Gedanken sind frei, Wer kann sie erraten?

______________________________________________________________________________
SMS verschicken und die Telefonnummer gleich im Adressbuch speichern.
Geht nicht? -  Geht doch! - http://freemail.web.de/features/?mc=021150


From noreply at sourceforge.net  Mon Dec  9 07:59:29 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec  9 10:59:33 2002
Subject: [Mailman-Developers] [ mailman-Bugs-650932 ] 'Administator' typos
Message-ID: <E18LQJd-00076m-00@sc8-sf-web2.sourceforge.net>

Bugs item #650932, was opened at 2002-12-09 10:59
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=650932&group_id=103

Category: Web/CGI
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: A.M. Kuchling (akuchling)
Assigned to: Nobody/Anonymous (nobody)
Summary: 'Administator' typos

Initial Comment:
'rgrep -i administator' (missing the R after the first T) 
turns up a number of places where this typo occurs;
some of them are still present in the 2.1b6 running on
python.org.


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

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

From noreply at sourceforge.net  Mon Dec  9 14:40:49 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec  9 17:40:56 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-651146 ] make distclean forgets some Makefiles
Message-ID: <E18LWa1-0005zH-00@sc8-sf-web3.sourceforge.net>

Bugs item #651146, was opened at 2002-12-09 23:40
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=651146&group_id=103

Category: configuring/installing
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthias Juchem (brightice)
Assigned to: Nobody/Anonymous (nobody)
Summary: make distclean forgets some Makefiles

Initial Comment:
Hi.

mailman/messages/Makefile and
mailman/tests/*/Makefile do not get cleaned up when
doing a 'make distclean'.

Patch 645421 should fix this, see patch description.

 Matthias


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

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

From claw at kanga.nu  Mon Dec  9 20:00:25 2002
From: claw at kanga.nu (J C Lawrence)
Date: Mon Dec  9 23:00:30 2002
Subject: [Mailman-Developers] Exim tweak
Message-ID: <30082.1039492825@kanga.nu>


As an experiment in analysing my system loads I added the following to
my exim.conf:

  # When this option is set, a delivery process is started whenever a
  # message is received, directing and routing is performed, and local
  # deliveries take place. However, if any SMTP deliveries are
  # required for domains that match queue_smtp_domains, they are not
  # immediately delivered, but instead the message waits on the queue
  # for the next queue run. Since routing of the message has taken
  # place, Exim knows to which remote hosts it must be delivered, and
  # so when the queue run happens, multiple messages for the same host
  # are delivered over a single SMTP connection. This option is
  # checked against the domains supplied in the incoming addresses,
  # before any widening is done (because that is part of routing). The
  # -odqs command line option causes all SMTP deliveries to be queued
  # in this way, and is equivalent to setting queue_smtp_domains to
  # *'. See also queue_remote_domains, which is subtly different.

  queue_smtp_domains = "*"

Note that all of my lists are hand moderated resulting in outbound mail
occurring in batches, typically in the range of 5K - 10K MTA spool
entries per batch.

The primary effect of adding this config item is that (in general) a
compleat moderation batch is enqueued by the MTA before delivery
attempts start on any of the component messages.  This turns out to have
a significant effect on delivery time performance.

Loosely what seems to be happening is that without the above config Exim
and Mailman's qrunner end up competing for CPU resources, with system
loads climbing into the 30's and 40's with parallel deliveries to the
same MX being infrequent to the point of nonexistence. [1] However with
the above config Exim has the opportunity to batch all mail targeted to
a given MX and parallel deliveries are the default. [2] This shows
clearly in the logs with blocks of deliveries to the same MX all
together.  The apparent result of this batching is that the total
delivery time [3] for a moderation batch is now reduced by a factor of
almost 5. [3]

Not a bad side effect for a little idle poking about.

-- 
J C Lawrence               
---------(*)                Satan, oscillate my metallic sonatas. 
claw@kanga.nu               He lived as a devil, eh?		  
http://www.kanga.nu/~claw/  Evil is a name of a foeman, as I live.

1) I use 20 queue runners with up to 10 parallel deliveries per MX.

2) I have low rates of duplicate MX use in my subscriber base.  AOL +
MSN + Hotmail together form less than 3% of my subscriber base.  Outside
of resource contention this low collision rate is the prime factor in
parallel deliveries not happening.

3) Loosely defining total delivery time as the taken to handle all
deliveries to all fast MX'es (no errors, warnings, or responses taking
more than a second).

4) This depends heavily on whether Mailman's qrunner can get the
compleat moderation queue dumped to the MTA before it starts another
queue run.  Typically for my setup I can get ~4K spool entries queued
between MTA queue runs.  I *should* be able to get at least an order of
magnitude more, and almost two (as determined by trivial test code doing
a canned loop).  I haven't yet analysed why the qrunner path is so slow
and am unlikely to before I deploy v2.1.  However as a general
observation Mailman v2.0's qrunner seems absurdly slow in iterating
across the membership roster and dumping RCPT TO bundles to the MTA.


From marc_news at merlins.org  Mon Dec  9 23:36:47 2002
From: marc_news at merlins.org (Marc MERLIN)
Date: Tue Dec 10 02:36:54 2002
Subject: [Mailman-Developers] Exim tweak
In-Reply-To: <30082.1039492825@kanga.nu>
References: <30082.1039492825@kanga.nu>
Message-ID: <20021210073647.GY27411@merlins.org>

On Mon, Dec 09, 2002 at 08:00:25PM -0800, J C Lawrence wrote:
> together.  The apparent result of this batching is that the total
> delivery time [3] for a moderation batch is now reduced by a factor of
> almost 5. [3]
> 
> Not a bad side effect for a little idle poking about.

Indeed, it will increase overall throughput.
However, you are sacrificing turnaround  time to several minutes or more
as a result, and this from mere seconds with mm 2.1
(for that matter, with some of my  lists, when I save my message in vim,
by the  time I get back  to the mutt  index, the message has  been sent,
processed by the MTA, handed out  to mailman, which exploded it and sent
it back to  my mailbox, so my message  shows up in my index  in the half
second that it took mutt to come back from vim and rescan my mailbox

If you ask me, that's pretty cool :-)

Now, I'm curious:
In your case, you get bursts of messages with lots of subscribers on
your list.
How about a list server with many lists so that you always have 50 to
100 exims running and trying to clean the queue, deliver mail, or
talking to mailman...
In that case (i.e. really loaded server), I'm not convinced that
spooling everything to disk and having exim process the message on the
next queue run is going to be that much more effective. Is it?

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/   |   Finger marc_f@merlins.org for PGP key

From claw at kanga.nu  Tue Dec 10 01:32:16 2002
From: claw at kanga.nu (J C Lawrence)
Date: Tue Dec 10 04:32:22 2002
Subject: [Mailman-Developers] Exim tweak 
In-Reply-To: Message from Marc MERLIN <marc_news@merlins.org> 
   of "Mon, 09 Dec 2002 23:36:47 PST." <20021210073647.GY27411@merlins.org> 
References: <30082.1039492825@kanga.nu>  <20021210073647.GY27411@merlins.org> 
Message-ID: <4576.1039512736@kanga.nu>

On Mon, 9 Dec 2002 23:36:47 -0800 
Marc MERLIN <marc_news@merlins.org> wrote:
> On Mon, Dec 09, 2002 at 08:00:25PM -0800, J C Lawrence wrote:

>> Not a bad side effect for a little idle poking about.

> Indeed, it will increase overall throughput.  However, you are
> sacrificing turnaround time to several minutes or more as a result,
> and this from mere seconds with mm 2.1 (for that matter, with some of
> my lists, when I save my message in vim, by the time I get back to the
> mutt index, the message has been sent, processed by the MTA, handed
> out to mailman, which exploded it and sent it back to my mailbox, so
> my message shows up in my index in the half second that it took mutt
> to come back from vim and rescan my mailbox

Yup.  

> If you ask me, that's pretty cool :-)

I can stand that pain, easily, especially as I generally moderate only
once or twice a day.  Adding a few minutes to a process which averages a
more than 6 hour latency is hardly expensive.

> Now, I'm curious: In your case, you get bursts of messages with lots
> of subscribers on your list.  

Yup, the largest burst I've played with to day this way was 20,000 spool
entries in one slam (I killed SMTP deliveries until qrunner had finished
injecting into the MTA).  It didn't quite drain proportionally to the
number of subscribers, but it wasn't a long way off either.

> How about a list server with many lists so that you always have 50 to
> 100 exims running and trying to clean the queue, deliver mail, or
> talking to mailman...  In that case (i.e. really loaded server), I'm
> not convinced that spooling everything to disk and having exim process
> the message on the next queue run is going to be that much more
> effective. Is it?

I expect that the efficiency *could* be maintained.  There are quite a
few variables.  (I've spent a lot more time tuning Postfix than I have
Exim) It depends on the distribution of the destination MX's (how much
repetition across your lists thus incurring parallel delivery), how much
of the default state of the "loaded mail server" is really repetitious
delivery attempts to slow MX'es (which defines your background sustained
load), the size of the message bursts (in terms of number of messages
prior to moderation, thus defining known parallel delivery
opportunities), the rate of MTA queue runner passes (defining windows of
opportunity for parallel deliveries), and the time required to inject a
burst into the MTA (which thus has a defined intersection rate with the
MTA queue runners).  The ___apparent___ critical bit is to get all (or
most/much of) the burst injected into the MTA before it starts
delivering it and then having a large number of moderated messages thus
being able to take advantage of parallel delivery and reduce the total
delivery time down to (optimally) linearly proportional to the number of
subscribers.

-- 
J C Lawrence                
---------(*)                Satan, oscillate my metallic sonatas. 
claw@kanga.nu               He lived as a devil, eh?		  
http://www.kanga.nu/~claw/  Evil is a name of a foeman, as I live.


From noreply at sourceforge.net  Tue Dec 10 04:38:03 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 10 07:38:07 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-651406 ] MM 2.0.13 to 2.1b5 upgrade fails
Message-ID: <E18LjeF-0003QM-00@sc8-sf-web4.sourceforge.net>

Patches item #651406, was opened at 2002-12-10 12:38
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=651406&group_id=103

Category: None
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: MM 2.0.13 to 2.1b5 upgrade fails

Initial Comment:
make install when updating a MM 2.0.13 installation to 
2.1b5 initally produced the following exception:

Updating mailing list: mailman
Traceback (most recent call last):
  File "bin/update", line 569, in ?
    errors = main()
  File "bin/update", line 446, in main
    errors = errors + dolist(listname)
  File "bin/update", line 186, in dolist
    mlist = MailList.MailList(listname, lock=0)
  File "/mailman/run/Mailman/MailList.py", line 101, in 
__init__
    self.Load()
  File "/mailman/run/Mailman/MailList.py", line 600, in 
Load
    self.CheckValues()
  File "/mailman/run/Mailman/MailList.py", line 650, in 
CheckValues
    for name, pattern, desc, emptyflag in self.topics:
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: topics
make: *** [update] Error 1

Having corrected the cause of this first exception the 
following exception was then encountered:

Upgrading from version 0x2000df0 to 0x20100b5
getting rid of old source files
Updating mailing list: mailman
Traceback (most recent call last):
  File "bin/update", line 569, in ?
    errors = main()
  File "bin/update", line 446, in main
    errors = errors + dolist(listname)
  File "bin/update", line 200, in dolist
    for addr, (reason, when) in mlist.delivery_status.items
():
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: delivery_status
make: *** [update] Error 1

These problems both seem to arise because of the 
following:

1. The MailList class is derived from the classes 
TopicMgr and Bouncer (amongst others).

2. The MailList __init__ function calls the __init__ 
functions of its superclasses if they have that function; 
which they do not in the case of the of TopicMgr and 
Bouncer classes

3. The MailList __init__ function calls its own 
InitTempVars function which in turn calls the 
InitTempVars functions of MailList's superclasses if they 
have that function; which they do not in the case of the 
of class TopicMgr and Bouncer classes

4. The MailList __init__ function does not call the 
InitVars functions of the TopicMgr and Bouncer classes 
which is why self.topics and self.delivery_status are 
undefined attributes of the MailList instance being 
created; these being instance variables introduced by 
MM 2.1b5 and missing from MM 2.0.13 instance of the 
MailList class which is what is being dealt with at the 
time the update is being done.

Adding the following definition to the TopicMgr and 
Bouncer class definitions seem to clear the problem 
although whether this is the best log-tem solution is 
questionable:

    InitTempVars = InitVars


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

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

From noreply at sourceforge.net  Tue Dec 10 05:13:56 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 10 08:14:07 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-651406 ] MM 2.0.13 to 2.1b5 upgrade fails
Message-ID: <E18LkCy-0003mU-00@sc8-sf-web1.sourceforge.net>

Patches item #651406, was opened at 2002-12-10 12:38
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=651406&group_id=103

Category: None
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: MM 2.0.13 to 2.1b5 upgrade fails

Initial Comment:
make install when updating a MM 2.0.13 installation to 
2.1b5 initally produced the following exception:

Updating mailing list: mailman
Traceback (most recent call last):
  File "bin/update", line 569, in ?
    errors = main()
  File "bin/update", line 446, in main
    errors = errors + dolist(listname)
  File "bin/update", line 186, in dolist
    mlist = MailList.MailList(listname, lock=0)
  File "/mailman/run/Mailman/MailList.py", line 101, in 
__init__
    self.Load()
  File "/mailman/run/Mailman/MailList.py", line 600, in 
Load
    self.CheckValues()
  File "/mailman/run/Mailman/MailList.py", line 650, in 
CheckValues
    for name, pattern, desc, emptyflag in self.topics:
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: topics
make: *** [update] Error 1

Having corrected the cause of this first exception the 
following exception was then encountered:

Upgrading from version 0x2000df0 to 0x20100b5
getting rid of old source files
Updating mailing list: mailman
Traceback (most recent call last):
  File "bin/update", line 569, in ?
    errors = main()
  File "bin/update", line 446, in main
    errors = errors + dolist(listname)
  File "bin/update", line 200, in dolist
    for addr, (reason, when) in mlist.delivery_status.items
():
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: delivery_status
make: *** [update] Error 1

These problems both seem to arise because of the 
following:

1. The MailList class is derived from the classes 
TopicMgr and Bouncer (amongst others).

2. The MailList __init__ function calls the __init__ 
functions of its superclasses if they have that function; 
which they do not in the case of the of TopicMgr and 
Bouncer classes

3. The MailList __init__ function calls its own 
InitTempVars function which in turn calls the 
InitTempVars functions of MailList's superclasses if they 
have that function; which they do not in the case of the 
of class TopicMgr and Bouncer classes

4. The MailList __init__ function does not call the 
InitVars functions of the TopicMgr and Bouncer classes 
which is why self.topics and self.delivery_status are 
undefined attributes of the MailList instance being 
created; these being instance variables introduced by 
MM 2.1b5 and missing from MM 2.0.13 instance of the 
MailList class which is what is being dealt with at the 
time the update is being done.

Adding the following definition to the TopicMgr and 
Bouncer class definitions seem to clear the problem 
although whether this is the best log-tem solution is 
questionable:

    InitTempVars = InitVars


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

>Comment By: Richard Barrett (ppsys)
Date: 2002-12-10 13:13

Message:
Logged In: YES 
user_id=75166

I was wrong about my hack working because on using the 
web admin GUI to update lists I got the error feedback given 
below.

The problem seems to be more deep seated in that the 
InitVars function of the MailList class does not seem to get 
called to initialse the MailList instance variables when loading 
an existing list via the __init__ function but only through the 
Create member function called from newlist and cgi create.py.

At first blush I would think that MailList InitVars function 
should be called from the class' __init__ function before 
loading an existing instance's data into the instance 
variables; but with three functions initialisation functions, 
__init__, InitTempVars and InitVars, I'm getting confused as 
to which are supposed to do what and when.

Bug in Mailman version 2.1b5

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 "/mailman/run/scripts/driver", line 87, in run_main
    main()
  File "/mailman/run/Mailman/Cgi/admin.py", line 76, in main
    i18n.set_language(mlist.preferred_language)
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: preferred_language




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

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

From Nigel.Metheringham at dev.InTechnology.co.uk  Tue Dec 10 09:21:02 2002
From: Nigel.Metheringham at dev.InTechnology.co.uk (Nigel Metheringham)
Date: Tue Dec 10 09:04:50 2002
Subject: [Mailman-Developers] Exim tweak
In-Reply-To: <20021210073647.GY27411@merlins.org>
References: <30082.1039492825@kanga.nu> <20021210073647.GY27411@merlins.org>
Message-ID: <1039512062.12991.8.camel@gaspode.localnet>

On Tue, 2002-12-10 at 07:36, Marc MERLIN wrote:
> How about a list server with many lists so that you always have 50 to
> 100 exims running and trying to clean the queue, deliver mail, or
> talking to mailman...
> In that case (i.e. really loaded server), I'm not convinced that
> spooling everything to disk and having exim process the message on the
> next queue run is going to be that much more effective. Is it?

Well the answer is I don't know....
However an interesting point is that all the hints files will be
updated, meaning that when the queue runner hits the first
message/address routed for mx1.example.com it will then normally pick up
the other messages with addresses waiting on mx1.example.com and push
them down the same SMTP connection.

How this interacts with the max_parallel settings, and TLS/SSL is an
interesting set of questions which early in the morning after a very
late night I am not equipped to deal with :-/   [Switching off all
outgoing TLS/SSL support on a mailing list machine may well be a good
plan, although I *like* the idea of making things more difficult to look
into].

	Nigel.
-- 
[ Nigel Metheringham           Nigel.Metheringham@InTechnology.co.uk ]
[ - Comments in this message are my own and not ITO opinion/policy - ]


From noreply at sourceforge.net  Tue Dec 10 06:19:19 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 10 09:19:35 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-651406 ] MM 2.0.13 to 2.1b5 upgrade fails
Message-ID: <E18LlEF-0006iw-00@sc8-sf-web1.sourceforge.net>

Patches item #651406, was opened at 2002-12-10 12:38
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=651406&group_id=103

Category: None
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: MM 2.0.13 to 2.1b5 upgrade fails

Initial Comment:
make install when updating a MM 2.0.13 installation to 
2.1b5 initally produced the following exception:

Updating mailing list: mailman
Traceback (most recent call last):
  File "bin/update", line 569, in ?
    errors = main()
  File "bin/update", line 446, in main
    errors = errors + dolist(listname)
  File "bin/update", line 186, in dolist
    mlist = MailList.MailList(listname, lock=0)
  File "/mailman/run/Mailman/MailList.py", line 101, in 
__init__
    self.Load()
  File "/mailman/run/Mailman/MailList.py", line 600, in 
Load
    self.CheckValues()
  File "/mailman/run/Mailman/MailList.py", line 650, in 
CheckValues
    for name, pattern, desc, emptyflag in self.topics:
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: topics
make: *** [update] Error 1

Having corrected the cause of this first exception the 
following exception was then encountered:

Upgrading from version 0x2000df0 to 0x20100b5
getting rid of old source files
Updating mailing list: mailman
Traceback (most recent call last):
  File "bin/update", line 569, in ?
    errors = main()
  File "bin/update", line 446, in main
    errors = errors + dolist(listname)
  File "bin/update", line 200, in dolist
    for addr, (reason, when) in mlist.delivery_status.items
():
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: delivery_status
make: *** [update] Error 1

These problems both seem to arise because of the 
following:

1. The MailList class is derived from the classes 
TopicMgr and Bouncer (amongst others).

2. The MailList __init__ function calls the __init__ 
functions of its superclasses if they have that function; 
which they do not in the case of the of TopicMgr and 
Bouncer classes

3. The MailList __init__ function calls its own 
InitTempVars function which in turn calls the 
InitTempVars functions of MailList's superclasses if they 
have that function; which they do not in the case of the 
of class TopicMgr and Bouncer classes

4. The MailList __init__ function does not call the 
InitVars functions of the TopicMgr and Bouncer classes 
which is why self.topics and self.delivery_status are 
undefined attributes of the MailList instance being 
created; these being instance variables introduced by 
MM 2.1b5 and missing from MM 2.0.13 instance of the 
MailList class which is what is being dealt with at the 
time the update is being done.

Adding the following definition to the TopicMgr and 
Bouncer class definitions seem to clear the problem 
although whether this is the best log-tem solution is 
questionable:

    InitTempVars = InitVars


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

>Comment By: Richard Barrett (ppsys)
Date: 2002-12-10 14:19

Message:
Logged In: YES 
user_id=75166

The problem is a by product of the 413752 (coerce to 
plaintext) patch for MM 2.0.13 (mailman-2.0.13-plaintext-
0.17.patch) which had been applied to the existing system

Patch 413752 for MM 2.0.13 changes Version.py as follows:

 # config.db schema version number
-DATA_FILE_VERSION = 21
+DATA_FILE_VERSION = (21, 'plaintext_patch')

In MM 2.1b5 Version.py

DATA_FILE_VERSION = 88

In the CheckVersion member function of the MailList class 
the following comparison succeeds, i.e. the existing data 
structure is seen as being a later revision than MM 2.1b5, 
when patch 413752 has been applied:

        if self.data_version >= mm_cfg.DATA_FILE_VERSION:

and the CheckVersion function returns without calling the 
InitVars function to preset the instance variables to the 
defaults before loading the pickled data values for an existing 
list.

Changing the comparisom to this solves the problem:

        if (type(self.data_version) is type
(mm_cfg.DATA_FILE_VERSION) and \
	    self.data_version >= 
mm_cfg.DATA_FILE_VERSION) or \
	   (type(self.data_version) is type(()) and \
	    self.data_version[0] >= 
mm_cfg.DATA_FILE_VERSION):


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

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

Message:
Logged In: YES 
user_id=75166

I was wrong about my hack working because on using the 
web admin GUI to update lists I got the error feedback given 
below.

The problem seems to be more deep seated in that the 
InitVars function of the MailList class does not seem to get 
called to initialse the MailList instance variables when loading 
an existing list via the __init__ function but only through the 
Create member function called from newlist and cgi create.py.

At first blush I would think that MailList InitVars function 
should be called from the class' __init__ function before 
loading an existing instance's data into the instance 
variables; but with three functions initialisation functions, 
__init__, InitTempVars and InitVars, I'm getting confused as 
to which are supposed to do what and when.

Bug in Mailman version 2.1b5

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 "/mailman/run/scripts/driver", line 87, in run_main
    main()
  File "/mailman/run/Mailman/Cgi/admin.py", line 76, in main
    i18n.set_language(mlist.preferred_language)
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: preferred_language




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

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

From noreply at sourceforge.net  Tue Dec 10 06:39:31 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 10 09:39:47 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-413752 ] Coerce posts to plain text.
Message-ID: <E18LlXn-0008Kw-00@sc8-sf-web3.sourceforge.net>

Patches item #413752, was opened at 2001-04-04 17:23
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103

Category: mail delivery
Group: Mailman 2.0.x
Status: Open
Resolution: None
Priority: 1
Submitted By: Geoffrey T. Dairiki (dairiki)
Assigned to: Nobody/Anonymous (nobody)
Summary: Coerce posts to plain text.

Initial Comment:
This patch adds the ability to have all posts
to a mailing list forced into a MIME text/plain
format.

Many mailing lists have a charter which forbids
binary and HTML posts to the list.  This patch
allows such a charter to be enforced is a
maximally transparent manner.

The feature is configurable on a per-list basis.
If enabled, all posts to the list are run through a 
filter which:

  Squashes multipart messages into a single
flat message (it picks the most plain-text-like
alternative from multipart/alternative entities.)

  Converts 'text/html', 'text/enriched', and
'text/richtext' entities to 'text/plain'.

  Deletes cruft headers from content of type 
'message/rfc822'.

  Deletes any uuencoded files from  'text/plain'
entities.

  Entities of any other types are assumed to
be binary attachements are are deleted.

This patch is on mailman-2.0.3.


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

Comment By: Richard Barrett (ppsys)
Date: 2002-12-10 14:39

Message:
Logged In: YES 
user_id=75166

I encountered some problems with upgrading from MM 2.0.13 
to MM 2.1b5 as a consequence of having installed this patch 
on our existing system.

See:

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

for details of the symptoms and the solution that worked for 
me.

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

Comment By: Jozeph Brasil (jozeph)
Date: 2002-09-12 17:51

Message:
Logged In: YES 
user_id=17693

Hey dairiki, please... look at
https://sourceforge.net/tracker/index.php?func=detail&aid=608524&group_id=103&atid=100103
I don't know if the problem is plaintext bug! :(

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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2002-08-30 17:16

Message:
Logged In: YES 
user_id=45814

Note also that the recent patch sets also incorporate patch
#415448 [1]: a minor patch so that Mailman recognizes bounce
messages from swbell.net ("Sun Internet Mail Server").

This patch inadvertently slipped in, but it does no harm. 
If you don't like it just delete the patches to
Mailman/Bouncers/SimpleMatch.py.

Reference:
[1] 
http://sf.net/tracker/?func=detail&aid=415448&group_id=103&atid=300103


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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2002-08-30 16:07

Message:
Logged In: YES 
user_id=45814

Enh?  The current version of Mailman is 2.0.13.
That said, the latest patch set (named
mailman-2.0.13-plaintext-0.17.patch, and attached below)
will work fine, I think, for Mailmain versions 2.0.x back to
at least 2.0.8, and probably earlier.

Feel free to e-mail me privately for more help. 
<dairiki@dairiki.org>



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

Comment By: Nobody/Anonymous (nobody)
Date: 2002-08-30 15:02

Message:
Logged In: NO 

I'm new to Mailman. I don't understand why you don't have a 
patch for the current version of Mailman, 2.0.10. Can I apply 
an earlier patch safely?

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-28 04:40

Message:
Logged In: YES 
user_id=12800

BTW, I've finally added that link from the wiki to this patch.

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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2002-08-28 03:44

Message:
Logged In: YES 
user_id=45814

It seems the patches continue to work (basically unchanged)
for Mailman-2.0.13. 

Updated patches are attached below.

The patches as well as a pre-patched Mailman-2.0.13 tarball
are at
  ftp://www.dairiki.org/pub/mailman/



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

Comment By: Nobody/Anonymous (nobody)
Date: 2002-08-28 00:22

Message:
Logged In: NO 

Hi Dairiki,

It's me... I added your patch in my latest version and it's
running OK... you can post the patch here! :)

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

Comment By: Jozeph Brasil (jozeph)
Date: 2002-08-27 19:00

Message:
Logged In: YES 
user_id=17693

Hello dairiki... do you have this patch for Mailman-2.0.13 ?

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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2002-08-13 15:43

Message:
Logged In: YES 
user_id=45814

I don't have strong feelings, but my druthers would be to
wait until 2.1 is officially designated "stable".

A link from the wiki would be great!
(There is/was already a link from the FAQ.)






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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-13 15:29

Message:
Logged In: YES 
user_id=12800

Since this patch is against 2.0.x and since MM2.1 provides
support for stuff like this, I'm inclined to close this
patch.  I'd be willing to add a link to this from the
unofficial patches wiki.  What do you think?

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

Comment By: Seb Wills (sebwills)
Date: 2002-02-23 16:20

Message:
Logged In: YES 
user_id=467580

This patch seems to leave any preamble above the first part 
of a multipart message intact. Many mailers put blurb such 
as "This is a MIME-encoded message; you will need a MIME-
aware mail client to see all of this message." here, which 
it makes no sense to reproduce after the mail has be 
coerced into plaintext.

Looks like it's easy enough to change this behaviour by 
commenting out the line

           mimetools.copybinary(infp, outfp) # copy preamble

from Mailman/FilteringMimeWriter.py



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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2001-12-15 18:15

Message:
Logged In: YES 
user_id=45814

Another bug fix.

  Lines which contain nothing but the word 'end'
mysteriously dissapear.  (Reported by David Gibbs.)

The only changed file in Mailman/FilteringMimeWriter.py,
I've attached the latest version of that file to this page.

As usual, patches on mailman 2.0.8 are also attached.

Diffs and a patched Mailman-2.0.8 tarball are at
  ftp://www.dairiki.org/pub/mailman/


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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2001-09-08 20:08

Message:
Logged In: YES 
user_id=45814

More fixes.

* Mailman/FilteringMimeWriter.py:
    Fixes for bugs in python 1.5.2's quopri library module.

The plaintext patches are at version 0.14.
Look for the patches on Mailman 2.0.6, as well as a complete
tarball of patched Mailman 2.0.6 code at
  ftp://www.dairiki.org/pub/mailman/

Patches on 2.0.6 are also attached to this page.


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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2001-08-25 19:34

Message:
Logged In: YES 
user_id=45814

More fixes:

* Mailman/PlaintextMimeWriter.py:
   Change Message-ID: of filtered messages.

* Mailman/pythonlib/multifile.py:
   Fix obscure but occasionally fatal bug.


The first fix is very minor.  The second fix fixes
a bug which caused the plaintext filter to fail 
occasionally.


Diffs from mailman-2.0.6 are available from this page and
are also at:

ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.patch.gz

Pre-patched mailman-2.0.6 source code is at:

ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.tgz


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

Comment By: Nobody/Anonymous (nobody)
Date: 2001-06-16 18:33

Message:
Logged In: NO 

After applying this patch to 2.0.5, I found that I had to 
add this line manually to my existing config file 
$prefix/Mailman/mm_cfg.py...

DEFAULT_FORCE_PLAIN_TEXT = 0

If this line is not added, any web requests and any 
messages posted will produce an error "AttributeError :  
DEFAULT_FORCE_PLAIN_TEXT".

Not sure if I did something wrong or if this is normal, but 
I wanted to advise others just in case

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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2001-05-19 23:49

Message:
Logged In: YES 
user_id=45814

More fixes:

* Mailman/FilteringMimeWriter.py:  Handle 'content-type:
multipart' (no subtype) gracefully.

* Mailman/Handlers/PlainText.py:  Catch exceptions (fatal
errors) from plaintext filter.   When exception is caught,
an error is logged, but the message is passed on
unfiltered.  (A diagnostic message is added to the message
headers.)  This should make it so little piddly bugs in the
filter will get noticed, but at the same time will not cause
messages to get stuck in the queue.

Patches from mailman-2.0.5 are available from this page and
are also at:

ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.patch.gz

Pre-patched mailman-2.0.5 source code is at:

ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.tgz


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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2001-05-17 19:27

Message:
Logged In: YES 
user_id=45814

Another minor bugfix: it turns out pythons mimetools doesn't
treat the content-transfer-encoding is a case insensitive
fashion --- so now we smash the case ourself.

A new patch set on mailman-2.0.5 is available on this page.
Pre-patched mailman source code can be found at:

ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.9.tgz


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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2001-05-08 04:38

Message:
Logged In: YES 
user_id=45814

Disregard last.  (Apparently one can't attache files bigger
than 256 kb.)

Mailman-2.0.5 with plaintext patches applied can be found
(for a limited time) at:
 
ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.8.tgz


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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2001-05-08 04:33

Message:
Logged In: YES 
user_id=45814

If you don't want to mess with patching the source, I've
also attached (below) a tarball of the mailman-2.0.5 source
with my patches already applied.

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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2001-05-08 04:16

Message:
Logged In: YES 
user_id=45814

Here's a rough outline of how to proceed:

1. Start by unpacking a fresh copy of mailman-2.0.5.tgz
2. Change into the top source directory (which was created
in the previous step.
3. Try applying my patches with:
     patch -p1 <
[where.ever]/mailman-2.0.5-plaintext-0.8.patch
(that's "dash pee one")
That should work --- you should not get any warnings or
prompts from patch.  If you do, something is fishy.
4. Run ./configure and 'make install' as usual (read
mailman's INSTALL for instructions on this.)

Feel free to write me at <dairiki@dairiki.org>.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2001-05-08 03:30

Message:
Logged In: NO 

For *some* reason when I apply the patch (the newest one) 
to my freshly downloaded version of Mailman 2.0.5 and 
compile and install mail never reaches the list.  I've 
tried without the patch and everything works fine...  
perhaps I'm patching wrong? I'm just saying:

patch < name_of_patch

It makes me fix a few paths to some of the files, but 
that's it... :-/ Any help would be appriciated!

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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2001-05-07 16:25

Message:
Logged In: YES 
user_id=45814

Fixed bug (reported by Pug Bainter <pug@pug.net> -- thanks!)

New patches,  on mailman-2.0.5 uploaded (below).

The only real change is:

--- 0.5/Mailman/FilteringMimeWriter.py Wed, 04 Apr 2001
10:04:36 -0700 dairiki (mailman/k/4_FilteringM 1.2 664)
+++ 0.8(w)/Mailman/FilteringMimeWriter.py Mon, 07 May 2001
09:05:18 -0700 dairiki (mailman/k/4_FilteringM 1.3 664)
@@ -185,8 +185,12 @@
             pname, pval = string.split(param, '=', 1)
             return (string.lower(pname),
rfc822.unquote(pval))
 
-        return map(split_param, message.getplist())
-
+        def valid_param(param):
+            return '=' in param
+        
+        # Trailing ;'s in content-type yield empty strings
from getplist().
+        return map(split_param,
+                   filter(valid_param, message.getplist()))
 
     def discards_data(fp):
         """Determine whether file object ignores data
written to it.


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

Comment By: Geoffrey T. Dairiki (dairiki)
Date: 2001-04-05 15:37

Message:
Logged In: YES 
user_id=45814

I've just made a minor change:

HTML converted to plain-text now includes a list of links at
the end of
the message.


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

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

From barry at python.org  Tue Dec 10 20:33:12 2002
From: barry at python.org (Barry A. Warsaw)
Date: Tue Dec 10 20:33:44 2002
Subject: [Mailman-Developers] RELEASED Mailman 2.1 beta 6
Message-ID: <15862.38360.272912.231108@gargle.gargle.HOWL>


I've released Mailman 2.1 beta 6.  This is the last planned beta
release before MM2.1 final, which I still expect to release before the
end of the year.  See below for a list of changes since 2.1b5.  There
have been lots of bug fxes and lots of translations updates.

The new tarball has been uploaded to SourceForge, and the various web
sites will be updated shortly.

Enjoy,
-Barry

-------------------- snip snip --------------------
2.1 beta 6 (09-Dec-2002)

    Lots and lots of bug fixes, and translation updates.  Also,

    - ARCHIVER_OBSCURES_EMAILADDRS is now set to true by default.

    - QRUNNER_SAVE_BAD_MESSAGES is now set to true by default.

    - Bounce messages which were recognized, but in which no member
      addresses were found are no longer forwarded to the list
      administrator.

    - bin/arch grew a --wipe option which first removes the entire old
      archive before regenerating the new one.

    - bin/mailmanctl -u now prints a warning that permission problems
      could appear, such as when trying to delete a list through the
      web that has some archives in it.

    - bin/remove_members grew --nouserack/-n and -noadminack/-N options.

    - A new script bin/list_owners has been added for printing out
      list owners and moderators.

    - Dates in the web version of archived messages are now relative
      to the local timezone, and include the timezone names, when
      available.

From david at midrange.com  Tue Dec 10 20:06:39 2002
From: david at midrange.com (David Gibbs)
Date: Tue Dec 10 21:06:44 2002
Subject: [Mailman-Developers] Re: Reply to munging not using correct host?
References: <5.2.0.9.2.20021208095808.02d15e78@linux.midrange.com>
Message-ID: <at66j5$2it$1@main.gmane.org>

"David Gibbs" <david@midrange.com> wrote in message
news:5.2.0.9.2.20021208095808.02d15e78@linux.midrange.com...
> I sent a message to a test list and it got sent out properly ... but the
> reply-to munging isn't set to the correct host.

I just installed beta 6 and this is still a problem.

david





From barry at python.org  Tue Dec 10 22:56:18 2002
From: barry at python.org (Barry A. Warsaw)
Date: Tue Dec 10 22:56:46 2002
Subject: [Mailman-Developers] Re: Reply to munging not using correct host?
References: <5.2.0.9.2.20021208095808.02d15e78@linux.midrange.com>
	<at66j5$2it$1@main.gmane.org>
Message-ID: <15862.46946.469826.370565@gargle.gargle.HOWL>


>>>>> "DG" == David Gibbs <david@midrange.com> writes:

    >> I sent a message to a test list and it got sent out properly
    >> ... but the reply-to munging isn't set to the correct host.

    DG> I just installed beta 6 and this is still a problem.

Be sure to log a SourceForge bug on this matter, with as much
information as you can provide (i.e. how do I reproduce this?).

-Barry

From webperson at now.org  Tue Dec 10 20:06:57 2002
From: webperson at now.org (NOW Website Coordinator)
Date: Tue Dec 10 23:10:03 2002
Subject: [Mailman-Developers] 
 unsubscribing an email address from all lists using the UI
Message-ID: <4.3.2.7.2.20021210195940.00ce3ab0@now.org>

Is there a way to unsubscribe someone from all lists from a web page?  (I'm 
using 2.1b5).I've found remove_members which works fine for the command 
line, and I've even set up a "find" page for myself for one list because 
the computer slows down horribly to load the UI members page.  Any ideas as 
to how to add a "remove from all" form?  Thanks in advance.

FYI, this code does the trick for others who are interested:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<html>
<body>
<FORM action="http://YOUR-DOMAIN/mailman/admin/YOUR-LIST/members" 
method="POST" enctype="multipart/form-data">
   <table WIDTH="100%">
     <tr>
       <td><div align="right">Find member <a 
href="http://www.python.org/doc/current/lib/re-syntax.html">(help)</a>:</div></td>
       <td><INPUT name="findmember" type="TEXT" value="" size="40" ></td>
       <td><INPUT name="findmember_btn" type="SUBMIT" value="Search..." ></td>
     </tr>
   </table>

</FORM>
</body>
</html>


Sarah Stapleton-Gray
--------------------------------------------
Web Site Coordinator
National Organization for Women
http://www.now.org


From barry at python.org  Tue Dec 10 23:20:04 2002
From: barry at python.org (Barry A. Warsaw)
Date: Tue Dec 10 23:20:48 2002
Subject: [Mailman-Developers] 
 unsubscribing an email address from all lists using the UI
References: <4.3.2.7.2.20021210195940.00ce3ab0@now.org>
Message-ID: <15862.48372.436084.720478@gargle.gargle.HOWL>


>>>>> "NWC" == NOW Website Coordinator <webperson@now.org> writes:

    NWC> Is there a way to unsubscribe someone from all lists from a
    NWC> web page?  (I'm using 2.1b5).I've found remove_members which
    NWC> works fine for the command line

That's the only official way at the moment, because the user databases
aren't linked in MM2.1 (they will be in MM3.0).
    
    NWC> and I've even set up a "find" page for myself for one list
    NWC> because the computer slows down horribly to load the UI
    NWC> members page.
    
There was a bug in 2.1b5 that the first page might show too many
members, but I think the alphabetized subgroups should be much
faster.  This is fixed in 2.1b6.

There's also DEFAULT_ADMIN_MEMBER_CHUNKSIZE but that defaults to 30
which should be plenty fast.

-Barry

From noreply at sourceforge.net  Wed Dec 11 03:48:13 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 06:48:33 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi
Message-ID: <E18M5LZ-00004z-00@sc8-sf-web3.sourceforge.net>

Patches item #444884, was opened at 2001-07-26 18:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103

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

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

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

This patch integrates htdig with Mailman and provides:

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

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

You probably want to run this patch as follows:

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=624179

Got a workaround!

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

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

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

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

Message:
Logged In: YES 
user_id=624179

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

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

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

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

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


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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=12800

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

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

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

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

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

Message:
Logged In: YES 
user_id=75166

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


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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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



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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.8

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

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

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to Mm 2.0.7

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

From noreply at sourceforge.net  Wed Dec 11 03:52:43 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 06:52:47 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-444879 ] Archive indexer control to improve index
Message-ID: <E18M5Pv-0000GQ-00@sc8-sf-web3.sourceforge.net>

Patches item #444879, was opened at 2001-07-26 18:01
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103

Category: Pipermail
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 3
Submitted By: Richard Barrett (ppsys)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: Archive indexer control to improve index

Initial Comment:
This patch is applicable to Mailman 2.0.6 release and 
supercedes ealier patches 401669 and 402422.

This patch should improve the quality of search 
results returned by search engines
such as htdig (http://www.htdig.org) where the seach 
engine's index builder responds 
to strings embedded in the html pages that are the 
subject of the indexing. The 
changes in this patch: 

1. allow strings for enabling and disabling indexing 
to be defined in mm_cfg.py.

2. embeds those strings in the pages generated as the 
html version of a list's
   archive.

By default nothing in the html changes. To get the 
desired effect, you must
define ARCHIVE_INDEXING_ENABLE and 
ARCHIVE_INDEXING_DISABLE in mm_cfg.py

You probably want to run this patch as follows:

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

See also the associated patch for integrating the 
htdig search software with mailman's internal archiver 
ouput.



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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

An additional file, README.NOINDEXtags is added to 
indexing-2.0.13-0.3.patch version that discusses the issue of 
what tags to use for controlling various search engine 
indexers.

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

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

Message:
Logged In: YES 
user_id=75166

An error when building the indexing-2.1b2-0.1.patch meant 
that copies of the originals of two of the files modified by this 
version of the patch were added when the patch was run. 
indexing-2.1b2-0.1.patch removes this error. However, the 
original error is benign and can be corrected by deleting the 
extra files HyperArch.py.orig and Defaults.py.in.orig.

An additional file, README.NOINDEXtags is added that 
discusses the issue of what tags to use for controlling various 
search engine indexers.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-08 14:19

Message:
Logged In: YES 
user_id=12800

Another question: is there no standard (de-facto or
otherwise) for generic markup that tells indexers not to
index a particular section?  IOW, for
ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is
there some generic value that would instruct most (all?)
indexers to ignore that section?  Or does it necessarily
have to be indexer specific?  

I'm thinking of the situation where you might have ht://Dig
installed locally, but your archives are still being
spidered by external indexers.  It would be good if
something more generic could be added to Defaults.py.in

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

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

Message:
Logged In: YES 
user_id=12800

Looking at the 2.1b2 patch, why does it try to create
HyperArch.py.orig and Defaults.py.in.orig?  Are those
included in the patch by mistake?

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

indexing-2.0.11-0.1.patch should apply without problems to 
MM 2.0.12

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

indexing-2.0.9-0.1.patch should apply without problems to 
MM 2.0.10

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

Corrects problem noted or 5 Mar 2002 by nobody

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

Comment By: Nobody/Anonymous (nobody)
Date: 2002-03-05 21:41

Message:
Logged In: NO 

When applying this patch I get an error with Hunk 1 and 
Defaults.py is not updated. This happens with the a clean 
download of the latest cvs installation (5 Mar 2002). Any 
ideas what the problem is?

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.8

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

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

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.7

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

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

From noreply at sourceforge.net  Wed Dec 11 03:53:31 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 06:53:36 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-444879 ] Archive indexer control to improve index
Message-ID: <E18M5Qh-0000Hx-00@sc8-sf-web3.sourceforge.net>

Patches item #444879, was opened at 2001-07-26 18:01
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103

Category: Pipermail
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 3
Submitted By: Richard Barrett (ppsys)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: Archive indexer control to improve index

Initial Comment:
This patch is applicable to Mailman 2.0.6 release and 
supercedes ealier patches 401669 and 402422.

This patch should improve the quality of search 
results returned by search engines
such as htdig (http://www.htdig.org) where the seach 
engine's index builder responds 
to strings embedded in the html pages that are the 
subject of the indexing. The 
changes in this patch: 

1. allow strings for enabling and disabling indexing 
to be defined in mm_cfg.py.

2. embeds those strings in the pages generated as the 
html version of a list's
   archive.

By default nothing in the html changes. To get the 
desired effect, you must
define ARCHIVE_INDEXING_ENABLE and 
ARCHIVE_INDEXING_DISABLE in mm_cfg.py

You probably want to run this patch as follows:

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

See also the associated patch for integrating the 
htdig search software with mailman's internal archiver 
ouput.



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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

An additional file, README.NOINDEXtags is added to 
indexing-2.0.13-0.3.patch version that discusses the issue of 
what tags to use for controlling various search engine 
indexers.

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

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

Message:
Logged In: YES 
user_id=75166

An error when building the indexing-2.1b2-0.1.patch meant 
that copies of the originals of two of the files modified by this 
version of the patch were added when the patch was run. 
indexing-2.1b2-0.1.patch removes this error. However, the 
original error is benign and can be corrected by deleting the 
extra files HyperArch.py.orig and Defaults.py.in.orig.

An additional file, README.NOINDEXtags is added that 
discusses the issue of what tags to use for controlling various 
search engine indexers.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-08 14:19

Message:
Logged In: YES 
user_id=12800

Another question: is there no standard (de-facto or
otherwise) for generic markup that tells indexers not to
index a particular section?  IOW, for
ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is
there some generic value that would instruct most (all?)
indexers to ignore that section?  Or does it necessarily
have to be indexer specific?  

I'm thinking of the situation where you might have ht://Dig
installed locally, but your archives are still being
spidered by external indexers.  It would be good if
something more generic could be added to Defaults.py.in

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

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

Message:
Logged In: YES 
user_id=12800

Looking at the 2.1b2 patch, why does it try to create
HyperArch.py.orig and Defaults.py.in.orig?  Are those
included in the patch by mistake?

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

indexing-2.0.11-0.1.patch should apply without problems to 
MM 2.0.12

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

indexing-2.0.9-0.1.patch should apply without problems to 
MM 2.0.10

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

Corrects problem noted or 5 Mar 2002 by nobody

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

Comment By: Nobody/Anonymous (nobody)
Date: 2002-03-05 21:41

Message:
Logged In: NO 

When applying this patch I get an error with Hunk 1 and 
Defaults.py is not updated. This happens with the a clean 
download of the latest cvs installation (5 Mar 2002). Any 
ideas what the problem is?

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.8

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

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

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.7

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

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

From noreply at sourceforge.net  Wed Dec 11 03:55:06 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 06:55:11 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-444879 ] Archive indexer control to improve index
Message-ID: <E18M5SE-0000ME-00@sc8-sf-web3.sourceforge.net>

Patches item #444879, was opened at 2001-07-26 18:01
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103

Category: Pipermail
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 3
Submitted By: Richard Barrett (ppsys)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: Archive indexer control to improve index

Initial Comment:
This patch is applicable to Mailman 2.0.6 release and 
supercedes ealier patches 401669 and 402422.

This patch should improve the quality of search 
results returned by search engines
such as htdig (http://www.htdig.org) where the seach 
engine's index builder responds 
to strings embedded in the html pages that are the 
subject of the indexing. The 
changes in this patch: 

1. allow strings for enabling and disabling indexing 
to be defined in mm_cfg.py.

2. embeds those strings in the pages generated as the 
html version of a list's
   archive.

By default nothing in the html changes. To get the 
desired effect, you must
define ARCHIVE_INDEXING_ENABLE and 
ARCHIVE_INDEXING_DISABLE in mm_cfg.py

You probably want to run this patch as follows:

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

See also the associated patch for integrating the 
htdig search software with mailman's internal archiver 
ouput.



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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

An additional file, README.NOINDEXtags is added to 
indexing-2.0.13-0.3.patch version that discusses the issue of 
what tags to use for controlling various search engine 
indexers.

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

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

Message:
Logged In: YES 
user_id=75166

An error when building the indexing-2.1b2-0.1.patch meant 
that copies of the originals of two of the files modified by this 
version of the patch were added when the patch was run. 
indexing-2.1b2-0.1.patch removes this error. However, the 
original error is benign and can be corrected by deleting the 
extra files HyperArch.py.orig and Defaults.py.in.orig.

An additional file, README.NOINDEXtags is added that 
discusses the issue of what tags to use for controlling various 
search engine indexers.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-08 14:19

Message:
Logged In: YES 
user_id=12800

Another question: is there no standard (de-facto or
otherwise) for generic markup that tells indexers not to
index a particular section?  IOW, for
ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is
there some generic value that would instruct most (all?)
indexers to ignore that section?  Or does it necessarily
have to be indexer specific?  

I'm thinking of the situation where you might have ht://Dig
installed locally, but your archives are still being
spidered by external indexers.  It would be good if
something more generic could be added to Defaults.py.in

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

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

Message:
Logged In: YES 
user_id=12800

Looking at the 2.1b2 patch, why does it try to create
HyperArch.py.orig and Defaults.py.in.orig?  Are those
included in the patch by mistake?

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

indexing-2.0.11-0.1.patch should apply without problems to 
MM 2.0.12

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

indexing-2.0.9-0.1.patch should apply without problems to 
MM 2.0.10

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

Corrects problem noted or 5 Mar 2002 by nobody

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

Comment By: Nobody/Anonymous (nobody)
Date: 2002-03-05 21:41

Message:
Logged In: NO 

When applying this patch I get an error with Hunk 1 and 
Defaults.py is not updated. This happens with the a clean 
download of the latest cvs installation (5 Mar 2002). Any 
ideas what the problem is?

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

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

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

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

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.8

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

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

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.7

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

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

From noreply at sourceforge.net  Wed Dec 11 03:58:39 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 06:58:42 2002
Subject: [Mailman-Developers] [ mailman-Patches-644797 ] Revised mailer exit
	status
Message-ID: <E18M5Vf-0000TH-00@sc8-sf-web3.sourceforge.net>

Patches item #644797, was opened at 2002-11-27 15:56
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103

Category: mail delivery
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Revised mailer exit status

Initial Comment:
This patch modifies the Python scripts in $prefix/scripts/ 
that are used by the MTA to deliver incoming mail to 
Mailman.

The exit statuses now returned are drawn from the mail 
related values defined in /usr/include/sysexits.h

This allows the MTA to return more meaningful 
responses to the sender when rejecting mail. It also 
allows a more sympathetic treatment of mail in the event 
that the Python script suffers an unexpected exception 
when handling incoming email.

Such exceptions are now logged to MM's 
$prefix/logs/erro in all but the most extreme error cases 
and the internal information about the Python exception 
is not passed into the response to the sender.

There are two patch versions; one for MM 2.0.13 and the 
other for MM 2.1b5

in the MM build directory say:

patch -p1 < patch-filename

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

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

Message:
Logged In: YES 
user_id=75166

exitstatus-2.1b6-0.1.patch is a revision of the patch for MM 
2.1b6 compatibility

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

Comment By: Richard Barrett (ppsys)
Date: 2002-11-27 15:58

Message:
Logged In: YES 
user_id=75166

version for MM 2.1b5

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

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

From noreply at sourceforge.net  Wed Dec 11 04:16:31 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 07:16:36 2002
Subject: [Mailman-Developers] [ mailman-Patches-644810 ] Sendmail mailer in
	Python
Message-ID: <E18M5mx-0006s6-00@sc8-sf-web4.sourceforge.net>

Patches item #644810, was opened at 2002-11-27 16:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103

Category: mail delivery
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Sendmail mailer in Python

Initial Comment:
This patch provide a Python implementation (with C 
wrapper) of a Sendmail mailer, if Sendmail is your MTA 
of choice, which removes the necessity of maintining an 
aliases database on your Mailman server. All subject to 
a bunch of conditions most prominent of which is that 
the server has to be pretty much dedicated to MM.

This patch draws on an original contribution by David 
Champion <dgc@uchicago.edu> which is included in 
the contrib directory of the Mailman 2.1b distribution as 
mm-handler.

See the README.SENDMAIL.mailer installed by this 
patch for differences between this and David's Perl 
original and more information of what you are getting into 
if you use this patch.

Versions of the patch for MM 2.0.13 and MM 2.1b5 are 
available.

This patch requires patch 644797 to be installed before 
it.

In the MM build directory say: 

patch -p1 < patch-filename 

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

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

Message:
Logged In: YES 
user_id=75166

mailer-2.1b6-0.1.patch is MM 2.1b6 compatible. It also folds 
the case of listname and servername for compaiblity with 
MMs naive belief that listnames are case all lower case. 
case "(Email addresses are not case sensitive, but they are 
sensitive to almost everything else :-)"


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

Comment By: Richard Barrett (ppsys)
Date: 2002-12-03 17:37

Message:
Logged In: YES 
user_id=75166

Fix for permissions related exceptions being generated by the 
subprocess spawned by mm_mailer script

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

Comment By: Richard Barrett (ppsys)
Date: 2002-12-03 17:36

Message:
Logged In: YES 
user_id=75166

Fix for permissions related exceptions being generated by the 
subprocess spawned by mm_mailer script.

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

Comment By: Richard Barrett (ppsys)
Date: 2002-11-27 16:29

Message:
Logged In: YES 
user_id=75166

version for MM 2.1b5

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

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

From noreply at sourceforge.net  Wed Dec 11 04:19:39 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 07:19:50 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-651406 ] MM 2.0.13 to 2.1b5 upgrade fails
Message-ID: <E18M5pz-0006v5-00@sc8-sf-web4.sourceforge.net>

Patches item #651406, was opened at 2002-12-10 12:38
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=651406&group_id=103

Category: None
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: MM 2.0.13 to 2.1b5 upgrade fails

Initial Comment:
make install when updating a MM 2.0.13 installation to 
2.1b5 initally produced the following exception:

Updating mailing list: mailman
Traceback (most recent call last):
  File "bin/update", line 569, in ?
    errors = main()
  File "bin/update", line 446, in main
    errors = errors + dolist(listname)
  File "bin/update", line 186, in dolist
    mlist = MailList.MailList(listname, lock=0)
  File "/mailman/run/Mailman/MailList.py", line 101, in 
__init__
    self.Load()
  File "/mailman/run/Mailman/MailList.py", line 600, in 
Load
    self.CheckValues()
  File "/mailman/run/Mailman/MailList.py", line 650, in 
CheckValues
    for name, pattern, desc, emptyflag in self.topics:
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: topics
make: *** [update] Error 1

Having corrected the cause of this first exception the 
following exception was then encountered:

Upgrading from version 0x2000df0 to 0x20100b5
getting rid of old source files
Updating mailing list: mailman
Traceback (most recent call last):
  File "bin/update", line 569, in ?
    errors = main()
  File "bin/update", line 446, in main
    errors = errors + dolist(listname)
  File "bin/update", line 200, in dolist
    for addr, (reason, when) in mlist.delivery_status.items
():
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: delivery_status
make: *** [update] Error 1

These problems both seem to arise because of the 
following:

1. The MailList class is derived from the classes 
TopicMgr and Bouncer (amongst others).

2. The MailList __init__ function calls the __init__ 
functions of its superclasses if they have that function; 
which they do not in the case of the of TopicMgr and 
Bouncer classes

3. The MailList __init__ function calls its own 
InitTempVars function which in turn calls the 
InitTempVars functions of MailList's superclasses if they 
have that function; which they do not in the case of the 
of class TopicMgr and Bouncer classes

4. The MailList __init__ function does not call the 
InitVars functions of the TopicMgr and Bouncer classes 
which is why self.topics and self.delivery_status are 
undefined attributes of the MailList instance being 
created; these being instance variables introduced by 
MM 2.1b5 and missing from MM 2.0.13 instance of the 
MailList class which is what is being dealt with at the 
time the update is being done.

Adding the following definition to the TopicMgr and 
Bouncer class definitions seem to clear the problem 
although whether this is the best log-tem solution is 
questionable:

    InitTempVars = InitVars


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

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

Message:
Logged In: YES 
user_id=75166

patch revised for MM 2.1b6 and better documented internally

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

Comment By: Richard Barrett (ppsys)
Date: 2002-12-10 14:19

Message:
Logged In: YES 
user_id=75166

The problem is a by product of the 413752 (coerce to 
plaintext) patch for MM 2.0.13 (mailman-2.0.13-plaintext-
0.17.patch) which had been applied to the existing system

Patch 413752 for MM 2.0.13 changes Version.py as follows:

 # config.db schema version number
-DATA_FILE_VERSION = 21
+DATA_FILE_VERSION = (21, 'plaintext_patch')

In MM 2.1b5 Version.py

DATA_FILE_VERSION = 88

In the CheckVersion member function of the MailList class 
the following comparison succeeds, i.e. the existing data 
structure is seen as being a later revision than MM 2.1b5, 
when patch 413752 has been applied:

        if self.data_version >= mm_cfg.DATA_FILE_VERSION:

and the CheckVersion function returns without calling the 
InitVars function to preset the instance variables to the 
defaults before loading the pickled data values for an existing 
list.

Changing the comparisom to this solves the problem:

        if (type(self.data_version) is type
(mm_cfg.DATA_FILE_VERSION) and \
	    self.data_version >= 
mm_cfg.DATA_FILE_VERSION) or \
	   (type(self.data_version) is type(()) and \
	    self.data_version[0] >= 
mm_cfg.DATA_FILE_VERSION):


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

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

Message:
Logged In: YES 
user_id=75166

I was wrong about my hack working because on using the 
web admin GUI to update lists I got the error feedback given 
below.

The problem seems to be more deep seated in that the 
InitVars function of the MailList class does not seem to get 
called to initialse the MailList instance variables when loading 
an existing list via the __init__ function but only through the 
Create member function called from newlist and cgi create.py.

At first blush I would think that MailList InitVars function 
should be called from the class' __init__ function before 
loading an existing instance's data into the instance 
variables; but with three functions initialisation functions, 
__init__, InitTempVars and InitVars, I'm getting confused as 
to which are supposed to do what and when.

Bug in Mailman version 2.1b5

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 "/mailman/run/scripts/driver", line 87, in run_main
    main()
  File "/mailman/run/Mailman/Cgi/admin.py", line 76, in main
    i18n.set_language(mlist.preferred_language)
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: preferred_language




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

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

From noreply at sourceforge.net  Wed Dec 11 04:41:00 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 07:41:06 2002
Subject: [Mailman-Developers] [ mailman-Bugs-650932 ] 'Administator' typos
Message-ID: <E18M6Ae-0000XU-00@sc8-sf-web1.sourceforge.net>

Bugs item #650932, was opened at 2002-12-09 10:59
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=650932&group_id=103

Category: Web/CGI
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: A.M. Kuchling (akuchling)
Assigned to: Nobody/Anonymous (nobody)
Summary: 'Administator' typos

Initial Comment:
'rgrep -i administator' (missing the R after the first T) 
turns up a number of places where this typo occurs;
some of them are still present in the 2.1b6 running on
python.org.


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-11 07:41

Message:
Logged In: YES 
user_id=12800

Thanks!

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

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

From noreply at sourceforge.net  Wed Dec 11 04:43:07 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 07:43:13 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-652001 ] Reply-to munging not using correct host
Message-ID: <E18M6Ch-0007lT-00@sc8-sf-web4.sourceforge.net>

Bugs item #652001, was opened at 2002-12-11 06:43
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=652001&group_id=103

Category: mail delivery
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: David Gibbs (midrangeman)
Assigned to: Nobody/Anonymous (nobody)
Summary: Reply-to munging not using correct host

Initial Comment:
Mailman 5.1b6 is not using the lists configured host 
name for the reply_to address ... it is using the default 
host name instead.


I have mailman configured for virtual hosting ... the two 
hosts registered are 'midrange.com' 
and 'lists.fallingrock.net'.

Default.py has the standard:
add_virtualhost(DEFAULT_URL_HOST, 
DEFAULT_EMAIL_HOST)

and I've added the following to mm_cfg.py:
VIRTUAL_HOST_OVERVIEW = 1
add_virtualhost('lists.fallingrock.net', 'lists.fallingrock.net')

My test list is configured with:
host_name = 'lists.fallingrock.net'
first_strip_reply_to = 1
reply_goes_to_list = 1
reply_to_address = ''

When I post a message to my test list, the reply-to 
header reflects my DEFAULT host name instead of the 
list's host name...

>Return-Path: <beta-testers-
bounces@lists.fallingrock.net>
>Received: from linux.midrange.com (localhost 
[127.0.0.1])
>         by linux.midrange.com (8.11.6/8.11.6) with 
ESMTP id gB8FtTa02925;
>         Sun, 8 Dec 2002 09:55:29 -0600
>Received: from GRYFFINDOR.midrange.com 
(gryffindor.midrange.com
>         [192.168.1.100])
>         by linux.midrange.com (8.11.6/8.11.6) with 
ESMTP id gB8FtLi02900
>         for <beta-testers@lists.fallingrock.net>;
>         Sun, 8 Dec 2002 09:55:21 -0600
>Message-Id: 
<5.2.0.9.2.20021208095147.02ccf150@linux.midrange.c
om>
>X-Sender: david@linux.midrange.com (Unverified)
>X-Mailer: QUALCOMM Windows Eudora Version 
5.2.0.9
>Date: Sun, 08 Dec 2002 09:55:17 -0600
>To: beta-testers@lists.fallingrock.net
>From: David Gibbs <david@midrange.com>
>Subject: Re: [beta-testers] Up for another round?
>In-Reply-To: 
<5.2.0.9.2.20021208094537.02c70330@linux.midrange.c
om>
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"; 
format=flowed
>X-MailScanner: Found to be clean
>X-BeenThere: beta-testers@lists.fallingrock.net
>X-Mailman-Version: 2.1b5
>Precedence: list
>Reply-To: New Feature Beta Testers <beta-
testers@midrange.com>
>List-Id: New Feature Beta Testers <beta-
testers.lists.fallingrock.net>
>List-Unsubscribe: 
><http://lists.fallingrock.net/mailman2/listinfo/beta-
testers>,
> 
><mailto:beta-testers-request@lists.fallingrock.net?
subject=unsubscribe>
>List-Archive: 
<http://lists.fallingrock.net/mailman2/private/beta-
testers>
>List-Post: <mailto:beta-testers@lists.fallingrock.net>
>List-Help: <mailto:beta-testers-
request@lists.fallingrock.net?subject=help>
>List-Subscribe: 
<http://lists.fallingrock.net/mailman2/listinfo/beta-
testers>,
>         <mailto:beta-testers-
request@lists.fallingrock.net?subject=subscribe>
>Sender: beta-testers-bounces@midrange.com
>Errors-To: beta-testers-bounces@midrange.com



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

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

From noreply at sourceforge.net  Wed Dec 11 05:51:09 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 08:51:20 2002
Subject: [Mailman-Developers] [ mailman-Patches-644797 ] Revised mailer exit
	status
Message-ID: <E18M7GX-0003Hl-00@sc8-sf-web1.sourceforge.net>

Patches item #644797, was opened at 2002-11-27 10:56
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103

Category: mail delivery
>Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Revised mailer exit status

Initial Comment:
This patch modifies the Python scripts in $prefix/scripts/ 
that are used by the MTA to deliver incoming mail to 
Mailman.

The exit statuses now returned are drawn from the mail 
related values defined in /usr/include/sysexits.h

This allows the MTA to return more meaningful 
responses to the sender when rejecting mail. It also 
allows a more sympathetic treatment of mail in the event 
that the Python script suffers an unexpected exception 
when handling incoming email.

Such exceptions are now logged to MM's 
$prefix/logs/erro in all but the most extreme error cases 
and the internal information about the Python exception 
is not passed into the response to the sender.

There are two patch versions; one for MM 2.0.13 and the 
other for MM 2.1b5

in the MM build directory say:

patch -p1 < patch-filename

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

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

Message:
Logged In: YES 
user_id=75166

exitstatus-2.1b6-0.1.patch is a revision of the patch for MM 
2.1b6 compatibility

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

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

Message:
Logged In: YES 
user_id=75166

version for MM 2.1b5

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

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

From noreply at sourceforge.net  Wed Dec 11 19:56:43 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 22:56:49 2002
Subject: [Mailman-Developers] [ mailman-Patches-645297 ] Add PGP support
Message-ID: <E18MKSp-0008Ux-00@sc8-sf-web1.sourceforge.net>

Patches item #645297, was opened at 2002-11-28 09:54
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: Nobody/Anonymous (nobody)
Summary: Add PGP support

Initial Comment:
Support PGP encrypted lists using GnuPG.

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-11 22: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  Wed Dec 11 20:01:33 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 23:01:39 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-646989 ] NAH6 Secure List patch: GPG plugin
Message-ID: <E18MKXV-0004i7-00@sc8-sf-web4.sourceforge.net>

Patches item #646989, was opened at 2002-12-02 11:07
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646989&group_id=103

Category: list administration
>Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Rop Gonggrijp (rop)
Assigned to: Nobody/Anonymous (nobody)
Summary: NAH6 Secure List patch: GPG plugin

Initial Comment:
"NAH6 Secure List" is a patch for Mailman 2.1b5 that 
adds GPG functionality. It is built around a key-scheme 
that allows an admin to create an encrypted list for 
which even the server operator doesn't have access to 
the messages.

Only the public key for the list is given to the server, so 
it can perform 'emergency encryption' in case someone 
forgets, and all users get the public and private key for 
the list.


We think we've done a decent job of describing the new 
functionality from server-operator, list-admin and list-
member points of view. There's also a technical 
document for those familiar with the Mailman code. 
Please have a look at:

http://www.nah6.com/products/secure-list/

and follow the links from there


We feel more people need this, and we'd really like it to 
be part of the Mailman distribution at some point...


Kind Regards,

Rop Gonggrijp
Joshua Eichen


Please forgive mangling the Mailman logo on the site: if 
y'all don't like it or think it's over the top we'll use 
something else....

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-11 23:01

Message:
Logged In: YES 
user_id=12800

The logo's fine (plus the original is free software).

I'm defering this until after MM2.1 because we're about
ready for the first release candidate.

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

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

From noreply at sourceforge.net  Wed Dec 11 20:12:35 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 23:12:41 2002
Subject: [Mailman-Developers] [ mailman-Patches-490029 ] more DIRSETGID for
	BSD
Message-ID: <E18MKiB-0000KV-00@sc8-sf-web1.sourceforge.net>

Patches item #490029, was opened at 2001-12-06 16:46
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=490029&group_id=103

Category: cross platform
Group: Mailman 2.1
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Don Porter (dgp)
Assigned to: Nobody/Anonymous (nobody)
Summary: more DIRSETGID for BSD

Initial Comment:
As described in README.BSD, 'chmod g+s' is troublesome,
so on BSD systems we

	% make DIRSETGID=: install

That only works if all 'chmod g+s' in all Makefiles
are replaced with $(DIRSETGID).  Two in
src/Makefile.in have been overlooked.  Here's the
simple patch fixing that.



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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-11 23:12

Message:
Logged In: YES 
user_id=12800

I rediscovered this patch and have now applied it.

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

Comment By: Don Porter (dgp)
Date: 2002-04-20 19:53

Message:
Logged In: YES 
user_id=80530

I just upgraded to 2.0.10 and this patch still
is not in place.  What's the holdup?

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

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

From noreply at sourceforge.net  Wed Dec 11 20:30:35 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 23:30:43 2002
Subject: [Mailman-Developers] [ mailman-Patches-602087 ] observe configure
	srcdir
Message-ID: <E18MKzb-0000dT-00@sc8-sf-web1.sourceforge.net>

Patches item #602087, was opened at 2002-08-29 16:44
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=602087&group_id=103

Category: configure/install
Group: Mailman 2.1
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Donn Cave (donnc)
Assigned to: Nobody/Anonymous (nobody)
Summary: observe configure srcdir

Initial Comment:
(2nd try, hopefully with attached file this time.)

These patches to Makefile.in in several directories make 
the --srcdir configure option work.  Which can be very 
useful if you have a multi-platform build system.

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-11 23:30

Message:
Logged In: YES 
user_id=12800

Applied

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

Comment By: Donn Cave (donnc)
Date: 2002-09-05 11:45

Message:
Logged In: YES 
user_id=42839

I'm sorry - that's a local modification, of course, and I shouldn't 
have included it with this patch.  I have hacked in another 
authentication system for our Kerberos realm, cf. http://www.mail-
archive.com/mailman-developers@python.org/msg03713.html

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-09-04 22:50

Message:
Logged In: YES 
user_id=12800

In CGI_PROGS in the src/Makefile.in patch, where did "login"
sneak in from?

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

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

From noreply at sourceforge.net  Wed Dec 11 20:35:43 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 11 23:35:47 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-645421 ] Remove all Makefiles on make distclean
Message-ID: <E18ML4Z-00048i-00@sc8-sf-web2.sourceforge.net>

Patches item #645421, was opened at 2002-11-28 15:50
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645421&group_id=103

Category: configure/install
Group: Mailman 2.1
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Matthias Juchem (brightice)
Assigned to: Nobody/Anonymous (nobody)
Summary: Remove all Makefiles on make distclean

Initial Comment:
mailman/messages/Makefile and 
mailman/tests/*/Makefile do not get cleaned up when
doing a 'make distclean'.

This should patch fix it.

Tested like this: 'configure --some-options; make
distclean'; seems to work


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

Comment By: Matthias Juchem (brightice)
Date: 2002-12-08 19:28

Message:
Logged In: YES 
user_id=60479

Stupid me, patch is for 2.1, not for 2.2/3.0.

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

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

From barry at python.org  Thu Dec 12 00:12:22 2002
From: barry at python.org (Barry A. Warsaw)
Date: Thu Dec 12 00:12:50 2002
Subject: [Mailman-Developers] Re: Legal trouble in Germany
References: <200212090917.gB99HoX13517@mailgate5.cinetic.de>
Message-ID: <15864.6838.691418.752245@gargle.gargle.HOWL>


>>>>> "MK" == Michael Kallas <michael.kallas@web.de> writes:

    MK> According to this court, you would have to write an email
    MK> instead of being able to sign up via web.  But we all know
    MK> that it's no problem to fake email addresses.  Therefore this
    MK> is a "chicken and egg" situation that could only be solved by
    MK> reliable identification of the subscriber :-( I don't have any
    MK> solution at hand but just wanted to inform so that maybe
    MK> something can be done about it.

I'll refrain from making an ass out of myself by trying to make sense
of German law or its legislature's intent.  I'm decidedly donkey-shaped
<wink> for trying that in my own country. ;)

In any event, don't forget that you have an audit trail in
logs/subscribe, of all pending subscriptions and subscriptions.  So
you're not completely hosed, assuming you have some way of legally
vouching for the veracity of that file (not Mailman's responsibility).
At least you can point to the file and say "see, soandso@example.com
requested subscription to my mailing list."  That's about the best
Mailman can do I think.

-Barry

From noreply at sourceforge.net  Thu Dec 12 03:17:43 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu Dec 12 06:17:47 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-642996 ] can't send Plain Digest w/multipart msg.
Message-ID: <E18MRLb-0006mP-00@sc8-sf-web2.sourceforge.net>

Bugs item #642996, was opened at 2002-11-24 16:42
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642996&group_id=103

Category: mail delivery
Group: 2.1 beta
Status: Open
Resolution: Works For Me
Priority: 4
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: can't send Plain Digest w/multipart msg.

Initial Comment:
cron/senddigests and cgi-bin/admin/digest
can't send plain digest when multipart
message(s) are contained.

Note: Attached file will solve this
problem for only cron/senddigests, but
not for cgi.


Traceback:

admin(17454):
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
admin(17454): [----- Mailman Version: 2.1b5 -----]
admin(17454): [----- Traceback ------]
admin(17454): Traceback (most recent call last):
admin(17454):   File
"/usr/local/mail/mailman/scripts/driver", line 87, in
run_main
admin(17454):     main()
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Cgi/admin.py", line
169, in main
admin(17454):     change_options(mlist, category,
subcat, cgidata, doc)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Cgi/admin.py", line
1229, in change_options
admin(17454):     gui.handleForm(mlist, category,
subcat, cgidata, doc)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Gui/GUIBase.py", line
169, in handleForm
admin(17454):     self._setValue(mlist, property, val,
doc)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Gui/Digest.py", line
148, in _setValue
admin(17454):     status = mlist.send_digest_now()
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Digester.py", line 60,
in send_digest_now
admin(17454):     ToDigest.send_digests(self, mboxfp)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py",
line 130, in send_digests
admin(17454):     send_i18n_digests(mlist, mboxfp)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py",
line 301, in send_i18n_digests
admin(17454):     g(msg, unixfrom=0)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 100, in flatten
admin(17454):     self._write(msg)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 128, in _write
admin(17454):     self._dispatch(msg)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 154, in _dispatch
admin(17454):     meth(msg)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 212, in _handle_text
admin(17454):     raise TypeError, 'string payload
expected: %s' % type(payload)
admin(17454): TypeError: string payload expected: <type
'list'>


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

>Comment By: Hatuka*nezumi (hatukanezumi)
Date: 2002-12-12 20:17

Message:
Logged In: YES 
user_id=529503

Hmm... It is not reproducible on 2.1b6 release.
Please delete.  Sorry.


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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-03 01:11

Message:
Logged In: YES 
user_id=12800

I tried some examples but couldn't get this to reproduce. 
Can you send me an example message which, when sent through
the plain text digest, causes it to barf like this?  IOW,
can you upload a reproducible test case?

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

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

From noreply at sourceforge.net  Thu Dec 12 06:18:57 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu Dec 12 09:19:04 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-642996 ] can't send Plain Digest w/multipart msg.
Message-ID: <E18MUAz-0001C6-00@sc8-sf-web1.sourceforge.net>

Bugs item #642996, was opened at 2002-11-24 02:42
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642996&group_id=103

Category: mail delivery
Group: 2.1 beta
>Status: Closed
Resolution: Works For Me
Priority: 4
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: can't send Plain Digest w/multipart msg.

Initial Comment:
cron/senddigests and cgi-bin/admin/digest
can't send plain digest when multipart
message(s) are contained.

Note: Attached file will solve this
problem for only cron/senddigests, but
not for cgi.


Traceback:

admin(17454):
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
admin(17454): [----- Mailman Version: 2.1b5 -----]
admin(17454): [----- Traceback ------]
admin(17454): Traceback (most recent call last):
admin(17454):   File
"/usr/local/mail/mailman/scripts/driver", line 87, in
run_main
admin(17454):     main()
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Cgi/admin.py", line
169, in main
admin(17454):     change_options(mlist, category,
subcat, cgidata, doc)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Cgi/admin.py", line
1229, in change_options
admin(17454):     gui.handleForm(mlist, category,
subcat, cgidata, doc)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Gui/GUIBase.py", line
169, in handleForm
admin(17454):     self._setValue(mlist, property, val,
doc)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Gui/Digest.py", line
148, in _setValue
admin(17454):     status = mlist.send_digest_now()
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Digester.py", line 60,
in send_digest_now
admin(17454):     ToDigest.send_digests(self, mboxfp)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py",
line 130, in send_digests
admin(17454):     send_i18n_digests(mlist, mboxfp)
admin(17454):   File
"/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py",
line 301, in send_i18n_digests
admin(17454):     g(msg, unixfrom=0)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 100, in flatten
admin(17454):     self._write(msg)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 128, in _write
admin(17454):     self._dispatch(msg)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 154, in _dispatch
admin(17454):     meth(msg)
admin(17454):   File
"/usr/local/mail/mailman/pythonlib/email/Generator.py",
line 212, in _handle_text
admin(17454):     raise TypeError, 'string payload
expected: %s' % type(payload)
admin(17454): TypeError: string payload expected: <type
'list'>


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-12 09:18

Message:
Logged In: YES 
user_id=12800

Cool, thanks for the update

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

Comment By: Hatuka*nezumi (hatukanezumi)
Date: 2002-12-12 06:17

Message:
Logged In: YES 
user_id=529503

Hmm... It is not reproducible on 2.1b6 release.
Please delete.  Sorry.


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

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

Message:
Logged In: YES 
user_id=12800

I tried some examples but couldn't get this to reproduce. 
Can you send me an example message which, when sent through
the plain text digest, causes it to barf like this?  IOW,
can you upload a reproducible test case?

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

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

From noreply at sourceforge.net  Thu Dec 12 13:01:47 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu Dec 12 16:01:51 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-652910 ] Codeset of header and footer
Message-ID: <E18MaSp-00089p-00@sc8-sf-web1.sourceforge.net>

Patches item #652910, was opened at 2002-12-12 22:01
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=652910&group_id=103

Category: internationalization
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Codeset of header and footer

Initial Comment:
This patch should arrange to put the proper (i.e. the
list's) charset fields into the header and footer.

It is completely untested.

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

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

From noreply at sourceforge.net  Thu Dec 12 19:41:09 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu Dec 12 22:41:17 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-652910 ] Codeset of header and footer
Message-ID: <E18MghJ-0007Pv-00@sc8-sf-web4.sourceforge.net>

Patches item #652910, was opened at 2002-12-12 16:01
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=652910&group_id=103

Category: internationalization
Group: Mailman 2.1
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Codeset of header and footer

Initial Comment:
This patch should arrange to put the proper (i.e. the
list's) charset fields into the header and footer.

It is completely untested.

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-12 22:41

Message:
Logged In: YES 
user_id=12800

Good catch, thanks!

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

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

From noreply at sourceforge.net  Fri Dec 13 03:57:58 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 13 06:58:06 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-648604 ] Crash from "article file missing" error
Message-ID: <E18MoS6-0003w8-00@sc8-sf-web2.sourceforge.net>

Bugs item #648604, was opened at 2002-12-04 20:51
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=648604&group_id=103

Category: None
Group: 2.1 beta
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: Crash from "article file missing" error

Initial Comment:
If I playfully delete the HTML version of a message and then re-run bin/arch, it crashes:

$ rm -f archives/private/mems-talk/2001-July/005007.html

$ /bin/arch mems-talk
#00000 <E15QYR8-0006UV-00@ute.cnri.reston.va.us>
figuring article archives
2001-July
Updating index files for archive [2001-July]
  Date
  Subject
  Author
  Thread
Computing threaded index
Updating HTML for article 8891
Updating HTML for article 8899
Updating HTML for article 8900
Updating HTML for article 8901
Updating HTML for article 8902
Updating HTML for article 8903
Updating HTML for article 8904
Updating HTML for article 5007
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1238, in update_article
    self.message(_("article file %s is missing!")
TypeError: format requires a mapping

To my embarassment, I can't make this simple %s work at all!  Must be some funky I18N thing.  If I remove the _() from the format string, it works.



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

Comment By: Patrick Finnerty (finnertyp)
Date: 2002-12-13 11:57

Message:
Logged In: YES 
user_id=594846

Hi,

I've got the same problem but I don't get how to resolve it. 

arch appears to be trying to index a html file that isn't there.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-05 05:53

Message:
Logged In: YES 
user_id=12800

It's an i18n thing.  Strings wrapped in _() can't have bare
%s's, they have to be %(name)s substitutions.

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

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

From noreply at sourceforge.net  Fri Dec 13 05:17:20 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 13 08:17:23 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-653242 ] Charset of original message
Message-ID: <E18Mpgu-00060T-00@sc8-sf-web4.sourceforge.net>

Patches item #653242, was opened at 2002-12-13 14:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=653242&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Charset of original message

Initial Comment:
The current decoration code strips the charset from the
new inner message, as get_charset returns None
(get_content_charset would correctly return the charset
from the content-type). However, since the content-type
gets copied already, copying the charset again isn't
needed.

I've tested this outside mailman on a single message.

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

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

From noreply at sourceforge.net  Fri Dec 13 06:05:02 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 13 09:05:25 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-648604 ] Crash from "article file missing" error
Message-ID: <E18MqR4-0007p7-00@sc8-sf-web4.sourceforge.net>

Bugs item #648604, was opened at 2002-12-04 15:51
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=648604&group_id=103

Category: None
Group: 2.1 beta
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Crash from "article file missing" error

Initial Comment:
If I playfully delete the HTML version of a message and then re-run bin/arch, it crashes:

$ rm -f archives/private/mems-talk/2001-July/005007.html

$ /bin/arch mems-talk
#00000 <E15QYR8-0006UV-00@ute.cnri.reston.va.us>
figuring article archives
2001-July
Updating index files for archive [2001-July]
  Date
  Subject
  Author
  Thread
Computing threaded index
Updating HTML for article 8891
Updating HTML for article 8899
Updating HTML for article 8900
Updating HTML for article 8901
Updating HTML for article 8902
Updating HTML for article 8903
Updating HTML for article 8904
Updating HTML for article 5007
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
    main()
  File "./bin/arch", line 176, in main
    archiver.close()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 303, in close
    self.update_dirty_archives()
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives
    self.update_archive(i)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1072, in update_archive
    self.__super_update_archive(archive)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive
    self._update_thread_index(archive, arcdir)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 479, in _update_thread_index
    self.update_article(arcdir, article, a1, a3)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1238, in update_article
    self.message(_("article file %s is missing!")
TypeError: format requires a mapping

To my embarassment, I can't make this simple %s work at all!  Must be some funky I18N thing.  If I remove the _() from the format string, it works.



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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-13 09:05

Message:
Logged In: YES 
user_id=12800

Upgrade to 2.1b6 -- it fixes the problem.

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

Comment By: Patrick Finnerty (finnertyp)
Date: 2002-12-13 06:57

Message:
Logged In: YES 
user_id=594846

Hi,

I've got the same problem but I don't get how to resolve it. 

arch appears to be trying to index a html file that isn't there.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-05 00:53

Message:
Logged In: YES 
user_id=12800

It's an i18n thing.  Strings wrapped in _() can't have bare
%s's, they have to be %(name)s substitutions.

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

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

From noreply at sourceforge.net  Fri Dec 13 08:25:58 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 13 11:26:06 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-653242 ] Charset of original message
Message-ID: <E18MsdS-00023w-00@sc8-sf-web3.sourceforge.net>

Patches item #653242, was opened at 2002-12-13 08:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=653242&group_id=103

Category: None
>Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Charset of original message

Initial Comment:
The current decoration code strips the charset from the
new inner message, as get_charset returns None
(get_content_charset would correctly return the charset
from the content-type). However, since the content-type
gets copied already, copying the charset again isn't
needed.

I've tested this outside mailman on a single message.

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

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

From noreply at sourceforge.net  Fri Dec 13 08:35:09 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 13 11:35:13 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-653242 ] Charset of original message
Message-ID: <E18MsmL-0005oW-00@sc8-sf-web4.sourceforge.net>

Patches item #653242, was opened at 2002-12-13 08:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=653242&group_id=103

Category: None
Group: Mailman 2.1
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Charset of original message

Initial Comment:
The current decoration code strips the charset from the
new inner message, as get_charset returns None
(get_content_charset would correctly return the charset
from the content-type). However, since the content-type
gets copied already, copying the charset again isn't
needed.

I've tested this outside mailman on a single message.

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

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

From noreply at sourceforge.net  Fri Dec 13 08:37:53 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 13 11:38:06 2002
Subject: [Mailman-Developers] 
 [ mailman-Feature Requests-626125 ] listinfo page doesn't show newsgrp name
Message-ID: <E18Msoz-0005v7-00@sc8-sf-web4.sourceforge.net>

Feature Requests item #626125, was opened at 2002-10-20 19:33
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=626125&group_id=103

>Category: None
>Group: None
Status: Open
Resolution: None
Priority: 7
Submitted By: Ben Elliston (elliston)
Assigned to: Nobody/Anonymous (nobody)
Summary: listinfo page doesn't show newsgrp name

Initial Comment:
If a mailing list is gatewayed to a newsgroup, the
listinfo page does not help a user discover what the
newsgroup is, or where to read it!

Can this be added?


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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-13 11:37

Message:
Logged In: YES 
user_id=12800

Moving to feature requests since I won't be adding this for
MM2.1

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

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

From marilyn at deliberate.com  Sat Dec 14 22:06:07 2002
From: marilyn at deliberate.com (Marilyn Davis)
Date: Sun Dec 15 01:06:13 2002
Subject: [Mailman-Developers] Mailman/eVote collaboration
Message-ID: <Pine.LNX.4.10.10212142152450.1075-100000@rosa.deliberate.com>

Hello Mailman developers,

I don't get to work on the port to Mailman as much as I'd like to
because I'm preparing to teach my first Python course in January!
What a brilliant language!

But, I do have it all working together now, and very nicely.

A complicated part was coordinating the nomail feature with eVote.
eVote has a "vacation" feature that puts the ballot on hold while the
name is taken off the majordomo list.  While on vacation, votes are
not accepted because that would break the security that eVote's vote
receipt gives.  To come back from vacation, when using the eVote
feature, you have to send a random-keyed confirmation message.

But, with mailman, I'm disabling eVote's vacation feature and telling
users to set 'nomail'.  And when 'nomail' is set, this info is
communicated to eVote, via a hack, so that votes aren't accepted.

eVote sends a message acknowledging this change in status, which is
redundant with mailman's acknowledgment. eVote also sends the
acknowledgment to the list's owner, so that the owner is aware of who
is voting and who is not.  So there's some duplication of
acknowledgments there.  I could stop it but I'd rather stop the
mailman acknowledgment because it happens when only half the job is
done, the mailman half.  So, I'll just leave both acknowledgments --
unless someone talks me into another point of view.

Mostly, this is just a status report, unless someone has a thought.

Next, I have to fix up an installation script and release the bundle.

Marilyn Davis






From mburton at jo.birdsense.com  Sun Dec 15 19:26:20 2002
From: mburton at jo.birdsense.com (Mike Burton)
Date: Sun Dec 15 22:26:40 2002
Subject: [Mailman-Developers] Personalization question
Message-ID: <002301c2a4b2$e9cebfd0$020a0a0a@ALFA>

Is there a reason that user_optionsurl returns the mailers address and
domain instead of the web sites address and domain?  Is this intentional
or should a bug report be generated on this?  If it's intentional, what
is the reasoning?

Take care,
Mike



From mburton at jo.birdsense.com  Mon Dec 16 20:06:32 2002
From: mburton at jo.birdsense.com (Mike Burton)
Date: Mon Dec 16 23:06:49 2002
Subject: [Mailman-Developers] Personalization question
In-Reply-To: <3DFE5B06.3070403@sun.com>
Message-ID: <003601c2a581$b2085550$020a0a0a@ALFA>

Hi Mick,

I take it I didn't make myself perfectly clear.  I understand that this
is issued per user (thus the name personalization).  At the bottom of my
lists mails it reads (using user_optionsurl)
http://jo.birdsense.com/mailman/options/[listname]/mburton%40jo.birdsens
e.com - this is my mail systems address (jo.birdsense.com).  

What I would expect is
http://www.birdsense.com/mailman/options/[listname]/mburton%40jo.birdsen
se.com which is my web server's address.  Note the www instead of jo in
the address.

This is what is shown at the bottom of the mailman-users list mails -
http://mail.python.org/mailman/options/mailman-users/mburton%40jo.birdse
nse.com.  Again I would suspect that it might want to read
www.python.org instead of mail.python.org, although I am not sure of
this one as I am not the admin for that system and really don't know how
they have it setup and configured.

Am I completely missing something here?  Are my expectations that it
would use the web server's address unreasonable?

Thanks,
Mike

> -----Original Message-----
> From: Dan Mick [mailto:Dan.Mick@sun.com] 
> Sent: Monday, December 16, 2002 3:00 PM
> To: Mike Burton
> Subject: Re: [Mailman-Developers] Personalization question
> 
> 
> Mike Burton wrote:
> 
> > Is there a reason that user_optionsurl returns the mailers 
> address and
> > domain instead of the web sites address and domain?  Is 
> this intentional
> > or should a bug report be generated on this?  If it's 
> intentional, what
> > is the reasoning?
> 
> I guess I don't quite understand; the whole point of "the 
> user's options" 
> is that it's per-user, yes...what would you expect?...



From dan.mick at sun.com  Mon Dec 16 20:33:06 2002
From: dan.mick at sun.com (Dan Mick)
Date: Mon Dec 16 23:38:04 2002
Subject: [Mailman-Developers] Personalization question
In-Reply-To: <003601c2a581$b2085550$020a0a0a@ALFA>
References: <003601c2a581$b2085550$020a0a0a@ALFA>
Message-ID: <3DFEA902.7080606@sun.com>

Mike Burton wrote:

> Hi Mick,

Dan...and I'd sent this to you privately to try to clarify off-list, but I 
guess my desires are secondary to yours.  Oh well, so be it.

> I take it I didn't make myself perfectly clear.  I understand that this
> is issued per user (thus the name personalization).  At the bottom of my
> lists mails it reads (using user_optionsurl)
> http://jo.birdsense.com/mailman/options/[listname]/mburton%40jo.birdsens
> e.com - this is my mail systems address (jo.birdsense.com).
>
> What I would expect is
> http://www.birdsense.com/mailman/options/[listname]/mburton%40jo.birdsen
> se.com which is my web server's address.  Note the www instead of jo in
> the address.
>
> This is what is shown at the bottom of the mailman-users list mails -
> http://mail.python.org/mailman/options/mailman-users/mburton%40jo.birdse
> nse.com.  Again I would suspect that it might want to read
> www.python.org instead of mail.python.org, although I am not sure of
> this one as I am not the admin for that system and really don't know how
> they have it setup and configured.
>
> Am I completely missing something here?  Are my expectations that it
> would use the web server's address unreasonable?

No, you're not being unreasonable; you just asked a question I couldn't 
understand.

So you mean "the hyperlink for the user options has a hostname which is 
apparently wrong; it looks like it's the hostname of the mail address 
rather than the hostname of the web server".  It is, of course, a 
coincidence; if you used dan.mick@sun.com's options, the link would not be
http://sun.com/...., but rather http://jo.birdsense.com/..., of course.
So no, it's not the domain of the email address at all.

Your question is really "why do the hyperlinks in my user-options links use 
the wrong hostname".

The problem is likely in your DEFAULT_ settings in mm_cfg.py (or 
Defaults.py).  See the comments in Defaults.py around DEFAULT_URL_HOST
(assuming you're using 2.1 latest or near to it).

>
>
> Thanks,
> Mike
>
>
> >-----Original Message-----
> >From: Dan Mick [mailto:Dan.Mick@sun.com]
> >Sent: Monday, December 16, 2002 3:00 PM
> >To: Mike Burton
> >Subject: Re: [Mailman-Developers] Personalization question
> >
> >
> >Mike Burton wrote:
> >
> >
> >>Is there a reason that user_optionsurl returns the mailers
> >
> >address and
> >
> >>domain instead of the web sites address and domain?  Is
> >
> >this intentional
> >
> >>or should a bug report be generated on this?  If it's
> >
> >intentional, what
> >
> >>is the reasoning?
> >
> >I guess I don't quite understand; the whole point of "the
> >user's options"
> >is that it's per-user, yes...what would you expect?...
>
>
>
>
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers@python.org
> http://mail.python.org/mailman/listinfo/mailman-developers




From noreply at sourceforge.net  Tue Dec 17 04:13:52 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 17 07:13:52 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-655144 ] Setting language through config_list
Message-ID: <E18OGbg-0001SM-00@sc8-sf-web2.sourceforge.net>

Bugs item #655144, was opened at 2002-12-17 13:13
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655144&group_id=103

Category: command line scripts
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Setting language through config_list

Initial Comment:
I tried changing a list's preferred_language through
config_list, and got this traceback

Traceback (most recent call last):
  File "config_list", line 336, in ?
    main()
  File "config_list", line 331, in main
    do_input(listname, infile, checkonly, verbose)
  File "config_list", line 283, in do_input
    gui._setValue(mlist, k, validval, fakedoc)
  File "/home/mailman/Mailman/Gui/Language.py", line
121, in _setValue
    doc.set_language(val)


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

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

From noreply at sourceforge.net  Tue Dec 17 06:49:32 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 17 09:49:33 2002
Subject: [Mailman-Developers] [ mailman-Patches-655214 ] Fix archiving
Message-ID: <E18OJ2K-0001qi-00@sc8-sf-web1.sourceforge.net>

Patches item #655214, was opened at 2002-12-17 15:49
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=655214&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix archiving

Initial Comment:
This patch restores MIME charset capabilities for
article archiving in CVS mailman.

It:
- removes the .charset attribute from articles; all
articles are encoded in the list's charset,

- decodes subject and author to Unicode; if this fails,
no decoding (not even MIME) is done to subject and author,

- MIME-decodes the body in the constructor using
get_payload, removes the hand-crafted qp decoding from
_get_body,

- Unicode-decodes the body in the constructor if the
body's charset differs from the list's charset,

- fixes processbody_URLquote to always return byte
strings (by escaping the URL also); comparing the old
and the new string is no longer possible since the old
string is Unicode and the new string is a list-encoded
byte string.

- changes text archiving to have the archives in the
list's encoding, with unsupported characters 'replace'd

- Fixes a bug in the scrubber, where a
content-transfer-encoding might have survived
flattening of the message.

With these changes, I can process the playground
archives correctly, to get mojibake-free pages.

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

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

From noreply at sourceforge.net  Tue Dec 17 00:13:49 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 17 12:02:28 2002
Subject: [Mailman-Developers] [ mailman-Bugs-655079 ] Major security hole.....
Message-ID: <E18OCrN-0007Jd-00@sc8-sf-web3.sourceforge.net>

Bugs item #655079, was opened at 2002-12-17 09:13
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655079&group_id=103

Category: security/privacy
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Nicolas Weeger (ryo_saeba)
Assigned to: Nobody/Anonymous (nobody)
Summary: Major security hole.....

Initial Comment:
Just found a nice security bug:
on the main list page, you have 2 fields to enter admin 
mail & password to view list subscriptions.
Well, you can just enter a valid admin password, and it'll 
work !!! Even if the mail address is blank / invalid !!

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

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

From noreply at sourceforge.net  Tue Dec 17 14:35:25 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 17 17:35:19 2002
Subject: [Mailman-Developers] [ mailman-Bugs-655079 ] Major security hole.....
Message-ID: <E18OQJB-0003CR-00@sc8-sf-web3.sourceforge.net>

Bugs item #655079, was opened at 2002-12-17 08:13
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655079&group_id=103

Category: security/privacy
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Nicolas Weeger (ryo_saeba)
Assigned to: Nobody/Anonymous (nobody)
Summary: Major security hole.....

Initial Comment:
Just found a nice security bug:
on the main list page, you have 2 fields to enter admin 
mail & password to view list subscriptions.
Well, you can just enter a valid admin password, and it'll 
work !!! Even if the mail address is blank / invalid !!

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

Comment By: Dan Mick (dmick)
Date: 2002-12-17 22:35

Message:
Logged In: YES 
user_id=10725

It's assumed that if you have the admin password, you're
allowed to view the archives.  Why is this a security hole?
 Seems perfectly appropriate to me.

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

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

From noreply at sourceforge.net  Tue Dec 17 14:52:02 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 17 17:51:57 2002
Subject: [Mailman-Developers] [ mailman-Bugs-655079 ] Major security hole.....
Message-ID: <E18OQZG-0003bR-00@sc8-sf-web3.sourceforge.net>

Bugs item #655079, was opened at 2002-12-17 03:13
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655079&group_id=103

Category: security/privacy
Group: 2.0.x
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Nicolas Weeger (ryo_saeba)
Assigned to: Nobody/Anonymous (nobody)
Summary: Major security hole.....

Initial Comment:
Just found a nice security bug:
on the main list page, you have 2 fields to enter admin 
mail & password to view list subscriptions.
Well, you can just enter a valid admin password, and it'll 
work !!! Even if the mail address is blank / invalid !!

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

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-17 17:52

Message:
Logged In: YES 
user_id=12800

Dan's right, the admin can always read the archives and by
design doesn't need to enter an email address.

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

Comment By: Dan Mick (dmick)
Date: 2002-12-17 17:35

Message:
Logged In: YES 
user_id=10725

It's assumed that if you have the admin password, you're
allowed to view the archives.  Why is this a security hole?
 Seems perfectly appropriate to me.

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

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

From noreply at sourceforge.net  Tue Dec 17 23:39:02 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 18 02:38:54 2002
Subject: [Mailman-Developers] [ mailman-Bugs-655079 ] Major security hole.....
Message-ID: <E18OYnG-0007M6-00@sc8-sf-web2.sourceforge.net>

Bugs item #655079, was opened at 2002-12-17 09:13
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655079&group_id=103

Category: security/privacy
Group: 2.0.x
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Nicolas Weeger (ryo_saeba)
Assigned to: Nobody/Anonymous (nobody)
Summary: Major security hole.....

Initial Comment:
Just found a nice security bug:
on the main list page, you have 2 fields to enter admin 
mail & password to view list subscriptions.
Well, you can just enter a valid admin password, and it'll 
work !!! Even if the mail address is blank / invalid !!

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

>Comment By: Nicolas Weeger (ryo_saeba)
Date: 2002-12-18 08:39

Message:
Logged In: YES 
user_id=303511

Well, granted, but only if the mail is left blank !
I mean, if you put an email address, aren't you supposed to 
enter YOUR password, not an admin's ?
Currently, put an admin password & ANY MAIL and it works...

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-17 23:52

Message:
Logged In: YES 
user_id=12800

Dan's right, the admin can always read the archives and by
design doesn't need to enter an email address.

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

Comment By: Dan Mick (dmick)
Date: 2002-12-17 23:35

Message:
Logged In: YES 
user_id=10725

It's assumed that if you have the admin password, you're
allowed to view the archives.  Why is this a security hole?
 Seems perfectly appropriate to me.

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

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

From harco.deHilster at cert-ro.nl  Wed Dec 11 17:13:10 2002
From: harco.deHilster at cert-ro.nl (Harco de Hilster)
Date: Wed Dec 18 07:41:05 2002
Subject: [Mailman-Developers] confirmation of email commands
Message-ID: <3DF76416.6000708@cert-ro.nl>

Dear developers,

I'am currently setting up a mailman mailinglist with mailman 2.1b5. I'am 
using the beta because
we need the i18n support.

I noticed that every mail send to the mail interface gets confirmed. So 
a subscription by email results
in four messages:

result of subscribe
confirm
result of confirm
welcome message

The subscription to this list resulted only in two messages 
(confirm+welcome) which is normal for mailing list subscription.

This is way to much and confusing for the average user. I looked through 
the code, and it is not
easy to fix this. Output is send regardless of the result and the kind 
of message.
A first quick fix is to send command response output only if the command 
fails, but then the 'help' command doesn't work anymore.

Only errors should result in a response mail, and output of commands 
(subscribe, help, etc) should go in a separate message imho.

Any ideas?

Thanks,

Harco


From Mark.Martinec at ijs.si  Wed Dec 18 02:12:16 2002
From: Mark.Martinec at ijs.si (Mark Martinec)
Date: Wed Dec 18 07:41:54 2002
Subject: [Mailman-Developers] Search order for obtaining envelope sender
	address
Message-ID: <01KQ5SPGOLMA006PQL@CATHY.IJS.SI>

Hi,

I'm new to the developers list, but not new to Mailman,
being happy with it since pre-v1 version.

Just installed 2.1b6, and I have a Christmas wish that I kept unexpressed
ever since v2 came out and broke the old behaviour that I liked,
and is the only one that realiably works here - namely:

Setting the mm_cfg.USE_ENVELOPE_SENDER gives us only two options:
namely the search order Sender:, From:, unixfrom,
or From:, Sender:, unixfrom.

I have to patch Mesage.py/get_sender for every new version
that I install, to make unixfrom override the other two header fields.

Please consider either giving USE_ENVELOPE_SENDER a multivalued choice,
or to provide some other variable or mechanism to specify search order
for obtaining sender address.

I hope I didn't miss something that already makes this possible.

Best regards
  Mark

-- 
  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  !!  Mark Martinec (system manager)     tel  +386 1 4773-575 !!
  !!  J. Stefan Institute, Jamova 39     fax  +386 1 2519-385 !!
  !!  SI-1000 Ljubljana, Slovenia        mark.martinec@ijs.si !!
  !!!!!!!!!!!!!!!!!!!!!!!!!! http://www.ijs.si/people/mark/ !!!!

From schulte+mailman at nospam.schulte.org  Wed Dec 11 17:29:59 2002
From: schulte+mailman at nospam.schulte.org (Christopher Schulte)
Date: Wed Dec 18 07:42:45 2002
Subject: [Mailman-Developers] upgrade from 2.1b5 to 2.1b6 fails
Message-ID: <5.2.0.9.2.20021211165821.073c0c10@localhost>

Just yesterday I went from 2.0.13 to 2.1b5 with no trouble.

Today I went from 2.1b5 to 2.1b6 on the same install, and had
problems.

I shut down smtpd, did a mailmanctl stop, disabled web access
and stopped all mailman cron jobs before doing the update.

This is where the make update fails:

monster# make update
Upgrading from version 0x20100b5 to 0x20100b6
getting rid of old source files
Updating mailing list: pptp-server
Updating the held requests database.
Traceback (most recent call last):
   File "bin/update", line 570, in ?
     errors = main()
   File "bin/update", line 447, in main
     errors = errors + dolist(listname)
   File "bin/update", line 217, in dolist
     mlist._UpdateRecords()
   File "/usr/local/mailman/Mailman/ListAdmin.py", line 536, in _UpdateRecords
     for id, (type, info) in self.__db.items():
ValueError: unpack tuple of wrong size
*** Error code 1

Stop in /usr/local/src/mailman-2.1b6.

Problem with held requests?  Well when I log in to try to clear them via web:

Bug in Mailman version 2.1b6

We're sorry, we hit a bug!


Traceback:

Traceback (most recent call last):
   File "/usr/local/mailman/scripts/driver", line 87, in run_main
     main()
   File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 226, in main
     num = show_pending_subs(mlist, form)
   File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 264, in 
show_pending_subs
     pendingsubs = mlist.GetSubscriptionIds()
   File "/usr/local/mailman/Mailman/ListAdmin.py", line 157, in 
GetSubscriptionIds
     return self.__getmsgids(SUBSCRIPTION)
   File "/usr/local/mailman/Mailman/ListAdmin.py", line 149, in __getmsgids
     ids = [k for k, (type, data) in self.__db.items() if type == rtype]
ValueError: unpack tuple of wrong size

Is there another way to clear the pending messages so I can update the DB?
I tried going back down to 2.1b5, but the same problem existed when I tried
to view pending requests.

My other lists appear to work OK with with 2.1b[56]

Thanks.


From scott at blast.com  Sun Dec 15 19:51:03 2002
From: scott at blast.com (Scott R. Every)
Date: Wed Dec 18 07:43:04 2002
Subject: [Mailman-Developers] Re: [Mailman-Users] RELEASED Mailman 2.1 beta 6
In-Reply-To: <15862.38360.272912.231108@gargle.gargle.HOWL>
References: <15862.38360.272912.231108@gargle.gargle.HOWL>
Message-ID: <2147483647.1039981863@[66.45.99.179]>

does version 2.1 have any good way to export all the email addresses EXCEPT 
the ones with the nomail option set?  using list_members gives ALL the 
emails regardless of whether this field is set.  my data set is very 
large(>600k) so dumping the whole db is not an option(it took over 8 
hours).  what i need is to be able to quickly dump just the current emails 
from a list.

any advice would be welcome.

thanks

s

--On Tuesday, December 10, 2002 8:33 PM -0500 "Barry A. Warsaw" 
<barry@python.org> wrote:

>
> I've released Mailman 2.1 beta 6.  This is the last planned beta
> release before MM2.1 final, which I still expect to release before the
> end of the year.  See below for a list of changes since 2.1b5.  There
> have been lots of bug fxes and lots of translations updates.
>
> The new tarball has been uploaded to SourceForge, and the various web
> sites will be updated shortly.
>
> Enjoy,
> -Barry
>
> -------------------- snip snip --------------------
> 2.1 beta 6 (09-Dec-2002)
>
>     Lots and lots of bug fixes, and translation updates.  Also,
>
>     - ARCHIVER_OBSCURES_EMAILADDRS is now set to true by default.
>
>     - QRUNNER_SAVE_BAD_MESSAGES is now set to true by default.
>
>     - Bounce messages which were recognized, but in which no member
>       addresses were found are no longer forwarded to the list
>       administrator.
>
>     - bin/arch grew a --wipe option which first removes the entire old
>       archive before regenerating the new one.
>
>     - bin/mailmanctl -u now prints a warning that permission problems
>       could appear, such as when trying to delete a list through the
>       web that has some archives in it.
>
>     - bin/remove_members grew --nouserack/-n and -noadminack/-N options.
>
>     - A new script bin/list_owners has been added for printing out
>       list owners and moderators.
>
>     - Dates in the web version of archived messages are now relative
>       to the local timezone, and include the timezone names, when
>       available.
>
> ------------------------------------------------------
> Mailman-Users mailing list
> Mailman-Users@python.org
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives:
> http://www.mail-archive.com/mailman-users%40python.org/
>
> This message was sent to: scott@emji.net
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/scott%40emji.net



From noreply at sourceforge.net  Wed Dec 18 05:28:07 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 18 08:27:56 2002
Subject: [Mailman-Developers] [ mailman-Bugs-655079 ] Major security hole.....
Message-ID: <E18OeF5-0003yW-00@sc8-sf-web3.sourceforge.net>

Bugs item #655079, was opened at 2002-12-17 03:13
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655079&group_id=103

Category: security/privacy
Group: 2.0.x
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Nicolas Weeger (ryo_saeba)
Assigned to: Nobody/Anonymous (nobody)
Summary: Major security hole.....

Initial Comment:
Just found a nice security bug:
on the main list page, you have 2 fields to enter admin 
mail & password to view list subscriptions.
Well, you can just enter a valid admin password, and it'll 
work !!! Even if the mail address is blank / invalid !!

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-18 08:28

Message:
Logged In: YES 
user_id=12800

The admin may not be a member of the list.  The specific
rule is that if the admin password is used, the email
address is ignored.  Yes, this means security is dependent
on the secrecy of your admin password, but if that leaks out
you're going to have bigger problems than someone viewing
your private archives.

----------------------------------------------------------------------

Comment By: Nicolas Weeger (ryo_saeba)
Date: 2002-12-18 02:39

Message:
Logged In: YES 
user_id=303511

Well, granted, but only if the mail is left blank !
I mean, if you put an email address, aren't you supposed to 
enter YOUR password, not an admin's ?
Currently, put an admin password & ANY MAIL and it works...

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-17 17:52

Message:
Logged In: YES 
user_id=12800

Dan's right, the admin can always read the archives and by
design doesn't need to enter an email address.

----------------------------------------------------------------------

Comment By: Dan Mick (dmick)
Date: 2002-12-17 17:35

Message:
Logged In: YES 
user_id=10725

It's assumed that if you have the admin password, you're
allowed to view the archives.  Why is this a security hole?
 Seems perfectly appropriate to me.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655079&group_id=103

From noreply at sourceforge.net  Wed Dec 18 07:55:23 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 18 10:55:10 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-655827 ] names w/ .'s + accents held for approval
Message-ID: <E18OgXb-0000ky-00@sc8-sf-web4.sourceforge.net>

Bugs item #655827, was opened at 2002-12-18 10:55
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655827&group_id=103

Category: mail delivery
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Rob Ellis (robellis)
Assigned to: Nobody/Anonymous (nobody)
Summary: names w/ .'s + accents held for approval

Initial Comment:
people who use microsoft outlook (at least) and
have accented characters and .'s in their names
(e.g.  "F. André") have their names encoded
in the From: line as per RFC 2049, like

 =?Windows-1252?Q?F._Andr=E9?= <fandre@example.ca>

the unescaped dots break Mailman's RFC822 parsing,
so the user's messages are held for approval when
member_posting_only=1, even if they're subscribed.

one fix is to escape the unescaped dots -- patch
for rfc822.py attached...

- rob

--
Rob Ellis <rob@web.ca>
System administrator, Web Networks

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655827&group_id=103

From dan.mick at sun.com  Wed Dec 18 14:40:48 2002
From: dan.mick at sun.com (Dan Mick)
Date: Wed Dec 18 17:41:17 2002
Subject: [Mailman-Developers] Re: [Mailman-Users] RELEASED Mailman 2.1
 beta 6
In-Reply-To: <15862.38360.272912.231108@gargle.gargle.HOWL>
References: <15862.38360.272912.231108@gargle.gargle.HOWL>
	<2147483647.1039981863@[66.45.99.179]>
Message-ID: <3E00F970.9050107@sun.com>

Scott R. Every wrote:

> does version 2.1 have any good way to export all the email addresses
> EXCEPT the ones with the nomail option set?  using list_members gives
> ALL the emails regardless of whether this field is set.

 From the usage message:

--nomail[=why] / -n [why]
     Print the members that have delivery disabled.  Optional argument can
     be "byadmin", "byuser", "bybounce", or "unknown" which prints just the
     users who have delivery disabled for that reason.  It can also be
     "enabled" which prints just those member for whom delivery is
     enabled.


From noreply at sourceforge.net  Wed Dec 18 15:58:59 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 18 18:58:43 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-656042 ] Digest message count incorrect in 2.0.6 
Message-ID: <E18Oo5b-0003OI-00@sc8-sf-web4.sourceforge.net>

Bugs item #656042, was opened at 2002-12-18 23:58
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656042&group_id=103

Category: mail delivery
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Bryce Harrington (bryce)
Assigned to: Nobody/Anonymous (nobody)
Summary: Digest message count incorrect in 2.0.6 

Initial Comment:
In digests, the # of messages reported does not match  
the actual number of messages contained in the digest.  
  
Take, for example, this digest :  
Cgl_proof_subgroup digest, Vol 1 #130 - 14 msgs  
which has :  
Today's Topics:  
  
   1. RE: Re: CGL-WG PoC-sg : Feature Sets   &  Ho  
       t Device Identity  ([Cgl_proof_subgroup] Proposed  
FS list) (Randy.Dunlap)  
   2. RE: Re: CGL-WG PoC-sg : Feature Sets   &  Ho  
       t Device Identity  ([Cgl_proof_subgroup] Proposed  
FS list) (Perez-Gonzalez,  
Inaky)  
   3. RE: Re: CGL-WG PoC-sg : Feature Sets   &  Ho  
       t Device Identity  ([Cgl_proof_subgroup] Proposed  
FS list) (Mika Kukkonen)  
   4. Re: 2.4 v. 2.5 (was RE: [Cgl_proof_subgroup] Re:  
CGL-WG PoC-sg :  
       Feature Sets   &  Ho t Device Identity   
([Cgl_proof_subgroup] Proposed FS  
       list)) (Mika Kukkonen)  
   5. Re: 2.4 v. 2.5 (was RE: [Cgl_proof_subgroup] Re:  
CGL-WG PoC-sg :  
       Feature Sets   &  Ho t Device Identity   
([Cgl_proof_subgroup] Proposed FS  
       list)) (Randy.Dunlap)  
   6. RE: Re: CGL-WG PoC-sg : Feature Sets   &  Ho  
       t Device Identity  ([Cgl_proof_subgroup] Proposed  
FS list) (Randy.Dunlap)  
  
6 messages, not the 14 claimed by the subject.  
In general, all the lists seem to double-count some  
messages. If the digest only  
contains one or two messages, the subject seems to be  
correct, but it is less and  
less accurate as the message count increases.  
  
Perhaps it is counting messages with wrapped subject  
lines as 2+ messages?  
  
This has also been reported elsewhere:  
  
http://mail.python.org/pipermail/mailman-users/2001-February/009697.html 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656042&group_id=103

From noreply at sourceforge.net  Wed Dec 18 19:07:38 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 18 22:07:20 2002
Subject: [Mailman-Developers] [ mailman-Patches-656097 ] fix for bug id 655144
Message-ID: <E18Or2A-00077x-00@sc8-sf-web3.sourceforge.net>

Patches item #656097, was opened at 2002-12-19 03:07
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=656097&group_id=103

Category: command line scripts
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: fix for bug id 655144

Initial Comment:
Here is a quick hack for fixing bug id 655144 -- fail
to set list preferred language through command line.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=656097&group_id=103

From noreply at sourceforge.net  Wed Dec 18 19:09:50 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 18 22:09:35 2002
Subject: [Mailman-Developers] [ mailman-Patches-656097 ] fix for bug id 655144
Message-ID: <E18Or4I-0007Bv-00@sc8-sf-web3.sourceforge.net>

Patches item #656097, was opened at 2002-12-19 03:07
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=656097&group_id=103

Category: command line scripts
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: fix for bug id 655144

Initial Comment:
Here is a quick hack for fixing bug id 655144 -- fail
to set list preferred language through command line.


----------------------------------------------------------------------

>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-19 03:09

Message:
Logged In: YES 
user_id=67709

forget to check attach?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=656097&group_id=103

From noreply at sourceforge.net  Wed Dec 18 19:13:55 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Wed Dec 18 22:13:38 2002
Subject: [Mailman-Developers] [ mailman-Patches-655214 ] Fix archiving
Message-ID: <E18Or8F-0007HV-00@sc8-sf-web3.sourceforge.net>

Patches item #655214, was opened at 2002-12-17 14:49
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=655214&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix archiving

Initial Comment:
This patch restores MIME charset capabilities for
article archiving in CVS mailman.

It:
- removes the .charset attribute from articles; all
articles are encoded in the list's charset,

- decodes subject and author to Unicode; if this fails,
no decoding (not even MIME) is done to subject and author,

- MIME-decodes the body in the constructor using
get_payload, removes the hand-crafted qp decoding from
_get_body,

- Unicode-decodes the body in the constructor if the
body's charset differs from the list's charset,

- fixes processbody_URLquote to always return byte
strings (by escaping the URL also); comparing the old
and the new string is no longer possible since the old
string is Unicode and the new string is a list-encoded
byte string.

- changes text archiving to have the archives in the
list's encoding, with unsupported characters 'replace'd

- Fixes a bug in the scrubber, where a
content-transfer-encoding might have survived
flattening of the message.

With these changes, I can process the playground
archives correctly, to get mojibake-free pages.

----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-19 03:13

Message:
Logged In: YES 
user_id=67709

Hi, Martin,
Haven't you forget to attach file? I am interested in
reviewing your patch.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=655214&group_id=103

From noreply at sourceforge.net  Wed Dec 18 22:55:21 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu Dec 19 01:55:05 2002
Subject: [Mailman-Developers] [ mailman-Patches-655214 ] Fix archiving
Message-ID: <E18OuaX-0001GW-00@sc8-sf-web2.sourceforge.net>

Patches item #655214, was opened at 2002-12-17 15:49
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=655214&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix archiving

Initial Comment:
This patch restores MIME charset capabilities for
article archiving in CVS mailman.

It:
- removes the .charset attribute from articles; all
articles are encoded in the list's charset,

- decodes subject and author to Unicode; if this fails,
no decoding (not even MIME) is done to subject and author,

- MIME-decodes the body in the constructor using
get_payload, removes the hand-crafted qp decoding from
_get_body,

- Unicode-decodes the body in the constructor if the
body's charset differs from the list's charset,

- fixes processbody_URLquote to always return byte
strings (by escaping the URL also); comparing the old
and the new string is no longer possible since the old
string is Unicode and the new string is a list-encoded
byte string.

- changes text archiving to have the archives in the
list's encoding, with unsupported characters 'replace'd

- Fixes a bug in the scrubber, where a
content-transfer-encoding might have survived
flattening of the message.

With these changes, I can process the playground
archives correctly, to get mojibake-free pages.

----------------------------------------------------------------------

>Comment By: Martin v. Löwis (loewis)
Date: 2002-12-19 07:55

Message:
Logged In: YES 
user_id=21627

Oops, attached.

----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-19 04:13

Message:
Logged In: YES 
user_id=67709

Hi, Martin,
Haven't you forget to attach file? I am interested in
reviewing your patch.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=655214&group_id=103

From noreply at sourceforge.net  Thu Dec 19 07:45:59 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu Dec 19 10:45:38 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-656341 ] logging of pending request without email
Message-ID: <E18P2s3-0001pw-00@sc8-sf-web2.sourceforge.net>

Bugs item #656341, was opened at 2002-12-19 15:45
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656341&group_id=103

Category: (un)subscribing
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: logging of pending request without email

Initial Comment:
2.1b6:

Pending requests are still not logged with email
addresses for me.

Patch upcoming.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656341&group_id=103

From noreply at sourceforge.net  Thu Dec 19 07:49:58 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu Dec 19 10:49:37 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-656346 ] correct logging of pending requests
Message-ID: <E18P2vu-0005an-00@sc8-sf-web3.sourceforge.net>

Patches item #656346, was opened at 2002-12-19 15:49
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=656346&group_id=103

Category: list administration
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: correct logging of pending requests

Initial Comment:
I have no idea what the previous code
was supposed to do.
The new version logs what I think it should log (for me).

--- Mailman/MailList.py.ORIG    Wed Nov 27 12:01:18 2002
+++ Mailman/MailList.py Wed Nov 27 12:01:44 2002
@@ -826,7 +826,7 @@
             if recipient <> email:
                 who = "%s (%s)" % (email,
recipient.split('@')[0])
             else:
-                who = name
+                who = "%s (%s)" % (email, name)
             syslog('subscribe', '%s: pending %s %s',
                    self.internal_name(), who, by)
             raise Errors.MMSubscribeNeedsConfirmation


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=656346&group_id=103

From noreply at sourceforge.net  Thu Dec 19 16:45:30 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu Dec 19 19:45:06 2002
Subject: [Mailman-Developers] [ mailman-Patches-655214 ] Fix archiving
Message-ID: <E18PBIA-0001Fh-00@sc8-sf-web1.sourceforge.net>

Patches item #655214, was opened at 2002-12-17 14:49
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=655214&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix archiving

Initial Comment:
This patch restores MIME charset capabilities for
article archiving in CVS mailman.

It:
- removes the .charset attribute from articles; all
articles are encoded in the list's charset,

- decodes subject and author to Unicode; if this fails,
no decoding (not even MIME) is done to subject and author,

- MIME-decodes the body in the constructor using
get_payload, removes the hand-crafted qp decoding from
_get_body,

- Unicode-decodes the body in the constructor if the
body's charset differs from the list's charset,

- fixes processbody_URLquote to always return byte
strings (by escaping the URL also); comparing the old
and the new string is no longer possible since the old
string is Unicode and the new string is a list-encoded
byte string.

- changes text archiving to have the archives in the
list's encoding, with unsupported characters 'replace'd

- Fixes a bug in the scrubber, where a
content-transfer-encoding might have survived
flattening of the message.

With these changes, I can process the playground
archives correctly, to get mojibake-free pages.

----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-20 00:45

Message:
Logged In: YES 
user_id=67709

Thanks.
 It looks like working for me (Japanese), except there was a
typo:

       if isinstance(body, unicode):
should be
       if isinstance(body, types.UnicodeType):



----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2002-12-19 06:55

Message:
Logged In: YES 
user_id=21627

Oops, attached.

----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-19 03:13

Message:
Logged In: YES 
user_id=67709

Hi, Martin,
Haven't you forget to attach file? I am interested in
reviewing your patch.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=655214&group_id=103

From noreply at sourceforge.net  Thu Dec 19 20:31:44 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu Dec 19 23:31:16 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-601117 ] add sequencial number in subject prefix
Message-ID: <E18PEp6-0006E9-00@sc8-sf-web3.sourceforge.net>

Patches item #601117, was opened at 2002-08-28 05:07
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103

Category: mail delivery
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 3
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: add sequencial number in subject prefix

Initial Comment:
This patch for 'CookHeaders.py' add an ability to add a
sequencial number in the subject prefix. You can define
a subject prefix like:
   [listname %d]
Then, the subject line of delivered mail becomes:
   Subject: [listname 123] Hoge hoge
When someone replied this mail, mailman receives a
messages with:
   Subject: Re: [listname 123] Hoge hoge
Then, this patch removes [listname \d+] part and
deliver it with:
   Subject: [listname 124] Re: Hoge hoge
And next, another person replies with
   Subject: Re: [listname 124] Re: Hoge hoge
Then, (magically!) you get:
   Subject: [listname 125] Re: Hoge hoge
Not with Re: Re: Hoge hoge.

Looks like complicated but this patch has been working
well with Japanese-enhanced Mailman for more than a year.

Without %d, this patch works like current version, I
believe.



----------------------------------------------------------------------

>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-20 04:31

Message:
Logged In: YES 
user_id=67709

update for 2.1b6+


----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-10-31 05:59

Message:
Logged In: YES 
user_id=67709

I have uploaded the patch with the same name as the old one.
Please download the upper one because it's newer.
Sorry for the inconvenience.


----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-10-31 05:53

Message:
Logged In: YES 
user_id=67709

Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103

From narnett at mccmedia.com  Sat Dec 21 09:48:16 2002
From: narnett at mccmedia.com (Nick Arnett)
Date: Sat Dec 21 12:49:47 2002
Subject: [Mailman-Developers] White space disappearing in subject header?
Message-ID: <PHEDLIMPMIAGAEPEFBGCIEHEEIAA.narnett@mccmedia.com>

Does this sound familiar to anyone -- I couldn't find it in the known bugs.
I haven't figured out how to reproduce this exactly, but some of my users
noticed that sometimes Mailman is dropping the spaces between words toward
the end of long subject lines.  They report that they've put the spaces back
in, but the message comes ot of the list server with them gone again.

If it's not a known bug, I'll look into it some more and submit a bug
report.

Nick

--
Nick Arnett
Phone/fax: (408) 904-7198
narnett@mccmedia.com



From marilyn at deliberate.com  Sat Dec 21 12:11:54 2002
From: marilyn at deliberate.com (Marilyn Davis)
Date: Sat Dec 21 15:12:00 2002
Subject: [Mailman-Developers] Patching 2.0.13 for eVote
Message-ID: <Pine.LNX.4.10.10212211201100.7379-100000@rosa.deliberate.com>

Hi Mailman Developers,

I'm trying to create a patch to 2.0.13 that makes eVote work.

I'm afraid that I'm not experienced at making patches so I'm reading
documentation and trying to figure out what to do.  

Clearly I should collect the 2.0.13 sources via CVS so I tried
following the instructions at http://sourceforge.net/cvs/?group_id=103
but I can't make it work:

> $ cvs -d:pserver:anonymous@CVS.mailman.sourceforge.net:/CVSroot/mailman login
> (Logging in to anonymous@CVS.mailman.sourceforge.net)
> CVS password: 

> cvs login: authorization failed: server CVS.mailman.sourceforge.net rejected access

Please tell me what I'm doing wrong.

Also, if there is any documentation about this process that I should be
studying, please point me there.

Thank you for your help.

Marilyn Davis




From spacey-mailman at lenin.nu  Sat Dec 21 12:46:43 2002
From: spacey-mailman at lenin.nu (Peter C. Norton)
Date: Sat Dec 21 15:46:47 2002
Subject: [Mailman-Developers] Patching 2.0.13 for eVote
In-Reply-To: <Pine.LNX.4.10.10212211201100.7379-100000@rosa.deliberate.com>
References: <Pine.LNX.4.10.10212211201100.7379-100000@rosa.deliberate.com>
Message-ID: <20021221204643.GC17311@lenin.nu>

2.0.13 is released.  Just download the tarball.  You can easily make
diffs by doing the following:

tar -xzf mailman-2.0.13.tar gz
mv mailman-2.0.13-dist
tar -xzf mailman-2.0.13.tar gz # Yes, again

Then make your edits in the mailman-2.0.13 directory.  When you've got
everything working, then do a:

diff -u mailman-2.0.13-dist mailman-2.0.13 > mailman-evote.diff

This'll recurse through both directories create a patch file.

-Peter

On Sat, Dec 21, 2002 at 12:11:54PM -0800, Marilyn Davis wrote:
> Hi Mailman Developers,
> 
> I'm trying to create a patch to 2.0.13 that makes eVote work.
> 
> I'm afraid that I'm not experienced at making patches so I'm reading
> documentation and trying to figure out what to do.  
> 
> Clearly I should collect the 2.0.13 sources via CVS so I tried
> following the instructions at http://sourceforge.net/cvs/?group_id=103
> but I can't make it work:
> 
> > $ cvs -d:pserver:anonymous@CVS.mailman.sourceforge.net:/CVSroot/mailman login
> > (Logging in to anonymous@CVS.mailman.sourceforge.net)
> > CVS password: 
> 
> > cvs login: authorization failed: server CVS.mailman.sourceforge.net rejected access
> 
> Please tell me what I'm doing wrong.
> 
> Also, if there is any documentation about this process that I should be
> studying, please point me there.
> 
> Thank you for your help.
> 
> Marilyn Davis
> 
> 
> 
> 
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers@python.org
> http://mail.python.org/mailman/listinfo/mailman-developers

-- 
The 5 year plan:
In five years we'll make up another plan.
Or just re-use this one.

From barry at python.org  Sat Dec 21 18:29:30 2002
From: barry at python.org (Barry A. Warsaw)
Date: Sat Dec 21 18:29:59 2002
Subject: [Mailman-Developers] Patching 2.0.13 for eVote
References: <Pine.LNX.4.10.10212211201100.7379-100000@rosa.deliberate.com>
Message-ID: <15876.63834.754936.695628@gargle.gargle.HOWL>


>>>>> "MD" == Marilyn Davis <marilyn@deliberate.com> writes:

    MD> I'm trying to create a patch to 2.0.13 that makes eVote work.

    MD> I'm afraid that I'm not experienced at making patches so I'm
    MD> reading documentation and trying to figure out what to do.

    MD> Clearly I should collect the 2.0.13 sources via CVS so I tried
    MD> following the instructions at
    MD> http://sourceforge.net/cvs/?group_id=103 but I can't make it
    MD> work:

    >> $ cvs
    >> -d:pserver:anonymous@CVS.mailman.sourceforge.net:/CVSroot/mailman
    >> login (Logging in to anonymous@CVS.mailman.sourceforge.net) CVS
    >> password:

I think there's some problems with case there.  Try the following:

% cvs -d :pserver:anonymous@cvs.mailman.sf.net:/cvsroot/mailman login
Logging in to :pserver:anonymous@cvs.mailman.sf.net:2401/cvsroot/mailman
CVS password: 
% cvs -d :pserver:anonymous@cvs.mailman.sf.net:/cvsroot/mailman co mailman

Now, remember that that will get you the head of the cvs tree, but
Mailman 2.0.x lives on a maintenance branch.  So after you've checked
the code out, cd into the mailman subdir and do:

% cvs -q up -P -d -rRelease_2_0_1-branch

You'll now have the head of the 2.0.x maint branch (yes the branch tag
is slightly misnamed).  If you want exactly 2.0.13 -- I can't remember
how much has diverged, but probably not much -- then use
-rRelease_2_0_13 instead.

To actually generate a patch, my recommendation is to use something
like the following from the top level (i.e. mailman) directory:

% cvs diff -u > /tmp/evote-patch.txt

Cheers,
-Barry

From barry at python.org  Sat Dec 21 18:32:12 2002
From: barry at python.org (Barry A. Warsaw)
Date: Sat Dec 21 18:32:41 2002
Subject: [Mailman-Developers] White space disappearing in subject header?
References: <PHEDLIMPMIAGAEPEFBGCIEHEEIAA.narnett@mccmedia.com>
Message-ID: <15876.63996.458680.402043@gargle.gargle.HOWL>


>>>>> "NA" == Nick Arnett <narnett@mccmedia.com> writes:

    NA> Does this sound familiar to anyone -- I couldn't find it in
    NA> the known bugs.  I haven't figured out how to reproduce this
    NA> exactly, but some of my users noticed that sometimes Mailman
    NA> is dropping the spaces between words toward the end of long
    NA> subject lines.  They report that they've put the spaces back
    NA> in, but the message comes ot of the list server with them gone
    NA> again.

    NA> If it's not a known bug, I'll look into it some more and
    NA> submit a bug report.

Yes, please do, thanks.
-Barry

From noreply at sourceforge.net  Sun Dec 22 00:08:19 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Sun Dec 22 03:08:29 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-657443 ] Header and footer in multipart
Message-ID: <E18Q19n-0006Eb-00@sc8-sf-web2.sourceforge.net>

Bugs item #657443, was opened at 2002-12-22 11:08
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=657443&group_id=103

Category: mail delivery
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Demeilliez Bruno (dive_bruno)
Assigned to: Nobody/Anonymous (nobody)
Summary: Header and footer in multipart

Initial Comment:
Hi,

I have install mailman 2.1b6 on redhat 7.1.
My mailling list is in french and when I received mail
from the list with theBat, the header and the footer is
in multipart (like at the end).
I would like the bady and the footer was in the same
message.
Can you tell me if it's a bug or a configuration problem ?
And how I can resolve it ?

Thank's for your help.

Bruno

Example :
....
From: Bruno Demeilliez <webmaster@aquanaute.com>
X-Mailer: The Bat! (v1.62 Christmas Edition)
Organization: Aquanaute.com
X-Priority: 3 (Normal)
Message-ID: <11916819925.20021222110418@aquanaute.com>
To: test2@aquanaute.com
MIME-Version: 1.0
Subject: Test
X-BeenThere: test2@aquanaute.com
X-Mailman-Version: 2.1b6
Precedence: list
Reply-To: Bruno Demeilliez <webmaster@aquanaute.com>,
        test2@aquanaute.com
List-Id: <test2.aquanaute.com>
List-Help:
<mailto:test2-request@aquanaute.com?subject=help>
List-Post: <mailto:test2@aquanaute.com>
List-Subscribe:
<http://www.aquanaute.com/mailman/listinfo/test2>,
       
<mailto:test2-request@aquanaute.com?subject=subscribe>
List-Archive: <http://www.aquanaute.com/pipermail/test2>
List-Unsubscribe:
<http://www.aquanaute.com/mailman/listinfo/test2>,
       
<mailto:test2-request@aquanaute.com?subject=unsubscribe>
Content-Type: multipart/mixed;
boundary="===============2617006012765839=="
Sender: test2-bounces@aquanaute.com
Errors-To: test2-bounces@aquanaute.com

--===============2617006012765839==
Content-Transfer-Encoding: 8bit
content-type: text/plain

Bonjour test2,

  

Amicalement,

Bruno
---
Pour l'équipe d'Aquanaute.com
http://www.aquanaute.com
SARL de presse Aquanaute.com
8 rue Duployé
38100 Grenoble
France
Tél et Fax : 04 76 99 93 77


--===============2617006012765839==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

_______________________________________________
Liste de discussion Test2
Liste hébergée et administrée gratuitement par
Aquanaute.com
Présentation de la liste, Abonnement / Désabonnement : 
http://www.aquanaute.com/mailman/listinfo/test2
Archives de la liste :
http://aquanaute.com/listes/Test2/

--===============2617006012765839==--

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=657443&group_id=103

From tkikuchi at is.kochi-u.ac.jp  Mon Dec 23 10:28:16 2002
From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi)
Date: Sun Dec 22 20:28:51 2002
Subject: [Mailman-Developers] White space disappearing in subject header?
References: <PHEDLIMPMIAGAEPEFBGCIEHEEIAA.narnett@mccmedia.com>
	<15876.63996.458680.402043@gargle.gargle.HOWL>
Message-ID: <3E0666B0.10405@is.kochi-u.ac.jp>

Barry A. Warsaw wrote:
>>>>>>"NA" == Nick Arnett <narnett@mccmedia.com> writes:

>     NA> If it's not a known bug, I'll look into it some more and
>     NA> submit a bug report.
> 
> Yes, please do, thanks.

Barry,

The problem has been reported in mimelib patch site,
https://sourceforge.net/tracker/index.php?func=detail&aid=585600&group_id=25568&atid=384680

And, I have just submitted a different patch.
https://sourceforge.net/tracker/index.php?func=detail&aid=657690&group_id=25568&atid=384680

-- 
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/


From noreply at sourceforge.net  Mon Dec 23 11:17:37 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 14:17:41 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-657951 ] Generate RSS summary in archives
Message-ID: <E18QY53-0008Q9-00@sc8-sf-web4.sourceforge.net>

Patches item #657951, was opened at 2002-12-23 14:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103

Category: Pipermail
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: A.M. Kuchling (akuchling)
Assigned to: Nobody/Anonymous (nobody)
Summary: Generate RSS summary in archives

Initial Comment:
Here's a first-draft patch.  Things that need fixing:

* The generated RSS feed needs to be validated.  (It passed the 
W3C's RDF validator, but RSS validators still need to be checked.)

* The date should be given in YYYY-MM-DD format, which requires
parsing the .fromdate attribute.

* How do I get the URL for an archived message?  The generated RSS
currently just uses the filename, which is wrong.  How do I get
at the PUBLIC_ARCHIVE_URL setting?

* Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them.
We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like.  (Would be nice to get this into 2.1final...)

* The list index page should have a LINK element pointing to
the RSS file.

Please make any comments you have, and I'll rework the patch accordingly.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103

From noreply at sourceforge.net  Mon Dec 23 11:21:40 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 14:21:47 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-657951 ] Generate RSS summary in archives
Message-ID: <E18QY8y-0003Sl-00@sc8-sf-web1.sourceforge.net>

Patches item #657951, was opened at 2002-12-23 14:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103

Category: Pipermail
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: A.M. Kuchling (akuchling)
Assigned to: Nobody/Anonymous (nobody)
Summary: Generate RSS summary in archives

Initial Comment:
Here's a first-draft patch.  Things that need fixing:

* The generated RSS feed needs to be validated.  (It passed the 
W3C's RDF validator, but RSS validators still need to be checked.)

* The date should be given in YYYY-MM-DD format, which requires
parsing the .fromdate attribute.

* How do I get the URL for an archived message?  The generated RSS
currently just uses the filename, which is wrong.  How do I get
at the PUBLIC_ARCHIVE_URL setting?

* Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them.
We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like.  (Would be nice to get this into 2.1final...)

* The list index page should have a LINK element pointing to
the RSS file.

Please make any comments you have, and I'll rework the patch accordingly.



----------------------------------------------------------------------

>Comment By: A.M. Kuchling (akuchling)
Date: 2002-12-23 14:21

Message:
Logged In: YES 
user_id=11375

Argh; SF choked on the file upload.  Attaching the patch again...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103

From noreply at sourceforge.net  Mon Dec 23 11:22:48 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 14:22:53 2002
Subject: [Mailman-Developers] 
 [ mailman-Feature Requests-534234 ] Automatic RSS feed generation
Message-ID: <E18QYA4-0006Rj-00@sc8-sf-web3.sourceforge.net>

Feature Requests item #534234, was opened at 2002-03-24 00:12
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: A.M. Kuchling (akuchling)
Date: 2002-12-23 14:22

Message:
Logged In: YES 
user_id=11375

Patch #657951 adds an RSS summary to mailing lists.






----------------------------------------------------------------------

Comment By: captain larry (captainlarry)
Date: 2002-08-07 13: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 01: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  Mon Dec 23 11:27:05 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 14:27:10 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-657951 ] Generate RSS summary in archives
Message-ID: <E18QYED-0006cD-00@sc8-sf-web3.sourceforge.net>

Patches item #657951, was opened at 2002-12-23 14:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103

Category: Pipermail
>Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: A.M. Kuchling (akuchling)
Assigned to: Nobody/Anonymous (nobody)
Summary: Generate RSS summary in archives

Initial Comment:
Here's a first-draft patch.  Things that need fixing:

* The generated RSS feed needs to be validated.  (It passed the 
W3C's RDF validator, but RSS validators still need to be checked.)

* The date should be given in YYYY-MM-DD format, which requires
parsing the .fromdate attribute.

* How do I get the URL for an archived message?  The generated RSS
currently just uses the filename, which is wrong.  How do I get
at the PUBLIC_ARCHIVE_URL setting?

* Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them.
We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like.  (Would be nice to get this into 2.1final...)

* The list index page should have a LINK element pointing to
the RSS file.

Please make any comments you have, and I'll rework the patch accordingly.



----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 14:27

Message:
Logged In: YES 
user_id=12800

Deferring until post-2.1

----------------------------------------------------------------------

Comment By: A.M. Kuchling (akuchling)
Date: 2002-12-23 14:21

Message:
Logged In: YES 
user_id=11375

Argh; SF choked on the file upload.  Attaching the patch again...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103

From noreply at sourceforge.net  Mon Dec 23 11:36:56 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 14:37:02 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-657951 ] Generate RSS summary in archives
Message-ID: <E18QYNk-0003h8-00@sc8-sf-web1.sourceforge.net>

Patches item #657951, was opened at 2002-12-23 19:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103

Category: Pipermail
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: A.M. Kuchling (akuchling)
Assigned to: Nobody/Anonymous (nobody)
Summary: Generate RSS summary in archives

Initial Comment:
Here's a first-draft patch.  Things that need fixing:

* The generated RSS feed needs to be validated.  (It passed the 
W3C's RDF validator, but RSS validators still need to be checked.)

* The date should be given in YYYY-MM-DD format, which requires
parsing the .fromdate attribute.

* How do I get the URL for an archived message?  The generated RSS
currently just uses the filename, which is wrong.  How do I get
at the PUBLIC_ARCHIVE_URL setting?

* Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them.
We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like.  (Would be nice to get this into 2.1final...)

* The list index page should have a LINK element pointing to
the RSS file.

Please make any comments you have, and I'll rework the patch accordingly.



----------------------------------------------------------------------

Comment By: captain larry (captainlarry)
Date: 2002-12-23 19:36

Message:
Logged In: YES 
user_id=147905

Just voting for support here.  This is *great* thanks for
the patch and I hope the maintainers include it as soon as
it's appropriate :)

Adam.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 19:27

Message:
Logged In: YES 
user_id=12800

Deferring until post-2.1

----------------------------------------------------------------------

Comment By: A.M. Kuchling (akuchling)
Date: 2002-12-23 19:21

Message:
Logged In: YES 
user_id=11375

Argh; SF choked on the file upload.  Attaching the patch again...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103

From noreply at sourceforge.net  Mon Dec 23 11:37:55 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 14:38:01 2002
Subject: [Mailman-Developers] [ mailman-Patches-645297 ] Add PGP support
Message-ID: <E18QYOh-0003jW-00@sc8-sf-web1.sourceforge.net>

Patches item #645297, was opened at 2002-11-28 14:54
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: Nobody/Anonymous (nobody)
Summary: Add PGP support

Initial Comment:
Support PGP encrypted lists using GnuPG.

----------------------------------------------------------------------

Comment By: captain larry (captainlarry)
Date: 2002-12-23 19: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-12 03: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  Mon Dec 23 12:42:25 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 15:42:31 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-657951 ] Generate RSS summary in archives
Message-ID: <E18QZP7-00051i-00@sc8-sf-web2.sourceforge.net>

Patches item #657951, was opened at 2002-12-23 14:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103

Category: Pipermail
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: A.M. Kuchling (akuchling)
Assigned to: Nobody/Anonymous (nobody)
Summary: Generate RSS summary in archives

Initial Comment:
Here's a first-draft patch.  Things that need fixing:

* The generated RSS feed needs to be validated.  (It passed the 
W3C's RDF validator, but RSS validators still need to be checked.)

* The date should be given in YYYY-MM-DD format, which requires
parsing the .fromdate attribute.

* How do I get the URL for an archived message?  The generated RSS
currently just uses the filename, which is wrong.  How do I get
at the PUBLIC_ARCHIVE_URL setting?

* Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them.
We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like.  (Would be nice to get this into 2.1final...)

* The list index page should have a LINK element pointing to
the RSS file.

Please make any comments you have, and I'll rework the patch accordingly.



----------------------------------------------------------------------

>Comment By: A.M. Kuchling (akuchling)
Date: 2002-12-23 15:42

Message:
Logged In: YES 
user_id=11375

Updated patch:

* Dates are now rendered as ISO-8601 (date only, not the time of the message)

* By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator.


----------------------------------------------------------------------

Comment By: captain larry (captainlarry)
Date: 2002-12-23 14:36

Message:
Logged In: YES 
user_id=147905

Just voting for support here.  This is *great* thanks for
the patch and I hope the maintainers include it as soon as
it's appropriate :)

Adam.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 14:27

Message:
Logged In: YES 
user_id=12800

Deferring until post-2.1

----------------------------------------------------------------------

Comment By: A.M. Kuchling (akuchling)
Date: 2002-12-23 14:21

Message:
Logged In: YES 
user_id=11375

Argh; SF choked on the file upload.  Attaching the patch again...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103

From noreply at sourceforge.net  Mon Dec 23 18:54:38 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 21:54:44 2002
Subject: [Mailman-Developers] [ mailman-Patches-655214 ] Fix archiving
Message-ID: <E18QfDK-0007z3-00@sc8-sf-web1.sourceforge.net>

Patches item #655214, was opened at 2002-12-17 09:49
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=655214&group_id=103

Category: Pipermail
Group: Mailman 2.1
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix archiving

Initial Comment:
This patch restores MIME charset capabilities for
article archiving in CVS mailman.

It:
- removes the .charset attribute from articles; all
articles are encoded in the list's charset,

- decodes subject and author to Unicode; if this fails,
no decoding (not even MIME) is done to subject and author,

- MIME-decodes the body in the constructor using
get_payload, removes the hand-crafted qp decoding from
_get_body,

- Unicode-decodes the body in the constructor if the
body's charset differs from the list's charset,

- fixes processbody_URLquote to always return byte
strings (by escaping the URL also); comparing the old
and the new string is no longer possible since the old
string is Unicode and the new string is a list-encoded
byte string.

- changes text archiving to have the archives in the
list's encoding, with unsupported characters 'replace'd

- Fixes a bug in the scrubber, where a
content-transfer-encoding might have survived
flattening of the message.

With these changes, I can process the playground
archives correctly, to get mojibake-free pages.

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 21:54

Message:
Logged In: YES 
user_id=12800

I like this patch and will now apply it.  Much better than
my feeble attempt. ;)  I was wondering why the 2nd letter in
Martin's last name was coming out as a Russian character
instead of o-umlaut in 2002-December/000056.html and was
going to complain --- until I realized that Python 2.1.3
doesn't have the windows-1252 codec!  I re-installed my test
list with Python 2.2.2 and everything looked great.

tkikuchi's mod is correct for PYthon 2.1.3 support, so the
combination is what I'm checking in.

Thank!

----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-19 19:45

Message:
Logged In: YES 
user_id=67709

Thanks.
 It looks like working for me (Japanese), except there was a
typo:

       if isinstance(body, unicode):
should be
       if isinstance(body, types.UnicodeType):



----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2002-12-19 01:55

Message:
Logged In: YES 
user_id=21627

Oops, attached.

----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-18 22:13

Message:
Logged In: YES 
user_id=67709

Hi, Martin,
Haven't you forget to attach file? I am interested in
reviewing your patch.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=655214&group_id=103

From noreply at sourceforge.net  Mon Dec 23 19:03:55 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 22:04:02 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-656346 ] correct logging of pending requests
Message-ID: <E18QfMJ-0007UF-00@sc8-sf-web2.sourceforge.net>

Patches item #656346, was opened at 2002-12-19 10:49
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=656346&group_id=103

Category: list administration
Group: Mailman 2.1
>Status: Closed
>Resolution: Rejected
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: correct logging of pending requests

Initial Comment:
I have no idea what the previous code
was supposed to do.
The new version logs what I think it should log (for me).

--- Mailman/MailList.py.ORIG    Wed Nov 27 12:01:18 2002
+++ Mailman/MailList.py Wed Nov 27 12:01:44 2002
@@ -826,7 +826,7 @@
             if recipient <> email:
                 who = "%s (%s)" % (email,
recipient.split('@')[0])
             else:
-                who = name
+                who = "%s (%s)" % (email, name)
             syslog('subscribe', '%s: pending %s %s',
                    self.internal_name(), who, by)
             raise Errors.MMSubscribeNeedsConfirmation


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 22:03

Message:
Logged In: YES 
user_id=12800

I believe this is outdated by changes already in MM2.1b6+

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=656346&group_id=103

From noreply at sourceforge.net  Mon Dec 23 19:11:12 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 22:11:18 2002
Subject: [Mailman-Developers] [ mailman-Patches-656097 ] fix for bug id 655144
Message-ID: <E18QfTM-0002qU-00@sc8-sf-web3.sourceforge.net>

Patches item #656097, was opened at 2002-12-18 22:07
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=656097&group_id=103

Category: command line scripts
Group: Mailman 2.1
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: fix for bug id 655144

Initial Comment:
Here is a quick hack for fixing bug id 655144 -- fail
to set list preferred language through command line.


----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-18 22:09

Message:
Logged In: YES 
user_id=67709

forget to check attach?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=656097&group_id=103

From noreply at sourceforge.net  Mon Dec 23 19:11:27 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 22:11:31 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-655144 ] Setting language through config_list
Message-ID: <E18QfTb-0004aF-00@sc8-sf-web4.sourceforge.net>

Bugs item #655144, was opened at 2002-12-17 07:13
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655144&group_id=103

Category: command line scripts
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Setting language through config_list

Initial Comment:
I tried changing a list's preferred_language through
config_list, and got this traceback

Traceback (most recent call last):
  File "config_list", line 336, in ?
    main()
  File "config_list", line 331, in main
    do_input(listname, infile, checkonly, verbose)
  File "config_list", line 283, in do_input
    gui._setValue(mlist, k, validval, fakedoc)
  File "/home/mailman/Mailman/Gui/Language.py", line
121, in _setValue
    doc.set_language(val)


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655144&group_id=103

From noreply at sourceforge.net  Mon Dec 23 19:14:20 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 22:14:26 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-651406 ] MM 2.0.13 to 2.1b5 upgrade fails
Message-ID: <E18QfWO-0002u5-00@sc8-sf-web3.sourceforge.net>

Patches item #651406, was opened at 2002-12-10 07:38
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=651406&group_id=103

Category: None
Group: Mailman 2.1
>Status: Closed
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: MM 2.0.13 to 2.1b5 upgrade fails

Initial Comment:
make install when updating a MM 2.0.13 installation to 
2.1b5 initally produced the following exception:

Updating mailing list: mailman
Traceback (most recent call last):
  File "bin/update", line 569, in ?
    errors = main()
  File "bin/update", line 446, in main
    errors = errors + dolist(listname)
  File "bin/update", line 186, in dolist
    mlist = MailList.MailList(listname, lock=0)
  File "/mailman/run/Mailman/MailList.py", line 101, in 
__init__
    self.Load()
  File "/mailman/run/Mailman/MailList.py", line 600, in 
Load
    self.CheckValues()
  File "/mailman/run/Mailman/MailList.py", line 650, in 
CheckValues
    for name, pattern, desc, emptyflag in self.topics:
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: topics
make: *** [update] Error 1

Having corrected the cause of this first exception the 
following exception was then encountered:

Upgrading from version 0x2000df0 to 0x20100b5
getting rid of old source files
Updating mailing list: mailman
Traceback (most recent call last):
  File "bin/update", line 569, in ?
    errors = main()
  File "bin/update", line 446, in main
    errors = errors + dolist(listname)
  File "bin/update", line 200, in dolist
    for addr, (reason, when) in mlist.delivery_status.items
():
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: delivery_status
make: *** [update] Error 1

These problems both seem to arise because of the 
following:

1. The MailList class is derived from the classes 
TopicMgr and Bouncer (amongst others).

2. The MailList __init__ function calls the __init__ 
functions of its superclasses if they have that function; 
which they do not in the case of the of TopicMgr and 
Bouncer classes

3. The MailList __init__ function calls its own 
InitTempVars function which in turn calls the 
InitTempVars functions of MailList's superclasses if they 
have that function; which they do not in the case of the 
of class TopicMgr and Bouncer classes

4. The MailList __init__ function does not call the 
InitVars functions of the TopicMgr and Bouncer classes 
which is why self.topics and self.delivery_status are 
undefined attributes of the MailList instance being 
created; these being instance variables introduced by 
MM 2.1b5 and missing from MM 2.0.13 instance of the 
MailList class which is what is being dealt with at the 
time the update is being done.

Adding the following definition to the TopicMgr and 
Bouncer class definitions seem to clear the problem 
although whether this is the best log-tem solution is 
questionable:

    InitTempVars = InitVars


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 22:14

Message:
Logged In: YES 
user_id=12800

I'm closing this one since I've added language to the
UPGRADING file alerting people to this (although I suspect
the Pinball Machine Rule will apply).

Thanks for figuring this one out.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-11 07:19

Message:
Logged In: YES 
user_id=75166

patch revised for MM 2.1b6 and better documented internally

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-10 09:19

Message:
Logged In: YES 
user_id=75166

The problem is a by product of the 413752 (coerce to 
plaintext) patch for MM 2.0.13 (mailman-2.0.13-plaintext-
0.17.patch) which had been applied to the existing system

Patch 413752 for MM 2.0.13 changes Version.py as follows:

 # config.db schema version number
-DATA_FILE_VERSION = 21
+DATA_FILE_VERSION = (21, 'plaintext_patch')

In MM 2.1b5 Version.py

DATA_FILE_VERSION = 88

In the CheckVersion member function of the MailList class 
the following comparison succeeds, i.e. the existing data 
structure is seen as being a later revision than MM 2.1b5, 
when patch 413752 has been applied:

        if self.data_version >= mm_cfg.DATA_FILE_VERSION:

and the CheckVersion function returns without calling the 
InitVars function to preset the instance variables to the 
defaults before loading the pickled data values for an existing 
list.

Changing the comparisom to this solves the problem:

        if (type(self.data_version) is type
(mm_cfg.DATA_FILE_VERSION) and \
	    self.data_version >= 
mm_cfg.DATA_FILE_VERSION) or \
	   (type(self.data_version) is type(()) and \
	    self.data_version[0] >= 
mm_cfg.DATA_FILE_VERSION):


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-10 08:13

Message:
Logged In: YES 
user_id=75166

I was wrong about my hack working because on using the 
web admin GUI to update lists I got the error feedback given 
below.

The problem seems to be more deep seated in that the 
InitVars function of the MailList class does not seem to get 
called to initialse the MailList instance variables when loading 
an existing list via the __init__ function but only through the 
Create member function called from newlist and cgi create.py.

At first blush I would think that MailList InitVars function 
should be called from the class' __init__ function before 
loading an existing instance's data into the instance 
variables; but with three functions initialisation functions, 
__init__, InitTempVars and InitVars, I'm getting confused as 
to which are supposed to do what and when.

Bug in Mailman version 2.1b5

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 "/mailman/run/scripts/driver", line 87, in run_main
    main()
  File "/mailman/run/Mailman/Cgi/admin.py", line 76, in main
    i18n.set_language(mlist.preferred_language)
  File "/mailman/run/Mailman/MailList.py", line 130, in 
__getattr__
    raise AttributeError, name
AttributeError: preferred_language




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=651406&group_id=103

From noreply at sourceforge.net  Mon Dec 23 19:23:07 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 22:23:10 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-645431 ] Filter spam on message body
Message-ID: <E18Qfet-0007pI-00@sc8-sf-web2.sourceforge.net>

Patches item #645431, was opened at 2002-11-28 16:20
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645431&group_id=103

Category: list administration
>Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: anser (anser)
Assigned to: Nobody/Anonymous (nobody)
Summary: Filter spam on message body

Initial Comment:
This patch adds a matching spam check for body content.
 It works exactly like the header check, except the
message body (after base64/quoted-printable decoding)
is scanned.

You will need to remove and re-add any lists that you
want to use this feature on after installing it.  Make
sure you get a new Defaults.py as well.

The patch is pretty clean.

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 22:23

Message:
Logged In: YES 
user_id=12800

Because this is a new feature, I have to defer it until
after MM2.1

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645431&group_id=103

From noreply at sourceforge.net  Mon Dec 23 19:29:02 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 22:29:08 2002
Subject: [Mailman-Developers] [ mailman-Patches-644797 ] Revised mailer exit
	status
Message-ID: <E18Qfkc-0000JE-00@sc8-sf-web1.sourceforge.net>

Patches item #644797, was opened at 2002-11-27 10:56
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103

Category: mail delivery
>Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Revised mailer exit status

Initial Comment:
This patch modifies the Python scripts in $prefix/scripts/ 
that are used by the MTA to deliver incoming mail to 
Mailman.

The exit statuses now returned are drawn from the mail 
related values defined in /usr/include/sysexits.h

This allows the MTA to return more meaningful 
responses to the sender when rejecting mail. It also 
allows a more sympathetic treatment of mail in the event 
that the Python script suffers an unexpected exception 
when handling incoming email.

Such exceptions are now logged to MM's 
$prefix/logs/erro in all but the most extreme error cases 
and the internal information about the Python exception 
is not passed into the response to the sender.

There are two patch versions; one for MM 2.0.13 and the 
other for MM 2.1b5

in the MM build directory say:

patch -p1 < patch-filename

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 22:29

Message:
Logged In: YES 
user_id=12800

Sorry Richard, I have to defer this one.  It's too much for
me to think about for MM2.1.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-11 06:58

Message:
Logged In: YES 
user_id=75166

exitstatus-2.1b6-0.1.patch is a revision of the patch for MM 
2.1b6 compatibility

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-11-27 10:58

Message:
Logged In: YES 
user_id=75166

version for MM 2.1b5

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103

From noreply at sourceforge.net  Mon Dec 23 19:27:15 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 22:30:26 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-645422 ] $prefix hardcoded in qmail-to-mailman.py
Message-ID: <E18Qfit-0007rm-00@sc8-sf-web2.sourceforge.net>

Patches item #645422, was opened at 2002-11-28 15:52
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645422&group_id=103

Category: mail delivery
Group: Mailman 2.1
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Matthias Juchem (brightice)
Assigned to: Nobody/Anonymous (nobody)
Summary: $prefix hardcoded in qmail-to-mailman.py

Initial Comment:
This patch replaces the hardcoded $prefix in
contrib/qmail-to-mailman.py  with @prefix@, which is
replaced with $prefix during configure.

Tested, works for me.

----------------------------------------------------------------------

Comment By: Matthias Juchem (brightice)
Date: 2002-12-08 19:29

Message:
Logged In: YES 
user_id=60479

Stupid me, patch is for 2.1, not for 2.2/3.0.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645422&group_id=103

From noreply at sourceforge.net  Mon Dec 23 19:32:00 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 22:32:16 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-643011 ] bug: Scrubbed messages are re-decoded
Message-ID: <E18QfnU-000518-00@sc8-sf-web4.sourceforge.net>

Patches item #643011, was opened at 2002-11-24 05:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643011&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: bug: Scrubbed messages are re-decoded

Initial Comment:
Content-Transfer-Encoding must be cleared.


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 22:32

Message:
Logged In: YES 
user_id=12800

Could you give more details about why this patch is
necessary?  If you have message examples, please attach them
(don't paste them into a comment).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643011&group_id=103

From barry at python.org  Mon Dec 23 22:36:55 2002
From: barry at python.org (Barry A. Warsaw)
Date: Mon Dec 23 22:37:23 2002
Subject: [Mailman-Developers] Qmailers, please comment
Message-ID: <15879.54871.194086.498711@gargle.gargle.HOWL>


Qmailers, could someone comment on the following patches:

http://sf.net/tracker/index.php?func=detail&aid=621257&group_id=103&atid=300103
http://sf.net/tracker/index.php?func=detail&aid=645513&group_id=103&atid=300103

The patches seem self-contained enough to include in MM2.1, but I
won't have any time to test them.

Please add comments to the tracker.  Should these be included?

Thanks,
-Barry

From barry at python.org  Mon Dec 23 23:14:07 2002
From: barry at python.org (Barry A. Warsaw)
Date: Mon Dec 23 23:14:41 2002
Subject: [Mailman-Developers] upgrade from 2.1b5 to 2.1b6 fails
References: <5.2.0.9.2.20021211165821.073c0c10@localhost>
Message-ID: <15879.57103.809471.214116@gargle.gargle.HOWL>


>>>>> "CS" == Christopher Schulte <schulte+mailman@nospam.schulte.org> writes:

    CS> Is there another way to clear the pending messages so I can
    CS> update the DB?  I tried going back down to 2.1b5, but the same
    CS> problem existed when I tried to view pending requests.

    CS> My other lists appear to work OK with with 2.1b[56]

I doubt the problem was specifically caused by the upgrade to 2.1b6.
What does bin/dumpdb on your list's request.db file say?

-Barry

From noreply at sourceforge.net  Mon Dec 23 20:23:52 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 23:23:57 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-656341 ] logging of pending request without email
Message-ID: <E18Qgbg-0001Uv-00@sc8-sf-web1.sourceforge.net>

Bugs item #656341, was opened at 2002-12-19 10:45
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656341&group_id=103

Category: (un)subscribing
Group: 2.1 beta
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: logging of pending request without email

Initial Comment:
2.1b6:

Pending requests are still not logged with email
addresses for me.

Patch upcoming.

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 23:23

Message:
Logged In: YES 
user_id=12800

I don't see a patch, but it definitely works for me,
attempting to subscribe either via the web or via email. 
Are you sure you see nothing in logs/subscribe?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656341&group_id=103

From noreply at sourceforge.net  Mon Dec 23 20:40:14 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 23:40:21 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-652001 ] Reply-to munging not using correct host
Message-ID: <E18QgrW-0000rI-00@sc8-sf-web2.sourceforge.net>

Bugs item #652001, was opened at 2002-12-11 07:43
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=652001&group_id=103

Category: mail delivery
Group: 2.1 beta
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: David Gibbs (midrangeman)
Assigned to: Nobody/Anonymous (nobody)
Summary: Reply-to munging not using correct host

Initial Comment:
Mailman 5.1b6 is not using the lists configured host 
name for the reply_to address ... it is using the default 
host name instead.


I have mailman configured for virtual hosting ... the two 
hosts registered are 'midrange.com' 
and 'lists.fallingrock.net'.

Default.py has the standard:
add_virtualhost(DEFAULT_URL_HOST, 
DEFAULT_EMAIL_HOST)

and I've added the following to mm_cfg.py:
VIRTUAL_HOST_OVERVIEW = 1
add_virtualhost('lists.fallingrock.net', 'lists.fallingrock.net')

My test list is configured with:
host_name = 'lists.fallingrock.net'
first_strip_reply_to = 1
reply_goes_to_list = 1
reply_to_address = ''

When I post a message to my test list, the reply-to 
header reflects my DEFAULT host name instead of the 
list's host name...

>Return-Path: <beta-testers-
bounces@lists.fallingrock.net>
>Received: from linux.midrange.com (localhost 
[127.0.0.1])
>         by linux.midrange.com (8.11.6/8.11.6) with 
ESMTP id gB8FtTa02925;
>         Sun, 8 Dec 2002 09:55:29 -0600
>Received: from GRYFFINDOR.midrange.com 
(gryffindor.midrange.com
>         [192.168.1.100])
>         by linux.midrange.com (8.11.6/8.11.6) with 
ESMTP id gB8FtLi02900
>         for <beta-testers@lists.fallingrock.net>;
>         Sun, 8 Dec 2002 09:55:21 -0600
>Message-Id: 
<5.2.0.9.2.20021208095147.02ccf150@linux.midrange.c
om>
>X-Sender: david@linux.midrange.com (Unverified)
>X-Mailer: QUALCOMM Windows Eudora Version 
5.2.0.9
>Date: Sun, 08 Dec 2002 09:55:17 -0600
>To: beta-testers@lists.fallingrock.net
>From: David Gibbs <david@midrange.com>
>Subject: Re: [beta-testers] Up for another round?
>In-Reply-To: 
<5.2.0.9.2.20021208094537.02c70330@linux.midrange.c
om>
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"; 
format=flowed
>X-MailScanner: Found to be clean
>X-BeenThere: beta-testers@lists.fallingrock.net
>X-Mailman-Version: 2.1b5
>Precedence: list
>Reply-To: New Feature Beta Testers <beta-
testers@midrange.com>
>List-Id: New Feature Beta Testers <beta-
testers.lists.fallingrock.net>
>List-Unsubscribe: 
><http://lists.fallingrock.net/mailman2/listinfo/beta-
testers>,
> 
><mailto:beta-testers-request@lists.fallingrock.net?
subject=unsubscribe>
>List-Archive: 
<http://lists.fallingrock.net/mailman2/private/beta-
testers>
>List-Post: <mailto:beta-testers@lists.fallingrock.net>
>List-Help: <mailto:beta-testers-
request@lists.fallingrock.net?subject=help>
>List-Subscribe: 
<http://lists.fallingrock.net/mailman2/listinfo/beta-
testers>,
>         <mailto:beta-testers-
request@lists.fallingrock.net?subject=subscribe>
>Sender: beta-testers-bounces@midrange.com
>Errors-To: beta-testers-bounces@midrange.com



----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 23:40

Message:
Logged In: YES 
user_id=12800

I still cannot reproduce this.  When I turn the reply-to
options on I get the expected virtual host, regardless of
whether the host was my primary or secondary host.

Without the patch, I'm going to have to close this as
irreproducible.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=652001&group_id=103

From noreply at sourceforge.net  Mon Dec 23 20:42:34 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 23:42:37 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-651146 ] make distclean forgets some Makefiles
Message-ID: <E18Qgtm-0000u9-00@sc8-sf-web2.sourceforge.net>

Bugs item #651146, was opened at 2002-12-09 17:40
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=651146&group_id=103

Category: configuring/installing
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Matthias Juchem (brightice)
Assigned to: Nobody/Anonymous (nobody)
Summary: make distclean forgets some Makefiles

Initial Comment:
Hi.

mailman/messages/Makefile and
mailman/tests/*/Makefile do not get cleaned up when
doing a 'make distclean'.

Patch 645421 should fix this, see patch description.

 Matthias


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 23:41

Message:
Logged In: YES 
user_id=12800

The patch was accepted but I forgot to close this bug
report.  Doing so now.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=651146&group_id=103

From noreply at sourceforge.net  Mon Dec 23 20:46:40 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 23:46:44 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-650711 ] add_members fails with specific address
Message-ID: <E18Qgxk-0006VR-00@sc8-sf-web4.sourceforge.net>

Bugs item #650711, was opened at 2002-12-09 01:23
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=650711&group_id=103

Category: command line scripts
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Cabel Sasser (cabelsa)
Assigned to: Nobody/Anonymous (nobody)
Summary: add_members fails with specific address

Initial Comment:
I am migrating from one list system to another, and in
the process of doing so I'm importing tens of thousands
of addresses using the command-line add_members utility.

Bug:

add_members reproducibly crashes when it gets to the
following obviously invalid e-mail address in the text
file I'm importing from:

----@---.---

Here is the error message:

[...]
Traceback (most recent call last):
  File "/usr/local/mailman/bin/add_members", line 297, in ?
    main()
  File "/usr/local/mailman/bin/add_members", line 274,
in main
    addall(mlist, nmembers, 0, send_welcome_msg, s)
  File "/usr/local/mailman/bin/add_members", line 173,
in addall
    except MMHostileAddress:
NameError: global name 'MMHostileAddress' is not defined

If I remove the above dash-tastic address, the
add_members import succeeds.

I hope this helps! Mailman totally rocks! :)


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 23:46

Message:
Logged In: YES 
user_id=12800

Well, the bug was still there in MM2.1b6 so I fixed it. :)


----------------------------------------------------------------------

Comment By: Cabel Sasser (cabelsa)
Date: 2002-12-09 01:24

Message:
Logged In: YES 
user_id=665207

BTW, this is 2.0b5. Sorry for not mentioning that above.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=650711&group_id=103

From noreply at sourceforge.net  Mon Dec 23 20:48:59 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 23:49:14 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-616674 ] bin/arch not processing mbox import corr
Message-ID: <E18Qgzz-0006XK-00@sc8-sf-web4.sourceforge.net>

Bugs item #616674, was opened at 2002-09-30 13:43
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=616674&group_id=103

Category: command line scripts
Group: 2.1 beta
>Status: Pending
Resolution: None
Priority: 7
Submitted By: fuzzy (fuzzynco)
Assigned to: Nobody/Anonymous (nobody)
Summary: bin/arch not processing mbox import corr

Initial Comment:
I needed to import an archive from yahoo!groups. a 
list formerly on Y!G is now on my server with 
MM2.1b3. After creating the mbox file with a perl 
script na dtesting it with pine (to make sure all the 
email is acuallu there), I tried to import it
using arch. there are a few thousand emails in the file, 
but arch only finds 2? I posted to the mm users 
mailing list and got a reply from Larry Weeks, said to 
send him a copy of the file, and he tested it with 
bin/arch from 2.0.6 and it works as expected. 
since the mbox file is readable by pine, shouldn't arch
handle it correctly?

email me if i can provide any thing that would help 
diagnose the problem.

thanks...
fuzzy@pooh.asarian.org


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 23:48

Message:
Logged In: YES 
user_id=12800

Moving this to Pending since there's been no follow up.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-07 11:33

Message:
Logged In: YES 
user_id=12800

arch only handles mbox files in "Unix mbox format".  Such
files delineate messages with a single line containing "From
" -- that's "F R O M space" at the front of the line.  There
can be stricter criteria on what follows that header, but
that's the gist of it.  Maybe your individual files don't
have the right separator.

You can try running bin/cleanarch on the file to see if it's
close.  Use --dry-run to just examine the file.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=616674&group_id=103

From noreply at sourceforge.net  Mon Dec 23 20:58:43 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 23 23:58:49 2002
Subject: [Mailman-Developers] [ mailman-Bugs-629616 ] Invalid admin
	notification
Message-ID: <E18Qh9P-00051z-00@sc8-sf-web3.sourceforge.net>

Bugs item #629616, was opened at 2002-10-27 19:43
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=629616&group_id=103

Category: (un)subscribing
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Daniel Buchmann (avalon)
Assigned to: Nobody/Anonymous (nobody)
Summary: Invalid admin notification

Initial Comment:
Using latest CVS (2.1b4).
When someone subscribes through the web interface (listinfo page), the 
list admin will receive an invalid email if subscription notification has 
been turned on. The email contains the content of 
adminsubscribeack.txt, but no string interpolation is done. This is not 
the case if  subscribing using the mail command interface or subscribed 
by the admin using the admin page.

Also, if the subscribing user chooses a different language than the list 
language, the email notification sent to the admin will have a Subject: 
according to the list language, but body according to what the 
subscribing user chose. Which is probably not what we want... ;)

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 23:58

Message:
Logged In: YES 
user_id=12800

I couldn't reproduce the first problem in 2.1b6+, but I
could reproduce the second, which is fixed now!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=629616&group_id=103

From noreply at sourceforge.net  Mon Dec 23 21:00:26 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 00:00:33 2002
Subject: [Mailman-Developers] [ mailman-Bugs-630497 ] Traceback in error file
Message-ID: <E18QhB4-00054U-00@sc8-sf-web3.sourceforge.net>

Bugs item #630497, was opened at 2002-10-29 09:41
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=630497&group_id=103

Category: bounce detection
Group: 2.1 beta
>Status: Pending
Resolution: None
Priority: 7
Submitted By: Andy Carpenter (acarpenter)
Assigned to: Nobody/Anonymous (nobody)
Summary: Traceback in error file

Initial Comment:
Since I upgraded to 2.1b4, I have started to get the 
following tracebacks in the error log file.  It is a 
characteristics of our busiest mail list that many of the posts 
come from the far east with unicode characters in their 
subject line.


Oct 29 14:19:35 2002 (26533) Uncaught runner exception: 
ASCII decoding error: or
dinal not in range(128)
Oct 29 14:19:35 2002 (26533) 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 
154, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  
File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py"
, line 129, in _dispo
se
    status = self._dopipeline(mlist, msg, msgdata, pipeline)
  
File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py"
, line 167, in _dopip
eline
    mlist.BounceMessage(msg, msgdata, e)
  File "/usr/local/mailman/Mailman/Bouncer.py", line 273, in 
BounceMessage
    lang=self.preferred_language)
  File "/usr/local/mailman/Mailman/Message.py", line 203, in 
__init__
    self['Subject'] = Header(subject, charset, 
header_name='Subject')
  File "/usr/local/mailman/pythonlib/email/Header.py", line 
164, in __init__
    self.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 
230, in append
    ustr = unicode(s, incodec)
UnicodeError: ASCII decoding error: ordinal not in range
(128)

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:00

Message:
Logged In: YES 
user_id=12800

There have been lots of related fixes in 2.1b6 (and in cvs),
so it would be good to know whether upgrading fixes the problem.

If not, please un-pend this bug report and attach (not
paste) one of the offending messages so I can try to
reproduce it.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=630497&group_id=103

From noreply at sourceforge.net  Mon Dec 23 21:01:48 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 00:01:53 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-643605 ] RFC2882 and / in subscriber address
Message-ID: <E18QhCO-0001MY-00@sc8-sf-web2.sourceforge.net>

Bugs item #643605, was opened at 2002-11-25 10:55
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643605&group_id=103

Category: (un)subscribing
>Group: Postponed
Status: Open
Resolution: None
Priority: 7
Submitted By: Christopher Kolar (ckolar)
Assigned to: Nobody/Anonymous (nobody)
Summary: RFC2882 and / in subscriber address

Initial Comment:
Reproduced from the mailman-users list.  Thanks to Bill
for the followup.

--chris

[][][][][][]

Majordomo would tell you the same thing but I agree
that it is a legal address (we use similar addresses
internally at work) and should be accepted.   RFC2822
(http://www.faqs.org/rfcs/rfc2822.html) clearly allows
it in the local-part (Section 3.4.1) as a dot-atom.

This should be fixed but in the mean time I don't think
you are going to get it into mailman.

Bill W.

At 09:31 AM 11/25/2002 -0600, Christopher Kolar wrote:

Hello.  I am trying to add a person to a mail list and
having some problems.  Their organization runs some
sort of bestial mail system where the addresses are of
the form:

        schmoe.j/bhs@dns.u99.k12.il.us

When I try to drop the address in through the mass
subscribe screen I get the following message from Mailman:

        * Joe Schmoe -- Hostile address (illegal
characters) 

My guess is that the / is getting parsed by Mm as an
attempt to reference a file (a la majordomo).  Is there
a way to force the address onto the subscriber list? 
It is an actual valid address for delivery.

Thanks in advance,

--chris


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:01

Message:
Logged In: YES 
user_id=12800

I agree that any RFC 2822 legal address should be allowed by
Mailman.  This won't get fixed for MM2.1, but I'll keep it
open so we can address it in MM3.0.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643605&group_id=103

From noreply at sourceforge.net  Mon Dec 23 21:03:24 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 00:03:29 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-643233 ] E-mail addresses not being obscured
Message-ID: <E18QhDw-00058h-00@sc8-sf-web3.sourceforge.net>

Bugs item #643233, was opened at 2002-11-24 16:09
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643233&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Terry Grace (tgrace)
Assigned to: Nobody/Anonymous (nobody)
Summary: E-mail addresses not being obscured

Initial Comment:
In 2.1b5, the archives contain the posters e-mail 
address even if the option to obscure the posters 
identity has been selected.

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:03

Message:
Logged In: YES 
user_id=12800

I believe this is fixed in 2.1b6+.  At least, it's probably
about as fixed as it's going to be.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643233&group_id=103

From noreply at sourceforge.net  Mon Dec 23 21:04:30 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 00:04:35 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-640360 ] path relative URLs with /base vs /base/
Message-ID: <E18QhF0-00059y-00@sc8-sf-web3.sourceforge.net>

Bugs item #640360, was opened at 2002-11-18 17:23
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640360&group_id=103

Category: Web/CGI
Group: 2.1 beta
>Status: Closed
>Resolution: Wont Fix
Priority: 7
Submitted By: Donn Cave (donnc)
Assigned to: Nobody/Anonymous (nobody)
Summary: path relative URLs with /base vs /base/

Initial Comment:
Our Apache server accepts path requests with or with a 
trailing slash, indifferently.  (I understand there is no 
redirect.)  This affects (cripples) relative paths, because 
http://host/mailman/private/name is the same page as http://
host/mailman/private/name/, but is different in reference to 
relative paths.  The relative location of a month would be 
`href="name/2002-November/subject.html"' for the former, but 
`href="2002-November/subject.html"' for the latter.

I suspect that the "private" URL is rarely entered by hand 
anyway, but FYI.  /mailman/private/name/2002-November/
subject.html is OK, as far as I know.

2.1b4

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:04

Message:
Logged In: YES 
user_id=12800

I don't expect to change this for MM2.1 final.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640360&group_id=103

From noreply at sourceforge.net  Mon Dec 23 21:05:08 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 00:05:15 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color
Message-ID: <E18QhFc-0005B6-00@sc8-sf-web3.sourceforge.net>

Bugs item #635462, was opened at 2002-11-08 07:13
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103

Category: Web/CGI
Group: 2.1 beta
>Status: Closed
Resolution: Wont Fix
Priority: 4
Submitted By: Marcin Orlowski (carl-os)
Assigned to: Nobody/Anonymous (nobody)
Summary: Admin pages HTML does not set TEXT color

Initial Comment:
Mailman admin pages believe that TEXT color is always
black and does not set it to, hoping nobody changes the
defaults. And this is false assumption ;-) For testing
purposes my defaults are black bg color and yellow
text. And since admin pages sets bg to white it now
exposes yellow fonts on white background here. Kinda
unreadable. Solution -> fix template/css/whatever to
set up text color to black.

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:05

Message:
Logged In: YES 
user_id=12800

Too late.  We'll probably integrate Fred Drake's css patch
after 2.1 final

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-02 11:12

Message:
Logged In: YES 
user_id=12800

There's no official css support yet.  I won't fix this for
MM2.1 unless someone can provide a really clean patch.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103

From noreply at sourceforge.net  Mon Dec 23 21:06:25 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 00:06:31 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-621689 ] Subscribe requests dropped from admin db
Message-ID: <E18QhGr-0002VD-00@sc8-sf-web1.sourceforge.net>

Bugs item #621689, was opened at 2002-10-10 23:10
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_id=103

Category: (un)subscribing
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 7
Submitted By: Mark Dadgar (mdadgar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Subscribe requests dropped from admin db

Initial Comment:
Occasionally, subscribe requests (via the web page) to a list that 
requires moderator approval for subscriptions never make it to the 
admin db for that list.  They are listed in the subscribe log file, but 
never show up on the admin db page.

Log file entries look like this:

Oct 10 18:43:43 2002 (31168) eventmasters: pending   
XXXXXX.swfla.rr.com

But the admin db page for the list shows no outstanding issues.

I have verified that there was an actual subscription request 
behind this log entry.

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:06

Message:
Logged In: YES 
user_id=12800

I definitely need more information.  I've neve been able to
reproduce the problem.  Do you think it could be related to
the unofficial patches you've applied?

----------------------------------------------------------------------

Comment By: Mark Dadgar (mdadgar)
Date: 2002-12-06 02:29

Message:
Logged In: YES 
user_id=598228

Ok, I verified that it's still a problem under 2.1b5 with the htdig and 
indexing patches.

It's a real drag, too.  :(

Please let me know if you need more debug info.

----------------------------------------------------------------------

Comment By: Mark Dadgar (mdadgar)
Date: 2002-11-22 01:08

Message:
Logged In: YES 
user_id=598228

Unfortunately, it's still occurring under 2.1b4.  

I'll check it under 2.1b5 as soon as the patches for htdig integration are 
released, as I need those to implement.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-10-22 10:11

Message:
Logged In: YES 
user_id=12800

I'm going to defer this one until 2.1b4 goes out.  I've
fixed some related bugs in cvs, so hopefully this will be
fixed in the new version.

----------------------------------------------------------------------

Comment By: Mark Dadgar (mdadgar)
Date: 2002-10-20 13:14

Message:
Logged In: YES 
user_id=598228

Sorry - I'm running 2.1b3.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-10-20 11:48

Message:
Logged In: YES 
user_id=12800

What version of Mailman are you using.  It's import to know
the exact version, i.e. 2.1beta3, or if you're running from
cvs.  A lot of these problems have been fixed in cvs, which
will soon be released as 2.1 beta 4.

----------------------------------------------------------------------

Comment By: Mark Dadgar (mdadgar)
Date: 2002-10-11 00:29

Message:
Logged In: YES 
user_id=598228

I just verified, by cat'ing pending.pck, that the appropriate changes 
seem to be in there.  But the web interface never picks them up.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_id=103

From noreply at sourceforge.net  Mon Dec 23 21:07:27 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 00:07:30 2002
Subject: [Mailman-Developers] [ mailman-Bugs-214205 ] e-mail&lt;-&gt;
 usenet gateway Reply-To header (PR#303)
Message-ID: <E18QhHr-0005Ee-00@sc8-sf-web3.sourceforge.net>

Bugs item #214205, was opened at 2000-09-11 16:25
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id=103

Category: nntp/news
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 7
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: e-mail&lt;-&gt;usenet gateway Reply-To header (PR#303)

Initial Comment:
Jitterbug-Id: 303
Submitted-By: orion@tribble.dyndns.org
Date: Mon, 24 Jul 2000 18:54:02 -0400 (EDT)
Version: 2.0beta4
OS: Debian linux potato


I'm running a plain e-mail<->usenet gateway.
When someone replies to a usenet post through the list, his e-mail client sets
an In-Reply-To: header instead of a Reply-To: header. This causes newsreaders to
improperly thread messages.

I inserted the following bit into Mailman/Handlers/ToUsenet.py at around line
82:

    # if the message is a reply to a previous post, change the header so
    # that newsreaders can thread it properly
    if msg.getheader('in-reply-to'):
        msg.headers.append('References: %s\n' % msg.getheader('in-reply-to'))
        del msg['in-reply-to']

I'm happy to say that this solved the problem.
 
(before you laugh at me, take note that I never looked at python before.)



====================================================================
Audit trail:
None

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:07

Message:
Logged In: YES 
user_id=12800

Sigh.  Very doubtful I'll get to look at the threading
issues before MM2.1 final.  I'll address this again after
the release.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-23 18:38

Message:
Logged In: YES 
user_id=12800

Changing the group to 2.1 beta because I want to look at
threading issues for gated messages before 2.1 final is
released.

----------------------------------------------------------------------

Comment By: Giovanni Lopedote (giuans)
Date: 2002-05-01 08:34

Message:
Logged In: YES 
user_id=531451

What a coincidence! I had the same problem and I looked 
into the code, then modified it to work properly. The 
coincidence is that my patch is *identical* to yours. So, 
for sure it works :-)


----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2000-09-27 17:00

Message:
RFC 2076 says nothing about using In-Reply-To for news, so it might not be a bad idea to copy In-Reply-To to References when gating a message from mail to news.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2000-09-19 12:48

Message:
This sounds like the email client in question is broken.  Mine for example, correctly inserts References: headers and the news readers properly thread the messages.  I'm not inclined to cater to broken email or news clients.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id=103

From noreply at sourceforge.net  Mon Dec 23 21:10:27 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 00:10:33 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-620033 ] gate_news should catch lost connection
Message-ID: <E18QhKl-0005IT-00@sc8-sf-web3.sourceforge.net>

Bugs item #620033, was opened at 2002-10-07 22:07
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620033&group_id=103

Category: nntp/news
Group: 2.1 beta
>Status: Closed
Resolution: Accepted
Priority: 7
Submitted By: Ron Jarrell (jarrell)
Assigned to: Nobody/Anonymous (nobody)
Summary: gate_news should catch lost connection

Initial Comment:
Sep 20 10:51:35 2002 gate_news(9301): Traceback 
(most recent call last):
Sep 20 10:51:35 2002 gate_news(9301):   
File "/home/mailman/cron/gate_news", line 270, 
in ?
Sep 20 10:51:35 2002 gate_news(9301):      main()
Sep 20 10:51:35 2002 gate_news(9301):   
File "/home/mailman/cron/gate_news", line 250, in 
main
Sep 20 10:51:35 2002 gate_news(9301):      
process_lists(lock)
Sep 20 10:51:35 2002 gate_news(9301):   
File "/home/mailman/cron/gate_news", line 194, in 
process_lists
Sep 20 10:51:35 2002 gate_news(9301):      conn, 
first, last = open_newsgroup(mlist)
Sep 20 10:51:35 2002 gate_news(9301):   
File "/home/mailman/cron/gate_news", line 89, in 
open_newsgroup
Sep 20 10:51:35 2002 gate_news(9301):      
password=mm_cfg.NNTP_PASSWORD)
Sep 20 10:51:35 2002 gate_news(9301):   
File "/usr/local/lib/python2.2/nntplib.py", line 
117, in __init__
Sep 20 10:51:35 2002 gate_news(9301):      
self.welcome = self.getresp()
Sep 20 10:51:35 2002 gate_news(9301):   
File "/usr/local/lib/python2.2/nntplib.py", line 
203, in getresp
Sep 20 10:51:35 2002 gate_news(9301):      resp = 
self.getline()
Sep 20 10:51:35 2002 gate_news(9301):   
File "/usr/local/lib/python2.2/nntplib.py", line 
192, in getline
Sep 20 10:51:35 2002 gate_news(9301):      line = 
self.file.readline()
Sep 20 10:51:35 2002 gate_news(9301): IOError :  
[Errno 131] Connection reset by peer 


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:10

Message:
Logged In: YES 
user_id=12800

Hmm, the specific traceback you pasted indicates an error
during the initial connection.  I think that's about the
best we're going to do for MM2.1 final.

----------------------------------------------------------------------

Comment By: Ron Jarrell (jarrell)
Date: 2002-10-22 11:19

Message:
Logged In: YES 
user_id=34619

Didn't work...  This comes up, btw, not during initial 
connection, but if the connection goes away during a 
gate_news run, like the daemon on the other end dies, 
or the news server reboots, etc.  You get an IOerror on 
the mailman side.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-10-15 15:00

Message:
Logged In: YES 
user_id=12800

I'm applying this patch

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-10-15 14:19

Message:
Logged In: YES 
user_id=12800

I didn't realize that nntplib.NNTP() can raise an IOError --
I thought it would have been a socket.error.  Oh well,
here's an untested patch.  I think I'll check this in just
because I don't see how it could break anything.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620033&group_id=103

From fil at rezo.net  Tue Dec 24 12:11:03 2002
From: fil at rezo.net (Fil)
Date: Tue Dec 24 06:11:08 2002
Subject: [Mailman-Developers] ugly traceback
Message-ID: <20021224111103.GA22978@rezo.net>

Hello,

I just tried to upgrade to the current CVS, and I'm stuck with this error: 

Traceback (most recent call last):
  File "bin/update", line 48, in ?
    from Mailman import MailList
  File "/usr/local/mailman/Mailman/MailList.py", line 49, in ?
    from Mailman.Archiver import Archiver
  File "/usr/local/mailman/Mailman/Archiver/__init__.py", line 17, in ?
    from Archiver import *
  File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 36, in ?
    from Mailman.i18n import _
  File "/usr/local/mailman/Mailman/i18n.py", line 52, in ?
    set_language()
  File "/usr/local/mailman/Mailman/i18n.py", line 35, in set_language
    language)
  File "/usr/lib/python2.1/gettext.py", line 245, in translation
    t = _translations.setdefault(key, class_(open(mofile, 'rb')))
  File "/usr/lib/python2.1/gettext.py", line 106, in __init__
    self._parse(fp)
  File "/usr/lib/python2.1/gettext.py", line 180, in _parse
    k, v = item.split(':', 1)
ValueError: unpack list of wrong size
make: *** [update] Erreur 1



From fil at rezo.net  Tue Dec 24 12:23:40 2002
From: fil at rezo.net (Fil)
Date: Tue Dec 24 06:23:43 2002
Subject: [Mailman-Developers] ugly traceback
In-Reply-To: <20021224111103.GA22978@rezo.net>
References: <20021224111103.GA22978@rezo.net>
Message-ID: <20021224112340.GC22978@rezo.net>

>   File "/usr/lib/python2.1/gettext.py", line 180, in _parse
>     k, v = item.split(':', 1)
> ValueError: unpack list of wrong size
> make: *** [update] Erreur 1

I upgraded to Python2.2, to no avail :
>   File "/usr/lib/python2.2/gettext.py", line 180, in _parse
>     k, v = item.split(':', 1)
> ValueError: unpack list of wrong size
> make: *** [update] Erreur 1

-- Fil


From fil at rezo.net  Tue Dec 24 12:49:31 2002
From: fil at rezo.net (Fil)
Date: Tue Dec 24 06:52:16 2002
Subject: [Mailman-Developers] ugly traceback
In-Reply-To: <20021224112340.GC22978@rezo.net>
References: <20021224111103.GA22978@rezo.net>
	<20021224112340.GC22978@rezo.net>
Message-ID: <20021224114931.GE22978@rezo.net>

> I upgraded to Python2.2, to no avail :
> >   File "/usr/lib/python2.2/gettext.py", line 180, in _parse
> >     k, v = item.split(':', 1)
> > ValueError: unpack list of wrong size
> > make: *** [update] Erreur 1

One of the .mo files must be corrupt, as I did a "cvs -D '1 month ago'" on
the messages/ folder and was able to compile and run.

-- Fil


From noreply at sourceforge.net  Tue Dec 24 06:15:54 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 09:15:58 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-643233 ] E-mail addresses not being obscured
Message-ID: <E18Qpqc-0002it-00@sc8-sf-web4.sourceforge.net>

Bugs item #643233, was opened at 2002-11-24 12:09
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643233&group_id=103

Category: Pipermail
Group: 2.1 beta
Status: Closed
Resolution: Fixed
Priority: 7
Submitted By: Terry Grace (tgrace)
Assigned to: Nobody/Anonymous (nobody)
Summary: E-mail addresses not being obscured

Initial Comment:
In 2.1b5, the archives contain the posters e-mail 
address even if the option to obscure the posters 
identity has been selected.

----------------------------------------------------------------------

>Comment By: Terry Grace (tgrace)
Date: 2002-12-24 05:15

Message:
Logged In: YES 
user_id=87771

Problem is still lthere with 2.1b6. E-mail addresses are being 
obscured in the article indexes but not in the articles 
themselves.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 20:03

Message:
Logged In: YES 
user_id=12800

I believe this is fixed in 2.1b6+.  At least, it's probably
about as fixed as it's going to be.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643233&group_id=103

From noreply at sourceforge.net  Tue Dec 24 06:27:46 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 09:27:52 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-658213 ] i18n problem on "Confirm subscription" 
Message-ID: <E18Qq26-0006VT-00@sc8-sf-web2.sourceforge.net>

Bugs item #658213, was opened at 2002-12-24 15:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658213&group_id=103

Category: (un)subscribing
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniel Buchmann (avalon)
Assigned to: Nobody/Anonymous (nobody)
Summary: i18n problem on "Confirm subscription" 

Initial Comment:
Mailman version: 2.1rc1

Wrong language is used for the heading, title and language selection 
box on the "Confirm subscription" page. The list language is used, not 
the language chosen by the subscribing user.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658213&group_id=103

From barry at python.org  Tue Dec 24 10:53:16 2002
From: barry at python.org (Barry A. Warsaw)
Date: Tue Dec 24 10:53:48 2002
Subject: [Mailman-Developers] ugly traceback
References: <20021224111103.GA22978@rezo.net>
Message-ID: <15880.33516.699160.414444@gargle.gargle.HOWL>


I've fixed the French catalog and submitted a bug report on gettext.py
for the Python project (I don't have time to fix that now).

Will be checking in updates shortly.

-Barry

From noreply at sourceforge.net  Tue Dec 24 08:45:19 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 11:45:23 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-643233 ] E-mail addresses not being obscured
Message-ID: <E18QsBD-0003sC-00@sc8-sf-web3.sourceforge.net>

Bugs item #643233, was opened at 2002-11-24 16:09
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643233&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Open
Resolution: Fixed
Priority: 7
Submitted By: Terry Grace (tgrace)
Assigned to: Nobody/Anonymous (nobody)
Summary: E-mail addresses not being obscured

Initial Comment:
In 2.1b5, the archives contain the posters e-mail 
address even if the option to obscure the posters 
identity has been selected.

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 11:45

Message:
Logged In: YES 
user_id=12800

Re-opening since I think I can fix this (we'll see)

----------------------------------------------------------------------

Comment By: Terry Grace (tgrace)
Date: 2002-12-24 09:15

Message:
Logged In: YES 
user_id=87771

Problem is still lthere with 2.1b6. E-mail addresses are being 
obscured in the article indexes but not in the articles 
themselves.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:03

Message:
Logged In: YES 
user_id=12800

I believe this is fixed in 2.1b6+.  At least, it's probably
about as fixed as it's going to be.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643233&group_id=103

From noreply at sourceforge.net  Tue Dec 24 09:02:24 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 12:02:30 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-643233 ] E-mail addresses not being obscured
Message-ID: <E18QsRk-0007IH-00@sc8-sf-web4.sourceforge.net>

Bugs item #643233, was opened at 2002-11-24 16:09
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643233&group_id=103

Category: Pipermail
Group: 2.1 beta
>Status: Closed
Resolution: Fixed
Priority: 7
Submitted By: Terry Grace (tgrace)
Assigned to: Nobody/Anonymous (nobody)
Summary: E-mail addresses not being obscured

Initial Comment:
In 2.1b5, the archives contain the posters e-mail 
address even if the option to obscure the posters 
identity has been selected.

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 12:02

Message:
Logged In: YES 
user_id=12800

Fixed obscuring in the body of email messages, when
ARCHIVER_OBSCURES_EMAILADDRS is true.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 11:45

Message:
Logged In: YES 
user_id=12800

Re-opening since I think I can fix this (we'll see)

----------------------------------------------------------------------

Comment By: Terry Grace (tgrace)
Date: 2002-12-24 09:15

Message:
Logged In: YES 
user_id=87771

Problem is still lthere with 2.1b6. E-mail addresses are being 
obscured in the article indexes but not in the articles 
themselves.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:03

Message:
Logged In: YES 
user_id=12800

I believe this is fixed in 2.1b6+.  At least, it's probably
about as fixed as it's going to be.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643233&group_id=103

From noreply at sourceforge.net  Tue Dec 24 09:29:27 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 12:29:31 2002
Subject: [Mailman-Developers] [ mailman-Bugs-658261 ] transcheck error for
	double %
Message-ID: <E18Qsrv-00033G-00@sc8-sf-web2.sourceforge.net>

Bugs item #658261, was opened at 2002-12-24 18:29
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658261&group_id=103

Category: command line scripts
Group: Postponed
Status: Open
Resolution: None
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Simone Piunno (pioppo)
Summary: transcheck error for double %

Initial Comment:
As reported by Daniel Buchmann, transcheck doesn't detect 
correctly when a literal % is expressed as a double %, e.g.

%%(&lt;variabelnavn&gt;)s

is detected a variable reference to interpolate insted
of a simple
text.

The fix would require a much more complex parser, which
is not
worth it now but could be in 2.2.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658261&group_id=103

From barry at python.org  Tue Dec 24 15:55:04 2002
From: barry at python.org (Barry A. Warsaw)
Date: Tue Dec 24 15:55:36 2002
Subject: [Mailman-Developers] RELEASED Mailman 2.1 rc 1
Message-ID: <15880.51624.526771.37799@gargle.gargle.HOWL>


Well, it's Christmas Eve and it's snowing outside, so what more
festive thing is there to do but announce the release candidate for
Mailman 2.1 final. :)

It's been a long time coming, but hopefully it's worth unwrapping this
present!  I believe we're on track to make the final release before
the end of the year.  My humble thanks to everyone who's been involved
in the project.

See below for the short list of changes since 2.1 beta 6.  Most
importantly, Lithuanian support has been added.  The new tarball has
been uploaded to SourceForge and the various web sites have been
updated too.

Enjoy, and seasons greetings to all,
-Barry

-------------------- snip snip --------------------
2.1 rc 1 (24-Dec-2002)

    Bug fixes and language updates.  Also,

    - Lithuanian support has been added.

    - bin/remove_members grew --nouserack and --noadminack switches

    - configure now honors --srcdir

From christopher.m.perez at exgate.tek.com  Wed Dec 18 16:40:08 2002
From: christopher.m.perez at exgate.tek.com (christopher.m.perez@exgate.tek.com)
Date: Tue Dec 24 16:11:34 2002
Subject: [Mailman-Developers] 
 File attachments cause scrambled URL information [Mailman v2.1b6]
Message-ID: <212D7E61C1F7D511B9270002A507DE7D039BE0FA@us-bv-m10.bv.tek.com>

Mailman Developers,

When we send the included file (see attachment to this email) through
Mailman 2.1b6 we get a URL region that starts with 
"z'??mj?Zrzz???+???t??x:"

The following usual information such as the following is completely replaced
with the aforementioned string:
A non-text attachment was scrubbed... 
Name: filname.fileextension 
Type: application/octet-stream 
Size: filesize bytes 
Desc: not available...

We've noticed this in testing with a few jpg files and one PowerPoint file.
We've sent the mail through 'Outlook', but a download of the full raw
archive coming out of Sendmail appears to be OK in all cases.  In fact, the
section of the Mailman garbled URL in our Sendmail archive is as follows:
------_=_NextPart_000_01C2A6F2.C38699F0 
Content-Type: image/jpeg; name="creigsmith2.jpg" 
Content-Transfer-Encoding: base64 
Content-Disposition: attachment;
 	filename="creigsmith2.jpg" 
/9j/4AAQSkZJRgABAQEBLAEsAAD/2wBDAAMCAgMCAgMDAwMEAwMEBQgFBQQEBQoHBwYIDAoMDAsK
CwsNDhIQDQ4RDgsLEBYQERMUFRUVDA8XGBYUGBIUFRT/2wBDAQMEBAUEBQkFBQkUDQsNFBQUFBQU
FBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBT/wAARCAGXAUcDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
...


Thoughts?  Ideas?  Comments?  Feedback?

 <<creigsmith2.jpg>> 

Christopher M. Perez 
Program Manager - Central Engineering, Software Engineering Services
Tektronix, Inc.
PO Box 500, M/S 39-549
Beaverton, Oregon  97077-0001
> *  EMail:	christopher.m.perez@tek.com
       AOL AIM:         CMarkPerez
> *  Phone:	(503) 627-5524
> *  Fax:		(503) 627-1388
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: creigsmith2.jpg
Type: image/jpeg
Size: 41917 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-developers/attachments/20021218/4051685c/creigsmith2.jpeg
From mch at cix.compulink.co.uk  Thu Dec 19 19:28:00 2002
From: mch at cix.compulink.co.uk (Mike Holderness)
Date: Tue Dec 24 16:11:41 2002
Subject: [Mailman-Developers] Archive templates in mm 2.1?
Message-ID: <memo.380185@cix.compulink.co.uk>

'Scuse me if I've missed something obvious... but is the 
code for HTML templates for the mailman/Pipermail archives
checked in for 2.1? 

I did look at the release notes for 2.1bN but didn't see it...

I'm asking because I'm planning upgrades for what will be 
a suite of mailing lists (for journalists :-)

Though I don't speak Python (yet) I can just about pick 
out the sense in it... so if there's specific help needed...

Mike Holderness
  in this instance,
  www.londonfreelance.org


From pmalone1 at swarthmore.edu  Fri Dec 20 16:01:19 2002
From: pmalone1 at swarthmore.edu (Tricia Maloney)
Date: Tue Dec 24 16:11:48 2002
Subject: [Mailman-Developers] Cost
Message-ID: <5.1.1.5.2.20021220160057.00cbd598@mail.swarthmore.edu>

Is this program free?

Tricia Maloney
Assistant Director of Alumni Relations
Swarthmore College
500 College Avenue
Swarthmore, PA 19081
(610) 328-8404
http://www.Swarthmore.edu



From ziad at wads.com  Wed Dec 18 12:58:08 2002
From: ziad at wads.com (Ziad Sidawi)
Date: Tue Dec 24 16:13:29 2002
Subject: [Mailman-Developers] adding to list without confirmation
Message-ID: <AFEOIMMCGPPKAPMAJEHMCEOECMAA.ziad@wads.com>

Dear developers,
I would like to keep the confirmation part when someone subscribe thru
email.
However, is there a way where a special email can be send to the Mailman
where confirmation of the user is not required?

let me explain: I have a shopping cart program, and when a user completes
his order, I want to issue an email to subscribe this user to the mailing
list without having the mailing list sending the user an email to confirm.
On the same hand, I do not want to disable the functionality of confirmation
if a user tries to subscribe to the mailing list.

I have worked in the past with a mail list program, where emails with a
[password] in
the subject area, would be verified and if correct (pas for admin) then this
email is treated as coming from the admin, and hence the user is registered
without requiring confirmation email.

Any ideas?


From barry at python.org  Tue Dec 24 16:15:44 2002
From: barry at python.org (Barry A. Warsaw)
Date: Tue Dec 24 16:16:14 2002
Subject: [Mailman-Developers] Cost
References: <5.1.1.5.2.20021220160057.00cbd598@mail.swarthmore.edu>
Message-ID: <15880.52864.593955.287624@gargle.gargle.HOWL>


>>>>> "TM" == Tricia Maloney <pmalone1@swarthmore.edu> writes:

    TM> Is this program free?

Yes, it is both free and free. :)  Or to put it another way, it costs
nothing, and you can do whatever you want with it.

-Barry

From barry at python.org  Tue Dec 24 16:18:00 2002
From: barry at python.org (Barry A. Warsaw)
Date: Tue Dec 24 16:18:31 2002
Subject: [Mailman-Developers] adding to list without confirmation
References: <AFEOIMMCGPPKAPMAJEHMCEOECMAA.ziad@wads.com>
Message-ID: <15880.53000.744950.710702@gargle.gargle.HOWL>


>>>>> "ZS" == Ziad Sidawi <ziad@wads.com> writes:

    ZS> Dear developers, I would like to keep the confirmation part
    ZS> when someone subscribe thru email.  However, is there a way
    ZS> where a special email can be send to the Mailman where
    ZS> confirmation of the user is not required?

    ZS> let me explain: I have a shopping cart program, and when a
    ZS> user completes his order, I want to issue an email to
    ZS> subscribe this user to the mailing list without having the
    ZS> mailing list sending the user an email to confirm.  On the
    ZS> same hand, I do not want to disable the functionality of
    ZS> confirmation if a user tries to subscribe to the mailing list.

    ZS> I have worked in the past with a mail list program, where
    ZS> emails with a [password] in the subject area, would be
    ZS> verified and if correct (pas for admin) then this email is
    ZS> treated as coming from the admin, and hence the user is
    ZS> registered without requiring confirmation email.

    ZS> Any ideas?

I'd do this by adding a little Python script that calls
ApprovedAddMember directly.  You could probably do this as a little
bin/withlist script.

-Barry

From noreply at sourceforge.net  Tue Dec 24 16:32:43 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 24 19:32:55 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-645513 ] qmail VERP-enabled delivery handler
Message-ID: <E18QzTX-0000Sn-00@sc8-sf-web4.sourceforge.net>

Patches item #645513, was opened at 2002-11-28 18:58
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103

Category: mail delivery
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Colin Palmer (tzs)
Assigned to: Nobody/Anonymous (nobody)
Summary: qmail VERP-enabled delivery handler

Initial Comment:
This is based on Peter D. Gray's popen-avoiding
Sendmail.py module, tweaked so it can use qmail-inject
instead of sendmail and ask qmail to do VERP when the
message is delivered, which is much faster than getting
Mailman to do it at message injection time.

You'll need the following in mm_cfg.py:
DELIVERY_MODULE = 'Qmail'
SENDMAIL_CMD = '/var/qmail/bin/qmail-inject'
DO_QMAIL_VERP = 1


----------------------------------------------------------------------

Comment By: Ed Lau (edlau)
Date: 2002-12-24 16:32

Message:
Logged In: YES 
user_id=675094

Running as listed except DO_QMAIL_VERP = 0, messages don't
appear to have the footer tacked on at the bottom. 
Everything else (header-wise) seems there.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103

From fil at rezo.net  Wed Dec 25 22:17:32 2002
From: fil at rezo.net (Fil)
Date: Wed Dec 25 16:17:42 2002
Subject: [Mailman-Developers] ugly traceback
In-Reply-To: <15880.33516.699160.414444@gargle.gargle.HOWL>
References: <20021224111103.GA22978@rezo.net>
	<15880.33516.699160.414444@gargle.gargle.HOWL>
Message-ID: <20021225211732.GB26981@rezo.net>

> I've fixed the French catalog and submitted a bug report on gettext.py
> for the Python project (I don't have time to fix that now).

Great! It works. I have another one now (current cvs), when doing
list_members, it fails on three lists with:

Traceback (most recent call last):
  File "/home/mailman/bin/list_members", line 232, in ?
    main()
  File "/home/mailman/bin/list_members", line 207, in main
    s = formataddr((name, addr)).encode(enc, 'replace')
UnicodeError: ASCII decoding error: ordinal not in range(128)


-- Fil


From fil at rezo.net  Wed Dec 25 22:21:54 2002
From: fil at rezo.net (Fil)
Date: Wed Dec 25 16:21:57 2002
Subject: [Mailman-Developers] ugly traceback
In-Reply-To: <20021225211732.GB26981@rezo.net>
References: <20021224111103.GA22978@rezo.net>
	<15880.33516.699160.414444@gargle.gargle.HOWL>
	<20021225211732.GB26981@rezo.net>
Message-ID: <20021225212154.GD26981@rezo.net>

> Great! It works. I have another one now (current cvs), when doing
> list_members, it fails on three lists with:
> 
> Traceback (most recent call last):
>   File "/home/mailman/bin/list_members", line 232, in ?
>     main()
>   File "/home/mailman/bin/list_members", line 207, in main
>     s = formataddr((name, addr)).encode(enc, 'replace')
> UnicodeError: ASCII decoding error: ordinal not in range(128)

It comes from an address that is registered as <b?a_xxxxxx@xxxxxx.com> ; it
seems that Mailman hasn't anticipated that an accent would creep in  ;-)

-- Fil


From marilyn at deliberate.com  Wed Dec 25 23:12:40 2002
From: marilyn at deliberate.com (Marilyn Davis)
Date: Thu Dec 26 02:13:04 2002
Subject: [Mailman-Developers] Patching 2.0.13 for eVote
In-Reply-To: <15876.63834.754936.695628@gargle.gargle.HOWL>
Message-ID: <Pine.LNX.4.10.10212252251550.7379-100000@rosa.deliberate.com>

Thank you Peter and Barry.  Patching seems to be under control now.

What a great facility!  It encouraged me to be more invasive into
mailman, and wax elegant in the code, since it keeps track of
everything for me.

One thing though.  When I worked on mailman, I worked on it in the
$prefix directory, not in the directory where we "make install".  But I
did alter common.c and mail-wrapper.c in the src directory, back in
the installation tree.  So I moved all these changes into the cvs
directory structure (by hand) and created my patch.

The patch will be part of the eVote distribution.  In eVote's
installation, Mailman's installation directory (mailman) gets copied
recursively into a mailman-eVote directory and I patch it and "make
install" in that directory.

Also, I created some new files in the mailman directory structure that
didn't seem to go into the patch (some new templates and an
bin/eVote_queries.py for eVote to pump for answers).  So I copied
these into the eVote directory tree and they get copied into
mailman-eVote during eVote's installation process.

My process seems a little scattered and I can't think of anyway to
improve it.  If you have the patience to follow any of this and have a
suggestion, I'd love it.

Thank you for any thoughts.

Marilyn

p.s.  Congratulations on your release candidate release, Barry.  I'm
so impressed with this whole operation.



From noreply at sourceforge.net  Wed Dec 25 23:17:04 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu Dec 26 02:17:08 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-658598 ] email obsuring eats up following text
Message-ID: <E18RSGO-0006Ew-00@sc8-sf-web3.sourceforge.net>

Patches item #658598, was opened at 2002-12-26 07:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=658598&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: email obsuring eats up following text

Initial Comment:
Obscure email address within message body was
introduced but it eats up the following text because
the calculation of next position is based on modified
(@ to _at_) text length.

e.g    a@b blah blar will become
<a href="...listinfo">a_at_b</a>ah blar

this quick patch fix this to

<a href="...listinfo">a_at_b</a> blah blar


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=658598&group_id=103

From noreply at sourceforge.net  Wed Dec 25 23:19:01 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu Dec 26 02:19:09 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-658598 ] email obsuring eats up following text
Message-ID: <E18RSIH-0006Gt-00@sc8-sf-web3.sourceforge.net>

Patches item #658598, was opened at 2002-12-26 07:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=658598&group_id=103

Category: Pipermail
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: email obsuring eats up following text

Initial Comment:
Obscure email address within message body was
introduced but it eats up the following text because
the calculation of next position is based on modified
(@ to _at_) text length.

e.g    a@b blah blar will become
<a href="...listinfo">a_at_b</a>ah blar

this quick patch fix this to

<a href="...listinfo">a_at_b</a> blah blar


----------------------------------------------------------------------

>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-26 07:19

Message:
Logged In: YES 
user_id=67709

Mmm... Attachment not uploaded. SF Bug?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=658598&group_id=103

From barry at python.org  Thu Dec 26 10:01:52 2002
From: barry at python.org (Barry A. Warsaw)
Date: Thu Dec 26 10:02:26 2002
Subject: [Mailman-Developers] Patching 2.0.13 for eVote
References: <15876.63834.754936.695628@gargle.gargle.HOWL>
	<Pine.LNX.4.10.10212252251550.7379-100000@rosa.deliberate.com>
Message-ID: <15883.6624.350183.377762@gargle.gargle.HOWL>


>>>>> "MD" == Marilyn Davis <marilyn@deliberate.com> writes:

    MD> One thing though.  When I worked on mailman, I worked on it in
    MD> the $prefix directory, not in the directory where we "make
    MD> install".  But I did alter common.c and mail-wrapper.c in the
    MD> src directory, back in the installation tree.  So I moved all
    MD> these changes into the cvs directory structure (by hand) and
    MD> created my patch.

    MD> The patch will be part of the eVote distribution.  In eVote's
    MD> installation, Mailman's installation directory (mailman) gets
    MD> copied recursively into a mailman-eVote directory and I patch
    MD> it and "make install" in that directory.

You should try to make all your changes in the checkout directory
(i.e. the ones with the CVS in them), because that will definitely
make your life easier in the long run.  It'll make it easier for you
to keep in sync with future Mailman fixes.  You'll just do a "cvs
update" and then you might have to resolve any conflict that may
result, but you shouldn't lose any of your work.  I often maintain
several checkouts as I vette other people's patches or work on fixes,
etc.

    MD> Also, I created some new files in the mailman directory
    MD> structure that didn't seem to go into the patch (some new
    MD> templates and an bin/eVote_queries.py for eVote to pump for
    MD> answers).  So I copied these into the eVote directory tree and
    MD> they get copied into mailman-eVote during eVote's installation
    MD> process.

Add -N to your diff command.  "man diff" (which cvs diff mimic) on
Linux says:

       -N
       --new-file
              In directory comparison, if a file is found in only
              one directory, treat it as present but empty in the
              other directory.

    MD> My process seems a little scattered and I can't think of
    MD> anyway to improve it.  If you have the patience to follow any
    MD> of this and have a suggestion, I'd love it.

See above.

    MD> Thank you for any thoughts.

    MD> Marilyn

    MD> p.s.  Congratulations on your release candidate release,
    MD> Barry.  I'm so impressed with this whole operation.

Thank you!
-Barry

From noreply at sourceforge.net  Thu Dec 26 09:24:39 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Thu Dec 26 12:24:45 2002
Subject: [Mailman-Developers] 
 [ mailman-Patches-658598 ] email obsuring eats up following text
Message-ID: <E18RbkN-0003oP-00@sc8-sf-web1.sourceforge.net>

Patches item #658598, was opened at 2002-12-26 02:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=658598&group_id=103

Category: Pipermail
Group: Mailman 2.1
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: email obsuring eats up following text

Initial Comment:
Obscure email address within message body was
introduced but it eats up the following text because
the calculation of next position is based on modified
(@ to _at_) text length.

e.g    a@b blah blar will become
<a href="...listinfo">a_at_b</a>ah blar

this quick patch fix this to

<a href="...listinfo">a_at_b</a> blah blar


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-26 12:24

Message:
Logged In: YES 
user_id=12800

Thanks!

----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2002-12-26 02:19

Message:
Logged In: YES 
user_id=67709

Mmm... Attachment not uploaded. SF Bug?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=658598&group_id=103

From marilyn at deliberate.com  Thu Dec 26 10:06:35 2002
From: marilyn at deliberate.com (Marilyn Davis)
Date: Thu Dec 26 13:06:40 2002
Subject: [Mailman-Developers] Patching 2.0.13 for eVote
In-Reply-To: <15883.6624.350183.377762@gargle.gargle.HOWL>
Message-ID: <Pine.LNX.4.10.10212260955500.7379-100000@rosa.deliberate.com>


Thank you again Barry.  It's so valuable to get these answers.

Do I understand right?

> You should try to make all your changes in the checkout directory
> (i.e. the ones with the CVS in them), because that will definitely
> make your life easier in the long run.  It'll make it easier for you

To do this, during installation, I'd make . (current directory) be my
$prefix for testing?

I'm taking a vacation soon but I expect to release my patch beta around
Jan 10.  It's not a deadline but a prediction.

Marilyn



From marilyn at deliberate.com  Thu Dec 26 10:30:46 2002
From: marilyn at deliberate.com (Marilyn Davis)
Date: Thu Dec 26 13:30:50 2002
Subject: [Mailman-Developers] Patching 2.0.13 for eVote
In-Reply-To: <15883.6624.350183.377762@gargle.gargle.HOWL>
Message-ID: <Pine.LNX.4.10.10212261026290.7379-100000@rosa.deliberate.com>


I'm messing up somehow.  I give this command:

[root@Xoko mailman]# cvs diff -N -u > /tmp/eVote-patch.txt

But my patch starts like:

? bin/eVote_queries.py
? templates/eVote.txt
? templates/eVotePetition.txt

and those files aren't in there.

What am I missing?

Marilyn


From pioppo at ferrara.linux.it  Fri Dec 27 00:49:31 2002
From: pioppo at ferrara.linux.it (Simone Piunno)
Date: Thu Dec 26 18:49:58 2002
Subject: [Mailman-Developers] Patching 2.0.13 for eVote
In-Reply-To: <Pine.LNX.4.10.10212261026290.7379-100000@rosa.deliberate.com>
References: <15883.6624.350183.377762@gargle.gargle.HOWL>
	<Pine.LNX.4.10.10212261026290.7379-100000@rosa.deliberate.com>
Message-ID: <20021226234930.GC2592@ferrara.linux.it>

On Thu, Dec 26, 2002 at 10:30:46AM -0800, Marilyn Davis wrote:

> I'm messing up somehow.  I give this command:
> 
> [root@Xoko mailman]# cvs diff -N -u > /tmp/eVote-patch.txt
> 
> But my patch starts like:
> 
> ? bin/eVote_queries.py
> ? templates/eVote.txt
> ? templates/eVotePetition.txt
> 
> and those files aren't in there.

"cvs diff" only looks in checked-out + cvs-added files.
If you create brand new files (instead of changing existing ones)
cvs diff will ignore them.... unless you "cvs add newfile" before
diffing.

Therefore, you should:

1. cvs add any new file
2. cvs diff -N -u

info:/cvs for details.
-- 
Adde parvum parvo magnus acervus erit.
Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo

From marilyn at deliberate.com  Thu Dec 26 16:00:39 2002
From: marilyn at deliberate.com (Marilyn Davis)
Date: Thu Dec 26 19:00:45 2002
Subject: [Mailman-Developers] Patching 2.0.13 for eVote
In-Reply-To: <20021226234930.GC2592@ferrara.linux.it>
Message-ID: <Pine.LNX.4.10.10212261552450.7379-100000@rosa.deliberate.com>

Thank you.

I see.  I was afraid of that.  I don't have write-access to cvs at
sourceforge, so I can't do that.

I don't think I should add stuff at sourceforge because we want people
to evaluate eVote before we put it into the repository.

So, I'll put the new files in eVote's distribution and the
installation will copy them into the mailman tree.  It doesn't really
matter since the mailman/eVote patch isn't any good without eVote.
It'll be invisible to the installer anyway.

Thank you again.

Marilyn

On Fri, 27 Dec 2002, Simone Piunno wrote:

> On Thu, Dec 26, 2002 at 10:30:46AM -0800, Marilyn Davis wrote:
> 
> > I'm messing up somehow.  I give this command:
> > 
> > [root@Xoko mailman]# cvs diff -N -u > /tmp/eVote-patch.txt
> > 
> > But my patch starts like:
> > 
> > ? bin/eVote_queries.py
> > ? templates/eVote.txt
> > ? templates/eVotePetition.txt
> > 
> > and those files aren't in there.
> 
> "cvs diff" only looks in checked-out + cvs-added files.
> If you create brand new files (instead of changing existing ones)
> cvs diff will ignore them.... unless you "cvs add newfile" before
> diffing.
> 
> Therefore, you should:
> 
> 1. cvs add any new file
> 2. cvs diff -N -u
> 
> info:/cvs for details.
> -- 
> Adde parvum parvo magnus acervus erit.
> Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo
> 


From barry at python.org  Thu Dec 26 19:49:47 2002
From: barry at python.org (Barry A. Warsaw)
Date: Thu Dec 26 19:50:16 2002
Subject: [Mailman-Developers] Patching 2.0.13 for eVote
References: <20021226234930.GC2592@ferrara.linux.it>
	<Pine.LNX.4.10.10212261552450.7379-100000@rosa.deliberate.com>
Message-ID: <15883.41899.967411.145968@gargle.gargle.HOWL>


>>>>> "MD" == Marilyn Davis <marilyn@deliberate.com> writes:

    MD> I see.  I was afraid of that.  I don't have write-access to
    MD> cvs at sourceforge, so I can't do that.

Marilyn, another thing you might consider: create your own cvs
repository and "cvs import" the Mailman code base into it.  You'd use
"cvs import" to track our changes and then you'd be able to add your
own files and generate your own "cvs diff -N" patches.

http://www.cvshome.org/docs/manual/cvs_13.html#SEC104

HTH,
-Barry

From noreply at sourceforge.net  Thu Dec 26 22:23:56 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 27 01:24:01 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-658892 ] traceback EOF read where object expected
Message-ID: <E18RnuW-0006tr-00@sc8-sf-web1.sourceforge.net>

Bugs item #658892, was opened at 2002-12-27 14:23
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658892&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Ubaida Othman (sirdeath)
Assigned to: Nobody/Anonymous (nobody)
Summary: traceback EOF read where object expected

Initial Comment:

ive got loads of these errors ... any ideas ?

Dec 27 14:20:02 2002 (21760) Delivery exception: EOF
read where object expected
Dec 27 14:20:02 2002 (21760) Traceback (most recent
call last):
  File
"/home/ml/mailman/Mailman/Handlers/HandlerAPI.py", line
82, in do_pipeline
    func(mlist, msg, msgdata)
  File "/home/ml/mailman/Mailman/Handlers/Hold.py",
line 152, in process
    hold_for_approval(mlist, msg, msgdata, NonMemberPost)
  File "/home/ml/mailman/Mailman/Handlers/Hold.py",
line 218, in hold_for_approval
    mlist.HoldMessage(msg, reason, msgdata)
  File "/home/ml/mailman/Mailman/ListAdmin.py", line
145, in HoldMessage
    self.__opendb()
  File "/home/ml/mailman/Mailman/ListAdmin.py", line
69, in __opendb
    self.__db = marshal.load(fp)
EOFError: EOF read where object expected


im running mailman 2.0.13 and python Python 2.2.2 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658892&group_id=103

From marilyn at deliberate.com  Thu Dec 26 22:28:31 2002
From: marilyn at deliberate.com (Marilyn Davis)
Date: Fri Dec 27 01:28:36 2002
Subject: [Mailman-Developers] Patching 2.0.13 for eVote
In-Reply-To: <15883.41899.967411.145968@gargle.gargle.HOWL>
Message-ID: <Pine.LNX.4.10.10212262217170.7379-100000@rosa.deliberate.com>

Thank you Barry.  That's a good idea.

If I keep my own repository so that I can have new files in my patch,
would it make sense to add all eVote/Clerk's source files into the patch?  
I would alter mailman's "make install" to call eVote's "make install".

I see one snag, the Clerk expects a "clerk" login so I'd have to give
instructions for that.  

Is this the most reasonable approach?  Might such a big patch get put
on the mailman site?

eVote/Clerk is only tested on Linux.  I'm quite sure won't port easily
to BSD.  Will this be a problem here?

Marilyn


On Thu, 26 Dec 2002, Barry A. Warsaw wrote:

> 
> >>>>> "MD" == Marilyn Davis <marilyn@deliberate.com> writes:
> 
>     MD> I see.  I was afraid of that.  I don't have write-access to
>     MD> cvs at sourceforge, so I can't do that.
> 
> Marilyn, another thing you might consider: create your own cvs
> repository and "cvs import" the Mailman code base into it.  You'd use
> "cvs import" to track our changes and then you'd be able to add your
> own files and generate your own "cvs diff -N" patches.
> 
> http://www.cvshome.org/docs/manual/cvs_13.html#SEC104
> 
> HTH,
> -Barry
> 



From noreply at sourceforge.net  Thu Dec 26 23:07:13 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 27 02:07:38 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-658892 ] traceback EOF read where object expected
Message-ID: <E18RoaP-0007gS-00@sc8-sf-web1.sourceforge.net>

Bugs item #658892, was opened at 2002-12-27 01:23
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658892&group_id=103

Category: None
>Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Ubaida Othman (sirdeath)
Assigned to: Nobody/Anonymous (nobody)
Summary: traceback EOF read where object expected

Initial Comment:

ive got loads of these errors ... any ideas ?

Dec 27 14:20:02 2002 (21760) Delivery exception: EOF
read where object expected
Dec 27 14:20:02 2002 (21760) Traceback (most recent
call last):
  File
"/home/ml/mailman/Mailman/Handlers/HandlerAPI.py", line
82, in do_pipeline
    func(mlist, msg, msgdata)
  File "/home/ml/mailman/Mailman/Handlers/Hold.py",
line 152, in process
    hold_for_approval(mlist, msg, msgdata, NonMemberPost)
  File "/home/ml/mailman/Mailman/Handlers/Hold.py",
line 218, in hold_for_approval
    mlist.HoldMessage(msg, reason, msgdata)
  File "/home/ml/mailman/Mailman/ListAdmin.py", line
145, in HoldMessage
    self.__opendb()
  File "/home/ml/mailman/Mailman/ListAdmin.py", line
69, in __opendb
    self.__db = marshal.load(fp)
EOFError: EOF read where object expected


im running mailman 2.0.13 and python Python 2.2.2 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658892&group_id=103

From noreply at sourceforge.net  Fri Dec 27 05:54:33 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 27 08:54:42 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-656341 ] logging of pending request without email
Message-ID: <E18Ruwb-0001tY-00@sc8-sf-web1.sourceforge.net>

Bugs item #656341, was opened at 2002-12-19 15:45
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656341&group_id=103

Category: (un)subscribing
Group: 2.1 beta
Status: Closed
Resolution: Works For Me
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: logging of pending request without email

Initial Comment:
2.1b6:

Pending requests are still not logged with email
addresses for me.

Patch upcoming.

----------------------------------------------------------------------

>Comment By: Jost Krieger (jkrieger)
Date: 2002-12-27 13:54

Message:
Logged In: YES 
user_id=45554

My problem is I get the following log line
Nov 27 11:49:04 2002 (15650) win-security: pending Sven
Kozma  134.147.156.3
which contains everything *but* the email address
(for a mail subscription).

I put the patch into the wrong place (patches list)..
II've appended it again.

Jost

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 04:23

Message:
Logged In: YES 
user_id=12800

I don't see a patch, but it definitely works for me,
attempting to subscribe either via the web or via email. 
Are you sure you see nothing in logs/subscribe?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656341&group_id=103

From noreply at sourceforge.net  Fri Dec 27 06:10:17 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 27 09:10:23 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-659011 ] add_members -c publishes member list
Message-ID: <E18RvBp-0005nu-00@sc8-sf-web4.sourceforge.net>

Bugs item #659011, was opened at 2002-12-27 14:10
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659011&group_id=103

Category: command line scripts
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: add_members -c publishes member list

Initial Comment:
add_members -c uses Message.UserNotification
for the "Big changes" message. This puts all
recipients into the "To:" field, which has already lead
to a privacy complaint at our site.
Of course it's also a Really Bad Idea with large lists.

Jost

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659011&group_id=103

From noreply at sourceforge.net  Fri Dec 27 06:25:02 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 27 09:25:06 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-659014 ] decoration problems with German lists
Message-ID: <E18RvQ6-0000zm-00@sc8-sf-web2.sourceforge.net>

Bugs item #659014, was opened at 2002-12-27 14:25
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659014&group_id=103

Category: mail delivery
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: decoration problems with German lists

Initial Comment:
1. German is one of the languages where the mapping
to a acharacter set is currently ambiguous:
If you want a Euro sign, you have to use iso-8859-15,
most people still have iso-8859-1 and some have
iso-8859-2 (which also contains all German glyphs).
2. People hat getting there mails in three text/plain parts
(partly due to the deficiencies of their mail readers).
3. List owners tend to put plain ASCII into their
header and
footer files, but this doesn't help, unfortunately, as
Mailman
still thinks it *must* be iso-8859-1.
4. MIME RFCs recommend taking the lowest compatible
charset. This sometimes leads to Mailman messages
consisting of three ASCII parts.

One longtime solution would be to upgrade everything to
Unicode and downgrade it later on as far as possible.
This sounds expensive, though.
Another, cheaper possibility might be to attach a
character set to haeders and footers.

Jost

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659014&group_id=103

From noreply at sourceforge.net  Fri Dec 27 06:42:27 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 27 09:42:30 2002
Subject: [Mailman-Developers] [ mailman-Patches-659021 ] Log open requests
	daily
Message-ID: <E18Rvgx-0004QT-00@sc8-sf-web3.sourceforge.net>

Patches item #659021, was opened at 2002-12-27 14:42
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=659021&group_id=103

Category: list administration
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: Log open requests daily

Initial Comment:
For large installations, it helps if the site administrator
sees if a list slowly turns bad :-)

This patch logs the number of open requests from
checkdbs.

Jost

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=659021&group_id=103

From noreply at sourceforge.net  Fri Dec 27 07:42:48 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 27 10:42:56 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-656341 ] logging of pending request without email
Message-ID: <E18RwdM-0005tF-00@sc8-sf-web3.sourceforge.net>

Bugs item #656341, was opened at 2002-12-19 10:45
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656341&group_id=103

Category: (un)subscribing
Group: 2.1 beta
>Status: Open
Resolution: Works For Me
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: logging of pending request without email

Initial Comment:
2.1b6:

Pending requests are still not logged with email
addresses for me.

Patch upcoming.

----------------------------------------------------------------------

Comment By: Jost Krieger (jkrieger)
Date: 2002-12-27 08:54

Message:
Logged In: YES 
user_id=45554

My problem is I get the following log line
Nov 27 11:49:04 2002 (15650) win-security: pending Sven
Kozma  134.147.156.3
which contains everything *but* the email address
(for a mail subscription).

I put the patch into the wrong place (patches list)..
II've appended it again.

Jost

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 23:23

Message:
Logged In: YES 
user_id=12800

I don't see a patch, but it definitely works for me,
attempting to subscribe either via the web or via email. 
Are you sure you see nothing in logs/subscribe?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656341&group_id=103

From noreply at sourceforge.net  Fri Dec 27 13:41:46 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Fri Dec 27 16:41:50 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-659157 ] wrong charset in discard notice
Message-ID: <E18S2Ek-0000YL-00@sc8-sf-web1.sourceforge.net>

Bugs item #659157, was opened at 2002-12-27 22:41
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659157&group_id=103

Category: None
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: wrong charset in discard notice

Initial Comment:
Hi,

attached a bugfix that sets the charset we use 
when auto-discarding.
(Moderate.py around line 150)


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659157&group_id=103

From Dale at Newfield.org  Sun Dec 29 10:42:04 2002
From: Dale at Newfield.org (Dale Newfield)
Date: Sun Dec 29 10:42:40 2002
Subject: [Mailman-Developers] adding to list without confirmation
In-Reply-To: <15880.53000.744950.710702@gargle.gargle.HOWL>
Message-ID: <Pine.OSX.4.44.0212291041080.18267-100000@core.newfield.org>

On Tue, 24 Dec 2002, Barry A. Warsaw wrote:
> I'd do this by adding a little Python script that calls
> ApprovedAddMember directly.  You could probably do this as a little
> bin/withlist script.

That assumes they're running on the same box...
...what would you suggest if they are not?

-Dale


From danny at terweij.nl  Sun Dec 29 23:12:30 2002
From: danny at terweij.nl (Danny Terweij)
Date: Sun Dec 29 17:12:51 2002
Subject: [Mailman-Developers] 
 Re: [Mailman-Users]  can't resolve "smrsh: mailman not available
 for sendmail programs" issue
References: <3E0F69B7.2000606@keithsteward.com>
Message-ID: <021501c2af87$61133650$1e00a8c0@onsnet.org>

|From: Keith Steward

|Arghhhh!!!

|After several attempts to get Mailman installed (including stable 2.0
final, and newest 2.1rc1), and hitting unresolvable "smrsh: |mailman not
available for sendmail programs" issues (despite trying numerous things),
i'm just about ready to give up.


|The /etc/aliases includes:
|## test1 mailing list
|test1:              "|/etc/smrsh/mailman post test1"
|test1-admin:        "|/etc/smrsh/mailman admin test1"
|test1-bounces:      "|/etc/smrsh/mailman bounces test1"
|test1-confirm:      "|/etc/smrsh/mailman confirm test1"
|test1-join:         "|/etc/smrsh/mailman join test1"
|test1-leave:        "|/etc/smrsh/mailman leave test1"
|test1-owner:        "|/etc/smrsh/mailman owner test1"
|test1-request:      "|/etc/smrsh/mailman request test1"
|test1-subscribe:    "|/etc/smrsh/mailman subscribe test1"
|test1-unsubscribe:  "|/etc/smrsh/mailman unsubscribe test1"

Keith, this above is not good!!!!
Must be like :

## poema-test mailing list mailman2.1
poema-test:              "|/usr/local/mailman/mail/mailman post poema-test"
poema-test-admin:        "|/usr/local/mailman/mail/mailman admin poema-test"
poema-test-bounces:      "|/usr/local/mailman/mail/mailman bounces
poema-test"
poema-test-confirm:      "|/usr/local/mailman/mail/mailman confirm
poema-test"
poema-test-join:         "|/usr/local/mailman/mail/mailman join poema-test"
poema-test-leave:        "|/usr/local/mailman/mail/mailman leave poema-test"
poema-test-owner:        "|/usr/local/mailman/mail/mailman owner poema-test"
poema-test-request:      "|/usr/local/mailman/mail/mailman request
poema-test"
poema-test-subscribe:    "|/usr/local/mailman/mail/mailman subscribe
poema-test"
poema-test-unsubscribe:  "|/usr/local/mailman/mail/mailman unsubscribe
poema-test"


Danny.






From jon at horde.org  Sun Dec 29 17:50:47 2002
From: jon at horde.org (Jon Parise)
Date: Sun Dec 29 17:50:53 2002
Subject: [Mailman-Developers] email package bug
Message-ID: <20021229225047.GA10776@csh.rit.edu>

One of my list members forwarded me the attached traceback.  I'm don't
have much clue with regard to the email package, though, so I'm
passing it along to the group.

The fact that the user who sent me the report is using the French
locale may be of note.

The attached traceback was generated when the user attempted to
unsubscribe from a mailing list to which they belonged.

-- 
Jon Parise (jon@horde.org) :: The Horde Project (http://horde.org/)
From jon at horde.org  Sun Dec 29 17:55:45 2002
From: jon at horde.org (Jon Parise)
Date: Sun Dec 29 17:55:49 2002
Subject: [Mailman-Developers] email package bug
In-Reply-To: <20021229225047.GA10776@csh.rit.edu>
References: <20021229225047.GA10776@csh.rit.edu>
Message-ID: <20021229225545.GB10776@csh.rit.edu>

On Sun, Dec 29, 2002 at 05:50:47PM -0500, Jon Parise wrote:

> The attached traceback was generated when the user attempted to
> unsubscribe from a mailing list to which they belonged.
 
It appears the attachment was stripped.  Here's an inlined plain text
version:

Traceback (most recent call last):
  File "/usr/local/mailman/scripts/driver", line 87, in run_main
    main()
  File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 118, in main
    unsubscription_confirm(mlist, doc, cookie)
  File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 392, in unsubscription_confirm
    op, addr = mlist.ProcessConfirmation(cookie)
  File "/usr/local/mailman/Mailman/MailList.py", line 1090, in ProcessConfirmation
    self.ApprovedDeleteMember(addr, whence=whence)
  File "/usr/local/mailman/Mailman/MailList.py", line 924, in ApprovedDeleteMember
    self.SendUnsubscribeAck(name)
  File "/usr/local/mailman/Mailman/Deliverer.py", line 78, in SendUnsubscribeAck
    Utils.wrap(self.goodbye_msg), self.getMemberLanguage(addr))
  File "/usr/local/mailman/Mailman/Message.py", line 203, in __init__
    self['Subject'] = Header(subject, charset, header_name='Subject')
  File "/usr/local/mailman/pythonlib/email/Header.py", line 164, in __init__
    self.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append
    ustr = unicode(s, incodec)
UnicodeError: ASCII decoding error: ordinal not in range(128)

-- 
Jon Parise (jon@horde.org) :: The Horde Project (http://horde.org/)

From ksteward at keithsteward.com  Sun Dec 29 13:31:35 2002
From: ksteward at keithsteward.com (Keith Steward)
Date: Sun Dec 29 21:18:42 2002
Subject: [Mailman-Developers] 
 can't resolve "smrsh: mailman not available for sendmail programs"
 issue
Message-ID: <3E0F69B7.2000606@keithsteward.com>


Arghhhh!!!  

After several attempts to get Mailman installed (including stable 2.0 
final, and newest 2.1rc1), and hitting unresolvable "smrsh: mailman not 
available for sendmail programs" issues (despite trying numerous 
things), i'm just about ready to give up.

I've been able to get Mailman to send  email to a new subscriber asking 
for confirmation, and the /var/log/maillog shows the response to the 
subscriber's confirmation email, but ALWAYS reporting the damn smrsh 
problem:
-------- /var/log/maillog segment ------------
sendmail[30785]: gBTEUjD30785: from=<ksteward@keithsteward.com>, 
size=2749, class=0, nrcpts=1, 
msgid=<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAebN2b6Pb1RGjtQJgjI3Ph8KAAAAQAAAAX+S3UuMa1xGjtQAFXc7j, 
proto=ESMTP, daemon=MTA, relay=steward-family.com [66.127.210.186]
smrsh: uid 8: attempt to use mailman request test1
sendmail[30786]: gBTEUjD30785: to="|/etc/smrsh/mailman request test1", 
ctladdr=<test1-request@justice4injuredworkers.org> (8/0), 
delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31743, dsn=5.0.0, 
stat=Service unavailable
sendmail[30786]: gBTEUjD30785: gBTEUjD30786: DSN: Service unavailable
sendmail[30786]: gBTEUjD30786: to=<ksteward@keithsteward.com>, 
delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=31843, 
relay=keithsteward.com. [66.127.210.186], dsn=2.0.0, stat=Sent 
(gBTERt820385 Message accepted for delivery)
----------- end segment ---------------

*System information:*
RedHat 7.2, Sendmail 8.11.6, Python-2.2.2
The /etc/aliases includes:
## test1 mailing list
test1:              "|/etc/smrsh/mailman post test1"
test1-admin:        "|/etc/smrsh/mailman admin test1"
test1-bounces:      "|/etc/smrsh/mailman bounces test1"
test1-confirm:      "|/etc/smrsh/mailman confirm test1"
test1-join:         "|/etc/smrsh/mailman join test1"
test1-leave:        "|/etc/smrsh/mailman leave test1"
test1-owner:        "|/etc/smrsh/mailman owner test1"
test1-request:      "|/etc/smrsh/mailman request test1"
test1-subscribe:    "|/etc/smrsh/mailman subscribe test1"
test1-unsubscribe:  "|/etc/smrsh/mailman unsubscribe test1"
Sendmail can send and receive successfully from a regular (non-Mailman) 
account on the machine running Mailman.
newaliases was run after the above aliases were added.
/etc/smrsh contains:
 lrwxrwxrwx    1 root     root           31 Dec 29 05:38 mailman -> 
/usr/local/mailman/mail/mailman
The permissions on the /usr/local/mailman/mail/mailman wrapper are:
 -rwxr-sr-x    1 mailman  mailman     39593 Dec 29 05:16 mailman


*Things i've tried:*

   1. ./configure --with-mail-gid=mail
   2. path to mailman wrapper in /etc/aliases as either
      '/usr/local/mailman/mail/mailman' or '/etc/smrsh/mailman'
   3. ln -s /etc/smrsh/mailman /usr/local/mailman/mail/mailman
   4. copying the compiled wrapper (/usr/local/mailman/mail/mailman)
      into /etc/smrsh
   5. changing uid/gid of the wrapper to mailman, to mail
   6. by-passing sendmail as a test as in: echo "confirm" |
      /etc/smrsh/mailman request test1, only to get mailman complaining
      about the gid
   7. by-passing root/sendmail as in: sudo -u mail "test" |
      /etc/smrsh/mailman request mailman, only to still get a gid complaint.
   8. restarting Sendmail daemon and Mailman's qrunner daemon after
      config changes.

By the way, i've done extensive reading of:

    * Mailman INSTALL
    * Mailman README.SENDMAIL
    * Mailman README.LINUX
    * Sendmails various READMES pertaining to SMRSH etc
    * the mailman-developers list archives

At this point, i'm out of ideas on what to try, except to abandon 
Mailman and switch to something like Majordomo, etc.   And frankly i 
think i've run out of time.  I've spent several evenings on this 
already.  Getting any kind of mailing list up and running is more 
important than the bells and whistles that Mailman offers.

thanks.

-keith s.



From ksteward at keithsteward.com  Sun Dec 29 17:28:56 2002
From: ksteward at keithsteward.com (Keith Steward)
Date: Sun Dec 29 21:18:47 2002
Subject: [Mailman-Developers] 
 FW: [Mailman-Users]  can't resolve "smrsh: mailman not available
 for sendmail programs" issue
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAebN2b6Pb1RGjtQJgjI3Ph8KAAAAQAAAA/ea3UuMa1xGjtQAFXc7jfAEAAAAA@keithsteward.com>

Danny,

I had it that way (i.e. "|/usr/local/mailman/mail/mailman post test1" in
the /etc/aliases) before, and then tried the "|/etc/smrsh/mailman post
test1", as indicated in the Mailman INSTALL doc.  Both gave the "smrsh:
mailman not available for sendmail" error.

thanks

 
Keith 


-----Original Message-----
From: Danny Terweij [mailto:danny@terweij.nl] 
Sent: Sunday, December 29, 2002 2:13 PM
To: Keith Steward; mailman-users@python.org;
mailman-developers@python.org
Subject: Re: [Mailman-Users] can't resolve "smrsh: mailman not available
for sendmail programs" issue


|From: Keith Steward

|Arghhhh!!!

|After several attempts to get Mailman installed (including stable 2.0
final, and newest 2.1rc1), and hitting unresolvable "smrsh: |mailman not
available for sendmail programs" issues (despite trying numerous
things), i'm just about ready to give up.


|The /etc/aliases includes:
|## test1 mailing list
|test1:              "|/etc/smrsh/mailman post test1"
|test1-admin:        "|/etc/smrsh/mailman admin test1"
|test1-bounces:      "|/etc/smrsh/mailman bounces test1"
|test1-confirm:      "|/etc/smrsh/mailman confirm test1"
|test1-join:         "|/etc/smrsh/mailman join test1"
|test1-leave:        "|/etc/smrsh/mailman leave test1"
|test1-owner:        "|/etc/smrsh/mailman owner test1"
|test1-request:      "|/etc/smrsh/mailman request test1"
|test1-subscribe:    "|/etc/smrsh/mailman subscribe test1"
|test1-unsubscribe:  "|/etc/smrsh/mailman unsubscribe test1"

Keith, this above is not good!!!!
Must be like :

## poema-test mailing list mailman2.1
poema-test:              "|/usr/local/mailman/mail/mailman post
poema-test"
poema-test-admin:        "|/usr/local/mailman/mail/mailman admin
poema-test"
poema-test-bounces:      "|/usr/local/mailman/mail/mailman bounces
poema-test"
poema-test-confirm:      "|/usr/local/mailman/mail/mailman confirm
poema-test"
poema-test-join:         "|/usr/local/mailman/mail/mailman join
poema-test"
poema-test-leave:        "|/usr/local/mailman/mail/mailman leave
poema-test"
poema-test-owner:        "|/usr/local/mailman/mail/mailman owner
poema-test"
poema-test-request:      "|/usr/local/mailman/mail/mailman request
poema-test"
poema-test-subscribe:    "|/usr/local/mailman/mail/mailman subscribe
poema-test"
poema-test-unsubscribe:  "|/usr/local/mailman/mail/mailman unsubscribe
poema-test"


Danny.





From barry at python.org  Sun Dec 29 21:20:12 2002
From: barry at python.org (Barry A. Warsaw)
Date: Sun Dec 29 21:20:41 2002
Subject: [Mailman-Developers] email package bug
References: <20021229225047.GA10776@csh.rit.edu>
	<20021229225545.GB10776@csh.rit.edu>
Message-ID: <15887.44380.624951.180599@gargle.gargle.HOWL>


Any possibility you can send me the message?
-Barry

From ksteward at keithsteward.com  Sun Dec 29 19:31:51 2002
From: ksteward at keithsteward.com (Keith Steward)
Date: Sun Dec 29 22:24:50 2002
Subject: [Mailman-Developers] 
 RE: [Mailman-Users]  can't resolve "smrsh: mailman not available
 for sendmail programs" issue
In-Reply-To: <106770000.1041211566@lerlaptop.lerctr.org>
Message-ID: <005801c2afb3$fe0459e0$3800a8c0@STEWARD>

Larry,

BINGO!  You hit the nail on the head !!! Problem solved!

Your comment prompted me to review the smrsh.c code within the sendmail
distribution.  When CMDDIR is not defined by the OS (I couldn't find in
in any system *.h files), then in smrsh.c it defaults to
/usr/adm/sm.bin/ .  Even though RedHat7.2 already has an /etc/smrsh/
directory (including a link entry there for slocal), the Sendmail (at
least the 8.11.6 version I downloaded and installed) was not using that
directory.  Instead, it was looking for the default /usr/adm/sm.bin/.
The /etc/smrsh/ directory was a red herring!  Once I created the
/usr/adm/sm.bin, and chmod 755 (recommended by the smrsch/README within
Sendmail), and then set up the symbolic link in there:
    mailman -> /usr/local/mailman/mail/mailman
the problem disappeared.

Thanks!!!

-keith


-----Original Message-----
From: Larry Rosenman [mailto:ler@lerctr.org]
Sent: Sunday, December 29, 2002 5:26 PM
To: keith@bioinformaticstech.com
Subject: RE: [Mailman-Users] can't resolve "smrsh: mailman not available
for sendmail programs" issue




--On Sunday, December 29, 2002 17:20:22 -0800 Keith Steward
<ksteward@keithsteward.com> wrote:

> Larry,
>
> Yes, the /etc/smrsh/ directory contains a symbolic link to the mailman
> wrapper:  ie.
>   /etc/smrsh/mailman -> /usr/local/mailman/mail/mailman
are you SURE that your SMRSH is set to use /etc/smrsh as it's CMDDIR?

Also, did you try it with the /usr/local/mailman/mail/mailman aliases as
someone else pointed out?

LER

>
> Thanks.
>
>
> Keith
>
> --
> Keith L. Steward, Ph.D.    work: 408-957-7777 x300   cell:
408-250-5213
> Email: keith@BioinformaticsTech.com
> Web: http://www.BioinformaticsTech.com
> Pager: http://www.skytel.com/Paging/pageme.cgi?pin=8499479,1
>           or call 1-888-849-9479
> FAX:  408-226-3215 408-40 (call ahead for setup)
>
>
> -----Original Message-----
> From: Larry Rosenman [mailto:ler@lerctr.org]
> Sent: Sunday, December 29, 2002 2:08 PM
> To: Keith Steward; mailman-users@python.org;
> mailman-developers@python.org
> Subject: Re: [Mailman-Users] can't resolve "smrsh: mailman not
> available for sendmail programs" issue
>
>
> Did you put links to the $MAILMANHOME/mail/mailman program in the
> CMDDIR directory for your copy of SMRSH?
>
> LER
>
>
> --On Sunday, December 29, 2002 13:31:35 -0800 Keith Steward
> <ksteward@keithsteward.com> wrote:
>
>>
>> Arghhhh!!!
>>
>> After several attempts to get Mailman installed (including stable 2.0
>> final, and newest 2.1rc1), and hitting unresolvable "smrsh: mailman
>> not available for sendmail programs" issues (despite trying numerous
>> things), i'm just about ready to give up. I've been able to get
>> Mailman to send  email to a new subscriber asking for confirmation,
>> and the /var/log/maillog shows the response to the subscriber's
>> confirmation email, but ALWAYS reporting the damn smrsh
>> problem:  -------- /var/log/maillog segment ------------
>>  sendmail[30785]: gBTEUjD30785: from=<ksteward@keithsteward.com>,
>> size=2749, class=0, nrcpts=1,
>> msgid=<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAebN2b6Pb1RGjtQJ
>> g
>> jI3
>> Ph8KAAAAQAAAAX+S3UuMa1xGjtQAFXc7j, proto=ESMTP, daemon=MTA,
>> relay=steward-family.com [66.127.210.186]  smrsh: uid 8: attempt to
>> use mailman request test1
>>  sendmail[30786]: gBTEUjD30785: to="|/etc/smrsh/mailman request
>> test1", ctladdr=<test1-request@justice4injuredworkers.org> (8/0),
>> delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31743, dsn=5.0.0,
>> stat=Service unavailable  sendmail[30786]: gBTEUjD30785:
>> gBTEUjD30786:
>
>> DSN: Service unavailable  sendmail[30786]: gBTEUjD30786:
>> to=<ksteward@keithsteward.com>, delay=00:00:01, xdelay=00:00:01,
>> mailer=esmtp, pri=31843, relay=keithsteward.com. [66.127.210.186],
>> dsn=2.0.0, stat=Sent (gBTERt820385 Message accepted for delivery)
>>  ----------- end segment ---------------
>>
>> System information:
>>  RedHat 7.2, Sendmail 8.11.6, Python-2.2.2
>>  The /etc/aliases includes:
>>  ## test1 mailing list
>>  test1:              "|/etc/smrsh/mailman post test1"
>>  test1-admin:        "|/etc/smrsh/mailman admin test1"
>>  test1-bounces:      "|/etc/smrsh/mailman bounces test1"
>>  test1-confirm:      "|/etc/smrsh/mailman confirm test1"
>>  test1-join:         "|/etc/smrsh/mailman join test1"
>>  test1-leave:        "|/etc/smrsh/mailman leave test1"
>>  test1-owner:        "|/etc/smrsh/mailman owner test1"
>>  test1-request:      "|/etc/smrsh/mailman request test1"
>>  test1-subscribe:    "|/etc/smrsh/mailman subscribe test1"
>>  test1-unsubscribe:  "|/etc/smrsh/mailman unsubscribe test1" 
>> Sendmail
>
>> can send and receive successfully from a regular (non-Mailman)
>> account
>
>> on the machine running Mailman.  newaliases was run after the above
>> aliases were added.  /etc/smrsh contains:
>>   lrwxrwxrwx    1 root     root           31 Dec 29 05:38 mailman ->
>> /usr/local/mailman/mail/mailman  The permissions on the
>> /usr/local/mailman/mail/mailman wrapper are:   -rwxr-sr-x    1
mailman
>> mailman     39593 Dec 29 05:16 mailman
>>
>> Things i've tried:
>>
>>   * ./configure --with-mail-gid=mail
>>   * path to mailman wrapper in /etc/aliases as either
>> '/usr/local/mailman/mail/mailman' or '/etc/smrsh/mailman'
>>   * ln -s /etc/smrsh/mailman /usr/local/mailman/mail/mailman
>>   * copying the compiled wrapper (/usr/local/mailman/mail/mailman)
> into
>> /etc/smrsh    * changing uid/gid of the wrapper to mailman, to mail
>>   * by-passing sendmail as a test as in: echo "confirm" |
>> /etc/smrsh/mailman request test1, only to get mailman complaining
> about
>> the gid    * by-passing root/sendmail as in: sudo -u mail "test" |
>> /etc/smrsh/mailman request mailman, only to still get a gid
>> complaint.
>> * restarting Sendmail daemon and Mailman's qrunner daemon after
config
>
>> changes. By the way, i've done extensive reading of:
>>
>>   * Mailman INSTALL
>>   * Mailman README.SENDMAIL
>>   * Mailman README.LINUX
>>   * Sendmails various READMES pertaining to SMRSH etc
>>   * the mailman-developers list archives
>> At this point, i'm out of ideas on what to try, except to abandon
> Mailman
>> and switch to something like Majordomo, etc.   And frankly i think
> i've
>> run out of time.  I've spent several evenings on this already.
>> Getting any kind of mailing list up and running is more important
>> than
>
>> the bells and whistles that Mailman offers. thanks.
>>
>> -keith s.
>>
>>
>>
>
>
>
> --
> Larry Rosenman                     http://www.lerctr.org/~ler
> Phone: +1 972-414-9812                 E-Mail: ler@lerctr.org
> US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
>



--
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 972-414-9812                 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749



From jon at horde.org  Sun Dec 29 22:51:52 2002
From: jon at horde.org (Jon Parise)
Date: Sun Dec 29 22:51:58 2002
Subject: [Mailman-Developers] email package bug
In-Reply-To: <15887.44380.624951.180599@gargle.gargle.HOWL>
References: <20021229225047.GA10776@csh.rit.edu>
	<20021229225545.GB10776@csh.rit.edu>
	<15887.44380.624951.180599@gargle.gargle.HOWL>
Message-ID: <20021230035152.GA17317@csh.rit.edu>

On Sun, Dec 29, 2002 at 09:20:12PM -0500, Barry A. Warsaw wrote:

> Any possibility you can send me the message?

It looks like it's in the process of building the message when it dies
(at least, that's my reading of the trace).  How would I go about
getting you the message contents?

-- 
Jon Parise (jon@horde.org) :: The Horde Project (http://horde.org/)

From ksteward at keithsteward.com  Sun Dec 29 20:56:43 2002
From: ksteward at keithsteward.com (Keith Steward)
Date: Sun Dec 29 23:49:27 2002
Subject: [Mailman-Developers] RE: Mailman-Developers Digest, Vol 164, Issue 48
In-Reply-To: <E18Sqzd-0000pB-02@mail.python.org>
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAebN2b6Pb1RGjtQJgjI3Ph8KAAAAQAAAApOi3UuMa1xGjtQAFXc7jfAEAAAAA@keithsteward.com>



 
Keith 

--
Keith L. Steward, Ph.D.    work: 408-957-7777 x300   cell: 408-250-5213
Email: keith@BioinformaticsTech.com
Web: http://www.BioinformaticsTech.com
Pager: http://www.skytel.com/Paging/pageme.cgi?pin=8499479,1
          or call 1-888-849-9479
FAX:  408-226-3215 408-40 (call ahead for setup)


-----Original Message-----
From: mailman-developers-bounces@python.org
[mailto:mailman-developers-bounces@python.org] On Behalf Of
mailman-developers-request@python.org
Sent: Sunday, December 29, 2002 7:54 PM
To: mailman-developers@python.org
Subject: Mailman-Developers Digest, Vol 164, Issue 48


Send Mailman-Developers mailing list submissions to
	mailman-developers@python.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://mail.python.org/mailman/listinfo/mailman-developers
or, via email, send a message with subject or body 'help' to
	mailman-developers-request@python.org

You can reach the person managing the list at
	mailman-developers-owner@python.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Mailman-Developers digest..."


Today's Topics:

   1. 
       Re: [Mailman-Users]  can't resolve "smrsh: mailman not available
       for sendmail programs" issue (Danny Terweij)
   2. email package bug (Jon Parise)
   3. Re: email package bug (Jon Parise)
   4. 
       can't resolve "smrsh: mailman not available for sendmail
programs"
       issue (Keith Steward)
   5. 
       FW: [Mailman-Users]  can't resolve "smrsh: mailman not available
       for sendmail programs" issue (Keith Steward)
   6. Re: email package bug (Barry A. Warsaw)
   7. 
       RE: [Mailman-Users]  can't resolve "smrsh: mailman not available
       for sendmail programs" issue (Keith Steward)
   8. Re: email package bug (Jon Parise)


----------------------------------------------------------------------

Date: Sun, 29 Dec 2002 23:12:30 +0100
From: "Danny Terweij" <danny@terweij.nl>
To: "Keith Steward" <ksteward@keithsteward.com>,
<mailman-users@python.org>,
   <mailman-developers@python.org>
Subject: [Mailman-Developers] 
 Re: [Mailman-Users]  can't resolve "smrsh: mailman not available  for
sendmail programs" issue
Message-ID: <021501c2af87$61133650$1e00a8c0@onsnet.org>
References: <3E0F69B7.2000606@keithsteward.com>
Content-Type: text/plain;
	charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: list
Message: 1

|From: Keith Steward

|Arghhhh!!!

|After several attempts to get Mailman installed (including stable 2.0
final, and newest 2.1rc1), and hitting unresolvable "smrsh: |mailman not
available for sendmail programs" issues (despite trying numerous
things), i'm just about ready to give up.


|The /etc/aliases includes:
|## test1 mailing list
|test1:              "|/etc/smrsh/mailman post test1"
|test1-admin:        "|/etc/smrsh/mailman admin test1"
|test1-bounces:      "|/etc/smrsh/mailman bounces test1"
|test1-confirm:      "|/etc/smrsh/mailman confirm test1"
|test1-join:         "|/etc/smrsh/mailman join test1"
|test1-leave:        "|/etc/smrsh/mailman leave test1"
|test1-owner:        "|/etc/smrsh/mailman owner test1"
|test1-request:      "|/etc/smrsh/mailman request test1"
|test1-subscribe:    "|/etc/smrsh/mailman subscribe test1"
|test1-unsubscribe:  "|/etc/smrsh/mailman unsubscribe test1"

Keith, this above is not good!!!!
Must be like :

## poema-test mailing list mailman2.1
poema-test:              "|/usr/local/mailman/mail/mailman post
poema-test"
poema-test-admin:        "|/usr/local/mailman/mail/mailman admin
poema-test"
poema-test-bounces:      "|/usr/local/mailman/mail/mailman bounces
poema-test"
poema-test-confirm:      "|/usr/local/mailman/mail/mailman confirm
poema-test"
poema-test-join:         "|/usr/local/mailman/mail/mailman join
poema-test"
poema-test-leave:        "|/usr/local/mailman/mail/mailman leave
poema-test"
poema-test-owner:        "|/usr/local/mailman/mail/mailman owner
poema-test"
poema-test-request:      "|/usr/local/mailman/mail/mailman request
poema-test"
poema-test-subscribe:    "|/usr/local/mailman/mail/mailman subscribe
poema-test"
poema-test-unsubscribe:  "|/usr/local/mailman/mail/mailman unsubscribe
poema-test"


Danny.






------------------------------

Date: Sun, 29 Dec 2002 17:50:47 -0500
From: Jon Parise <jon@horde.org>
To: mailman-developers@python.org
Subject: [Mailman-Developers] email package bug
Message-ID: <20021229225047.GA10776@csh.rit.edu>
Content-Type: multipart/mixed; boundary="6TrnltStXW4iwmi0"
MIME-Version: 1.0
Precedence: list
Message: 2


--6TrnltStXW4iwmi0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

One of my list members forwarded me the attached traceback.  I'm don't
have much clue with regard to the email package, though, so I'm passing
it along to the group.

The fact that the user who sent me the report is using the French locale
may be of note.

The attached traceback was generated when the user attempted to
unsubscribe from a mailing list to which they belonged.

-- 
Jon Parise (jon@horde.org) :: The Horde Project (http://horde.org/)

--6TrnltStXW4iwmi0--

------------------------------

Date: Sun, 29 Dec 2002 17:55:45 -0500
From: Jon Parise <jon@horde.org>
To: mailman-developers@python.org
Subject: Re: [Mailman-Developers] email package bug
Message-ID: <20021229225545.GB10776@csh.rit.edu>
In-Reply-To: <20021229225047.GA10776@csh.rit.edu>
References: <20021229225047.GA10776@csh.rit.edu>
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Precedence: list
Message: 3

On Sun, Dec 29, 2002 at 05:50:47PM -0500, Jon Parise wrote:

> The attached traceback was generated when the user attempted to 
> unsubscribe from a mailing list to which they belonged.
 
It appears the attachment was stripped.  Here's an inlined plain text
version:

Traceback (most recent call last):
  File "/usr/local/mailman/scripts/driver", line 87, in run_main
    main()
  File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 118, in main
    unsubscription_confirm(mlist, doc, cookie)
  File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 392, in
unsubscription_confirm
    op, addr = mlist.ProcessConfirmation(cookie)
  File "/usr/local/mailman/Mailman/MailList.py", line 1090, in
ProcessConfirmation
    self.ApprovedDeleteMember(addr, whence=whence)
  File "/usr/local/mailman/Mailman/MailList.py", line 924, in
ApprovedDeleteMember
    self.SendUnsubscribeAck(name)
  File "/usr/local/mailman/Mailman/Deliverer.py", line 78, in
SendUnsubscribeAck
    Utils.wrap(self.goodbye_msg), self.getMemberLanguage(addr))
  File "/usr/local/mailman/Mailman/Message.py", line 203, in __init__
    self['Subject'] = Header(subject, charset, header_name='Subject')
  File "/usr/local/mailman/pythonlib/email/Header.py", line 164, in
__init__
    self.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in
append
    ustr = unicode(s, incodec)
UnicodeError: ASCII decoding error: ordinal not in range(128)

-- 
Jon Parise (jon@horde.org) :: The Horde Project (http://horde.org/)

------------------------------

Date: Sun, 29 Dec 2002 13:31:35 -0800
From: Keith Steward <ksteward@keithsteward.com>
To: mailman-users@python.org, mailman-developers@python.org
Subject: [Mailman-Developers] 
 can't resolve "smrsh: mailman not available for sendmail programs"
issue
Message-ID: <3E0F69B7.2000606@keithsteward.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: list
Message: 4


Arghhhh!!!  

After several attempts to get Mailman installed (including stable 2.0 
final, and newest 2.1rc1), and hitting unresolvable "smrsh: mailman not 
available for sendmail programs" issues (despite trying numerous 
things), i'm just about ready to give up.

I've been able to get Mailman to send  email to a new subscriber asking 
for confirmation, and the /var/log/maillog shows the response to the 
subscriber's confirmation email, but ALWAYS reporting the damn smrsh 
problem:
-------- /var/log/maillog segment ------------
sendmail[30785]: gBTEUjD30785: from=<ksteward@keithsteward.com>, 
size=2749, class=0, nrcpts=1, 
msgid=<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAebN2b6Pb1RGjtQJgjI
3Ph8KAAAAQAAAAX+S3UuMa1xGjtQAFXc7j, 
proto=ESMTP, daemon=MTA, relay=steward-family.com [66.127.210.186]
smrsh: uid 8: attempt to use mailman request test1
sendmail[30786]: gBTEUjD30785: to="|/etc/smrsh/mailman request test1", 
ctladdr=<test1-request@justice4injuredworkers.org> (8/0), 
delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31743, dsn=5.0.0, 
stat=Service unavailable
sendmail[30786]: gBTEUjD30785: gBTEUjD30786: DSN: Service unavailable
sendmail[30786]: gBTEUjD30786: to=<ksteward@keithsteward.com>, 
delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=31843, 
relay=keithsteward.com. [66.127.210.186], dsn=2.0.0, stat=Sent 
(gBTERt820385 Message accepted for delivery)
----------- end segment ---------------

*System information:*
RedHat 7.2, Sendmail 8.11.6, Python-2.2.2
The /etc/aliases includes:
## test1 mailing list
test1:              "|/etc/smrsh/mailman post test1"
test1-admin:        "|/etc/smrsh/mailman admin test1"
test1-bounces:      "|/etc/smrsh/mailman bounces test1"
test1-confirm:      "|/etc/smrsh/mailman confirm test1"
test1-join:         "|/etc/smrsh/mailman join test1"
test1-leave:        "|/etc/smrsh/mailman leave test1"
test1-owner:        "|/etc/smrsh/mailman owner test1"
test1-request:      "|/etc/smrsh/mailman request test1"
test1-subscribe:    "|/etc/smrsh/mailman subscribe test1"
test1-unsubscribe:  "|/etc/smrsh/mailman unsubscribe test1" Sendmail can
send and receive successfully from a regular (non-Mailman) 
account on the machine running Mailman.
newaliases was run after the above aliases were added. /etc/smrsh
contains:
 lrwxrwxrwx    1 root     root           31 Dec 29 05:38 mailman -> 
/usr/local/mailman/mail/mailman
The permissions on the /usr/local/mailman/mail/mailman wrapper are:
 -rwxr-sr-x    1 mailman  mailman     39593 Dec 29 05:16 mailman


*Things i've tried:*

   1. ./configure --with-mail-gid=mail
   2. path to mailman wrapper in /etc/aliases as either
      '/usr/local/mailman/mail/mailman' or '/etc/smrsh/mailman'
   3. ln -s /etc/smrsh/mailman /usr/local/mailman/mail/mailman
   4. copying the compiled wrapper (/usr/local/mailman/mail/mailman)
      into /etc/smrsh
   5. changing uid/gid of the wrapper to mailman, to mail
   6. by-passing sendmail as a test as in: echo "confirm" |
      /etc/smrsh/mailman request test1, only to get mailman complaining
      about the gid
   7. by-passing root/sendmail as in: sudo -u mail "test" |
      /etc/smrsh/mailman request mailman, only to still get a gid
complaint.
   8. restarting Sendmail daemon and Mailman's qrunner daemon after
      config changes.

By the way, i've done extensive reading of:

    * Mailman INSTALL
    * Mailman README.SENDMAIL
    * Mailman README.LINUX
    * Sendmails various READMES pertaining to SMRSH etc
    * the mailman-developers list archives

At this point, i'm out of ideas on what to try, except to abandon 
Mailman and switch to something like Majordomo, etc.   And frankly i 
think i've run out of time.  I've spent several evenings on this 
already.  Getting any kind of mailing list up and running is more 
important than the bells and whistles that Mailman offers.

thanks.

-keith s.



------------------------------

Date: Sun, 29 Dec 2002 17:28:56 -0800
From: "Keith Steward" <ksteward@keithsteward.com>
To: <mailman-users@python.org>, <mailman-developers@python.org>
Subject: [Mailman-Developers] 
 FW: [Mailman-Users]  can't resolve "smrsh: mailman not available  for
sendmail programs" issue
Message-ID:
<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAebN2b6Pb1RGjtQJgjI3Ph8KA
AAAQAAAA/ea3UuMa1xGjtQAFXc7jfAEAAAAA@keithsteward.com>
Content-Type: text/plain;
	charset="Windows-1252"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: list
Reply-To: keith@bioinformaticstech.com
Message: 5

Danny,

I had it that way (i.e. "|/usr/local/mailman/mail/mailman post test1" in
the /etc/aliases) before, and then tried the "|/etc/smrsh/mailman post
test1", as indicated in the Mailman INSTALL doc.  Both gave the "smrsh:
mailman not available for sendmail" error.

thanks

 
Keith 


-----Original Message-----
From: Danny Terweij [mailto:danny@terweij.nl] 
Sent: Sunday, December 29, 2002 2:13 PM
To: Keith Steward; mailman-users@python.org;
mailman-developers@python.org
Subject: Re: [Mailman-Users] can't resolve "smrsh: mailman not available
for sendmail programs" issue


|From: Keith Steward

|Arghhhh!!!

|After several attempts to get Mailman installed (including stable 2.0
final, and newest 2.1rc1), and hitting unresolvable "smrsh: |mailman not
available for sendmail programs" issues (despite trying numerous
things), i'm just about ready to give up.


|The /etc/aliases includes:
|## test1 mailing list
|test1:              "|/etc/smrsh/mailman post test1"
|test1-admin:        "|/etc/smrsh/mailman admin test1"
|test1-bounces:      "|/etc/smrsh/mailman bounces test1"
|test1-confirm:      "|/etc/smrsh/mailman confirm test1"
|test1-join:         "|/etc/smrsh/mailman join test1"
|test1-leave:        "|/etc/smrsh/mailman leave test1"
|test1-owner:        "|/etc/smrsh/mailman owner test1"
|test1-request:      "|/etc/smrsh/mailman request test1"
|test1-subscribe:    "|/etc/smrsh/mailman subscribe test1"
|test1-unsubscribe:  "|/etc/smrsh/mailman unsubscribe test1"

Keith, this above is not good!!!!
Must be like :

## poema-test mailing list mailman2.1
poema-test:              "|/usr/local/mailman/mail/mailman post
poema-test"
poema-test-admin:        "|/usr/local/mailman/mail/mailman admin
poema-test"
poema-test-bounces:      "|/usr/local/mailman/mail/mailman bounces
poema-test"
poema-test-confirm:      "|/usr/local/mailman/mail/mailman confirm
poema-test"
poema-test-join:         "|/usr/local/mailman/mail/mailman join
poema-test"
poema-test-leave:        "|/usr/local/mailman/mail/mailman leave
poema-test"
poema-test-owner:        "|/usr/local/mailman/mail/mailman owner
poema-test"
poema-test-request:      "|/usr/local/mailman/mail/mailman request
poema-test"
poema-test-subscribe:    "|/usr/local/mailman/mail/mailman subscribe
poema-test"
poema-test-unsubscribe:  "|/usr/local/mailman/mail/mailman unsubscribe
poema-test"


Danny.





------------------------------

Date: Sun, 29 Dec 2002 21:20:12 -0500
From: barry@python.org (Barry A. Warsaw)
To: Jon Parise <jon@horde.org>
Cc: mailman-developers@python.org
Subject: Re: [Mailman-Developers] email package bug
Message-ID: <15887.44380.624951.180599@gargle.gargle.HOWL>
References: <20021229225047.GA10776@csh.rit.edu>
	<20021229225545.GB10776@csh.rit.edu>
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: list
Message: 6


Any possibility you can send me the message?
-Barry

------------------------------

Date: Sun, 29 Dec 2002 19:31:51 -0800
From: "Keith Steward" <ksteward@keithsteward.com>
To: "'Larry Rosenman'" <ler@lerctr.org>
Cc: mailman-developers@python.org
Cc: mailman-users@python.org
Subject: [Mailman-Developers] 
 RE: [Mailman-Users]  can't resolve "smrsh: mailman not available  for
sendmail programs" issue
Message-ID: <005801c2afb3$fe0459e0$3800a8c0@STEWARD>
In-Reply-To: <106770000.1041211566@lerlaptop.lerctr.org>
Content-Type: text/plain;
	charset="Windows-1252"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: list
Reply-To: keith@bioinformaticstech.com
Message: 7

Larry,

BINGO!  You hit the nail on the head !!! Problem solved!

Your comment prompted me to review the smrsh.c code within the sendmail
distribution.  When CMDDIR is not defined by the OS (I couldn't find in
in any system *.h files), then in smrsh.c it defaults to
/usr/adm/sm.bin/ .  Even though RedHat7.2 already has an /etc/smrsh/
directory (including a link entry there for slocal), the Sendmail (at
least the 8.11.6 version I downloaded and installed) was not using that
directory.  Instead, it was looking for the default /usr/adm/sm.bin/.
The /etc/smrsh/ directory was a red herring!  Once I created the
/usr/adm/sm.bin, and chmod 755 (recommended by the smrsch/README within
Sendmail), and then set up the symbolic link in there:
    mailman -> /usr/local/mailman/mail/mailman
the problem disappeared.

Thanks!!!

-keith


-----Original Message-----
From: Larry Rosenman [mailto:ler@lerctr.org]
Sent: Sunday, December 29, 2002 5:26 PM
To: keith@bioinformaticstech.com
Subject: RE: [Mailman-Users] can't resolve "smrsh: mailman not available
for sendmail programs" issue




--On Sunday, December 29, 2002 17:20:22 -0800 Keith Steward
<ksteward@keithsteward.com> wrote:

> Larry,
>
> Yes, the /etc/smrsh/ directory contains a symbolic link to the mailman
> wrapper:  ie.
>   /etc/smrsh/mailman -> /usr/local/mailman/mail/mailman
are you SURE that your SMRSH is set to use /etc/smrsh as it's CMDDIR?

Also, did you try it with the /usr/local/mailman/mail/mailman aliases as
someone else pointed out?

LER

>
> Thanks.
>
>
> Keith
>
> --
> Keith L. Steward, Ph.D.    work: 408-957-7777 x300   cell:
408-250-5213
> Email: keith@BioinformaticsTech.com
> Web: http://www.BioinformaticsTech.com
> Pager: http://www.skytel.com/Paging/pageme.cgi?pin=8499479,1
>           or call 1-888-849-9479
> FAX:  408-226-3215 408-40 (call ahead for setup)
>
>
> -----Original Message-----
> From: Larry Rosenman [mailto:ler@lerctr.org]
> Sent: Sunday, December 29, 2002 2:08 PM
> To: Keith Steward; mailman-users@python.org; 
> mailman-developers@python.org
> Subject: Re: [Mailman-Users] can't resolve "smrsh: mailman not 
> available for sendmail programs" issue
>
>
> Did you put links to the $MAILMANHOME/mail/mailman program in the 
> CMDDIR directory for your copy of SMRSH?
>
> LER
>
>
> --On Sunday, December 29, 2002 13:31:35 -0800 Keith Steward 
> <ksteward@keithsteward.com> wrote:
>
>>
>> Arghhhh!!!
>>
>> After several attempts to get Mailman installed (including stable 2.0

>> final, and newest 2.1rc1), and hitting unresolvable "smrsh: mailman 
>> not available for sendmail programs" issues (despite trying numerous 
>> things), i'm just about ready to give up. I've been able to get 
>> Mailman to send  email to a new subscriber asking for confirmation, 
>> and the /var/log/maillog shows the response to the subscriber's 
>> confirmation email, but ALWAYS reporting the damn smrsh
>> problem:  -------- /var/log/maillog segment ------------
>>  sendmail[30785]: gBTEUjD30785: from=<ksteward@keithsteward.com>, 
>> size=2749, class=0, nrcpts=1, 
>> msgid=<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAebN2b6Pb1RGjtQJ
>> g
>> jI3
>> Ph8KAAAAQAAAAX+S3UuMa1xGjtQAFXc7j, proto=ESMTP, daemon=MTA,
>> relay=steward-family.com [66.127.210.186]  smrsh: uid 8: attempt to 
>> use mailman request test1
>>  sendmail[30786]: gBTEUjD30785: to="|/etc/smrsh/mailman request 
>> test1", ctladdr=<test1-request@justice4injuredworkers.org> (8/0), 
>> delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31743, dsn=5.0.0, 
>> stat=Service unavailable  sendmail[30786]: gBTEUjD30785:
>> gBTEUjD30786:
>
>> DSN: Service unavailable  sendmail[30786]: gBTEUjD30786: 
>> to=<ksteward@keithsteward.com>, delay=00:00:01, xdelay=00:00:01, 
>> mailer=esmtp, pri=31843, relay=keithsteward.com. [66.127.210.186], 
>> dsn=2.0.0, stat=Sent (gBTERt820385 Message accepted for delivery)
>>  ----------- end segment ---------------
>>
>> System information:
>>  RedHat 7.2, Sendmail 8.11.6, Python-2.2.2
>>  The /etc/aliases includes:
>>  ## test1 mailing list
>>  test1:              "|/etc/smrsh/mailman post test1"
>>  test1-admin:        "|/etc/smrsh/mailman admin test1"
>>  test1-bounces:      "|/etc/smrsh/mailman bounces test1"
>>  test1-confirm:      "|/etc/smrsh/mailman confirm test1"
>>  test1-join:         "|/etc/smrsh/mailman join test1"
>>  test1-leave:        "|/etc/smrsh/mailman leave test1"
>>  test1-owner:        "|/etc/smrsh/mailman owner test1"
>>  test1-request:      "|/etc/smrsh/mailman request test1"
>>  test1-subscribe:    "|/etc/smrsh/mailman subscribe test1"
>>  test1-unsubscribe:  "|/etc/smrsh/mailman unsubscribe test1"
>> Sendmail
>
>> can send and receive successfully from a regular (non-Mailman) 
>> account
>
>> on the machine running Mailman.  newaliases was run after the above 
>> aliases were added.  /etc/smrsh contains:
>>   lrwxrwxrwx    1 root     root           31 Dec 29 05:38 mailman ->
>> /usr/local/mailman/mail/mailman  The permissions on the
>> /usr/local/mailman/mail/mailman wrapper are:   -rwxr-sr-x    1
mailman
>> mailman     39593 Dec 29 05:16 mailman
>>
>> Things i've tried:
>>
>>   * ./configure --with-mail-gid=mail
>>   * path to mailman wrapper in /etc/aliases as either 
>> '/usr/local/mailman/mail/mailman' or '/etc/smrsh/mailman'
>>   * ln -s /etc/smrsh/mailman /usr/local/mailman/mail/mailman
>>   * copying the compiled wrapper (/usr/local/mailman/mail/mailman)
> into
>> /etc/smrsh    * changing uid/gid of the wrapper to mailman, to mail
>>   * by-passing sendmail as a test as in: echo "confirm" | 
>> /etc/smrsh/mailman request test1, only to get mailman complaining
> about
>> the gid    * by-passing root/sendmail as in: sudo -u mail "test" |
>> /etc/smrsh/mailman request mailman, only to still get a gid 
>> complaint.
>> * restarting Sendmail daemon and Mailman's qrunner daemon after
config
>
>> changes. By the way, i've done extensive reading of:
>>
>>   * Mailman INSTALL
>>   * Mailman README.SENDMAIL
>>   * Mailman README.LINUX
>>   * Sendmails various READMES pertaining to SMRSH etc
>>   * the mailman-developers list archives
>> At this point, i'm out of ideas on what to try, except to abandon
> Mailman
>> and switch to something like Majordomo, etc.   And frankly i think
> i've
>> run out of time.  I've spent several evenings on this already. 
>> Getting any kind of mailing list up and running is more important 
>> than
>
>> the bells and whistles that Mailman offers. thanks.
>>
>> -keith s.
>>
>>
>>
>
>
>
> --
> Larry Rosenman                     http://www.lerctr.org/~ler
> Phone: +1 972-414-9812                 E-Mail: ler@lerctr.org
> US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
>



--
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 972-414-9812                 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749



------------------------------

Date: Sun, 29 Dec 2002 22:51:52 -0500
From: Jon Parise <jon@horde.org>
To: "Barry A. Warsaw" <barry@python.org>
Cc: mailman-developers@python.org
Subject: Re: [Mailman-Developers] email package bug
Message-ID: <20021230035152.GA17317@csh.rit.edu>
In-Reply-To: <15887.44380.624951.180599@gargle.gargle.HOWL>
References: <20021229225047.GA10776@csh.rit.edu>
	<20021229225545.GB10776@csh.rit.edu>
	<15887.44380.624951.180599@gargle.gargle.HOWL>
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Precedence: list
Message: 8

On Sun, Dec 29, 2002 at 09:20:12PM -0500, Barry A. Warsaw wrote:

> Any possibility you can send me the message?

It looks like it's in the process of building the message when it dies
(at least, that's my reading of the trace).  How would I go about
getting you the message contents?

-- 
Jon Parise (jon@horde.org) :: The Horde Project (http://horde.org/)

------------------------------

_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers


End of Mailman-Developers Digest, Vol 164, Issue 48
***************************************************


From barry at python.org  Mon Dec 30 09:01:57 2002
From: barry at python.org (Barry A. Warsaw)
Date: Mon Dec 30 09:02:42 2002
Subject: [Mailman-Developers] Checkins
Message-ID: <15888.20949.909028.482749@gargle.gargle.HOWL>


If anybody has any last minute checkins, get them in now.  I plan to
tag the tree and make the tarball for the release some time today.
It's possible I'll have some time during the next 8 hours or so, but
most likely it'll be when I'm done with work tonight (it's 9am my time
right now).

Cheers,
-Barry

From noreply at sourceforge.net  Mon Dec 30 19:20:58 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 30 22:20:55 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-658213 ] i18n problem on "Confirm subscription" 
Message-ID: <E18TCxe-00059E-00@sc8-sf-web4.sourceforge.net>

Bugs item #658213, was opened at 2002-12-24 09:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658213&group_id=103

Category: (un)subscribing
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Daniel Buchmann (avalon)
Assigned to: Nobody/Anonymous (nobody)
>Summary: i18n problem on "Confirm subscription" 

Initial Comment:
Mailman version: 2.1rc1

Wrong language is used for the heading, title and language selection 
box on the "Confirm subscription" page. The list language is used, not 
the language chosen by the subscribing user.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658213&group_id=103

From noreply at sourceforge.net  Mon Dec 30 19:29:10 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 30 22:29:04 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-659157 ] wrong charset in discard notice
Message-ID: <E18TD5a-0003Qq-00@sc8-sf-web2.sourceforge.net>

Bugs item #659157, was opened at 2002-12-27 16:41
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659157&group_id=103

Category: None
Group: 2.1 beta
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: wrong charset in discard notice

Initial Comment:
Hi,

attached a bugfix that sets the charset we use 
when auto-discarding.
(Moderate.py around line 150)


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-30 22:29

Message:
Logged In: YES 
user_id=12800

There was no attachment, but your clue was enough for me to
guess it. :)  Fixed!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659157&group_id=103

From noreply at sourceforge.net  Mon Dec 30 19:37:31 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 30 22:37:26 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-656341 ] logging of pending request without email
Message-ID: <E18TDDf-0003av-00@sc8-sf-web2.sourceforge.net>

Bugs item #656341, was opened at 2002-12-19 10:45
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656341&group_id=103

Category: (un)subscribing
Group: 2.1 beta
Status: Open
>Resolution: Out of Date
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: logging of pending request without email

Initial Comment:
2.1b6:

Pending requests are still not logged with email
addresses for me.

Patch upcoming.

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-30 22:37

Message:
Logged In: YES 
user_id=12800

Already fixed in 2.1rc1

----------------------------------------------------------------------

Comment By: Jost Krieger (jkrieger)
Date: 2002-12-27 08:54

Message:
Logged In: YES 
user_id=45554

My problem is I get the following log line
Nov 27 11:49:04 2002 (15650) win-security: pending Sven
Kozma  134.147.156.3
which contains everything *but* the email address
(for a mail subscription).

I put the patch into the wrong place (patches list)..
II've appended it again.

Jost

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 23:23

Message:
Logged In: YES 
user_id=12800

I don't see a patch, but it definitely works for me,
attempting to subscribe either via the web or via email. 
Are you sure you see nothing in logs/subscribe?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656341&group_id=103

From noreply at sourceforge.net  Mon Dec 30 19:38:08 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 30 22:38:02 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-656341 ] logging of pending request without email
Message-ID: <E18TDEG-00070d-00@sc8-sf-web1.sourceforge.net>

Bugs item #656341, was opened at 2002-12-19 10:45
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656341&group_id=103

Category: (un)subscribing
Group: 2.1 beta
>Status: Closed
Resolution: Out of Date
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: logging of pending request without email

Initial Comment:
2.1b6:

Pending requests are still not logged with email
addresses for me.

Patch upcoming.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-30 22:37

Message:
Logged In: YES 
user_id=12800

Already fixed in 2.1rc1

----------------------------------------------------------------------

Comment By: Jost Krieger (jkrieger)
Date: 2002-12-27 08:54

Message:
Logged In: YES 
user_id=45554

My problem is I get the following log line
Nov 27 11:49:04 2002 (15650) win-security: pending Sven
Kozma  134.147.156.3
which contains everything *but* the email address
(for a mail subscription).

I put the patch into the wrong place (patches list)..
II've appended it again.

Jost

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 23:23

Message:
Logged In: YES 
user_id=12800

I don't see a patch, but it definitely works for me,
attempting to subscribe either via the web or via email. 
Are you sure you see nothing in logs/subscribe?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=656341&group_id=103

From noreply at sourceforge.net  Mon Dec 30 20:43:21 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 30 23:43:15 2002
Subject: [Mailman-Developers] [ mailman-Bugs-214205 ] e-mail&amp;lt;-&amp;gt;
 usenet gateway Reply-To header (PR#303)
Message-ID: <E18TEFN-0000EM-00@sc8-sf-web1.sourceforge.net>

Bugs item #214205, was opened at 2000-09-11 16:25
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id=103

Category: nntp/news
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 7
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Barry A. Warsaw (bwarsaw)
>Summary: e-mail&amp;lt;-&amp;gt;usenet gateway Reply-To header (PR#303)

Initial Comment:
Jitterbug-Id: 303
Submitted-By: orion@tribble.dyndns.org
Date: Mon, 24 Jul 2000 18:54:02 -0400 (EDT)
Version: 2.0beta4
OS: Debian linux potato


I'm running a plain e-mail<->usenet gateway.
When someone replies to a usenet post through the list, his e-mail client sets
an In-Reply-To: header instead of a Reply-To: header. This causes newsreaders to
improperly thread messages.

I inserted the following bit into Mailman/Handlers/ToUsenet.py at around line
82:

    # if the message is a reply to a previous post, change the header so
    # that newsreaders can thread it properly
    if msg.getheader('in-reply-to'):
        msg.headers.append('References: %s\n' % msg.getheader('in-reply-to'))
        del msg['in-reply-to']

I'm happy to say that this solved the problem.
 
(before you laugh at me, take note that I never looked at python before.)



====================================================================
Audit trail:
None

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:07

Message:
Logged In: YES 
user_id=12800

Sigh.  Very doubtful I'll get to look at the threading
issues before MM2.1 final.  I'll address this again after
the release.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-23 18:38

Message:
Logged In: YES 
user_id=12800

Changing the group to 2.1 beta because I want to look at
threading issues for gated messages before 2.1 final is
released.

----------------------------------------------------------------------

Comment By: Giovanni Lopedote (giuans)
Date: 2002-05-01 08:34

Message:
Logged In: YES 
user_id=531451

What a coincidence! I had the same problem and I looked 
into the code, then modified it to work properly. The 
coincidence is that my patch is *identical* to yours. So, 
for sure it works :-)


----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2000-09-27 17:00

Message:
RFC 2076 says nothing about using In-Reply-To for news, so it might not be a bad idea to copy In-Reply-To to References when gating a message from mail to news.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2000-09-19 12:48

Message:
This sounds like the email client in question is broken.  Mine for example, correctly inserts References: headers and the news readers properly thread the messages.  I'm not inclined to cater to broken email or news clients.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id=103

From noreply at sourceforge.net  Mon Dec 30 20:43:20 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 30 23:43:24 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-659014 ] decoration problems with German lists
Message-ID: <E18TEFM-0000Du-00@sc8-sf-web1.sourceforge.net>

Bugs item #659014, was opened at 2002-12-27 09:25
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659014&group_id=103

Category: mail delivery
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: decoration problems with German lists

Initial Comment:
1. German is one of the languages where the mapping
to a acharacter set is currently ambiguous:
If you want a Euro sign, you have to use iso-8859-15,
most people still have iso-8859-1 and some have
iso-8859-2 (which also contains all German glyphs).
2. People hat getting there mails in three text/plain parts
(partly due to the deficiencies of their mail readers).
3. List owners tend to put plain ASCII into their
header and
footer files, but this doesn't help, unfortunately, as
Mailman
still thinks it *must* be iso-8859-1.
4. MIME RFCs recommend taking the lowest compatible
charset. This sometimes leads to Mailman messages
consisting of three ASCII parts.

One longtime solution would be to upgrade everything to
Unicode and downgrade it later on as far as possible.
This sounds expensive, though.
Another, cheaper possibility might be to attach a
character set to haeders and footers.

Jost

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659014&group_id=103

From noreply at sourceforge.net  Mon Dec 30 20:43:20 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 30 23:43:30 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-659011 ] add_members -c publishes member list
Message-ID: <E18TEFM-0000Dy-00@sc8-sf-web1.sourceforge.net>

Bugs item #659011, was opened at 2002-12-27 09:10
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659011&group_id=103

Category: command line scripts
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: add_members -c publishes member list

Initial Comment:
add_members -c uses Message.UserNotification
for the "Big changes" message. This puts all
recipients into the "To:" field, which has already lead
to a privacy complaint at our site.
Of course it's also a Really Bad Idea with large lists.

Jost

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659011&group_id=103

From noreply at sourceforge.net  Mon Dec 30 20:43:21 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 30 23:43:42 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-621689 ] Subscribe requests dropped from admin db
Message-ID: <E18TEFN-0000E7-00@sc8-sf-web1.sourceforge.net>

Bugs item #621689, was opened at 2002-10-10 23:10
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_id=103

Category: (un)subscribing
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 7
Submitted By: Mark Dadgar (mdadgar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Subscribe requests dropped from admin db

Initial Comment:
Occasionally, subscribe requests (via the web page) to a list that 
requires moderator approval for subscriptions never make it to the 
admin db for that list.  They are listed in the subscribe log file, but 
never show up on the admin db page.

Log file entries look like this:

Oct 10 18:43:43 2002 (31168) eventmasters: pending   
XXXXXX.swfla.rr.com

But the admin db page for the list shows no outstanding issues.

I have verified that there was an actual subscription request 
behind this log entry.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:06

Message:
Logged In: YES 
user_id=12800

I definitely need more information.  I've neve been able to
reproduce the problem.  Do you think it could be related to
the unofficial patches you've applied?

----------------------------------------------------------------------

Comment By: Mark Dadgar (mdadgar)
Date: 2002-12-06 02:29

Message:
Logged In: YES 
user_id=598228

Ok, I verified that it's still a problem under 2.1b5 with the htdig and 
indexing patches.

It's a real drag, too.  :(

Please let me know if you need more debug info.

----------------------------------------------------------------------

Comment By: Mark Dadgar (mdadgar)
Date: 2002-11-22 01:08

Message:
Logged In: YES 
user_id=598228

Unfortunately, it's still occurring under 2.1b4.  

I'll check it under 2.1b5 as soon as the patches for htdig integration are 
released, as I need those to implement.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-10-22 10:11

Message:
Logged In: YES 
user_id=12800

I'm going to defer this one until 2.1b4 goes out.  I've
fixed some related bugs in cvs, so hopefully this will be
fixed in the new version.

----------------------------------------------------------------------

Comment By: Mark Dadgar (mdadgar)
Date: 2002-10-20 13:14

Message:
Logged In: YES 
user_id=598228

Sorry - I'm running 2.1b3.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-10-20 11:48

Message:
Logged In: YES 
user_id=12800

What version of Mailman are you using.  It's import to know
the exact version, i.e. 2.1beta3, or if you're running from
cvs.  A lot of these problems have been fixed in cvs, which
will soon be released as 2.1 beta 4.

----------------------------------------------------------------------

Comment By: Mark Dadgar (mdadgar)
Date: 2002-10-11 00:29

Message:
Logged In: YES 
user_id=598228

I just verified, by cat'ing pending.pck, that the appropriate changes 
seem to be in there.  But the web interface never picks them up.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_id=103

From noreply at sourceforge.net  Mon Dec 30 20:43:21 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 30 23:43:57 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-657443 ] Header and footer in multipart
Message-ID: <E18TEFN-0000E3-00@sc8-sf-web1.sourceforge.net>

Bugs item #657443, was opened at 2002-12-22 03:08
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=657443&group_id=103

Category: mail delivery
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 5
Submitted By: Demeilliez Bruno (dive_bruno)
Assigned to: Nobody/Anonymous (nobody)
Summary: Header and footer in multipart

Initial Comment:
Hi,

I have install mailman 2.1b6 on redhat 7.1.
My mailling list is in french and when I received mail
from the list with theBat, the header and the footer is
in multipart (like at the end).
I would like the bady and the footer was in the same
message.
Can you tell me if it's a bug or a configuration problem ?
And how I can resolve it ?

Thank's for your help.

Bruno

Example :
....
From: Bruno Demeilliez <webmaster@aquanaute.com>
X-Mailer: The Bat! (v1.62 Christmas Edition)
Organization: Aquanaute.com
X-Priority: 3 (Normal)
Message-ID: <11916819925.20021222110418@aquanaute.com>
To: test2@aquanaute.com
MIME-Version: 1.0
Subject: Test
X-BeenThere: test2@aquanaute.com
X-Mailman-Version: 2.1b6
Precedence: list
Reply-To: Bruno Demeilliez <webmaster@aquanaute.com>,
        test2@aquanaute.com
List-Id: <test2.aquanaute.com>
List-Help:
<mailto:test2-request@aquanaute.com?subject=help>
List-Post: <mailto:test2@aquanaute.com>
List-Subscribe:
<http://www.aquanaute.com/mailman/listinfo/test2>,
       
<mailto:test2-request@aquanaute.com?subject=subscribe>
List-Archive: <http://www.aquanaute.com/pipermail/test2>
List-Unsubscribe:
<http://www.aquanaute.com/mailman/listinfo/test2>,
       
<mailto:test2-request@aquanaute.com?subject=unsubscribe>
Content-Type: multipart/mixed;
boundary="===============2617006012765839=="
Sender: test2-bounces@aquanaute.com
Errors-To: test2-bounces@aquanaute.com

--===============2617006012765839==
Content-Transfer-Encoding: 8bit
content-type: text/plain

Bonjour test2,

  

Amicalement,

Bruno
---
Pour l'équipe d'Aquanaute.com
http://www.aquanaute.com
SARL de presse Aquanaute.com
8 rue Duployé
38100 Grenoble
France
Tél et Fax : 04 76 99 93 77


--===============2617006012765839==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

_______________________________________________
Liste de discussion Test2
Liste hébergée et administrée gratuitement par
Aquanaute.com
Présentation de la liste, Abonnement / Désabonnement : 
http://www.aquanaute.com/mailman/listinfo/test2
Archives de la liste :
http://aquanaute.com/listes/Test2/

--===============2617006012765839==--

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=657443&group_id=103

From noreply at sourceforge.net  Mon Dec 30 20:43:21 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 30 23:44:10 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-219808 ] Missing dependancy for 'configure'.
Message-ID: <E18TEFN-0000EH-00@sc8-sf-web1.sourceforge.net>

Bugs item #219808, was opened at 2000-10-30 17:13
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=219808&group_id=103

Category: configuring/installing
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 7
Submitted By: Thomas Wouters (twouters)
Assigned to: Thomas Wouters (twouters)
Summary: Missing dependancy for 'configure'.

Initial Comment:
The Mailman makefile is missing a dependancy on 'configure', so when 'configure' is updated, it isn't re-run automatically, and you aren't warned to reconfigure. (definately low-priority bug though :)

(I also ran into something weird when running 'config.status' to do the reconfiguring for me... it set 'MAILMAN_UID' in Defaults.py to 'mailman', without quotes, instead of the numeric uid. That might be caused by a mix of an old config.status and a new configure, though, as I wasn't able to reproduce it on another box.)


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=219808&group_id=103

From noreply at sourceforge.net  Mon Dec 30 20:43:21 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Mon Dec 30 23:44:18 2002
Subject: [Mailman-Developers] 
 [ mailman-Bugs-451475 ] header munging ruins threading
Message-ID: <E18TEFN-0000EC-00@sc8-sf-web1.sourceforge.net>

Bugs item #451475, was opened at 2001-08-16 03:55
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=451475&group_id=103

Category: nntp/news
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 7
Submitted By: CrackMonkey (monkeymaster)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: header munging ruins threading

Initial Comment:
The header hacking done by ToUsenet.py ruins threading
in mail!  It takes a perfectly good message ID, and
throws it away!  news replies to a mail message appear
to be replies to the parent (since the news messag
references contain the references of the parent + some
crazy mailman message ID).  

This is bogus.

At the very least, could you add the real message ID
somewhere so that newsreaders will include it in the
references headers?  Some of us actually use threaded
mailers, you know!

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-04-12 12:16

Message:
Logged In: YES 
user_id=12800

The problem is that many NNTP servers are really picky about
message-id's; they won't allow duplicates, and they won't
allow cross-postings with the same message-id.  I suppose if
the message had an id we could try to preserve it, attempt a
post, and if that's rejected by the nntpd, we could try
again with our own crafted message-id.

I'm up for any suggestions that are rfc-compliant and work
with the widest range of currently existing nntpds.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=451475&group_id=103

From barry at python.org  Tue Dec 31 00:38:42 2002
From: barry at python.org (Barry A. Warsaw)
Date: Tue Dec 31 00:39:12 2002
Subject: [Mailman-Developers] Mailman 2.1 pre-announcement
Message-ID: <15889.11618.371033.419775@gargle.gargle.HOWL>


Happy New Year everyone!

Mailman 2.1 is pushed out to the web sites and the download sites.
See http://www.list.org for the new web pages.

The only thing left is to make the announcement, and I'll do that
tomorrow some time.  You'll notice that these lists have been
upgraded to 2.1 final, and hopefully everything's a-okay.

Note to i18n'ers: I've created a maintenance branch for future 2.1
patch releases.  This way we can continue to develop new versions on
the trunk (whether that's 2.2 or 3.0 is still up in the air).  If you
are making changes to i18n stuff for 2.1.1, please for now do so on
both the trunk and the branch, which is labeled Release_2_1-maint.
I would suggest having both checked out into different directories.

If you have cvs questions, please start here:

http://www.cvshome.org/docs/manual/cvs_5.html#SEC54

And follow up on this list with questions.

Cheers and g'night.
-Barry

From jon at horde.org  Tue Dec 31 16:21:10 2002
From: jon at horde.org (Jon Parise)
Date: Tue Dec 31 16:21:17 2002
Subject: [Mailman-Developers] email package bug
In-Reply-To: <20021230035152.GA17317@csh.rit.edu>
References: <20021229225047.GA10776@csh.rit.edu>
	<20021229225545.GB10776@csh.rit.edu>
	<15887.44380.624951.180599@gargle.gargle.HOWL>
	<20021230035152.GA17317@csh.rit.edu>
Message-ID: <20021231212110.GB15395@csh.rit.edu>

On Sun, Dec 29, 2002 at 10:51:52PM -0500, Jon Parise wrote:

> > Any possibility you can send me the message?
> 
> It looks like it's in the process of building the message when it dies
> (at least, that's my reading of the trace).  How would I go about
> getting you the message contents?
 
FYI -

The problem has been fixed after the latest set of updates (i.e. it
works fine in Mailman 2.1).

Thanks!

-- 
Jon Parise (jon@horde.org) :: The Horde Project (http://horde.org/)

From barry at python.org  Tue Dec 31 17:28:39 2002
From: barry at python.org (Barry A. Warsaw)
Date: Tue Dec 31 17:29:10 2002
Subject: [Mailman-Developers] RELEASED Mailman 2.1 - final
Message-ID: <15890.6679.815374.10775@gargle.gargle.HOWL>


After nearly two years of development, we are happy to announce the
release of GNU Mailman 2.1.  Mailman is free software that enables
users to manage email mailing lists and e-newsletters.  Its integrated
web interface provides easy-to-use access for list members and list
administrators.  Mailman supports built-in archiving, automatic bounce
processing, content filtering, digest delivery, spam filters, and
more.

Mailman 2.1 is fully internationalized, supporting 17 languages
out-of-the-box.  A summary of additional new features in Mailman 2.1
is outlined below.  The NEWS file in the source distribution contains
more details about all the new features.

For more information on Mailman, including downloading and
installation instructions, please visit one of the following mirror
sites:

    http://www.list.org
    http://www.gnu.org/software/mailman
    http://mailman.sf.net

The Mailman developers wish to thank Control.com for their sponsorship
of several Mailman 2.1 features, Zope Corporation for their support,
and the entire Mailman community for their contributions.

-Barry Warsaw
Pythonlabs, Zope Corporation

-------------------- snip snip --------------------
- Multi-lingual support for all web pages and Mailman generated email
  notices, with languages selectable on a per-site, per-list, and
  per-user basis.

- Through-the-web list creation and removal; (with automatic support
  depending on the MTA)

- "Real name" support for members

- Improved simple user-task operation (e.g. no passwords required for
  subscription and unsubscription).

- Support for personalized deliveries and VERP-like message delivery
  for foolproof bounce detection

- Emergency moderation

- MIME-based content-filtering, with demime/stripmime-like options

- Regular expression based topic-filtering

- Better membership management, including searching

- Re-organized administrative requests pages

- Moderated newsgroup support

- A new architecture for the mail delivery subsystem, removing
  dependence on cron, resulting in improved responsiveness and
  scalability

- New moderation and privacy controls

- Invitations

- Autoresponse governors

- Users can now change some delivery options globally, for all lists
  at a site, including their password, delivery status, real name, and
  more.

- Improved MIME and I18n support in the archiver

- Addition of a separate "list moderator" role

- Urgent: header support (bypasses digests to reach all users
  immediately).


From noreply at sourceforge.net  Tue Dec 31 16:33:45 2002
From: noreply at sourceforge.net (noreply@sourceforge.net)
Date: Tue Dec 31 19:33:30 2002
Subject: [Mailman-Developers] [ mailman-Patches-640518 ] SpamAssassin handler
Message-ID: <E18TWpN-0004if-00@sc8-sf-web2.sourceforge.net>

Patches item #640518, was opened at 2002-11-19 00:26
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_id=103

Category: list administration
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Jon Parise (jparise)
Assigned to: Nobody/Anonymous (nobody)
Summary: SpamAssassin handler

Initial Comment:
I've updated the existing SpamAssassin patch (534577)
for Mailman 2.1.

----------------------------------------------------------------------

>Comment By: Jon Parise (jparise)
Date: 2002-12-31 19:33

Message:
Logged In: YES 
user_id=485579

The attached patch adds the SpamAssassin handler to
Mailman's mail processing pipelines.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-11-27 11:13

Message:
Logged In: YES 
user_id=12800

I'm only moving this to the MM2.2/3.0 group so I can
concentrate on patches for 2.1.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_id=103

From ksteward at keithsteward.com  Tue Dec 31 18:18:07 2002
From: ksteward at keithsteward.com (Keith Steward)
Date: Tue Dec 31 21:10:50 2002
Subject: [Mailman-Developers] FW: [Mailman-Announce] RELEASED Mailman 2.1 -
	final
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAebN2b6Pb1RGjtQJgjI3Ph8KAAAAQAAAA6pZ4BMcc1xGjtQAFXc7jfAEAAAAA@keithsteward.com>

Congratulations guys on a nice piece of software!!

Although my earlier posts to this list were problem posts, I don't want
anyone to infer that Mailman is problematic.  The problem was with
sendmail, not Mailman, and now that I've had Mailman 2.1rc1 running for
a few days, I can confidently say that Mailman "Rocks!".  The developers
really deserve a round of applause for their dedication and hard work.

Thanks!!

 
Keith 

--
Keith L. Steward, Ph.D.    work: 408-957-7777 x300   cell: 408-250-5213
Email: keith@BioinformaticsTech.com
Web: http://www.BioinformaticsTech.com
Pager: http://www.skytel.com/Paging/pageme.cgi?pin=8499479,1
          or call 1-888-849-9479
FAX:  408-226-3215 408-40 (call ahead for setup)


-----Original Message-----
From: mailman-announce-bounces@python.org
[mailto:mailman-announce-bounces@python.org] On Behalf Of Barry A.
Warsaw
Sent: Tuesday, December 31, 2002 2:29 PM
To: mailman-announce@python.org
Cc: mailman-developers@python.org; mailman-users@python.org
Subject: [Mailman-Announce] RELEASED Mailman 2.1 - final



After nearly two years of development, we are happy to announce the
release of GNU Mailman 2.1.  Mailman is free software that enables users
to manage email mailing lists and e-newsletters.  Its integrated web
interface provides easy-to-use access for list members and list
administrators.  Mailman supports built-in archiving, automatic bounce
processing, content filtering, digest delivery, spam filters, and more.

Mailman 2.1 is fully internationalized, supporting 17 languages
out-of-the-box.  A summary of additional new features in Mailman 2.1 is
outlined below.  The NEWS file in the source distribution contains more
details about all the new features.

For more information on Mailman, including downloading and installation
instructions, please visit one of the following mirror
sites:

    http://www.list.org
    http://www.gnu.org/software/mailman
    http://mailman.sf.net

The Mailman developers wish to thank Control.com for their sponsorship
of several Mailman 2.1 features, Zope Corporation for their support, and
the entire Mailman community for their contributions.

-Barry Warsaw
Pythonlabs, Zope Corporation

-------------------- snip snip --------------------
- Multi-lingual support for all web pages and Mailman generated email
  notices, with languages selectable on a per-site, per-list, and
  per-user basis.

- Through-the-web list creation and removal; (with automatic support
  depending on the MTA)

- "Real name" support for members

- Improved simple user-task operation (e.g. no passwords required for
  subscription and unsubscription).

- Support for personalized deliveries and VERP-like message delivery
  for foolproof bounce detection

- Emergency moderation

- MIME-based content-filtering, with demime/stripmime-like options

- Regular expression based topic-filtering

- Better membership management, including searching

- Re-organized administrative requests pages

- Moderated newsgroup support

- A new architecture for the mail delivery subsystem, removing
  dependence on cron, resulting in improved responsiveness and
  scalability

- New moderation and privacy controls

- Invitations

- Autoresponse governors

- Users can now change some delivery options globally, for all lists
  at a site, including their password, delivery status, real name, and
  more.

- Improved MIME and I18n support in the archiver

- Addition of a separate "list moderator" role

- Urgent: header support (bypasses digests to reach all users
  immediately).


_______________________________________________
Mailman-announce mailing list
Mailman-announce@python.org
http://mail.python.org/mailman/listinfo/mailman-announce