Mark Sapiro wrote:
>
>Also, you may be able to work around the problem by just removing the
>pythonlib/email/ directory from your Mailman installation. This won't
>stop the deprecation warnings, but it may allow your current Mailman
>to run.
Actually, that won't work. removing the pythonlib/email
[EMAIL PROTECTED]
>I am running Mailman 2.1.10. A few days ago I updated my Python to
>version 2.6 and everything looked good, list mail was flowing without
>problem.
>
>All of a sudden this afternoon, I started getting errors
>"ImportError: No module named message" on everything. This particu
I am running Mailman 2.1.10. A few days ago I updated my Python to
version 2.6 and everything looked good, list mail was flowing without
problem.
All of a sudden this afternoon, I started getting errors
"ImportError: No module named message" on everything. This particular
one is frim an attem