On 9/9/05, Joel Aelwyn <joel@lightbearer.com> wrote:
My copy, from the same source but hand-built to handle a few other tweaks
(like my variant of "support characters other than + as a separator", which I
need to tweak slightly given something pointed out on the list), certainly
doesn't appear to have this issue. However, there is one thing you should
probably check, given the description of the problem: make sure the 'index'
file exists, and is writeable, since that appears to be what mlmmj uses to
keep track of the archive's last posting number (and thus, if it doesn't
exist, it probably thinks that it should write out '0', and does so... and if
it can't create the index file, well... lather, rinse, repeat). Did you check
your logfile to see if it reported anything?
I think this is the problem.
The index file does exist but it's owned by root:root (the user I was
when I ran mlmmj-make-ml) and not writable by anybody else.
I have exim launching the mlmmj-recieve program as nobody:nogroup since
that's what all of the files in my mailing list directory (except
index) were owned by. Could this be a bug in mlmmj-make-ml?
I didn't realize that index needed to be written to by the user running mlmmj-receive. This is definitely good to know.
I only have two log files in my mailing list directory:
mlmmj-maintd.lastrun.log and mlmmj.operation.log. Neither of them
mentions not being able to write to index.
Thanks!
--
Jason