Bug 633129

I've a similar behaviour when trying to rebuild the archives for a mailing list:

# bin/arch xyz /var/lib/mailman/archives/private/xyz.mbox/xyz.mbox 
Schreibe Archivzustand in Datei /var/lib/mailman/archives/private/h2o/pipermail.pck
Traceback (most recent call last):
  File "bin/arch", line 200, in <module>
    main()
  File "bin/arch", line 188, in main
    archiver.processUnixMailbox(fp, start, end)
  File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 564, in processUnixMailbox
    m = mbox.next()
  File "/usr/lib/python2.6/mailbox.py", line 1955, in next
    return self.factory(_PartialFile(self.fp, start, stop))
  File "/usr/lib/mailman/Mailman/Mailbox.py", line 89, in scrubber
    return mailbox.scrub(msg)
  File "/usr/lib/mailman/Mailman/Mailbox.py", line 109, in scrub
    return self._scrubber(self._mlist, msg)
  File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 192, in process
    ctype = part.get_type(part.get_default_type())
AttributeError: Message instance has no attribute 'get_type'

# rpm -q mailman python
mailman-2.1.11-13.2.i586
python-2.6.5-2.11.i586

Seems to be similar to the problem mentioned here: http://www.mail-archive.com/mailman-users@python.org/msg56608.html

It said that mailman 2.1.11 is not compatible to python 2.6.x :(

So please update to 2.1.12 or newer!

I've been able to get mailman working again by applying this patch:

http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1140

Select "download diff" on that page, save the patch to e.g. /tmp/MailmanPatch, then

cd /usr/lib/mailman
patch -p0 < /tmp/MailmanPatch

Thanx. Worked for me. :)

Works for me too, no mail today :-)

What I find slightly worrisome is that the exact same problem was also present in openSuSE 11.1 (bug 448530). I skipped 11.2, so not sure about that one. Seems the process to carry forward bug fixes from one version to the next is severely broken. Plus testing, at least on this package, appears to be non-existent.

I've been hit by this issue either. Digest ain't working.
Any changes of updates?

we have mailman 2.1.14 in server:mail, would that fix the issue?
Adding Dirk, who did the update there.

If there will be a package for openSUSE-11.3 too, then "yes! great job!"

mailman is currently disabled for 11.3:
https://build.opensuse.org/project/monitor?arch_i586=1&defaults=0&disabled=1&project=server%3Amail&repo_openSUSE_11_3=1

mailman-2.1.14 is now avail in server:mail repository. I installed and run "unshunt". No more shunt files avail, digest mbox filled up (as expected) and the error logfile didn't grow.

I think it's working fine, but didn't test all the functionality of the package, but main functionality distributing e-mails to various recipients is working too. :-)

I would suggest to do close the bug and to do the swamp/update with the new package from server:mail repository. :-)

I ran into this issue as well upgrading from opensuse 11.2 (32 bit) to 11.3 (64 bit). In my case I can confirm that the functionality was working in 11.2 because I used that for a longer time. 

Perhaps also good to mention that the repo URL is http://download.opensuse.org/repositories/server:/mail/openSUSE_11.3/ 

I fixed the problem by downloading only the mailman rpm from the repo and installing it (do not want to deviate too much from the mainline by getting upgrades for other mail related functionality).

Erik,
the issue is in "zypper dup". It doesn't "refresh" the repositories and as a matter of fact you didn't get the bugfixed mailman installed.

The fixed packages are already avail. I cost me several hours to find this out.

Either you enable the Refresh option in the repositories (use zypper, yast or similar for this), or you a "zypper ref" before any of your "zypper up" calls. I would suggest the first, as it it less error prone. :-)

That doesn't work for me. All repositories that are enabled are also automatically refreshed. Also running 'zypper ref' followed by 'zypper dup' reinstalled the old mailman version again. 

NOTE: I do not have the server:mail repository in my repository list.

Also, I am running 64 bit, not 32 bit as indicated in the bug.

This problem was just brought up on the german postfixbuch-users mailinglist, however in a more critical version: at least one of his users can't post to the mailinglist.

Error log copied from the mail:
Jan 10 12:17:03 2011 (2497) SHUNTING:
1294658221.996407+045e901544f18611fa2eb3ad7627f69c4486f7f7
Jan 10 12:19:06 2011 (2497) Uncaught runner exception: Message instance
has no attribute 'get_type'
Jan 10 12:19:06 2011 (2497) Traceback (most recent call last):
File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop
self._onefile(msg, msgdata)
File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 191, in
_onefile
keepqueued = self._dispose(mlist, msg, msgdata)
ile "/usr/lib/mailman/Mailman/Queue/OutgoingRunner.py",
ine 74, in _dispose
self._func(mlist, msg, msgdata)
File
"/usr/lib/mailman/Mailman/Handlers/SMTPDirect.py",
line 159, in process
deliveryfunc(mlist, msg, msgdata, envsender,
refused, conn)
File
"/usr/lib/mailman/Mailman/Handlers/SMTPDirect.py",
line 292, in verpdeliver
Decorate.process(mlist, msgcopy, msgdata)
File
"/usr/lib/mailman/Mailman/Handlers/Decorate.py",
line 133, in process
elif msg.get_type() ==
'multipart/mixed':
AttributeError: Message instance has
no attribute 'get_type'


-> Please release the fix (see comment #3) or a newer mailman version as
   maintenance update!

-> Please also update mailman in Factory, it's still at version 2.1.11 and most 
   probably shares the same bug

this was fixed by updating Factory and 11.3 to mailman 2.1.14
(hopefully the same update will happen in 11.2 and SLE11)