From davidianbell at gmail.com  Wed Feb  6 11:09:43 2013
From: davidianbell at gmail.com (David Bell)
Date: Wed, 06 Feb 2013 10:09:43 -0000
Subject: [Bug 1117176] [NEW] Mailman 3 allows the creating of lists with upper
	case but they don't work
References: <20130206100943.18806.75075.malonedeb@gac.canonical.com>
Message-ID: <20130206100943.18806.75075.malonedeb@gac.canonical.com>

Public bug reported:

lists can be created with upper case names e.g. my-LIST at example.com but,
once created, mails are not handled as the addresses are lower cased
(see src/mailman/runners/lmtp.py:203)

Should upper case be allowed at the creation stage?

** Affects: mailman
     Importance: Undecided
         Status: New


** Tags: mailman3

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1117176

Title:
  Mailman 3 allows the creating of lists with upper case but they don't
  work

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1117176/+subscriptions

From davidianbell at gmail.com  Wed Feb  6 11:05:59 2013
From: davidianbell at gmail.com (David Bell)
Date: Wed, 06 Feb 2013 10:05:59 -0000
Subject: [Bug 1117174] [NEW] mailman remove list fails due to constraint error
	on contentfilter
References: <20130206100600.1671.21029.malonedeb@chaenomeles.canonical.com>
Message-ID: <20130206100600.1671.21029.malonedeb@chaenomeles.canonical.com>

Public bug reported:

running the mailman3 command mailman remove <list> throws an
IntegrityError when run agains postgres.

psycopg2.IntegrityError: update or delete on table "mailinglist" violates foreign key constraint "contentfilter_mailing_list_id" on table "contentfilter"
DETAIL:  Key (id)=(6) is still referenced from table "contentfilter".

Schema requires a cascade delete or the code should delete the filters
first.

** Affects: mailman
     Importance: Undecided
         Status: New


** Tags: mailman3

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1117174

Title:
  mailman remove list fails due to constraint error on contentfilter

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1117174/+subscriptions

From teddydlv at yahoo.com  Wed Feb 13 19:33:20 2013
From: teddydlv at yahoo.com (Debra Virden)
Date: Wed, 13 Feb 2013 18:33:20 -0000
Subject: [Bug 266873] Re: Patch to help report spam in moderator queue
References: <20080905194314.1806.82556.launchpad@forster.canonical.com>
Message-ID: <20130213183321.8801.5615.launchpad@gac.canonical.com>

** Description changed:

  You're moderating one of your lists, looking at the 'admindbsummary' page.
  You're already ticked 'accept' to all the non-spam entries and clicked
  submit. You're now left with a queue consisting only of spam.
  
  Some days, you feel calm and rational and just delete the rest using the
  handy 'discard all deferred' tickboxes and move on. Other times, you have
  spam-rage and feel frustrated that it's not trivial to forward all this
  spam on to a reporting service, such as Spamcop or Knujon (or whatever else
  comes along) and help those who do have more time and resources to hunt
- down and shut down these bastards. The problem is that you'd have to go
+ down and shut down these trouble makers. The problem is that you'd have to go
  through the list, ticking 'forward to' and cutting'n'pasting your spam
  submission address(es) in for the whole list manually before you can submit
  it.
  
  One solution would be to add another tickbox like 'report all deferred' and
  do some server-side patching to act on the tickbox. A quicker (dirtier?)
  solution is just to add a few lines of Javascript to the 'admindbsummary'
  page to automate the task client-side. I added the following to the
  template on my home server:
  
  <script type="text/javascript"><!--
  function sendspamto() {
- 	email = document.getElementById("fwdspamto").value;
- 	for (elnum in document.forms[1].elements) {
- 		elem = document.forms[1].elements[elnum];
- 		name = elem.name;
- 		if(name.substr(0, 14) == 'senderforward-') {
- 			elem.checked = true;
- 		}
- 		if(name.substr(0, 16) == 'senderforwardto-') {
- 			elem.value = email;
- 		}
- 	}
+ ?email = document.getElementById("fwdspamto").value;
+ ?for (elnum in document.forms[1].elements) {
+ ??elem = document.forms[1].elements[elnum];
+ ??name = elem.name;
+ ??if(name.substr(0, 14) == 'senderforward-') {
+ ???elem.checked = true;
+ ??}
+ ??if(name.substr(0, 16) == 'senderforwardto-') {
+ ???elem.value = email;
+ ??}
+ ?}
  }
  --></script>
  <form method="GET" action="javascript: sendspamto(); return false;">
  <p><b>Forward spam</b> to : <input id="fwdspamto"
  value="knujon at coldrain.net"/> <input type="submit" value="Set"
  onclick="sendspamto()"/></p>
  </form>
