Exim doesn't forward messages to mailman
![](https://secure.gravatar.com/avatar/c36225540dac244e84c2ad9e32caea53.jpg?s=120&d=mm&r=g)
My mailman setup, which has been running fine for months now, suddenly stopped working on the 13th.
That is to say, I had all the directors, etc., set up in exim already, and everything was working fine. Suddenly, it has all stopped. It seems at first glance like an exim problem, but exim is handling all mail fine-- including unsubscribe messages!
When I send a message to a list, I get this in /var/log/exim/mainlog:
2001-06-19 21:54:25 15CY8P-0008Sd-00 <= moacir@zuikis.uchicago.edu H=zuikis.uchi cago.edu [128.135.57.157] U=moacir P=esmtp S=982 id=20010619214935.A11301@zuikis .uchicago.edu 2001-06-19 21:54:28 15CY8P-0008Sd-00 => test <test@mydomain.com> D=list_director T=list_transport 2001-06-19 21:54:28 15CY8P-0008Sd-00 Completed
It never goes from there to actually funnel the messages.
My one hint that I've already got is this:
yet ~mailman/lists/test/config.db exists, which is, I think, how exim tells if a list exists.
This has me completely stumped, and I don't even know where to look on the mailman side of things for help. Error logs end on the 13th--the same day the lists stopped working ;)
I upgraded from 2.0.3 to 2.0.5 and nothing changed. I made a completely new installation of mailman (and changed the web and exim.confs accordingly) and nothing changed. In short, and to repeat, I'm stumped.
So I have mailman 2.0.5, exim 3.22 (built Apr 10) and debian (though the mailman install was done by hand).
--m
![](https://secure.gravatar.com/avatar/c36225540dac244e84c2ad9e32caea53.jpg?s=120&d=mm&r=g)
I wrote on 19 June 01:
My mailman setup, which has been running fine for months now, suddenly stopped working on the 13th.
I still don't know why.
I found all the messages inside ~mailman/qfiles. I hand-ran qrunner, and it looks like it flushed out only two messages--the most recent.
Any ideas how I can flush the qfiles directory of all the messages in there and get them to be processed?
tia,
--m
![](https://secure.gravatar.com/avatar/cb6b2a19d7ea20358a4c4f0332afc3ef.jpg?s=120&d=mm&r=g)
"M" == Moacir <moacir@zuikis.uchicago.edu> writes:
M> I found all the messages inside ~mailman/qfiles. I hand-ran
M> qrunner, and it looks like it flushed out only two
M> messages--the most recent.
See if there are any relevant entries in logs/error.
-Barry
![](https://secure.gravatar.com/avatar/c36225540dac244e84c2ad9e32caea53.jpg?s=120&d=mm&r=g)
Barry A. Warsaw wrote on 23 June 01:
There wasn't anything that looked particularly useful. I was having separate problems with cron, so I just moved all the lists to a new install on a different partition, and everything is working smoothly now.
--m
![](https://secure.gravatar.com/avatar/c36225540dac244e84c2ad9e32caea53.jpg?s=120&d=mm&r=g)
I wrote on 19 June 01:
My mailman setup, which has been running fine for months now, suddenly stopped working on the 13th.
I still don't know why.
I found all the messages inside ~mailman/qfiles. I hand-ran qrunner, and it looks like it flushed out only two messages--the most recent.
Any ideas how I can flush the qfiles directory of all the messages in there and get them to be processed?
tia,
--m
![](https://secure.gravatar.com/avatar/cb6b2a19d7ea20358a4c4f0332afc3ef.jpg?s=120&d=mm&r=g)
"M" == Moacir <moacir@zuikis.uchicago.edu> writes:
M> I found all the messages inside ~mailman/qfiles. I hand-ran
M> qrunner, and it looks like it flushed out only two
M> messages--the most recent.
See if there are any relevant entries in logs/error.
-Barry
![](https://secure.gravatar.com/avatar/c36225540dac244e84c2ad9e32caea53.jpg?s=120&d=mm&r=g)
Barry A. Warsaw wrote on 23 June 01:
There wasn't anything that looked particularly useful. I was having separate problems with cron, so I just moved all the lists to a new install on a different partition, and everything is working smoothly now.
--m
participants (2)
-
barry@digicool.com
-
Moacir