On 07/31/2011 05:36 PM, Alex Stanley wrote: > > Because the count is having issues, I'll do manual counts on top posters: > > --- In FairfieldLife@yahoogroups.com, FFL PostCount<ffl.postcount@...> wrote: >> Fairfield Life Post Counter >> =========================== >> Start Date (UTC): Sat Jul 30 00:00:00 2011 >> End Date (UTC): Sat Aug 06 00:00:00 2011 >> 210 messages as of (UTC) Sun Jul 31 23:46:20 2011 >> >> 28 authfriend<jstein@...> > This is accurate. > >> 20 Buck<dhamiltony2k5@...> > Actual count: 21 > >> 14 RoryGoff<rorygoff@...> > Actual count: 18 > >> 13 turquoiseb<no_re...@yahoogroups.com> > Actual count: 16 > >> 13 Mark Landau<m...@sky5.com> > Actual count: 15 > >> 12 whynotnow7<whynotnow7@...> > Actual count: 24 > >> 11 Tom Pall<thomas.pall@...> > Actual count: 13 > >> 3 Ravi Yogi<raviyogi@...> > Since he raised the issue, actual count: 9
It's actually pretty easy to add missing header information into the header file. Just back it up and then edit it copying a header of someone who has missing email headers and insert them. For instance for Ravi you would find one of his message headers, copy both lines and then insert them 6 times. What you really need is the section that generates the report broken out so you can test if it works or not. It would just parse the header file and write the report without downloading any new headers nor emailing it out. Technically running the script should not mess up the count. However given we get error messages like these from Yahoo when they "supposedly" can't deliver and email doesn't give us much confidence in their software: Hi. This is the qmail-send program at m10.grp.re1.yahoo.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <fairfieldlife@yahoogroups.com>: ylock initialization failure: You may need "yinst start ylock_kern" to load kernel module. Abort trap (core dumped) I'm not going to try again; this message has been in the queue too long. -- It reads like some manager scolded the programmer for making the error message too terse so the programmer wrote a goofy one. Or the programmer is 16 years old. :-D
