MLMMJ Mailing List Manager
 help / color / mirror / Atom feed
From: "Søren Boll Overgaard" <boll+mlmmj@fork.dk>
To: mlmmj@mlmmj.org
Subject: Re: archive directory only has one message in it
Date: Sat, 10 Sep 2005 19:25:01 +0000	[thread overview]
Message-ID: <20050910192501.GK26388@freesbee.wheel.dk> (raw)
In-Reply-To: <4320A09D.9060608@diamond.name>

Hello,

On Fri, Sep 09, 2005 at 07:50:31AM -0700, Jason Diamond wrote:
> > 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?

This indeed turned out to be the problem. The patched version of mlmmj-make-ml
in 1.2.5 failed to set proper permissions in $LISTDIR/index. I've fixed this in
version 1.2.8-3 which I have just uploaded to the Debian unstable archive. If
you would like a copy of the package before it hits the mirrors, please let me 
know in private mail.

Also, to avoid Debian specific bugs related to mlmmj-make-ml making it past the
Debian Bug Tracking System, the Debian version of mlmmj-make-ml now tells users
where to report bugs.

> 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.

I would like to second the request for this sort of information to appear as a
warning in the logs.

-- 
Søren O.                                           ,''`.
                                                  : :' :
GPG key id: 0x1EB2DE66                            `. `'
GPG signed mail preferred.                          `-

  parent reply	other threads:[~2005-09-10 19:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08 20:35 archive directory only has one message in it Jason Diamond
2005-09-09  7:20 ` Joel Aelwyn
2005-09-09 14:50 ` Jason Diamond
2005-09-10 17:37 ` Søren Boll Overgaard
2005-09-10 19:25 ` Søren Boll Overgaard [this message]
2005-09-11  8:36 ` Mads Martin Joergensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050910192501.GK26388@freesbee.wheel.dk \
    --to=boll+mlmmj@fork.dk \
    --cc=mlmmj@mlmmj.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox