Re: Problems with weekly digests

These two problems are probably unrelated. The way in which the minimum 
size of the digest is displayed is probably a formatting bug. The more 
serious problem is the delivery of weekly digests, which apparently 
worked fine up until December of last year. Did anything significant 
happen at that time?

Also, I strongly recommend in general that administrators of Mj2 master 
the report command and begin their diagnoses by using it. In this case, 
you expect the weekly digest to be delivered sometime between 11pm and 
midnight on Friday. Is the trigger command completed within that time 
frame, is it completed later, or does it crash?

Michael

Steven W. Orr wrote:
> On Saturday, Mar 28th 2009 at 16:23 -0000, quoth Steven W. Orr:
>
> =>I just found out that people don't seem to be getting the digests if they
> =>asked for them to be weekly. Here is my digests setting.
> =>
> =>configset framcom digests <<ENDAAC
> =>daily
> =>times=5
> =>minsize=1
> =>minmsg=1
> =>maxmsg=200
> =>maxsize=0
> =>maxage=1d
> =>minage=0
> =>newmsg=0
> =>desc=The framcom daily digest
> =>subject=[$LIST] Daily digest ($MESSAGECOUNT messages)
> =>
> =>weekly
> =>times=fr(23)
> =>minsize=1
> =>minmsg=1
> =>maxsize=0
> =>maxmsg=400
> =>type=mime
> =>desc=The framcom weekly digest
> =>subject=[$LIST] Weekly digest ($MESSAGECOUNT messages)
> =>
> =>ENDAAC
> =>
> =>
> =>Am I doing something wrong? I need to fix this :-(
> =>
> =>TIA
>
> I'm sorry, I'd like to try again. When I wrote this I didn't know about 
> the existence of the digest command. I had a bunch of weekly digests that 
> had backed up and I cleared the backup, but I still have a couple of 
> problems.
>
> I have two lists. The first list described above now looks like this:
>
> configset framcom digests <<ENDAAB
> daily
> times=5
> minsize=1
> minmsg=1
> maxmsg=200
> maxsize=0
> maxage=1d
> type=mime
> newmsg=0
> desc=The framcom daily digest
> subject=[$LIST] Daily digest ($MESSAGECOUNT messages)
>
> weekly
> times=fr(23)
> minsize=1
> minmsg=1
> maxmsg=400
> maxsize=0
> maxage=7d
> type=mime
> desc=The framcom weekly digest
> subject=[$LIST] Weekly digest ($MESSAGECOUNT messages)
>
> ENDAAB
>
> The other list (frambors) is next:
>
> configset frambors digests <<ENDAAD
> daily
> times=5
> minsize=1
> minmsg=1
> maxmsg=200
> maxsize=0
> maxage=1d
> newmsg=0
> type=mime
> desc=The frambors daily digest
> subject=[$LIST] Daily digest ($MESSAGECOUNT messages)
>
> weekly
> times=fr(23)
> minsize=1
> minmsg=1
> maxsize=0
> maxmsg=400
> maxage=7d
> type=mime
> desc=The frambors weekly digest
> subject=[$LIST] Weekly digest ($MESSAGECOUNT messages)
>
> ENDAAD
>
> If I run a digest-status framcom weekly, I see the following header info:
>
> Digest name                weekly
> Last delivered on          Sat Mar 28 21:52:53 2009
> Next delivery on or after  Sat Mar 28 22:07:53 2009
> Age of oldest message      17 hours
> Oldest age allowed         7 days
> Age of newest message      1 hour
> Minimum message count      1
> Maximum message count      400
> Messages awaiting delivery 6
> Total message size         15352 bytes
>
> But if I run the same command on the frambors list, the minimum digest 
> size comes out funky.
>
> Majordomo>digest-status frambors weekly
>
> Digest name                weekly
> Last delivered on          Sat Mar 28 22:01:46 2009
> Next delivery on or after  Sat Mar 28 22:16:46 2009
> Age of oldest message      17 hours
> Oldest age allowed         7 days
> Age of newest message      2 hours
> Minimum message count      1
> Maximum message count      400
> Minimum digest size        $VAR1->{'parsed'}{'message_footer'}[0][4]
> Messages awaiting delivery 5
> Total message size         15746 bytes
>  
> Somehow the _config got torked. I fixed it by hand editing the _config 
> file. We'll see if weekly goes out on this coming Fr.
>
> Sorry for the confusion.
>
>