Achiving not working, no .mbox file is being created
We’re running v 2.1.12 under CentOS 6. Lists have been running fine for years, but recently a list owner wanted to start archiving the list messages. He turned on archiving, made them private, set the frequency ,, but nothing is being archived.
I’ve reproduced the issue for a test list; the archive directories are created, but no .mbox file is being created when messages are sent.
I’ve run check-perm -f to fix any permissions issues, but that did not fix it.
we’re sending email via postfix set up to relay to our actual SMTP server.
There are no errors associated with ArchRunner in the error or qrunner logs, and no errors associated with the unarchived posts in any of the logs. I don’t see anything in the system logs either.
-- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group
Institutions do not have opinions, merely customs
On 12/5/19 10:03 AM, Bruce Johnson wrote:
I’ve reproduced the issue for a test list; the archive directories are created, but no .mbox file is being created when messages are sent.
I’ve run check-perm -f to fix any permissions issues, but that did not fix it.
we’re sending email via postfix set up to relay to our actual SMTP server.
There are no errors associated with ArchRunner in the error or qrunner logs, and no errors associated with the unarchived posts in any of the logs. I don’t see anything in the system logs either.
What is the mm_cfg.py setting for ARCHIVE_TO_MBOX. The possibilities are
#-1 - do not do any archiving # 0 - do not archive to mbox, use builtin mailman html archiving only # 1 - do not use builtin mailman html archiving, archive to mbox only # 2 - archive to both mbox and builtin mailman html archiving.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Dec 5, 2019, at 2:04 PM, Mark Sapiro
On 12/5/19 10:03 AM, Bruce Johnson wrote:
I’ve reproduced the issue for a test list; the archive directories are created, but no .mbox file is being created when messages are sent.
I’ve run check-perm -f to fix any permissions issues, but that did not fix it.
we’re sending email via postfix set up to relay to our actual SMTP server.
There are no errors associated with ArchRunner in the error or qrunner logs, and no errors associated with the unarchived posts in any of the logs. I don’t see anything in the system logs either.
What is the mm_cfg.py setting for ARCHIVE_TO_MBOX. The possibilities are
#-1 - do not do any archiving # 0 - do not archive to mbox, use builtin mailman html archiving only # 1 - do not use builtin mailman html archiving, archive to mbox only # 2 - archive to both mbox and builtin mailman html archiving.
Thanks, that was it, it was set to -1. If I set it to anything else this only affects lists that have archiving turned on?
-- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group
Institutions do not have opinions, merely customs
On 12/5/19 1:25 PM, Bruce Johnson wrote:
Thanks, that was it, it was set to -1. If I set it to anything else this only affects lists that have archiving turned on?
Correct.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Bruce Johnson -
Mark Sapiro