Hello mark,

On Friday February 27 2015 03:24, you wrote to me:

 MvdV>>> It can, but thatis the exception.

 ml>> really? when most systems use XXXXYYYY.mo1 naming for their mail
 ml>> bundles?

Really?

 MvdV>> ArcMail naming convention? That's as archaic as ARC itself.

 ml> really? that is the basis of BSO file names...

All of the tossers I ever used, employed fifferetn naming schemes for
compressed mail. And so they were are listed in the flo files.

 ml> flo files are named in this manner as are .req files... files that do
 ml> not follow this naming method must be listed inside the flo file...

The latter apllies to all tghe compressed mail bundles that my tossers produce.

 ml>> you get your statistics from which gov't agency?

 MvdV>> I see what goes in and out of my system.

 ml> ok... so 99.99% of the traffic on /your/ system...

Of which over 95% originates from other systems.

 ml>>> then you loose the timing capability...

 MvdV>>> I can not loose what I never had.

 ml>> you've always had it...

 MvdV>> Not for any of my BSO mailers.

 ml> yes you have... it is inherent in the naming of the flo files...

It only applies for mailers that follow that naming convention. Binkd does not.
It assumes that all systems that are not hold are CM and that itself may always
send, so it makes no disctinction between flo, clo, ilo and dlo.

I can not loose what I never had.

 ml>>  dynamic mailers built on it in their feature capabilities...

 MvdV>> We are not discussing dynamic mailers. We are discussing the
 MvdV>> BSO mailer binkd.

 ml> no shit, sherlock... we're also discussing mailers in general... that
 ml> make three topics going on in here...

Maybe others are discussing mailers in general, *I* amm not. Se "we" are not.

 ml>>  just because you didn't know you had it doesn't mean that you
 ml>> haven't had it the whole time...

 MvdV>> I know that the dynamic mailers that I have used had it. But
 MvdV>> dynamic mailers is not what we are discussing here.

 MvdV>> Binkd does not have it and it is the only BSO mailer that I
 MvdV>> ever used.

 ml> binkd /does/ have it... it has it in the same manner that all BSO
 ml> mailers have had it since opus and binkleyterm were birthed into this
 ml> network...

No, it does not, It makes no disctintion bewteen flo, ilo, clo and dlo.

 MvdV>> I am aware of the differences bewteen dynamic mailers and BSO
 MvdV>> style mailers. It is one of the reasons why I hesitated so long
 MvdV>> in converting my system from dynamic to BSO. I made the plunge
 MvdV>> anyway because it was the only way to get Fido over IP6.

 ml> i know the feeling on converting... it is the reason why i run a
 ml> hybrid setup...

When I dump something I don't look back. I move on. Whan I swicthed form AMA to
BSO, I made a fresh start. No hybrid setup for me.

 MvdV>> It was a steep learning curve, but now that I took that hurdle
 MvdV>> I do not regret it. It was an opportinuty to clean out a lot of
 MvdV>> no longer needed ballast.

 ml> you are still learning, though... BSO has more fiddling and messing
 ml> about behind the scenes than you are apparently aware of... this
 ml> "timing" thing is one of those... how does it work? a flo file is set
 ml> as hlo /or/ its extension is changed to something other than standard
 ml> flo file extensions... that causes the associated files to sit on the
 ml> system until such time as the hlo or non-?lo extension is changed...

That is not how it works on my system.

 ml>> exactly... the timing is controlled by the naming of the flo
 ml>> file... direct, immediate and crash are affected by the event
 ml>> manager...

 MvdV>> Binkd has no event manager.

 ml> you still have some sort of event manager there... if you didn't you
 ml> couldn't schedule polls or know when to toss mail...

My system runs on a strict crashme/crashyou regime. Mail is tossed when mail
comes in. If that results in mail that is to be send out, it is send out right
away. I do not make scheduled polls. If you want to get mail from your system
tio mine, you have to come bring it yourself. Don't like it? Find another link.

 ml>> so the timing is performed by having a hlo until the desired time
 ml>> is reached when it is renamed to flo, dlo, ilo, or clo...

 MvdV>> That is needlessly complicated.

 ml> needlessly complicated??!?

Yes. No need for it any more in the 21st century environment that binkd runs
in. No need to hold it until the time comes to send. Just send it.

 ml> bite your tongue, man! /that's/ specifically why dynamic mailers were
 ml> so popular!! there is no other way to do this in a BSO environment...
 ml> it is inherent in the design...

I have left all that behind and it looks like I am not the only one. Scheduling
mail events was needed in the POTS age when making a call cost money and so you
wanted to collect mail and send it out or pick it up only a limited times a
day.

But Fido over IP is different. There is no cost in making a call. The line is
always open. No more need for scheduling mail.

There still is need for scheduling a few other things though. I have a dialy
sysyem clean up event and  have a weekly event that hatches the R28 point list.
In the DOS age, there was no event manager that came with the OS, so the
mailers had event managers to start events. No longer needed either. The
Windows task manager does fine.

 MvdV>> When one uses an event manager, one might as well have it place
 MvdV>> the .req in the outbound when the time arises. hat is if one
 MvdV>> has a need to do that for .req files at all.

 ml> that's another way to do it...

So renaming flo files from hlo to flo, clo, ilo or dlo is not the only way to
do it as you claimed above.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111