Altho I haven't seen the problem on any of the lists I run on my own
server, I have experienced this exact problem on both mailman-users and
mailman-developers lists here.
What gets me about this is that altho it says I'm generating excessive
bounces, I get the bounce notification just fine. Bu
Someone asked about the content of the qrunner log and another some other
questions about processes and such, as well as the status of the archives.
The archives are a bit behind. The last seven messages to the list have
yet to appear in the archive pages. In fact, I notice a huge time lag
betwe
We've had several instances lately where Mailman 2.1 just dies silently and
no more mail goes out. I've resorted to putting a cron job in that
restarts mailmanctl but when that happens I get the following returned...
Shutting down Mailman's master qrunner
PID unreadable in: /usr/home/circle/usr/l
After playing with this a bit, I've found that it's specificly because of
the Windows-1252 charset not being recognized. The linefeed/tab in the
header didn't make any difference as it choked on another message that
didn't have the linefeed/tab, but was also Windows-1252 charset.
Now... a new pr
-> On 12:22 PM 1/23/2003 -0800, Tom Maddox was quoted as saying...:
->In addition to this problem, the Reply-To: header includes the short list
->description (not the title but the description). Is there any way to change
->*that*?
Here, Here! The "short list description" isn't so short in some
A couple days ago our digests stopped going out automatically. I forced it
to run this morning via a special cron entry and received the following
report. Can anyone give me a clue as to where to go find out what's
happening?Thanks.
Traceback (most recent call last):
File "/usr/home/circle
