From noreply at sourceforge.net  Tue Sep  5 20:48:40 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 05 Sep 2006 11:48:40 -0700
Subject: [ mailman-Feature Requests-966157 ] login page should have
	username/password
Message-ID: <E1GKfyS-0001jT-QN@sc8-sf-web6.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jack Jansen (jackjansen)
Assigned to: Nobody/Anonymous (nobody)
Summary: login page should have username/password

Initial Comment:
The login page for mailman administration should have username/
password in stead of just password.

The main reason for me asking this is that it will allow Safari (and 
probably other browsers as well) to remember all the passwords to 
all the mailman lists I manage.

In addition, if the username was actually used (from the previous 
paragraph you'll understand I'm happy enough if it is ignored:-) 
you could have per-admin passwords. And that would of course 
open the door for keeping logs of which admin did what, which'll 
lead to finding scapegoats when things go wrong, etc etc etc.

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

Comment By: David Dyer-Bennet (dd-b)
Date: 2006-09-05 13:48

Message:
Logged In: YES 
user_id=108413

This problem also occurs with Firefox.  

The name of the form field for administrator login (on the
"<listname> Administrator Authentication" page) is "adminpw"
rather than "password".  I'm not sure that Firefox will pick
up the password without an accompanying username either. 

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

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

From noreply at sourceforge.net  Tue Sep  5 23:26:58 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 05 Sep 2006 14:26:58 -0700
Subject: [ mailman-Feature Requests-966157 ] login page should have
	username/password
Message-ID: <E1GKiRe-0001dT-1H@sc8-sf-web4.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jack Jansen (jackjansen)
Assigned to: Nobody/Anonymous (nobody)
Summary: login page should have username/password

Initial Comment:
The login page for mailman administration should have username/
password in stead of just password.

The main reason for me asking this is that it will allow Safari (and 
probably other browsers as well) to remember all the passwords to 
all the mailman lists I manage.

In addition, if the username was actually used (from the previous 
paragraph you'll understand I'm happy enough if it is ignored:-) 
you could have per-admin passwords. And that would of course 
open the door for keeping logs of which admin did what, which'll 
lead to finding scapegoats when things go wrong, etc etc etc.

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

Comment By: David Dyer-Bennet (dd-b)
Date: 2006-09-05 16:26

Message:
Logged In: YES 
user_id=108413

Firefox bug 235336
https://bugzilla.mozilla.org/show_bug.cgi?id=235336 appears
to address this issue, and says it is fixed, and appears to
say it will be in Firefox release 1.8.1. 

Sorry, not sure how this relates to the Safari release
structure.

The underlying problem in Firefox is not that it doesn't
recognize and save the password initially, but rather that
it doesn't offer it *back* when you revisit the page later.

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

Comment By: David Dyer-Bennet (dd-b)
Date: 2006-09-05 13:48

Message:
Logged In: YES 
user_id=108413

This problem also occurs with Firefox.  

The name of the form field for administrator login (on the
"<listname> Administrator Authentication" page) is "adminpw"
rather than "password".  I'm not sure that Firefox will pick
up the password without an accompanying username either. 

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

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

From noreply at sourceforge.net  Wed Sep  6 11:46:59 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 06 Sep 2006 02:46:59 -0700
Subject: [ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1
Message-ID: <E1GKtzn-0002ew-E6@sc8-sf-web1.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configure/install
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Kev Green (kyrian)
Assigned to: Nobody/Anonymous (nobody)
Summary: MySQL MemberAdaptor for Mailman 2.1

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

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

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

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

>Comment By: Kev Green (kyrian)
Date: 2006-09-06 10:46

Message:
Logged In: YES 
user_id=99923

..."you should use backticks in all SELECT, UPDATE, and
INSERT commands"...

Thank you, I hadn't thought of that when writing the
original. Your patch will be applied to the next version I
release, and you will be credited accordingly.

Unfortunately I've just started using Eclipse & CVS for this
and other projects, which has nuked all the RCS tags I had
before. I'll have to fix that before the next release can be
issued.

As regards the getDeliveryStatus() issue. If I haven't fixed
it yet, I will try to do so as soon as reasonably possible.

There are a couple of other additions and changes I'd also
like to do as suggested by other people. We shall see... 

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

Comment By: Gergely EGERVARY (egervary)
Date: 2006-05-04 09:19

Message:
Logged In: YES 
user_id=1255996

Thank you again for this SQL adaptor.

Non-alphanumeric characters (such as "-", the dash
character, what is valid, and quite common in email and
maillist addresses) in list names generates SQL syntax
errors, you should use backticks in all SELECT, UPDATE, and
INSERT commands, like "SELECT name FROM `%s` WHERE ..."

my patch is available here:
http://www.expertlan.hu/egervary/forum/MysqlMemberships.py.diff

Another issue is with getDeliveryStatus, which does not work
for me. row[0] does not return the value stored in the sql
table, so the function always returns MemberAdaptor.ENABLED.
(the sql table contains '3' properly, so there's no problem
with setDeliveryStatus)


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

Comment By: Gustavo Peters (gustavo_peters)
Date: 2005-10-19 02:08

Message:
Logged In: YES 
user_id=1272569

asa<cdzxcx

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

Comment By: adrianwi (adrianwi)
Date: 2005-09-14 20:32

Message:
Logged In: YES 
user_id=1175103

Thank you for developing this adaptor!  So far it's working
well with the limited testing I've done.

There seems to be a minor bug in the addNewMember method of
this adaptor (version 1.61).

At lines 579-584, there are SQL statements which add a new
row in the MySQL database for a new member.  In those
statements, the column 'delivery_status' is given the value
of MemberAdaptor.UNKNOWN.  MemberAdaptor.py defines:

# Delivery statuses
ENABLED  = 0      # enabled
UNKNOWN  = 1      # legacy disabled
BYUSER   = 2      # disabled by user choice
BYADMIN  = 3      # disabled by admin choice
BYBOUNCE = 4      # disabled by bounces

So, it appears that the SQL statements should be changed to
use the value of MemberAdaptor.ENABLED instead of
MemberAdaptor.UNKNOWN (which is "legacy disabled").

Making this change prevents "nomail [reason]" ? from being
set in the user's options for new members (as seen in the
web interface).  This was tested with Mailman 2.1.6.

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

Comment By: Kev Green (kyrian)
Date: 2005-07-27 13:38

Message:
Logged In: YES 
user_id=99923

Folks,

For my own sanity I have decided to create a dedicated area
of my business website for various opensource projects, and
put this project among others under there, so please refer
to this location for updates to this patch in future:

http://www.orenet.co.uk/opensource/

I will still be reading bug reports via sourceforge, but if
nothing else, their user interface is much more fiddly and
time consuming to publish files than a quick tar -czvf and
an scp, so I'll be using my own environment to host the
files at least for the time being.

The latest version at this time is 1.61, I belive it still
requires substantial testing which I'll get around to one of
these days.

K.

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

Comment By: Kev Green (kyrian)
Date: 2005-05-31 19:57

Message:
Logged In: YES 
user_id=99923

Folks,

Well, I've finally gotten around to releasing an update to
this thing, after a phone conversation with the client who
are using it, and I've incorporated a couple of cosmetic
fixes, fairly substantial changes to make the bounce
processing work properly (the ability to set people to
NOMAIL now exists, and real world testing is commencing
soon), and incorporated the flat vs. wide table archivecture
types with various bugfixes.

Main notes:

* It would be a good idea to change all your delivery_status
fields from VARCHAR(255) to INT(10) or similar, so that they
will work properly, and not bomb out on this new version
(they should be okay I think, but I'd advise the change).

* The missing-'AND' typo has been rectified.

Any suggestions and bugs should be sent to my sourceforge
account address, which ends up in the right place.

K.

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

Comment By: Gergely EGERVARY (egervary)
Date: 2005-04-09 11:14

Message:
Logged In: YES 
user_id=1255996

Thank you for your good work.

FYI: there's a missing "AND" in MysqlMemberships.py in line 494.


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

Comment By: simboforge (simboforge)
Date: 2005-03-11 23:22

Message:
Logged In: YES 
user_id=1226150

excellent. can you please give me a list of the files
modified from the original distro? grep sees six that grep
have msyql in them. thx

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

Comment By: Kev Green (kyrian)
Date: 2005-03-11 22:56

Message:
Logged In: YES 
user_id=99923

The flat file databases are unused when you put the MySQL adaptor in 
place, and they are untouched (and indeed not deleted) by it, the MySQL 
adaptor only queries the MySQL tables for membership information, without 
trying to force you into using it fulltime by deleting anything, etc.

Once you unconfigure the MySQL adaptor, Mailman should revert back to 
your existing flat file databases.

Of course, I could have missed something, etc. so do back up your flat file 
databases before installing the MySQL adaptor, and then you can just 
migrate back to them by restoring the backups.

Either way, you have come up with a good question for an FAQ on the SQL 
adaptor :-)

