[nos-bbs] Old BIDs

[Michael Fox - N6MEF]

Thanks Jack.  Can you explain further?  

Specifically:

1) What is the recommended value?  In other words, is there a convention used by most sysops for how old is too old to be forwarding around?  A week?  A month? ...

2)  Whatever the value, I'm thinking that oldbid should be set to at least that value.  For example:

	autoexec.nos:
		bulletin holdold 183  # 6 months
		oldbid 24 183

The result being:  anything less than 6 months old would be subjected to a history check and anything older than that would go to hold.  Does that make sense?

3) When "bulletin holdold" puts the message in hold, does it literally put it in the "hold" mailbox?  And, if so, then I presume I can set an expiry time for the hold mailbox to the same value to get rid of it?  For example:

	autoexec.nos:
		bulletin holdold 183

	expire.dat:
		hold	183

Does that make sense?

Thanks,
Michael



> -----Original Message-----
> From: nos-bbs [mailto:nos-bbs-bounces at tapr.org] On Behalf Of Jack Eifer
> Sent: Thursday, February 9, 2017 1:04 AM
> To: TAPR xNOS Mailing List <nos-bbs at tapr.org>
> Subject: Re: [nos-bbs] Old BIDs
> 
> On Jnos:
> 
> 'Bulletin holdold <n days>'
> 
> 
> > On Feb 9, 2017, at 12:08 AM, Gustavo Ponza <g.ponza at tin.it> wrote:
> >
> >
> >
> >> On 02/08/2017 05:42 PM, Michael Fox - N6MEF wrote:
> >> I was contacted yesterday by an FBB sysop because a bunch of old (> 1
> year)
> >> WP bulletins have been flooding him.  The source of the old bulletins
> is
> >> probably someone restoring an old backup.
> >>
> >>
> >>
> >> But the issue is that they're being forwarded around the net over RF
> links.
> >> According to the FBB sysop, FBB immediately expires them upon receipt.
> So
> >> it does not forward these old bulletins to others.  But, evidently,
> other
> >> BBSs do not do that.
> >>
> >>
> >>
> >> My understanding of JNOS is that expiry occurs as an "at" job.  I
> currently
> >> run it twice a day.  But even if it ran every hour, it still wouldn't
> stop
> >> such forwarding, since I might receive an old bulletin one minute and
> then
> >> connect to many other BBSs before the next hourly expiry function.
> >>
> >>
> >>
> >> One way to stop it would be to keep longer history.  I currently have
> JNOS
> >> set to keep 6 months of history.  But even a whole year of history
> wouldn't
> >> have stopped the current case because the bulletins were > 1 year old.
> >>
> >>
> >>
> >> Back in the 80s, CPU power and disk speed were not the same as today.
> With
> >> the capabilities of today's machines, I'm wondering if it makes sense
> for
> >> JNOS to perform expiry on the fly.  That is, it would use the current
> >> rewrite process to determine the destination mailbox, and then look up
> the
> >> expiry interval for that mailbox, and, if the message is expired, then
> not
> >> save it to the mailbox.
> >>
> >>
> >>
> >> Perhaps there is another way?
> >>
> >>
> >>
> >> Michael
> >>
> >> N6MEF
> >
> > The two basic methods I know are the 'epurmess' method
> > implemented by WA7MBL/F6FBB and similar oriented PBBSs
> > and the one perhaps more efficient/sophisticated
> > 'purge/reorg' method adopted by the obcm and other
> > German PBBSs.
> >
> > --
> >
> > 73 and ciao, gus i0ojj
> > A proud member of linux team
> > _______________________________________________
> > nos-bbs mailing list
> > nos-bbs at tapr.org
> > http://www.tapr.org/mailman/listinfo/nos-bbs
> 
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs