Uncaught runner exception: No module named header

[Paul MacKenzie]

We are getting this error on a basic install of the program when we run the admin mass subscription feature.

Aug 11 11:27:34 2009 (843) Skipping and preserving unparseable message: 1250004454.356652+24ea084412711d7d3179d2dbaeb5d23548089129
Aug 11 11:27:34 2009 (843) Uncaught runner exception: No module named header
Aug 11 11:27:34 2009 (843) Traceback (most recent call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 100, in _oneloop
    msg, msgdata = self._switchboard.dequeue(filebase)
  File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 160, in dequeue
    msg = cPickle.load(fp)
ImportError: No module named header

No subscription messages are sent out and each attempt reports the above error in the error log file. This is in a Freebsd 7.X machine with mailman-2.1.12 installed.

[Mark Sapiro (msapiro)]

Is this a "basic install" from source or a FreeBSD package?

It looks like there might be an issue with multiple versions of the python email library. Mailman 2.1.12 should be using the email library from the installed Python. If there is an email package in Mailman's pythonlib/ directory, it should be removed. If you installed from source, make install should have removed it.

I'm not certain that this is the only issue as if there is an email package in Mailman's pythonlib, the admin CGI should be using it too when it makes the queue entry for VirginRunner (presumably, PID 843 is VirginRunner). Also, if the admin CGI is using the wrong email package, posting to a list and other email functions should have problems too, since all those scripts import the same paths module as does the CGI driver script.

Also, is this an upgrade, and if so, have you restarted Mailman since the upgrade?