- 
  
  If someone wants to take the above, polish it or whatever and use it in
  upstream mailman that'd make my (and probably a few thousands other
  moderators) lives a little easier :)
  
  Otherwise, please feel free to put it in the FAQ for others to use as they
  wish.
  
  [http://sourceforge.net/tracker/index.php?func=detail&aid=1897575&group_id=103&atid=350103]

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/266873

Title:
  Patch to help report spam in moderator queue

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/266873/+subscriptions

From bojieli at gmail.com  Wed Feb 13 18:07:00 2013
From: bojieli at gmail.com (Bojie Li)
Date: Wed, 13 Feb 2013 17:07:00 -0000
Subject: [Bug 1124313] [NEW] Archiver does not support GBK encoding
References: <20130213170700.28744.22009.malonedeb@chaenomeles.canonical.com>
Message-ID: <20130213170700.28744.22009.malonedeb@chaenomeles.canonical.com>

Public bug reported:

For Chinese mails encoded in GBK, many E-mail softwares errorously puts
"GB2312" in the charset field of message header. GBK is a superset of
GB2312, so decoding GBK message body with GB2312 charset will produce
some wrong characters. There is no problem in decoding GB2312 messages
with GBK charset.

The patch in attachment is quick-and-dirty: It simply regards every
message which claims itself in GB2312 encoding as GBK encoded. This
approach has been tested in 3 Chinese mailing lists.

** Affects: mailman
     Importance: Undecided
         Status: New

** Patch added: "patch for /Mailman/Archiver/HyperArch.py (revision 1374)"
   https://bugs.launchpad.net/bugs/1124313/+attachment/3526752/+files/HyperArch.patch

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1124313

Title:
  Archiver does not support GBK encoding

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1124313/+subscriptions

From jared at puck.nether.net  Fri Feb 15 18:05:22 2013
From: jared at puck.nether.net (Jared Mauch)
Date: Fri, 15 Feb 2013 17:05:22 -0000
Subject: [Bug 1126418] [NEW] Mailman sort patch
References: <20130215170522.29193.56388.malonedeb@chaenomeles.canonical.com>
Message-ID: <20130215170522.29193.56388.malonedeb@chaenomeles.canonical.com>

Public bug reported:

When using sendmail, you can see suboptimal performance.  While there
are some tweaks that can be done, eg: adjusting SMTP_MAX_RCPTS, you can
also see a significant performance gain by sorting by domain.

I have been using this patch privately since at least 2004 and wanted to
share it to be included in future releases if feasible.

There is a second part of it that also adjusts the chunk map which can
either be incorporated or excluded as well.

This will put folks who are @gmail.com all together when handed to
sendmail (for example) instead of interspersed in some other ordering.

One can argue the MTA should do this, but this is a light-weight
approach to optimally utilize resources if the MTA doesn't handle it
properly.

** Affects: mailman
     Importance: Undecided
         Status: New

** Patch added: "sort by domain before handing to SMTP handler"
   https://bugs.launchpad.net/bugs/1126418/+attachment/3530304/+files/mailman.patch

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1126418

Title:
  Mailman sort patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1126418/+subscriptions

From mayesgr at gmail.com  Tue Feb 19 04:39:53 2013
From: mayesgr at gmail.com (Geoff Mayes)
Date: Tue, 19 Feb 2013 03:39:53 -0000
Subject: [Bug 1129742] [NEW] New Majordomo-to-Mailman-2.x import script
References: <20130219033953.8931.61201.malonedeb@gac.canonical.com>
Message-ID: <20130219033953.8931.61201.malonedeb@gac.canonical.com>

Public bug reported:

Hi,

I'm not sure it's worth the trouble at this point (i.e. Mailman 3 dev
focus and Majordomo hardly in existence anymore), but I nonetheless
wanted to let you know about a, IMHO, more current (i.e. handles Mailman
2.15) and thorough Majordomo-to-Mailman script to potentially add to the
contrib/ directory of the Mailman-2.x tarball, just in case this might
help out other folks:
https://github.com/mayesgr/import_majordomo_into_mailman

Kind regards, Geoff Mayes

** Affects: mailman
     Importance: Undecided
         Status: New


** Tags: import majordomo

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1129742

Title:
  New Majordomo-to-Mailman-2.x import script

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1129742/+subscriptions

From aurelien at bompard.org  Wed Feb 20 15:37:00 2013
From: aurelien at bompard.org (=?utf-8?q?Aur=C3=A9lien_Bompard?=)
Date: Wed, 20 Feb 2013 14:37:00 -0000
Subject: [Bug 1130696] [NEW] AttributeError: Message instance has no attribute
	'sender'
References: <20130220143700.9136.57708.malonedeb@gac.canonical.com>
Message-ID: <20130220143700.9136.57708.malonedeb@gac.canonical.com>

Public bug reported:

This is with mailman3:

Feb 20 14:23:07 2013 (5721) Uncaught runner exception: MIMEMultipart instance has no attribute 'sender'
Feb 20 14:23:07 2013 (5721) Traceback (most recent call last):
  File "/srv/dev/mailman/mailman/src/mailman/core/runner.py", line 145, in _one_iteration
    self._process_one_file(msg, msgdata)
  File "/srv/dev/mailman/mailman/src/mailman/core/runner.py", line 218, in _process_one_file
    elif msg.sender:
AttributeError: MIMEMultipart instance has no attribute 'sender'
Feb 20 14:23:07 2013 (5721) SHUNTING: 1361370187.943257+1fba5014964bdeae413f5280cd0f4d2cb5f7727b
Feb 20 14:23:07 2013 (5721) Uncaught runner exception: Message instance has no attribute 'sender'
Feb 20 14:23:07 2013 (5721) Traceback (most recent call last):
  File "/srv/dev/mailman/mailman/src/mailman/core/runner.py", line 145, in _one_iteration
    self._process_one_file(msg, msgdata)
  File "/srv/dev/mailman/mailman/src/mailman/core/runner.py", line 218, in _process_one_file
    elif msg.sender:
AttributeError: Message instance has no attribute 'sender'
Feb 20 14:23:08 2013 (5721) SHUNTING: 1361370187.973463+909c4b5e80497ec67e97765281e7ada77a865143

The message seems to be originating from mailman, it's a digest.

I'm attaching a very simple patch that handles the case where there is
no sender header.

** Affects: mailman
     Importance: Undecided
         Status: New


** Tags: easy mailman3

** Patch added: "mailman-nosender.patch"
   https://bugs.launchpad.net/bugs/1130696/+attachment/3538395/+files/mailman-nosender.patch

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1130696

Title:
  AttributeError: Message instance has no attribute 'sender'

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1130696/+subscriptions

From aurelien at bompard.org  Thu Feb 21 00:18:58 2013
From: aurelien at bompard.org (=?utf-8?q?Aur=C3=A9lien_Bompard?=)
Date: Wed, 20 Feb 2013 23:18:58 -0000
Subject: [Bug 1130957] [NEW] Unicode errors in mailman3
References: <20130220231858.9018.27307.malonedeb@gac.canonical.com>
Message-ID: <20130220231858.9018.27307.malonedeb@gac.canonical.com>

Public bug reported:

This is with mailman3. I'm getting the following unicode errors:

Feb 20 23:07:43 2013 (13496) Uncaught runner exception: Expected unicode, found <type 'str'>: 'foobar at example.com'
Feb 20 23:07:43 2013 (13496) Traceback (most recent call last):
  File "/srv/dev/mailman/mailman/src/mailman/core/runner.py", line 145, in _one_iteration
    self._process_one_file(msg, msgdata)
  File "/srv/dev/mailman/mailman/src/mailman/core/runner.py", line 228, in _process_one_file
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "/srv/dev/mailman/mailman/src/mailman/runners/outgoing.py", line 93, in _dispose
    self._func(mlist, msg, msgdata)
  File "/srv/dev/mailman/mailman/src/mailman/mta/deliver.py", line 93, in deliver
    refused = agent.deliver(mlist, msg, msgdata)
  File "/srv/dev/mailman/mailman/src/mailman/mta/base.py", line 167, in deliver
    member = mlist.members.get_member(recipient)
  File "/srv/dev/mailman/mailman/src/mailman/database/transaction.py", line 78, in wrapper
    return function(args[0], config.db.store, *args[1:], **kws)
  File "/srv/dev/mailman/mailman/src/mailman/model/roster.py", line 111, in get_member
    Address.email == address,
  File "/srv/dev/mailman/venv/lib/python2.7/site-packages/storm-0.19-py2.7-linux-x86_64.egg/storm/expr.py", line 412, in __eq__
    other = getattr(self, "variable_factory", Variable)(value=other)
  File "/srv/dev/mailman/venv/lib/python2.7/site-packages/storm-0.19-py2.7-linux-x86_64.egg/storm/variables.py", line 396, in parse_set
    % (type(value), value))