K.


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

Comment By: simboforge (simboforge)
Date: 2005-03-11 22:42

Message:
Logged In: YES 
user_id=1226150

neat. just what i was looking for. i have a couple of live
lists running on version version 2.1.5. i am a bit leary
about unzipping this distrobution over the top of my working
mailman as i am not sure how to backup the existing flat
file databases. i would prefer to experiment with dropping
the adapter into my existing installation. any pointers as
to where to start? thx

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

Comment By: Kev Green (kyrian)
Date: 2004-12-13 18:34

Message:
Logged In: YES 
user_id=99923

Oh, btw. v1.57 hasn't been tested yet, so it might kill your
server, eat your dog, and stick your wife in the oven. Be
careful using it!

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

Comment By: Kev Green (kyrian)
Date: 2004-12-13 18:33

Message:
Logged In: YES 
user_id=99923

Version 1.57: 2004/12/13

* Merge in Daniel Shriver patch/code for a flat table
architecture.
  [ Suggested by Kevin McCann <kmccann(at)bellanet.org>, but
I hadn't found time to do it myself... ]
* Add bugfix information from Jinhyok Heo
<novembre at NOSPAM.ournature.org>
* Add in mksqlmailman script from TheSin
<thesin at SPAMNOTHANKS.southofheaven.org>
* Follow Barry Warsaw's suggestion on delivery status timestamp.


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

Comment By: Kev Green (kyrian)
Date: 2004-01-08 11:38

Message:
Logged In: YES 
user_id=99923

Latest version incorporates automated generation of the necessary tables, 
cleaner error reporting, and updated documentation.

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

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

Message:
Logged In: YES 
user_id=99923

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

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

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

From noreply at sourceforge.net  Mon Sep 11 16:15:31 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 11 Sep 2006 07:15:31 -0700
Subject: [ mailman-Patches-1556401 ] Another withlist backup script
Message-ID: <E1GMmZP-0007Pm-SO@sc8-sf-web5.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: command line scripts
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Raimo Niskanen (raimo_niskanen)
Assigned to: Nobody/Anonymous (nobody)
Summary: Another withlist backup script

Initial Comment:
I hereby submit a withlist script that picles all
members and all their options from a mailing list to
file, for backup.

It can also restore all members and options from such a
pickle file.


/ Raimo Niskanen, Ericsson AB, Erlang/OTP

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

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

From noreply at sourceforge.net  Mon Sep 11 21:46:13 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 11 Sep 2006 12:46:13 -0700
Subject: [ mailman-Bugs-1556617 ] Changing content filtering settings produces
	no changes
Message-ID: <E1GMrjR-0006dd-AE@sc8-sf-web4.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Justin Harper (gtg944q)
Assigned to: Nobody/Anonymous (nobody)
Summary: Changing content filtering settings produces no changes

Initial Comment:
Hi,

I am running a highly moderated closed list, and I 
need my users to be able to send HTML mail and 
attachments back and forth.

I've tried changing the settings under the 'Content 
filtering' section, but changing them seems to have 
no effect whatsoever.

Here are my current settings:
filter_content = no
filter_mime_types = [empty]
pass_mime_types = [empty]
filter_filename_extensions = [empty]
pass_filename_extensions = [empty]
collapse_alternatives = yes
convert_html_to_plaintext = no
filter_action = preserve

I've tried all sorts of different combinations based 
on different 'solutions' that I found on the web, but 
none have worked.  The attachment in my test message 
that keeps being removed is a V-card file (.vcf); 
I've tried adding 'vcf' to pass_filename_extensions, 
but still, the attachment is stripped.

Please help!!!  Let me know what config files you 
need to see and I'll get back to you within hours.

Thanks,

Justin Harper
justin.harper at gatech.edu

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

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

From noreply at sourceforge.net  Tue Sep 12 01:43:06 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 11 Sep 2006 16:43:06 -0700
Subject: [ mailman-Bugs-1556617 ] Changing content filtering settings produces
	no changes
Message-ID: <E1GMvQg-0004db-BY@sc8-sf-web4.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Justin Harper (gtg944q)
Assigned to: Nobody/Anonymous (nobody)
Summary: Changing content filtering settings produces no changes

Initial Comment:
Hi,

I am running a highly moderated closed list, and I 
need my users to be able to send HTML mail and 
attachments back and forth.

I've tried changing the settings under the 'Content 
filtering' section, but changing them seems to have 
no effect whatsoever.

Here are my current settings:
filter_content = no
filter_mime_types = [empty]
pass_mime_types = [empty]
filter_filename_extensions = [empty]
pass_filename_extensions = [empty]
collapse_alternatives = yes
convert_html_to_plaintext = no
filter_action = preserve

I've tried all sorts of different combinations based 
on different 'solutions' that I found on the web, but 
none have worked.  The attachment in my test message 
that keeps being removed is a V-card file (.vcf); 
I've tried adding 'vcf' to pass_filename_extensions, 
but still, the attachment is stripped.

Please help!!!  Let me know what config files you 
need to see and I'll get back to you within hours.

Thanks,

Justin Harper
justin.harper at gatech.edu

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

>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-09-11 23:43

Message:
Logged In: YES 
user_id=67709

What is your mailman version?  The above settings works just
fine for me on my latest version (2.1.9rc1) installation.


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

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

From noreply at sourceforge.net  Tue Sep 12 04:19:00 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 11 Sep 2006 19:19:00 -0700
Subject: [ mailman-Bugs-1556617 ] Changing content filtering settings produces
	no changes
Message-ID: <E1GMxrY-0002rZ-Jo@sc8-sf-web4.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Justin Harper (gtg944q)
Assigned to: Nobody/Anonymous (nobody)
Summary: Changing content filtering settings produces no changes

Initial Comment:
Hi,

I am running a highly moderated closed list, and I 
need my users to be able to send HTML mail and 
attachments back and forth.

I've tried changing the settings under the 'Content 
filtering' section, but changing them seems to have 
no effect whatsoever.

Here are my current settings:
filter_content = no
filter_mime_types = [empty]
pass_mime_types = [empty]
filter_filename_extensions = [empty]
pass_filename_extensions = [empty]
collapse_alternatives = yes
convert_html_to_plaintext = no
filter_action = preserve

I've tried all sorts of different combinations based 
on different 'solutions' that I found on the web, but 
none have worked.  The attachment in my test message 
that keeps being removed is a V-card file (.vcf); 
I've tried adding 'vcf' to pass_filename_extensions, 
but still, the attachment is stripped.

Please help!!!  Let me know what config files you 
need to see and I'll get back to you within hours.

Thanks,

Justin Harper
justin.harper at gatech.edu

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

>Comment By: Justin Harper (gtg944q)
Date: 2006-09-11 22:19

Message:
Logged In: YES 
user_id=1595739

Version: 2.1.8

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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-09-11 19:43

Message:
Logged In: YES 
user_id=67709

What is your mailman version?  The above settings works just
fine for me on my latest version (2.1.9rc1) installation.


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

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

From noreply at sourceforge.net  Tue Sep 12 07:47:28 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 11 Sep 2006 22:47:28 -0700
Subject: [ mailman-Patches-1556858 ] Precautions for digest processing fail
Message-ID: <E1GN17I-0005Wm-Gn@sc8-sf-web6.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 7
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Precautions for digest processing fail

Initial Comment:
Digester.py is called from cron/senddigests and Web CGI
and is responsible in processing the digest.mbox file
to generate single digest message.  As the process may
contain complicated task, it may fail by unknown reason.

With this patch, we put the digest.mbox file which
caused a error off by renaming as digest.mbox.(unixtime).

Without this patch, the cause of the error remeins in
the digest.mbox file and may prevent from being
processed forever.



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

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

From noreply at sourceforge.net  Mon Sep 18 14:38:11 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 18 Sep 2006 05:38:11 -0700
Subject: [ mailman-Bugs-1015096 ] UnicodeEncodeError rejecting smap through
	web admin
Message-ID: <E1GPIO3-0002Me-FT@sc8-sf-web2.sourceforge.net>

Bugs item #1015096, was opened at 2004-08-24 09:01
Message generated for change (Comment added) made by sungeer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1015096&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Niclas Ek (nikke_ek)
Assigned to: Nobody/Anonymous (nobody)
Summary: UnicodeEncodeError rejecting smap through web admin

Initial Comment:
While trying to discard spam from a list:

https://server/admin/list -> 
Tend to pending moderator requests ->
Discard

an error message will appear:

Bug in Mailman version 2.1.5

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/admindb.py", line 163, in main
    process_form(mlist, doc, cgidata)
  File "/home/mailman/Mailman/Cgi/admindb.py", line 711, in 
process_form
    forward, forwardaddr)
  File "/home/mailman/Mailman/ListAdmin.py", line 159, in 
