On 4/26/20 11:04 PM, Lothar Schilling wrote:
>
> ps -fwwA | grep qrunner
>
> mailman 7439 7438 0 07:51 ? 00:00:00 /usr/bin/python
> /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
> mailman 7440 7438 0 07:51 ? 00:00:00 /usr/bin/python
> /usr/lib/mailman/bin/qrunner -
Am 26.04.2020 um 19:46 schrieb Mark Sapiro:
On 4/26/20 9:57 AM, Lothar Schilling wrote:
Yes I did check the permissons several times, everything is fine. And
no, SELinux was and still is disabled.
What user is running Mailman's qrunners?
ps -fwwA|grep qrunner
And what does
ls -laR /var/spoo
On 4/26/20 9:57 AM, Lothar Schilling wrote:
> Yes I did check the permissons several times, everything is fine. And
> no, SELinux was and still is disabled.
What user is running Mailman's qrunners?
ps -fwwA|grep qrunner
And what does
ls -laR /var/spool/mailman /var/lib/mailman
give?
--
Mark
Hi Tom,
this is not meant for me, is it? My name's not David. Also, my problem
is of a different kind.
Regards
Lothar Schilling
Am 26.04.2020 um 18:44 schrieb Tom Coradeschi:
David: Your qrunner exceptions sound surprisingly like a problem I had
earlier this week with a new install of 2.1.3
Yes I did check the permissons several times, everything is fine. And
no, SELinux was and still is disabled.
Am 26.04.2020 um 18:37 schrieb Mark Sapiro:
On 4/26/20 9:05 AM, Lothar Schilling wrote:
Hi everybody,
today I tried to migrate our whole mailman installation to another server.
Old se
David: Your qrunner exceptions sound surprisingly like a problem I had earlier
this week with a new install of 2.1.30.
In Mailman/Archiver/pipermail.py
change line 60
from: while i>0 and (L[i-1][0] in lowercase or
to: while i>0 and (L[i-1][0] in lowercase[:26] or
Restart mailman and see how th
On 4/26/20 9:05 AM, Lothar Schilling wrote:
> Hi everybody,
>
> today I tried to migrate our whole mailman installation to another server.
>
> Old server: Centos 6.10, Mailman 2.1.29, Python 2.6.6
>
> New server: Centos 7.7, Mailman 2.1.30 (from the tgz file), Python 2.7.5
>
> It seemed to be a
Peter wrote:
>
>I fixed the URL problem (I forgot the vital option: the URL) except I see that
>for one link the URL did not change. In the archives "More information about
>this list" is still the old one.
>
>Any ideas why this may be?
Those links are built when the archive pages are created. I
Le Jeudi 22 Mars 2007 14:01, Peter a écrit :
> Le Jeudi 22 Mars 2007 13:14, Dragon a écrit :
> > Peter wrote:
> > >I'm resending this one. Can anyone help?
> > >
> > >I have migrated a list from an old installation (2.1.5) to a new machine
> > >(running 2.1.8). It appears that the move was succes
Peter wrote:
>
>I accessed the list's admin page [I don't know how it worked with the password
>I gave (it was the one I use for my other test lists)] and any links I choose
>(like the privacy options; to make it advertised) does not use the correct
>URL. It uses localhost.my.domain. I thought
Le Jeudi 22 Mars 2007 13:14, Dragon a écrit :
> Peter wrote:
> >I'm resending this one. Can anyone help?
> >
> >I have migrated a list from an old installation (2.1.5) to a new machine
> >(running 2.1.8). It appears that the move was successful since I can
> > access its page at:
> >
> >http://ma
Peter wrote:
>I'm resending this one. Can anyone help?
>
>I have migrated a list from an old installation (2.1.5) to a new machine
>(running 2.1.8). It appears that the move was successful since I can access
>its page at:
>
>http://mailman.domain.com/mailman/admin/
>
>But it does not show up on t
Quoting Peter ([EMAIL PROTECTED]):
> I'm resending this one. Can anyone help?
>
> I have migrated a list from an old installation (2.1.5) to a new machine
> (running 2.1.8). It appears that the move was successful since I can access
> its page at:
>
> http://mailman.domain.com/mailman/admin/
13 matches
Mail list logo
