SP wrote:
>
> In fact so far my solution to the problem has been a cron job which
> sends a SIGHUP signal to outgoin runner once a day at a fixed time, just
> to fix the situation in case something was wrong, and sometimes in
> correspondece to the time of that cron job I can find a similar ent
Mark Sapiro ha scritto:
> Was this at the time that you restarted Mailman?
Yes, possibly it was that time...
In fact so far my solution to the problem has been a cron job which
sends a SIGHUP signal to outgoin runner once a day at a fixed time, just
to fix the situation in case something was w
ippaso wrote:
>SP ha scritto:
>
>> Ok, thanks: I will patch mailman immediately and post here the 'error'
>> log as soon as the error appears again.
>
>Here the relevant part of mailman 'error' log (the time of the last sent
>message is 22.29 and the time of the first message which gets stuck in
>
ippaso wrote:
>
>After a look at the log of the smtp server (see below), I can guess that
>the reason might be an high load on the system due to intense
>spamassassin activity: at the time of the error there were 20
>connections (the maximum number of allowable concurrent connections) to
>the serve
SP wrote:
>
>Thanks for the suggestion: this is what I did yesterday. :-)
>A message is sent to a test list every 2 minutes: the last sent message
>was that of 13:36 so whatever happened to mailman, it happened between
>13:36 and 13:38, the time of the first message which got stuck in
>qfiles/out.
