Hi,
then how about 'strings' ?
Email-Addresses. A lot of them, although I can't see how many. But I
fear something is not right as it (partly) looks as follows:
---
[EMAIL PROTECTED]
kJVe0ZnAr
[EMAIL PROTECTED]
John Doe
[EMAIL PROTECTED] U
Jane Doe
[EMAIL PROTECTED]
Janis Doe
l ElikararU
Hello,
Have you also tried bin/update --force ?
I have now... It produced quite a bit of output, such as e.g.:
Updating mailing list: LISTNAME
Updating the held requests database. // every list
- updating old private mbox file
- updating old public mbox file
Fixing language templates:
Hi again.
Have you also tried bin/update --force ?
However, it didn't help at all. Again, it stripped the backup-file
(that I had renamed to config.pck before executing the above command)
from 533 KB to 83 KB - and still the old (no good) subscriber list.
I guess there is config.pck.last and
Hi,
sorry for this rather long email, but I made some observations, see
below.
I guess there is config.pck.last and mailman fallbacks to it knowing
the backup config.pck is corrupted.
Anticipating that, I had deleted the .last-file, even replaced them
with the backup-file. No difference.
Hi, it's time to go to bed here in Japan. ;-)
Hmm, but the traceback says your config.pck is broken. You should
use 'cat' or 'od' to read what your config.pck really has.
od gives me an almost endless list of 9 columns with numbers. The
(snip)
then how about 'strings' ?
Other useful tool may be
Hello Tokio,
[sorry, this got only mailed to you personally; again to the list;
strange list setting btw...]
Have you done 'bin/update' after moving the backup config.pck file
into the newly installed list directory ?
No updates are necessary. The more I think about it I get the
feeling that
Have you done 'bin/update' after moving the backup config.pck file
into the newly installed list directory ?
No updates are necessary. The more I think about it I get the
feeling that my backup-files somehow got screwed up... Still, can no
one tell me where I can at least find the subscribed
Hello,
I'm a bit in a loss here: I was running Mailman 2.1.2 on Debian 3.0
with no problems. Using apt-get... to upgrade Mailman to 2.1.4
produced an error. Well, besides the fact that all my archives got
deleted (why would a script (!) do that??), I finally got Mailman back
up and running
Hi,
Have you done 'bin/update' after moving the backup config.pck file
into the newly installed list directory ?
Alex Dupont wrote:
Hello,
I'm a bit in a loss here: I was running Mailman 2.1.2 on Debian 3.0
with no problems. Using apt-get... to upgrade Mailman to 2.1.4
produced an error. Well,
