At 1:43 PM -0400 6/21/02, Steve Thomas is rumored to have typed:
LOGABSTRACT is set to yes, but logging stops after the message is added to the digest folder.
Hum...this can't _possibly_ be right, but would explain what I perceive to be what you're saying. In my connections between interactive lists and digests, I don't follow the "acceptable" method of subscribing the digest list to the interactive one. Instead, I manually pipe the message to `flist list-d` in the interactive list's rc.local.s20...this solves a whole boatloads of problems, not the least of which is piping _before_ list-specific header/footers are added, headers are removed (or lord help us, munged), etc., etc. So the recipe would look something like: # rc.local.s20 # # First, send this to the digest (which will send it back...) # :0c | flist list-d Now, if one were to forget to pipe a COPY, as in: # # First, send this to the digest (which will send it back...) # :0 | flist list-d ...that would deliver the ORIGINAL message off to the digested list before SmartList got around to distributing it to the dist list, instead of delivering a COPY of the message. That would, "stop logging after the message is added to the digest folder" and show the message in the digested list without it appearing in the interactive one (the digest would send it back, but by rc.local.s20 the Message-ID's already been added, so the return would be silently discarded). Charlie (who knows this isn't "the answer," but it bothered the heck out of him anyway)