[Mailman-Users] no mail from list
jkomala at gmail.com
Thu Oct 18 02:28:34 CEST 2007
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.
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.
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.
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?
What could be other location of qfiles?
On 10/17/07, Mark Sapiro <msapiro at value.net> wrote:
> Jeffry Komala wrote:
> >1. I sent an email to a test list which only has 2 members and it went
> >2. I set the trouble list to moderated and sent a test message. I could
> >my test message in the pending moderator page. However, when I approved
> >I did not get it in my email.
> >3. I checked /var/spool/mailman/qfiles and it's empty
> >4. I checked /var/spool/mqueue and it is also empty.
> >5. qfiles/shunt has a lot of messages.
> 3. and 5. seem contradictory unless Mailman's real qfiles/ directory is
> not the one in /var/spool/mailman.
> 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. Once the underlying problem is resolved, you can run
> bin/unshunt to reprocess the shunted messages.
> Also see
> Mark Sapiro <msapiro at value.net> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users