Myron Kowalski wrote:
>I think I found the (a) problem. There was a corrupted .db and .pck
>file in the
>qfiles/virgin directory. After I deleted those files, mailman would
>start up w/o error
>messages.
But I don't see that that would stop outgoing mail, so there may also
be a problem in th
Myron Kowalski wrote:
>
>I found one .pck out of place and move it. Restarted mailman with the
>same error.
>I moved the whole directory out of the way and restarted mailman--
>same error.
Originally, you said the messages were being archived, so that
indicated that IncomingRunner and ArchRunn
Myron Kowalski wrote:
>On Oct 25, 2007, at 5:54 PM, Mark Sapiro wrote:
>
>> Presumably, this is OutgoingRunner encountering the problem, because
>> IncomingRunner and ArchRunner both have to work for messages to be
>> archived.
>>
>> The problem may be as simple as some spurious file in qfiles/out
I think I found the (a) problem. There was a corrupted .db and .pck
file in the
qfiles/virgin directory. After I deleted those files, mailman would
start up w/o error
messages.
--myron
=
Myron Kowalski
MoCoSIN Network/Systems Administrator
Moravian College
[EMAI
On Oct 26, 2007, at 7:58 AM, Myron Kowalski wrote:
> On Oct 25, 2007, at 5:54 PM, Mark Sapiro wrote:
>
>> Myron Kowalski wrote:
>>
>>> I noticed that messages were not going out to my mailing lists. When
>>> I restarted mailman, this comes up. Any mail sent to the list is
>>> being archived,
>>> b
On Oct 25, 2007, at 5:54 PM, Mark Sapiro wrote:
> Myron Kowalski wrote:
>
>> I noticed that messages were not going out to my mailing lists. When
>> I restarted mailman, this comes up. Any mail sent to the list is
>> being archived,
>> but is not going to the members.
>>
>> Traceback (most recent
Myron Kowalski wrote:
>I noticed that messages were not going out to my mailing lists. When
>I restarted mailman, this comes up. Any mail sent to the list is
>being archived,
>but is not going to the members.
>
>Traceback (most recent call last):
> File "/users/mailman/bin/qrunner", line 270,
Young, Darren wrote:
>Mailman 2.1.5 on RedHat EL 3.0... Getting the following error, any
>thoughts?
>
>[EMAIL PROTECTED] bin]# ./qrunner -r Outgoing:0:1 -v
>Traceback (most recent call last):
> File "./qrunner", line 270, in ?
>main()
> File "./qrunner", line 230, in main
>qrunner.run()
I am also having qrunner problems, but they have to do with the
/etc/cron.d/mailman that tries to run. I am getting an authentication error
in my logs, (Nov 24 22:03:01 livingsky CRON[27016]: Authentication service
cannot retrieve authentication info.) and was wondering (after someone else
told me
I am also having qrunner problems, but they have to do with the
/etc/cron.d/mailman that tries to run. I am getting an authentication error
in my logs, (Nov 24 22:03:01 livingsky CRON[27016]: Authentication service
cannot retrieve authentication info.) and was wondering (after someone else
told me
Your logs tell it all;)
Check the permissions on the files, I believe there's a permcheck script in
the mailman directory.. Run that as root.
On Sunday 24 November 2002 8:50 pm, Victor Allen wrote:
> Background:
>
> Debian Stable with Postfix as MTA and Apache as webserver.
>
> After apt-get insta
This error is a known problem if you are using an older version of Python
than 2.0 and the subject of prior postings to this list.
Installing Mailman 2.0.13 should cure it: the Mailman 2.0.13 the release
note says:
This release fixes some Python 1.5.2 incompatibilities that crept into
Mailma
12 matches
Mail list logo
