I've seen this happen, but I can't for the life of me remember the exact
cause. Anyway, the problem is that after the digest is assembled together
from the files containing the individual messages, majordomo fids it
impossible to delete those files -- so they stay around and when the next
message comes in, majordomo thinks that there are all those as-yet-undigested
messages and emits another digest. Check the perms on the directory
containing the individual pre-digested message files (on my system it's
/usr/majordomo/digests/LISTNAME-digest) and also maybe check if there is
a leftover .LOCK file (I forget if this is relevant).
-m
Follow-Ups:
References:
|
|
