Comment 7 for bug 266450

Originator: YES

Hi,

thanks for looking into this. To address your questions:

- we are running 2.1.9
- we have a cronjob in cron.daily that does an "unshunt"
- the file I mentioned originally doesn't exist anymore (because it has
been unshunted?)
- the file I attached had this error message:
Mar 05 07:56:19 2008 (4711) SHUNTING:
1167220351.925714+67431f92e260e4da420214c9a343ace677ca1acd
Mar 05 07:56:19 2008 (4711) Uncaught runner exception: iteration over
non-sequence
Mar 05 07:56:19 2008 (4711) Traceback (most recent call last):
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop
    self._onefile(msg, msgdata)
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 170, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
...

So the error is different from what I see with show_qfiles.

- We have not modified the charset of German to UTF-8

Now my question is whether the "unshunt" cron job is evil? I confess I
never properly understood how it works. It seemed to get messages delivered
that were shunted originally, so at some point I set up that cronjob ...

I suppose I should just remove all files that are too old. But: how do I
see the contents when show_qfiles does not work? Are there other tools?

Thanks for all your help!