Mark Sapiro wrote:
dann s washko wrote:
I've been looking through the logs and no, I don't see any error regarding the digest. I looked through the digest.mbox and it still contains all the old messages. I verified that the permissions on the digest were rw for for the owner and group (which are mailman.mailman).
Do you see any errors at all in the error log at the time a digest is produced?
Nope, the only thing in my errors logs are the few failed login attempts to non-existent lists from the web adminstration page.
I did notice something with regards to permissions though. While all the files in the list directory were owned by mailman.mailman, the directory itself was root.mailman. I'm not sure whether this makes a difference or not. I have since set the entire mailman directory and it's contents to be owned by mailman.mailman just to be sure.The owner, group and permissions on digest.mbox are as they should be. When digests are produced, the MIME format digest is queued to be sent, then the plain digest is queued, then a couple of calls return and
os.unlink(digestmbox)
is called to remove digest.mbox. Since the digests get sent, about the only thing that can go wrong is the os.unlink() call itself unless only MIME and not plain digests are being sent.
Without more clues, I'm stuck.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
