I was not clear in my previous posts, so just to clarify:
Brad Knowles ha scritto:
> You really want to avoid doing any kind of anti-spam check for outgoing
> mail from Mailman. All those checks should be done on input, and should
> not need to be done on output.
The antispam check is perfo
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
g delivery 106876: msg 232144 to
local [EMAIL PROTECTED]
2008-01-27 13:38:32.364079500 status: local 2/10 remote 0/200
2008-01-27 13:38:32.365545500 new msg 232142
2008-01-27 13:38:32.365553500 info msg 232142: bytes 4932 from
<[EMAIL PROTECTED]> qp 28542 uid 509
2008-01-27 13:38:32.408993500
Stephen J. Turnbull ha scritto:
> Find the last few logs from Mailman and the MTA before the stoppage.
> This may give experts some clue. (If I knew what to tell you to look
> for, I would, but experts often can see things that we can't. :)
Good suggestion: I have to wait for the problem to appe
Hi everybody.
Since a couple of months I have started having some problems with
mailman. Sometimes it stops sending out e-mail: outgoing messages get
stuck in ~/qfiles/out.
The qrunner for outgoing mail is up and running, but it simply does not
process the messages in the queue. Restarting mailma