HandleRequest
    forward, addr)
  File "/home/mailman/Mailman/ListAdmin.py", line 345, in __handlepost
    syslog('vette', note)
  File "/home/mailman/Mailman/Logging/Syslog.py", line 40, in write
    self.write_ex(kind, msg, args, kws)
  File "/home/mailman/Mailman/Logging/Syslog.py", line 58, in write_ex
    logf.write(msg + '\n')
  File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in 
write
    Logger.write(self, "%s %s" % (prefix, msg))
  File "/home/mailman/Mailman/Logging/Logger.py", line 91, in write
    f.write(msg)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in 
position 122: ordinal not in range(128)

Python information:

Variable             Value
sys.version         2.3.4 (#2, Jul 5 2004, 09:15:05) [GCC 3.3.4 (Debian 
1:3.3.4-2)] 
sys.executable   /usr/bin/python 
sys.prefix           /usr 
sys.exec_prefix  /usr 
sys.path             /usr 
sys.platform        linux2 

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

Comment By: sungeer (sungeer)
Date: 2006-09-18 12:38

Message:
Logged In: YES 
user_id=1600709

sungeer

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

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

From noreply at sourceforge.net  Mon Sep 18 14:44:02 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 18 Sep 2006 05:44:02 -0700
Subject: [ mailman-Bugs-928624 ] bin/arch break on one possibly broken message
Message-ID: <E1GPITi-0003PT-86@sc8-sf-web5.sourceforge.net>

Bugs item #928624, was opened at 2004-04-02 23:26
Message generated for change (Comment added) made by sungeer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=928624&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin Mokrejs (mmokrejs)
Assigned to: Nobody/Anonymous (nobody)
Summary: bin/arch break on one possibly broken message

Initial Comment:
I have 2.1.4 version with soem sSF patches isntalled.
However, this bug has been occuring even with plain
mailman-2.1.4 (linux).

$ /usr/bin/python /usr/local/mailman/bin/arch --wipe
montana montana.200101 
Ukl?d?m stav archivu
do/usr/local/mailman/archives/private/montana/pipermail.pck
Traceback (most recent call last):
  File "/usr/local/mailman/bin/arch", line 189, in ?
    main()
  File "/usr/local/mailman/bin/arch", line 177, in main
    archiver.processUnixMailbox(fp, start, end)
  File
"/usr/local/mailman/Mailman/Archiver/pipermail.py",
line 592, in processUnixMailbox
    m = mbox.next()
  File "/usr/lib/python2.3/mailbox.py", line 35, in next
    return self.factory(_Subfile(self.fp, start, stop))
  File "/usr/local/mailman/Mailman/Mailbox.py", line
89, in scrubber
    return mailbox.scrub(msg)
  File "/usr/local/mailman/Mailman/Mailbox.py", line
109, in scrub
    return self._scrubber(self._mlist, msg)
  File
"/usr/local/mailman/Mailman/Handlers/Scrubber.py", line
278, in process
    submsg = part.get_payload(0)
  File "/usr/local/mailman/pythonlib/email/Message.py",
line 189, in get_payload
    raise TypeError, 'Expected list, got %s' %
type(self._payload)
TypeError: Expected list, got <type 'str'>
$

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

Comment By: sungeer (sungeer)
Date: 2006-09-18 12:44

Message:
Logged In: YES 
user_id=1600709

>From owner-montana at prfdec.natur.cuni.cz Fri Jan 19 15:46:13 
2001 Received: by prfdec.natur.cuni.cz (TLB v0.11a (1.26 
tibbs 1998/09/22 04:41:41)); Fri, 19 Jan 2001 15:46:15 
+0000 (CET) Received: (from listserv at localhost) by 
prfdec.natur.cuni.cz (8.10.1/8.10.1) id f0JEjFQ17397 for 
montana-outgoing-*-*-*; Fri, 19 Jan 2001 15:45:15 +0100 
(MET) X-Authentication-Warning: prfdec.natur.cuni.cz: 
listserv set sender to owner-montana at mail.natur.cuni.cz 
using -f Received: from email.seznam.cz (omx.seznam.cz 
[195.119.180.41]) by prfdec.natur.cuni.cz (8.10.1/8.10.1) 
with SMTP id f0JEj1Y18402 for ; Fri, 19 Jan 2001 15:45:01 
+0100 (MET) X-Envelope-From: ataman at seznam.cz X-Envelope-
To: Posted-Date: Fri, 19 Jan 2001 15:45:01 +0100 (MET) 
Received-Date: Fri, 19 Jan 2001 15:45:01 +0100 (MET) 
Received: (qmail 10614 invoked by uid 0); 19 Jan 2001 
14:44:56 -0000 Content-Type: 
multipart/mixed;boundary="MessagePart:9799147811250108342" 
Content-Transfer-Encoding: 8bit X-Rofmid: 108 Date: Fri, 19 
Jan 2001 15:44:54 +0100 (CET) Old-From: =?iso-8859-2?Q?
Petr=20Koz=E1k?= From: Petr Koz??k Old-Reply-To: =?iso-8859-
2?Q?Petr=20Koz=E1k?= To: montana at natur.cuni.cz Old-Subject: 
=?iso-8859-2?Q?Re=3A=20=5Bmontana=5D=20Korsika?= Subject: 
Re: [montana] Korsika Mime-Version: 1.0 Message-Id: 
<38097.16369-4659-861128007-979915494 at seznam.cz> X-Loop: 
montana at natur.cuni.cz X-Mailing-List: montana at natur.cuni.cz 
List-Help: To receive a help file List-Help: , List-Info: 
List-Unsubscribe: (Use this command to get off the list) 
List-Subscribe: (Use this command to join the list) List-
Post: List-Archive: (Web Archive of this list) X-Info: This 
message header tries to follow 
http://www.faqs.org/rfcs/rfc2369.html reccommendatitions 
Sender: owner-montana at natur.cuni.cz Precedence: bulk Reply-
To: montana at natur.cuni.cz --MessagePart:9799147811250108342 
Content-Type: text/plain; charset=ISO-8859-2 Content-
Transfer-Encoding: quoted-printable Co jsme byli na Korsice 
prelom srpen/zari tak se celkem vyplnila slova = cestovnich 
kancelari. Srpen neprselo skoro vubec az na asi jednu nebo 
d= ve nocni prehanky z cehoz jedna byla "horska" 
(Vizzavona) A pocatkem za= ri hned jak skoncila sezona 
deste trochu pribylo a celkem se i ochladil= o. Ale myslim 
ze na kolo celkove lepsi zari teda kdyz neprsi v srpnu je= 
starsny vedro. Co se tyce pruvodce tak v roce 1999 jsme nic 
cyklo nese= hnali. Jely jsme s mapou Michellin + turisticky 
pruvodce od Kompasu. kd= yby te zajimal itineri=E1=F8 cesty 
tak se koukni na 
http://www.volny.cz= /dajvos/Cesty/Corse99/iti-c99.htm Cau 
Ataman. 
=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 Po=E8ten=ED=E8ko pro ka=BEd=FD den: 
http://www.novinky.cz --MessagePart:9799147811250108342 
Content-Type: 
message/rfc822;boundary="MessagePart:9799147811712015314" 
Content-Transfer-Encoding: 8bit --
MessagePart:9799147811250108342-- 

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

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

From noreply at sourceforge.net  Wed Sep 20 02:13:10 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 19 Sep 2006 17:13:10 -0700
Subject: [ mailman-Bugs-1556617 ] Changing content filtering settings produces
	no changes
Message-ID: <E1GPpiA-0007Hs-Us@sc8-sf-web3.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Justin Harper (gtg944q)
Assigned to: Nobody/Anonymous (nobody)
Summary: Changing content filtering settings produces no changes

Initial Comment:
Hi,

I am running a highly moderated closed list, and I 
need my users to be able to send HTML mail and 
attachments back and forth.

I've tried changing the settings under the 'Content 
filtering' section, but changing them seems to have 
no effect whatsoever.

Here are my current settings:
filter_content = no
filter_mime_types = [empty]
pass_mime_types = [empty]
filter_filename_extensions = [empty]
pass_filename_extensions = [empty]
collapse_alternatives = yes
convert_html_to_plaintext = no
filter_action = preserve

I've tried all sorts of different combinations based 
on different 'solutions' that I found on the web, but 
none have worked.  The attachment in my test message 
that keeps being removed is a V-card file (.vcf); 
I've tried adding 'vcf' to pass_filename_extensions, 
but still, the attachment is stripped.

Please help!!!  Let me know what config files you 
need to see and I'll get back to you within hours.

Thanks,

Justin Harper
justin.harper at gatech.edu

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

>Comment By: Justin Harper (gtg944q)
Date: 2006-09-19 20:13

Message:
Logged In: YES 
user_id=1595739

Upgraded to 2.1.9rc1 with no effect.  Any other ideas??

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

Comment By: Justin Harper (gtg944q)
Date: 2006-09-11 22:19

Message:
Logged In: YES 
user_id=1595739

Version: 2.1.8

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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-09-11 19:43

Message:
Logged In: YES 
user_id=67709

What is your mailman version?  The above settings works just
fine for me on my latest version (2.1.9rc1) installation.


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

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

From noreply at sourceforge.net  Wed Sep 20 05:16:22 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 19 Sep 2006 20:16:22 -0700
Subject: [ mailman-Bugs-1556617 ] Changing content filtering settings produces
	no changes
Message-ID: <E1GPsZS-0006s7-5C@sc8-sf-web1.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Justin Harper (gtg944q)
Assigned to: Nobody/Anonymous (nobody)
Summary: Changing content filtering settings produces no changes

Initial Comment:
Hi,

I am running a highly moderated closed list, and I 
need my users to be able to send HTML mail and 
attachments back and forth.

I've tried changing the settings under the 'Content 
filtering' section, but changing them seems to have 
no effect whatsoever.

Here are my current settings:
filter_content = no
filter_mime_types = [empty]
pass_mime_types = [empty]
filter_filename_extensions = [empty]
pass_filename_extensions = [empty]
collapse_alternatives = yes
convert_html_to_plaintext = no
filter_action = preserve

I've tried all sorts of different combinations based 
on different 'solutions' that I found on the web, but 
none have worked.  The attachment in my test message 
that keeps being removed is a V-card file (.vcf); 
I've tried adding 'vcf' to pass_filename_extensions, 
but still, the attachment is stripped.

Please help!!!  Let me know what config files you 
need to see and I'll get back to you within hours.

Thanks,

Justin Harper
justin.harper at gatech.edu

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

>Comment By: Mark Sapiro (msapiro)
Date: 2006-09-19 20:16

Message:
Logged In: YES 
user_id=1123998

If filter_content is set to 'no', Mailman does no content
filtering.

Other things which Mailman does that may affect the MIME
structure of the message are adding msg_header and/or
msg_footer and scrubbing messages as controlled by
scrub_nondigest.

If the .vcf attachment is being removed and filter_content
and scrub_nondigest are both 'no', I think it is not Mailman
that's removing it.

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

Comment By: Justin Harper (gtg944q)
Date: 2006-09-19 17:13

Message:
Logged In: YES 
user_id=1595739

Upgraded to 2.1.9rc1 with no effect.  Any other ideas??

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

Comment By: Justin Harper (gtg944q)
Date: 2006-09-11 19:19

Message:
Logged In: YES 
user_id=1595739

Version: 2.1.8

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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-09-11 16:43

Message:
Logged In: YES 
user_id=67709

What is your mailman version?  The above settings works just
fine for me on my latest version (2.1.9rc1) installation.


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

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

From noreply at sourceforge.net  Wed Sep 20 07:58:22 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 19 Sep 2006 22:58:22 -0700
Subject: [ mailman-Bugs-1556617 ] Changing content filtering settings produces
	no changes
Message-ID: <E1GPv6E-0008VM-9R@sc8-sf-web4.sourceforge.net>

Bugs item #1556617, was opened at 2006-09-11 15:46
Message generated for change (Settings changed) made by gtg944q
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1556617&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
>Resolution: Accepted
Priority: 5
Submitted By: Justin Harper (gtg944q)
Assigned to: Nobody/Anonymous (nobody)
Summary: Changing content filtering settings produces no changes

Initial Comment:
Hi,

I am running a highly moderated closed list, and I 
need my users to be able to send HTML mail and 
attachments back and forth.

I've tried changing the settings under the 'Content 
filtering' section, but changing them seems to have 
no effect whatsoever.

Here are my current settings:
filter_content = no
filter_mime_types = [empty]
pass_mime_types = [empty]
filter_filename_extensions = [empty]
pass_filename_extensions = [empty]
collapse_alternatives = yes
convert_html_to_plaintext = no
filter_action = preserve

I've tried all sorts of different combinations based 
on different 'solutions' that I found on the web, but 
none have worked.  The attachment in my test message 
that keeps being removed is a V-card file (.vcf); 
I've tried adding 'vcf' to pass_filename_extensions, 
but still, the attachment is stripped.

Please help!!!  Let me know what config files you 
need to see and I'll get back to you within hours.

Thanks,

Justin Harper
justin.harper at gatech.edu

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

Comment By: Mark Sapiro (msapiro)
Date: 2006-09-19 23:16

Message:
Logged In: YES 
user_id=1123998

If filter_content is set to 'no', Mailman does no content
filtering.

Other things which Mailman does that may affect the MIME
structure of the message are adding msg_header and/or
msg_footer and scrubbing messages as controlled by
scrub_nondigest.

If the .vcf attachment is being removed and filter_content
and scrub_nondigest are both 'no', I think it is not Mailman
that's removing it.

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

Comment By: Justin Harper (gtg944q)
Date: 2006-09-19 20:13

Message:
Logged In: YES 
user_id=1595739

Upgraded to 2.1.9rc1 with no effect.  Any other ideas??

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

Comment By: Justin Harper (gtg944q)
Date: 2006-09-11 22:19

Message:
Logged In: YES 
user_id=1595739

Version: 2.1.8

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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-09-11 19:43

Message:
Logged In: YES 
user_id=67709

What is your mailman version?  The above settings works just
fine for me on my latest version (2.1.9rc1) installation.


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

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

From noreply at sourceforge.net  Wed Sep 20 07:58:38 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 19 Sep 2006 22:58:38 -0700
Subject: [ mailman-Bugs-1556617 ] Changing content filtering settings produces
	no changes
Message-ID: <E1GPv6U-0008Vs-Qg@sc8-sf-web4.sourceforge.net>

Bugs item #1556617, was opened at 2006-09-11 15:46
Message generated for change (Settings changed) made by gtg944q
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1556617&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
>Resolution: Fixed
Priority: 5
Submitted By: Justin Harper (gtg944q)
Assigned to: Nobody/Anonymous (nobody)
Summary: Changing content filtering settings produces no changes

Initial Comment:
Hi,

I am running a highly moderated closed list, and I 
need my users to be able to send HTML mail and 
attachments back and forth.

I've tried changing the settings under the 'Content 
filtering' section, but changing them seems to have 
no effect whatsoever.

Here are my current settings:
filter_content = no
filter_mime_types = [empty]
pass_mime_types = [empty]
filter_filename_extensions = [empty]
pass_filename_extensions = [empty]
collapse_alternatives = yes
convert_html_to_plaintext = no
filter_action = preserve

I've tried all sorts of different combinations based 
on different 'solutions' that I found on the web, but 
none have worked.  The attachment in my test message 
that keeps being removed is a V-card file (.vcf); 
I've tried adding 'vcf' to pass_filename_extensions, 
but still, the attachment is stripped.

Please help!!!  Let me know what config files you 
need to see and I'll get back to you within hours.

Thanks,

Justin Harper
justin.harper at gatech.edu

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

Comment By: Mark Sapiro (msapiro)
Date: 2006-09-19 23:16

Message:
Logged In: YES 
user_id=1123998

If filter_content is set to 'no', Mailman does no content
filtering.

Other things which Mailman does that may affect the MIME
structure of the message are adding msg_header and/or
msg_footer and scrubbing messages as controlled by
scrub_nondigest.

If the .vcf attachment is being removed and filter_content
and scrub_nondigest are both 'no', I think it is not Mailman
that's removing it.

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

Comment By: Justin Harper (gtg944q)
Date: 2006-09-19 20:13

Message:
Logged In: YES 
user_id=1595739

Upgraded to 2.1.9rc1 with no effect.  Any other ideas??

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

Comment By: Justin Harper (gtg944q)
Date: 2006-09-11 22:19

Message:
Logged In: YES 
user_id=1595739

Version: 2.1.8

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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-09-11 19:43

Message:
Logged In: YES 
user_id=67709

What is your mailman version?  The above settings works just
fine for me on my latest version (2.1.9rc1) installation.


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

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

From noreply at sourceforge.net  Wed Sep 20 07:59:23 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 19 Sep 2006 22:59:23 -0700
Subject: [ mailman-Bugs-1556617 ] Changing content filtering settings produces
	no changes
Message-ID: <E1GPv7D-0000A9-Sb@sc8-sf-web4.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
Resolution: Fixed
Priority: 5
Submitted By: Justin Harper (gtg944q)
Assigned to: Nobody/Anonymous (nobody)
Summary: Changing content filtering settings produces no changes