TypeError: Expected unicode, found <type 'str'>: 'foobar at example.com'
Feb 20 23:07:43 2013 (13496) SHUNTING: 1361401663.441109+267302c50d71d512974fe5caa7aa0214eab699f6

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

Feb 20 22:20:45 2013 (13337) Uncaught runner exception: decoding Unicode is not supported
Feb 20 22:20:45 2013 (13337) Traceback (most recent call last):
  File "/srv/dev/mailman/mailman/src/mailman/core/runner.py", line 145, in _one_iteration
    self._process_one_file(msg, msgdata)
  File "/srv/dev/mailman/mailman/src/mailman/core/runner.py", line 228, in _process_one_file
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "/srv/dev/mailman/mailman/src/mailman/runners/digest.py", line 344, in _dispose
    rfc1153_digest.add_message(message, count)
  File "/srv/dev/mailman/mailman/src/mailman/runners/digest.py", line 269, in add_message
    payload = unicode(payload, 'us-ascii', 'replace')
TypeError: decoding Unicode is not supported
Feb 20 22:20:45 2013 (13337) SHUNTING: 1361398845.847068+d12dc2ef44dcca60ade2fc94f6f830bd09a6b912
Feb 20 22:20:52 2013 (13337) Uncaught runner exception: decoding Unicode is not supported
Feb 20 22:20:52 2013 (13337) Traceback (most recent call last):
  File "/srv/dev/mailman/mailman/src/mailman/core/runner.py", line 145, in _one_iteration
    self._process_one_file(msg, msgdata)
  File "/srv/dev/mailman/mailman/src/mailman/core/runner.py", line 228, in _process_one_file
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "/srv/dev/mailman/mailman/src/mailman/runners/digest.py", line 344, in _dispose
    rfc1153_digest.add_message(message, count)
  File "/srv/dev/mailman/mailman/src/mailman/runners/digest.py", line 269, in add_message
    payload = unicode(payload, 'us-ascii', 'replace')
TypeError: decoding Unicode is not supported
Feb 20 22:20:52 2013 (13337) SHUNTING: 1361398852.901291+bc2f1ab7dad828020238e06815fd2b4adab0fe61


The attached patch fixes both tracebacks.

** Affects: mailman
     Importance: Undecided
         Status: New


** Tags: mailman3

** Patch added: "mailman-unicode.patch"
   https://bugs.launchpad.net/bugs/1130957/+attachment/3539184/+files/mailman-unicode.patch

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1130957

Title:
  Unicode errors in mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1130957/+subscriptions