Mark Sapiro wrote:
I think that was the problem, the directory owner. A digest went out at
noon and I no longer see the digest file in the list directory anymore.
We'll see what happens tomorrow.
If it succeeded in deleting the digest.mbox, you should be OK. I wonder
about changing the own
Mark Sapiro wrote:
dann s washko wrote:
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 se
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
Mark Sapiro wrote:
It seems that for some reason, the list's digest.mbox file is not being
removed after production of the day's digest. Have you checked
Mailman's logs for possible reasons?
I've been looking through the logs and no, I don't see any error
regarding the digest. I looked through
Perhaps I am missing something here and I appologize if that is the
case. I set up Mailman 2.1.5 to handle some very low-traffic, moderated
lists. Some users subscribed to the digest and we are noticing that the
digest is being sent out everyday, even if there are no posts for that
day, and i
On Thu, 18 Mar 2004 03:18:44 -0500
dann <[EMAIL PROTECTED]> wrote:
> I just upgraded from mailman 2.0.13 to 2.1.4 and everything is working
> great, except for one minor quark with the links to the archives. If I
> visit the listinfo or admin pages, the link to the archive is
should be seeing this:
www.mydomain/pipermail/lvlug
I am baffled on how to fix this. All the other links seem to work fine,
it seems as if the value MM-List-Name is not being set or passed
correctly.
Any suggestions on correcting this?
--
Dann S. Washko
Lehigh Valley Linux Users Group
http