Initial Comment:
Hi,

I am running a highly moderated closed list, and I 
need my users to be able to send HTML mail and 
attachments back and forth.

I've tried changing the settings under the 'Content 
filtering' section, but changing them seems to have 
no effect whatsoever.

Here are my current settings:
filter_content = no
filter_mime_types = [empty]
pass_mime_types = [empty]
filter_filename_extensions = [empty]
pass_filename_extensions = [empty]
collapse_alternatives = yes
convert_html_to_plaintext = no
filter_action = preserve

I've tried all sorts of different combinations based 
on different 'solutions' that I found on the web, but 
none have worked.  The attachment in my test message 
that keeps being removed is a V-card file (.vcf); 
I've tried adding 'vcf' to pass_filename_extensions, 
but still, the attachment is stripped.

Please help!!!  Let me know what config files you 
need to see and I'll get back to you within hours.

Thanks,

Justin Harper
justin.harper at gatech.edu

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

>Comment By: Justin Harper (gtg944q)
Date: 2006-09-20 01:59

Message:
Logged In: YES 
user_id=1595739

It was scrub_nondigest.  Thanks.

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

Comment By: Mark Sapiro (msapiro)
Date: 2006-09-19 23:16

Message:
Logged In: YES 
user_id=1123998

If filter_content is set to 'no', Mailman does no content
filtering.

Other things which Mailman does that may affect the MIME
structure of the message are adding msg_header and/or
msg_footer and scrubbing messages as controlled by
scrub_nondigest.

If the .vcf attachment is being removed and filter_content
and scrub_nondigest are both 'no', I think it is not Mailman
that's removing it.

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

Comment By: Justin Harper (gtg944q)
Date: 2006-09-19 20:13

Message:
Logged In: YES 
user_id=1595739

Upgraded to 2.1.9rc1 with no effect.  Any other ideas??

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

Comment By: Justin Harper (gtg944q)
Date: 2006-09-11 22:19

Message:
Logged In: YES 
user_id=1595739

Version: 2.1.8

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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-09-11 19:43

Message:
Logged In: YES 
user_id=67709

What is your mailman version?  The above settings works just
fine for me on my latest version (2.1.9rc1) installation.


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

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

From noreply at sourceforge.net  Wed Sep 20 16:44:18 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 20 Sep 2006 07:44:18 -0700
Subject: [ mailman-Bugs-1556617 ] Changing content filtering settings produces
	no changes
Message-ID: <E1GQ3JC-0006hH-8L@sc8-sf-web5.sourceforge.net>

Bugs item #1556617, was opened at 2006-09-11 12:46
Message generated for change (Settings changed) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1556617&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
>Status: Deleted
>Resolution: Invalid
Priority: 5
Submitted By: Justin Harper (gtg944q)
Assigned to: Nobody/Anonymous (nobody)
Summary: Changing content filtering settings produces no changes

Initial Comment:
Hi,

I am running a highly moderated closed list, and I 
need my users to be able to send HTML mail and 
attachments back and forth.

I've tried changing the settings under the 'Content 
filtering' section, but changing them seems to have 
no effect whatsoever.

Here are my current settings:
filter_content = no
filter_mime_types = [empty]
pass_mime_types = [empty]
filter_filename_extensions = [empty]
pass_filename_extensions = [empty]
collapse_alternatives = yes
convert_html_to_plaintext = no
filter_action = preserve

I've tried all sorts of different combinations based 
on different 'solutions' that I found on the web, but 
none have worked.  The attachment in my test message 
that keeps being removed is a V-card file (.vcf); 
I've tried adding 'vcf' to pass_filename_extensions, 
but still, the attachment is stripped.

Please help!!!  Let me know what config files you 
need to see and I'll get back to you within hours.

Thanks,

Justin Harper
justin.harper at gatech.edu

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

Comment By: Justin Harper (gtg944q)
Date: 2006-09-19 22:59

Message:
Logged In: YES 
user_id=1595739

It was scrub_nondigest.  Thanks.

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

Comment By: Mark Sapiro (msapiro)
Date: 2006-09-19 20:16

Message:
Logged In: YES 
user_id=1123998

If filter_content is set to 'no', Mailman does no content
filtering.

Other things which Mailman does that may affect the MIME
structure of the message are adding msg_header and/or
msg_footer and scrubbing messages as controlled by
scrub_nondigest.

If the .vcf attachment is being removed and filter_content
and scrub_nondigest are both 'no', I think it is not Mailman
that's removing it.

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

Comment By: Justin Harper (gtg944q)
Date: 2006-09-19 17:13

Message:
Logged In: YES 
user_id=1595739

Upgraded to 2.1.9rc1 with no effect.  Any other ideas??

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

Comment By: Justin Harper (gtg944q)
Date: 2006-09-11 19:19

Message:
Logged In: YES 
user_id=1595739

Version: 2.1.8

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

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-09-11 16:43

Message:
Logged In: YES 
user_id=67709

What is your mailman version?  The above settings works just
fine for me on my latest version (2.1.9rc1) installation.


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

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

From noreply at sourceforge.net  Wed Sep 20 19:42:45 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 20 Sep 2006 10:42:45 -0700
Subject: [ mailman-Bugs-1562369 ] error if reading web archive while changing
	address
Message-ID: <E1GQ65t-0000mb-RA@sc8-sf-web4.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Steven Robbins (smr99)
Assigned to: Nobody/Anonymous (nobody)
Summary: error if reading web archive while changing address

Initial Comment:
I triggered a bug in the mailing list software, Mailman.

I was reading the insight-developers mailing list
archives
(http://www.itk.org/mailman/listinfo/insight-developers)
 via the web, logged in with my old email address,
steven.robbins at videotron.ca. While I was doing that, I
updated my email to this one,
smr at sumost.ca. After responding positively to the
confirmatory email, I went back to
reading the archives in the *same* browser session,
resulting in an error page (below).

Once I cleared my cookie cache, all is well again.

Cheers,
-Steve



Bug in Mailman version 2.1.4

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 \"/var/lib/mailman/scripts/driver\", line 96, in
run_main
main()
File \"/usr/lib/mailman/Mailman/Cgi/private.py\", line
120, in main
password, username):
File \"/var/lib/mailman/Mailman/SecurityManager.py\",
line 220, in WebAuthenticate
ok = self.CheckCookie(ac, user)
File \"/var/lib/mailman/Mailman/SecurityManager.py\",
line 300, in CheckCookie
ok = self.__checkone(c, authcontext, user)
File \"/var/lib/mailman/Mailman/SecurityManager.py\",
line 310, in __checkone
key, secret = self.AuthContextInfo(authcontext, user)
File \"/var/lib/mailman/Mailman/SecurityManager.py\",
line 105, in AuthContextInfo
secret = self.getMemberPassword(user)
File
\"/var/lib/mailman/Mailman/OldStyleMemberships.py\",
line 102, in getMemberPassword
raise Errors.NotAMemberError, member
NotAMemberError: steven.robbins at videotron.ca



Python information:

Variable Value
sys.version 2.3.4 (#2, Jul 5 2004, 09:15:05) [GCC 3.3.4
(Debian 1:3.3.4-2)]
sys.executable /usr/bin/python
sys.prefix /usr
sys.exec_prefix /usr
sys.path /usr
sys.platform linux2

Environment variables:

Variable Value
HTTP_REFERER
http://www.itk.org/mailman/listinfo/insight-developers
SERVER_SOFTWARE Apache/1.3.33 (Debian GNU/Linux)
mod_gzip/1.3.26.1a mod_ssl/2.8.22
OpenSSL/0.9.7e PHP/4.3.10-16 mod_perl/1.29 mod_layout/3.2.1
SCRIPT_NAME /mailman/private
SERVER_SIGNATURE
Apache/1.3.33 Server at www.itk.org Port 80
REQUEST_METHOD GET
HTTP_KEEP_ALIVE 300
SERVER_PROTOCOL HTTP/1.1
QUERY_STRING
HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7
HTTP_USER_AGENT Mozilla/5.0 (Windows; U; Windows NT
5.1; en-US; rv:1.8.0.7)
Gecko/20060909 Firefox/1.5.0.7
HTTP_CONNECTION keep-alive
HTTP_COOKIE
insight-developers+user+steven.robbins--at--videotron.ca=280200000069931a0f45732800000037363963626234366538656630316532326531613230346364326334323062353966373332383935
SERVER_NAME www.itk.org
REMOTE_ADDR 64.4.70.10
PATH_TRANSLATED
/projects/Insight/WWW/InsightDocuments/Web/insight-developers/
SERVER_PORT 80
SERVER_ADDR 192.168.115.100
DOCUMENT_ROOT /projects/Insight/WWW/InsightDocuments/Web
PYTHONPATH /var/lib/mailman
SCRIPT_FILENAME /usr/lib/cgi-bin/mailman/private
SERVER_ADMIN webmaster at public.kitware.com
HTTP_HOST www.itk.org
REQUEST_URI /mailman/private/insight-developers/
HTTP_ACCEPT
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
GATEWAY_INTERFACE CGI/1.1
REMOTE_PORT 16695
HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5
HTTP_ACCEPT_ENCODING gzip,deflate
PATH_INFO /insight-developers/


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

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

