<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>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.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Perhaps there is another way?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Michael<o:p></o:p></p><p class=MsoNormal>N6MEF<o:p></o:p></p></div></body></html>