Re: [Mailman-Users] correcting archive URLs

2009-05-25 Thread Mark Sapiro
admin2 wrote: > >I have Migrating a mail list from one Host to another host. I see that >the archives have URL pointers to domain1.com . I no longer own >domain1.com and would like to replace domain1.com with domain2.com > >is there an application already written to do that? bin/arch --wipe L

[Mailman-Users] correcting archive URLs

2009-05-25 Thread admin2
Hi there, I have Migrating a mail list from one Host to another host. I see that the archives have URL pointers to domain1.com . I no longer own domain1.com and would like to replace domain1.com with domain2.com is there an application already written to do that? Here is what I see in the

Re: [Mailman-Users] check_perms does not fix permissions

2009-05-25 Thread Adam McGreggor
On Mon, May 25, 2009 at 08:04:39AM -0700, Mark Sapiro wrote: > >Problems found: 1283 > >Re-run as list (or root) with -f flag to fix > > The most likely explanation is there are directories in Mailman's tree > that are symlinks. check_perms looks at the permissions of the link > itself (generally

Re: [Mailman-Users] How to unshunt?

2009-05-25 Thread Mark Sapiro
Ulf Dunkel wrote: > Does /var/lib/mailman/bin/unshunt exist and is it executable (mode -rwxr-xr-x)? >>> Yes, it exists there physically (no link or stuff) and is executable >>> with mode -rwxr-xr-x. >> >> >> Then the #! first line points at a non-existent python, or if it says >> "#! @

Re: [Mailman-Users] How to unshunt?

2009-05-25 Thread Ulf Dunkel
Hi Mark. Does /var/lib/mailman/bin/unshunt exist and is it executable (mode -rwxr-xr-x)? Yes, it exists there physically (no link or stuff) and is executable with mode -rwxr-xr-x. Then the #! first line points at a non-existent python, or if it says "#! @PYTHON@", this is a file that has not

Re: [Mailman-Users] How to unshunt?

2009-05-25 Thread Mark Sapiro
Ulf Dunkel wrote: > >/qfiles/retry/ contains *.pck files. Which are messages that have "retryable" delivery problems which should be retried at intervals (default 15 minutes) for some period (default 5 days) or until they are delivered. There should be smtp-failure log entries for the failed deli

Re: [Mailman-Users] How to unshunt?

2009-05-25 Thread Ulf Dunkel
Hi Mark. The files in qfiles/retry/ and qfiles/virgin/ are not shunted. If they are *.pck files, they should be processed normally by RetryRunner and VirginRunner respectively if those runners are running. If they are *.bak files, they are 'backup' queue entries that were possibly left behind if

Re: [Mailman-Users] check_perms does not fix permissions

2009-05-25 Thread Mark Sapiro
admin2 wrote: > >okay I am running check_perms with the -f switch and find that the same >Problems occur over and over. Why are they not getting fixed? I am >running check_perms as root. > > >Problems found: 1283 >Re-run as list (or root) with -f flag to fix The most likely explanation is the

Re: [Mailman-Users] How to unshunt?

2009-05-25 Thread Mark Sapiro
Ulf Dunkel wrote: > >I have found various error reports in /var/log/mailman/error and fixed >everything to have a usable Mailman again. But there are still many >shunted emails in /qfiles/retry/, /qfiles/shunt/ and /qfiles/virgin/. The files in qfiles/retry/ and qfiles/virgin/ are not shunted.

[Mailman-Users] How to unshunt?

2009-05-25 Thread Ulf Dunkel
I recently changed my Mailman 2.1.9 installation to use and support Unicode. I cannot update to a newer Mailman version as long as my Debian Etch hasn't been upgraded to the current Debian version, as I have been told by my ISP. I have found various error reports in /var/log/mailman/error and