From noreply at sourceforge.net  Thu Sep 21 17:05:25 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 21 Sep 2006 08:05:25 -0700
Subject: [ mailman-Bugs-1562922 ] "Discard all...Defer" button appears on mod.
	detail page
Message-ID: <E1GQQ7B-0007qF-V8@sc8-sf-web6.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Dan Astoorian (djast)
Assigned to: Nobody/Anonymous (nobody)
Summary: "Discard all...Defer" button appears on mod. detail page

Initial Comment:
This is a clarification and restatement of bug
#1000699, which was marked "closed" but describes a bug
which is still present.

On the admindb pages, there is a checkbox labelled
"Discard all messages marked Defer" near each of the
submit buttons at the top and bottom of the page.  This
checkbox appears on the default admindb page (where the
requests are grouped by sender), and also on the
"?details=all" page (which is reached by following the
"You can also view the details of all held postings" link).

The checkboxes have no effect on the "?details=all"
page (because the form is structured differently from
the default admindb page).

The comments in Bug #1000699 says that "the 'discard
all deferred' checkbox was intended to work only on the
summary page. It's appearance on the detail pages was a
mistake that was fixed in 2.1.6"; from this I assume
that the checkboxes are not supposed to appear on the
"?details=all" page, but they're still there.

The test in Cgi/admindb.py for whether to supply the
button is "if not (sender or msgid):"; perhaps the test
should be changed to something like "if not (details or
sender or msgid):".

(I mentioned this in a comment I attached to closed bug
#1000699, but there's been no further discussion, and
the bug is still present as of 2.1.9.)


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

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

From noreply at sourceforge.net  Thu Sep 21 20:28:59 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 21 Sep 2006 11:28:59 -0700
Subject: [ mailman-Bugs-1562922 ] "Discard all...Defer" button appears on mod.
	detail page
Message-ID: <E1GQTIB-0002dn-Ev@sc8-sf-web6.sourceforge.net>

Bugs item #1562922, was opened at 2006-09-21 08:05
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1562922&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Web/CGI
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Dan Astoorian (djast)
Assigned to: Nobody/Anonymous (nobody)
Summary: "Discard all...Defer" button appears on mod. detail page

Initial Comment:
This is a clarification and restatement of bug
#1000699, which was marked "closed" but describes a bug
which is still present.

On the admindb pages, there is a checkbox labelled
"Discard all messages marked Defer" near each of the
submit buttons at the top and bottom of the page.  This
checkbox appears on the default admindb page (where the
requests are grouped by sender), and also on the
"?details=all" page (which is reached by following the
"You can also view the details of all held postings" link).

The checkboxes have no effect on the "?details=all"
page (because the form is structured differently from
the default admindb page).

The comments in Bug #1000699 says that "the 'discard
all deferred' checkbox was intended to work only on the
summary page. It's appearance on the detail pages was a
mistake that was fixed in 2.1.6"; from this I assume
that the checkboxes are not supposed to appear on the
"?details=all" page, but they're still there.

The test in Cgi/admindb.py for whether to supply the
button is "if not (sender or msgid):"; perhaps the test
should be changed to something like "if not (details or
sender or msgid):".

(I mentioned this in a comment I attached to closed bug
#1000699, but there's been no further discussion, and
the bug is still present as of 2.1.9.)


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

>Comment By: Mark Sapiro (msapiro)
Date: 2006-09-21 11:28

Message:
Logged In: YES 
user_id=1123998

Your comment on bug # 1000699 slipped through the cracks.
I'm sorry.

This has now been fixed as you suggest in subversion on both
the trunk and the Release_2_1-maint branch.

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

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

From noreply at sourceforge.net  Sun Sep 24 15:26:25 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 24 Sep 2006 06:26:25 -0700
Subject: [ mailman-Patches-1564527 ] Patch to separate Makefile arch-dep and
	arch-indep install
Message-ID: <E1GRU01-0008VL-Gx@sc8-sf-web1.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configure/install
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: Patch to separate Makefile arch-dep and arch-indep install

Initial Comment:
Hello!

When packaging Mailman for Debian, we create different
packages for architecture-specific files and
architecture-independent ones. For this we need to
separate those install steps.

Attached patch adds that possibility to the Mailman
makefile; it adds two new targets "do-arch-install" and
"do-indep-install"; the old "doinstall" remains and
calls both new targets.

I think this might be useful to others who wish to
separate arch-dep and arch-indep files and it doesn't
hurt other users. That's why I request this patch to be
included into Mailman.


regards,
Thijs Kinkhorst
Debian Developer

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

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

From noreply at sourceforge.net  Tue Sep 26 14:53:43 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 26 Sep 2006 05:53:43 -0700
Subject: [ mailman-Bugs-1565707 ] Newlist and groups
Message-ID: <E1GSCRT-0007NW-8f@sc8-sf-web1.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: command line scripts
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Hypnos Software (alexcomps)
Assigned to: Nobody/Anonymous (nobody)
Summary: Newlist and groups

Initial Comment:
In function main:

    if os.getgid() != mm_cfg.MAILMAN_GROUP:
        os.setgid(gid)

it is comparing a string and a number, so it always run
os.setgid(gid)

Also I think that it would be better if it checks if
you belong to the group, because maybe it is not your
primary group but it is one of you secondary ones.

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

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

From noreply at sourceforge.net  Fri Sep 29 03:15:31 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 28 Sep 2006 18:15:31 -0700
Subject: [ mailman-Patches-534298 ] forward unhandled bounces to admin
Message-ID: <E1GT6yR-00080E-B6@sc8-sf-web4.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: list administration
Group: Mailman 2.0.x
Status: Closed
Resolution: Out of Date
Priority: 1
Submitted By: Martin Pool (mbp)
Assigned to: Nobody/Anonymous (nobody)
Summary: forward unhandled bounces to admin

Initial Comment:
samba.org handles a lot of mail messages, and therefore
suffers a lot of bounced messages.  Mailman's automatic
bounce handling is great, but the problem is that
people keep dreaming up new and wierd bounce messages. 

With Mailman 2.0.8, if I turn on automatic bounce
handling then some bouncing addresses are not correctly
detected and therefore keep generating large amounts of
traffic indefinitely.  If I turn it off, we get about
3000 bounces per day. 

Some of these are just not handled yet by the
BouncerAPI and need patches.  In some cases there is in
fact no deterministic way to work out the bouncing
address (at least until we have VERP), and human
intervention is required.  For example, Novell's
brilliant mail software includes no information in the
Received lines or bounce message to indicate what the
bouncing address is!

Anyhow, this patch changes the behaviour of the bounce
handler so that bounce messages which do not cause any
positive action are forwarded to the list
administrator.  &quot;Positive action&quot; can mean noticing
that the address is already disabled, or marking it as
bouncing, or similar things.  It doesn't include
addresses which don't seem to be on the list, which
probably means that we have not interpreted the message
properly and more help is required.  

So in summary bounces which can be automatically
handled will be, and others will go to the admin.

I'm not sure this is the perfect behaviour, but it
certainly seems like an improvement.  Perhaps you want
to make it more configurable.  Please merge this, or
something like it.

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

Comment By: Bron Gondwana (brong)
Date: 2006-09-29 11:15

Message:
Logged In: YES 
user_id=9941

Does this make you responsible for this behaviour?  Next 
time you're down in Melbourne remind me to buy you a beer 
and tip it over you.

(consider the case where the admin addres is bouncing)

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

Comment By: Thomas Wouters (twouters)
Date: 2003-03-12 11:48

Message:
Logged In: YES 
user_id=34209

As mentioned in email, I'll re-check the other
bounce-detection patches, but the ones I checked didn't
apply to 2.1 for other reasons as well (like their original
module being completely rewritten.)


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

Comment By: Martin Pool (mbp)
Date: 2003-03-12 11:43

Message:
Logged In: YES 
user_id=521

&gt; Yeah, Mailman 2.1's bounce detection and handling was
&gt; largely rewritten. It also uses VERP now, so it should solve
&gt; most of your bounce problems, if not all.
                                                           
                                                           
     
Yes, we're using VERP now and it's beautiful.  In particular
we have a
lot of Exchange subscribers, and their bounce messages are
nearly
unintelligible.
                                                           
                                                           
     
