[Mailman-Users] no mail from list

[Mark Sapiro]

Jeffry Komala wrote:
>
>Thanks for the response.
>I went through the troubleshooting page last night.
>There is no mailmanctl but my other test lists are working.
>System is an old RH9.


And what is the Mailman version? If it is 2.0.x, there is no mailmanctl
or qrunners, but we already know that is not the issue because of the
shunted messages.


>The same problem happened a few months ago. I believe the cause of the
>problem is either a malformed or spam email.
>Unfortunately I don't remember how I fixed it last time. I should have
>written it down.


Possibly a malformed or spam email in the list's
lists/<listname>/digest.mbox file.


>It may also have something to do with the archive. Perhaps, it could not
>write to archive file? I turned off archiving but it didn't help.


Probably not as archiving is separate from delivery.


>At this point I'm not too worry about the email already sent and stuck in
>shunt. Can I just delete them all?
>Will this help?


You can delete them all, but it won't help. They are a symptom of the
problem, not the cause.


>What could be other location of qfiles?


I don't know. You are the one that said "I checked
/var/spool/mailman/qfiles and it's empty" and then said "qfiles/shunt
has a lot of messages." or did you just mean that
/var/spool/mailman/qfiles/ contained only subdirectories?


As I said in my original reply,


>> In any case, the messages are being shunted because of some list
>> specific processing error (occurring after the moderation hold). You
>> have to look in Mailman's 'error' log and find what the error is. You
>> should find an error message with a traceback for each shunted
>> message. If you post one or more of those, we can help determine the
>> problem.


So, what's in the error log?

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan