Anil Jangity wrote: >Yup, that's exactly what I've done. I had mailman compiled with python 2.4. >After I ran into that digest issue, I installed Python 2.7 in a separate >directory, which I used for doing 'senddigest'. >Do I need to run through the mailman "configure" again or can I point mailman >to different python binary. I am sure I need to reconfigure, but just wanted >to double check.
You need to rerun configure with the option --with-python=/gcs/app/mail/listsp/python2.7/bin/python (or wherever your Python 2.7 binary is now) in addition to the options you originally used, and then make install. >Also, how do I re-inject the emails in qfiles/bad back into system? First look at those entries with Mailman's bin/dumpdb, e.g. bin/dumpdb -p qfiles/bad/1327270411.424971ea345bed52b63ad4d2c02cec5964d2df915a4b43.psv Although that probably won't work unless you either change the shebang line at the top of bin/dumpdb to point to Python 2.7, or do it after you reconfigure and make install or just run it with /path/to/python2.7 bin/dumpdb -p qfiles/bad/1327270411.424971ea345bed52b63ad4d2c02cec5964d2df915a4b43.psv It will be best to do the reconfigure and make install first. In any case, you must do it before the step below, or the same exception will recur. Then, you will see what the messages are. If they are the digests you are looking for, mv the files to qfiles/virgin, but change the extension from .psv to .pck. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