&gt; I'm going to close this patch, as well as your other pending
&gt; bounce-detection patches, but if you see any new unhandled
bounces
&gt; (or find that previously-reported ones still fail to
detect) please
&gt; do open a new bug- or patch-report.
                                                           
                                                           
     
I am OK about closing this one, but please reopen the
others.  Since
Mailman still has the option of using a bounce parser rather
than VERP
it seems to make sense to have the parser be as smart as
possible.
Some people might not want to use VERP.  Unless the patches
no longer
merge, I would encourage you to put them in.
                                                           
                                                           
     
&gt; (Preferably with an example message for us to test on.)
                                                           
                                                           
     
I will do that in future.  I think that was not mentioned
when I sent
them, though I do think the patches have partial examples in
their
comments.
                                                           
                                                           
     
&gt; I promise we wont let it rest as long as this one has. :-)
                                                           
                                                           
     
Thanks.  I know it can be hard to get around to these things.
                                                           
                                                           
     
--
Martin


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

Comment By: Thomas Wouters (twouters)
Date: 2003-03-12 11:19

Message:
Logged In: YES 
user_id=34209

Yeah, Mailman 2.1's bounce detection and handling was
largely rewritten. It also uses VERP now, so it should solve
most of your bounce problems, if not all. I'm going to close
this patch, as well as your other pending bounce-detection
patches, but if you see any new unhandled bounces (or find
that previously-reported ones still fail to detect) please
do open a new bug- or patch-report. (Preferably with an
example message for us to test on.) I promise we wont let it
rest as long as this one has. :-)


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

Comment By: Martin Pool (mbp)
Date: 2003-03-11 12:16

Message:
Logged In: YES 
user_id=521

This seems to be already fixed in 2.1.

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

Comment By: Martin Pool (mbp)
Date: 2002-04-03 12:18

Message:
Logged In: YES 
user_id=521

Tim, that's not quite so much of a problem as you might
think.  When excessive bounces are detected Mailman only
*disables* addresses rather than removing them.  With or
without this patch, bouncing addresses which are already
disabled are noted in the log file and not further action is
taken.

Problems can occur if the address is actually removed.  This
can arise in two ways.

One way is that the mail administrator might explicitly
remove the user from the list because of manual bounce
processing.  In that case, any later bounces will also go
through to the admin.  That's the reason for my patch to add
--disable to remove_members.

Secondly, users might unsubscribe themselves and then have
their address start bouncing.

You can imagine Mailman remembering previously-subscribed
members so that it could handle these cases, but that's a
much bigger project, and probably best done in conjunction
with VERP.

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

Comment By: Martin Pool (mbp)
Date: 2002-03-25 12:03

Message:
Logged In: YES 
user_id=521

This patch modifies the behaviour when handling bounce
messages with multiple addresses, such as from Postfix.  Now
messages in which any of the bouncing addresses cannot be
automatically handled are forwarded to the administrator.

Eventually it might be nice to put a notice in the message
explaining the problem -- e.g. user not found, is not a
member, etc.

This update also makes &quot;digester lucked out&quot; be considered
successful processing.

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

Comment By: Tim Potter (tpot)
Date: 2002-03-25 10:18

Message:
Logged In: YES 
user_id=9949

The scenario where addresses which don't seem to be on the
list can be caused by bounces received after the user has
been disabled due to the size of the mail queue.  It may
cause confusion forwarding them to the admin as there is
nothing they can do about it except puzzle over why it was
received.


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

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

From noreply at sourceforge.net  Fri Sep 29 03:30:05 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 28 Sep 2006 18:30:05 -0700
Subject: [ mailman-Patches-1567408 ] Admin address over quota causes bounce
	loop
Message-ID: <E1GT7CX-0007qC-Dg@sc8-sf-web3.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: bounce processing
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Bron Gondwana (brong)
Assigned to: Nobody/Anonymous (nobody)
Summary: Admin address over quota causes bounce loop

Initial Comment:
X-Mailman-Version: 2.1.9.cp1

Hi,

I'm not the administrator of the Mailman instance, 
just the poor sysadmin of a mail service who was 
woken in the middle of the night by our MX servers 
being severely overloaded by a mail loop.

One of our users hit their quota in Cyrus and hence 
their mail was bouncing.  This user is the admin for 
a Mailman list, and the list has been configured to 
forward all bounces to the admin.

The message was:

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

As list administrator, your authorization is 
requested for the
following mailing list posting:

    List:    *****
    From:    *****
    Subject: *****
    Reason:  Message body is too big: 7519566 bytes 
with a limit of 40 KB

At your convenience, visit:

    http://...
 
to approve or deny the request.


And above that stacks of:

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

The attached message was received as a bounce, but 
either the bounce
format was not recognized, or no member addresses 
could be extracted
from it.  This mailing list has been configured to 
send all
unrecognized bounce messages to the list 
administrator(s).

For more information see:
http://.../bounce

I will point the owners of the offending bug at this 
thread so they can provide more specific information 
if they wish, without giving their privacy away.

Bron.

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

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

From noreply at sourceforge.net  Fri Sep 29 04:56:03 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 28 Sep 2006 19:56:03 -0700
Subject: [ mailman-Bugs-1567408 ] Admin address over quota causes bounce loop
Message-ID: <E1GT8Xj-0007iD-74@sc8-sf-web3.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: None
>Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Bron Gondwana (brong)
>Assigned to: Mark Sapiro (msapiro)
Summary: Admin address over quota causes bounce loop

Initial Comment:
X-Mailman-Version: 2.1.9.cp1

Hi,

I'm not the administrator of the Mailman instance, 
just the poor sysadmin of a mail service who was 
woken in the middle of the night by our MX servers 
being severely overloaded by a mail loop.

One of our users hit their quota in Cyrus and hence 
their mail was bouncing.  This user is the admin for 
a Mailman list, and the list has been configured to 
forward all bounces to the admin.

The message was:

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

As list administrator, your authorization is 
requested for the
following mailing list posting:

    List:    *****
    From:    *****
    Subject: *****
    Reason:  Message body is too big: 7519566 bytes 
with a limit of 40 KB

At your convenience, visit:

    http://...
 
to approve or deny the request.


And above that stacks of:

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

The attached message was received as a bounce, but 
either the bounce
format was not recognized, or no member addresses 
could be extracted
from it.  This mailing list has been configured to 
send all
unrecognized bounce messages to the list 
administrator(s).

For more information see:
http://.../bounce

I will point the owners of the offending bug at this 
thread so they can provide more specific information 
if they wish, without giving their privacy away.

Bron.

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

>Comment By: Mark Sapiro (msapiro)
Date: 2006-09-28 19:56

Message:
Logged In: YES 
user_id=1123998

I am moving this to bugs as it is a bug report, not a patch.

Your list owners don't need to provide any additional
information. I understand exactly what's happening here.
(but see below)

There are two issues. The first is that we don't protect
against this loop and I think we should try to. I'll look
into fixing it, although I suspect it will not be easy as
anything I might put in the 'unrecognized bounce' message to
try to detect a loop can be munged or dropped by the MTA
that returns the next bounce.

The other part of the issue is that the MTA that is
returning the 'over quota' denial is not returning an RFC
3464 or RFC 1894 compliant DSN or any of the many other
formats that Mailman heuristically recognizes. If it were,
it would be recognized and not sent back to the list owner.

There is one thing you can provide and that is the actual
'delivery status' part of the unrecognized bounce. You can
alter addresses and domains if you wish for privacy, but if
I have the exact message including headers, I can add a
recognizer for it. What I need is the contents of the
message/rfc822 part that follows the "The attached message
was received" notice you quote above up to the first
"original message follows". I.e., just the DSN part and it's
headers, not any of the multiple preceeding messages/DSNs/etc.


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

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

From noreply at sourceforge.net  Fri Sep 29 05:29:14 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 28 Sep 2006 20:29:14 -0700
Subject: [ mailman-Patches-534298 ] forward unhandled bounces to admin
Message-ID: <E1GT93q-0004rj-He@sc8-sf-web2.sourceforge.net>

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: list administration
Group: Mailman 2.0.x
Status: Closed
Resolution: Out of Date
Priority: 1
Submitted By: Martin Pool (mbp)
Assigned to: Nobody/Anonymous (nobody)
Summary: forward unhandled bounces to admin

Initial Comment:
samba.org handles a lot of mail messages, and therefore
suffers a lot of bounced messages.  Mailman's automatic
bounce handling is great, but the problem is that
people keep dreaming up new and wierd bounce messages. 

With Mailman 2.0.8, if I turn on automatic bounce
handling then some bouncing addresses are not correctly
detected and therefore keep generating large amounts of
traffic indefinitely.  If I turn it off, we get about
3000 bounces per day. 

Some of these are just not handled yet by the
BouncerAPI and need patches.  In some cases there is in
fact no deterministic way to work out the bouncing
address (at least until we have VERP), and human
intervention is required.  For example, Novell's
brilliant mail software includes no information in the
Received lines or bounce message to indicate what the
bouncing address is!

Anyhow, this patch changes the behaviour of the bounce
handler so that bounce messages which do not cause any
positive action are forwarded to the list
administrator.  &quot;Positive action&quot; can mean noticing
that the address is already disabled, or marking it as
bouncing, or similar things.  It doesn't include
addresses which don't seem to be on the list, which
probably means that we have not interpreted the message
properly and more help is required.  

So in summary bounces which can be automatically
handled will be, and others will go to the admin.

I'm not sure this is the perfect behaviour, but it
certainly seems like an improvement.  Perhaps you want
to make it more configurable.  Please merge this, or
something like it.

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

>Comment By: Martin Pool (mbp)
Date: 2006-09-29 13:29

Message:
Logged In: YES 
user_id=521

> Does this make you responsible for this behaviour? 

Since my patch was closed/out-of-date, presumably not.  At
any rate the behaviour is optional.

> (consider the case where the admin addres is bouncing)

Are you suggesting it will loop?  I'm not sure whether admin
messages are subject to normal bounce processing, but I
think not.  Anyhow, it will make it obvious that you need to
fix the admin address. :)

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

Comment By: Bron Gondwana (brong)
Date: 2006-09-29 11:15

Message:
Logged In: YES 
user_id=9941

Does this make you responsible for this behaviour?  Next 
time you're down in Melbourne remind me to buy you a beer 
and tip it over you.

(consider the case where the admin addres is bouncing)

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

Comment By: Thomas Wouters (twouters)
Date: 2003-03-12 11:48

Message:
Logged In: YES 
user_id=34209

As mentioned in email, I'll re-check the other
bounce-detection patches, but the ones I checked didn't
apply to 2.1 for other reasons as well (like their original
module being completely rewritten.)


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

Comment By: Martin Pool (mbp)
Date: 2003-03-12 11:43

Message:
Logged In: YES 
user_id=521

&gt; Yeah, Mailman 2.1's bounce detection and handling was
&gt; largely rewritten. It also uses VERP now, so it should solve
&gt; most of your bounce problems, if not all.
                                                           
                                                           
     
Yes, we're using VERP now and it's beautiful.  In particular
we have a
lot of Exchange subscribers, and their bounce messages are
nearly
unintelligible.
                                                           
                                                           
     
&gt; I'm going to close this patch, as well as your other pending
&gt; bounce-detection patches, but if you see any new unhandled
bounces
&gt; (or find that previously-reported ones still fail to
detect) please
&gt; do open a new bug- or patch-report.
                                                           
                                                           
     
I am OK about closing this one, but please reopen the
others.  Since
Mailman still has the option of using a bounce parser rather
than VERP
it seems to make sense to have the parser be as smart as
possible.
Some people might not want to use VERP.  Unless the patches
no longer
merge, I would encourage you to put them in.
                                                           
                                                           
     
&gt; (Preferably with an example message for us to test on.)
                                                           
                                                           
     
I will do that in future.  I think that was not mentioned
when I sent
them, though I do think the patches have partial examples in
their
comments.
                                                           
                                                           
     
&gt; I promise we wont let it rest as long as this one has. :-)
                                                           
                                                           
     
Thanks.  I know it can be hard to get around to these things.
                                                           
                                                           
     
--
Martin


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

Comment By: Thomas Wouters (twouters)
Date: 2003-03-12 11:19

Message:
Logged In: YES 
user_id=34209

Yeah, Mailman 2.1's bounce detection and handling was
largely rewritten. It also uses VERP now, so it should solve
most of your bounce problems, if not all. I'm going to close
this patch, as well as your other pending bounce-detection
patches, but if you see any new unhandled bounces (or find
that previously-reported ones still fail to detect) please
do open a new bug- or patch-report. (Preferably with an
example message for us to test on.) I promise we wont let it
rest as long as this one has. :-)


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

Comment By: Martin Pool (mbp)
Date: 2003-03-11 12:16

Message:
Logged In: YES 
user_id=521

This seems to be already fixed in 2.1.

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

Comment By: Martin Pool (mbp)
Date: 2002-04-03 12:18

Message:
Logged In: YES 
user_id=521

Tim, that's not quite so much of a problem as you might
think.  When excessive bounces are detected Mailman only
*disables* addresses rather than removing them.  With or
without this patch, bouncing addresses which are already
disabled are noted in the log file and not further action is
taken.

Problems can occur if the address is actually removed.  This
can arise in two ways.

One way is that the mail administrator might explicitly
remove the user from the list because of manual bounce
processing.  In that case, any later bounces will also go
through to the admin.  That's the reason for my patch to add
--disable to remove_members.

Secondly, users might unsubscribe themselves and then have
their address start bouncing.

You can imagine Mailman remembering previously-subscribed
members so that it could handle these cases, but that's a
much bigger project, and probably best done in conjunction
with VERP.

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

Comment By: Martin Pool (mbp)
Date: 2002-03-25 12:03

Message:
Logged In: YES 
user_id=521

This patch modifies the behaviour when handling bounce
messages with multiple addresses, such as from Postfix.  Now
messages in which any of the bouncing addresses cannot be
automatically handled are forwarded to the administrator.

Eventually it might be nice to put a notice in the message
explaining the problem -- e.g. user not found, is not a
member, etc.

This update also makes &quot;digester lucked out&quot; be considered
successful processing.

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

Comment By: Tim Potter (tpot)
Date: 2002-03-25 10:18

Message:
Logged In: YES 
user_id=9949

The scenario where addresses which don't seem to be on the
list can be caused by bounces received after the user has
been disabled due to the size of the mail queue.  It may
cause confusion forwarding them to the admin as there is
nothing they can do about it except puzzle over why it was
received.


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

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

From noreply at sourceforge.net  Fri Sep 29 05:39:00 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 28 Sep 2006 20:39:00 -0700
Subject: [ mailman-Bugs-1567408 ] Admin address over quota causes bounce loop
Message-ID: <E1GT9DI-0005kX-5R@sc8-sf-web2.sourceforge.net>

Bugs item #1567408, was opened at 2006-09-28 18:30
Message generated for change (Settings changed) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1567408&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: bounce detection
>Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Bron Gondwana (brong)
Assigned to: Mark Sapiro (msapiro)
Summary: Admin address over quota causes bounce loop

Initial Comment:
X-Mailman-Version: 2.1.9.cp1

Hi,

I'm not the administrator of the Mailman instance, 
just the poor sysadmin of a mail service who was 
woken in the middle of the night by our MX servers 
being severely overloaded by a mail loop.

One of our users hit their quota in Cyrus and hence 
their mail was bouncing.  This user is the admin for 
a Mailman list, and the list has been configured to 
forward all bounces to the admin.

The message was:

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

As list administrator, your authorization is 
requested for the
following mailing list posting:

    List:    *****
    From:    *****
    Subject: *****
    Reason:  Message body is too big: 7519566 bytes 
with a limit of 40 KB

At your convenience, visit:

    http://...
 
to approve or deny the request.


And above that stacks of:

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

The attached message was received as a bounce, but 
either the bounce
format was not recognized, or no member addresses 
could be extracted
from it.  This mailing list has been configured to 
send all
unrecognized bounce messages to the list 
administrator(s).

For more information see:
http://.../bounce

I will point the owners of the offending bug at this 
thread so they can provide more specific information 
if they wish, without giving their privacy away.

Bron.

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

Comment By: Mark Sapiro (msapiro)
Date: 2006-09-28 19:56

Message:
Logged In: YES 
user_id=1123998

I am moving this to bugs as it is a bug report, not a patch.

Your list owners don't need to provide any additional
information. I understand exactly what's happening here.
(but see below)

There are two issues. The first is that we don't protect
against this loop and I think we should try to. I'll look
into fixing it, although I suspect it will not be easy as
anything I might put in the 'unrecognized bounce' message to
try to detect a loop can be munged or dropped by the MTA
that returns the next bounce.

The other part of the issue is that the MTA that is
returning the 'over quota' denial is not returning an RFC
3464 or RFC 1894 compliant DSN or any of the many other
formats that Mailman heuristically recognizes. If it were,
it would be recognized and not sent back to the list owner.

There is one thing you can provide and that is the actual
'delivery status' part of the unrecognized bounce. You can
alter addresses and domains if you wish for privacy, but if
I have the exact message including headers, I can add a
recognizer for it. What I need is the contents of the
message/rfc822 part that follows the "The attached message
was received" notice you quote above up to the first
"original message follows". I.e., just the DSN part and it's
headers, not any of the multiple preceeding messages/DSNs/etc.


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

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