| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | bbs was Re: Addy. |
NB> IIRC, the Bluewave door was* based on the areaname. I know NB> there were some BW-compatible doors (not the original GH NB> ones) that were still working after the Y2K fixes.. maybe on the areaname assigned by the sysop but not the fidonet echotag (again, unless assigned by the sysop)... the problem with some software is that it uses areas based on number... the hudson message base format is like this... it has areas from 1 to 200 (by the spec)... trying to tie those areanumbers to the area name is the problem... and then you have those systems that give the area an "english spoken area name" instead of the areatag so that their users will know what the area is about... so that leaves us with something like this... area# 42 == BLUEWAVE == Bluewave Offline Mail Reader Discussions or some such... the problem is tieing all those together to mean the same thing... RemoteAccess is one of those bbs packages that don't offer an additional field in the message base configs that can be used as the bluewave (or rather offline mail) are name and one can't rely on the descriptive area name for the link... in the case of RemoteAccess (and many other software packages), we need an additional field that can contain, for instance, the echotag or the area... then, the offline mail door needs to coordinate between the areaname and the stored area number for the placement of the messages... NB> EleBBS NB> had one built in that handled BW packets natively, not as QWK NB> packets. (That's what my last local homebase bbs was using NB> before he closed down...) elebbs is supposedly a dropin replacement for RA... however, its not up to the latest RA beta's specs in this regard... at least not to my knowledge... ML>> there was a point package designed for this way back but i ML>> cannot remember what it was called... it was a competitor ML>> with BW, QWK, OPX and SOUP... heck, it might have been OPX ML>> but i doubt it... in any case, it had a mailer function that ML>> tapped the boss node's mailer and pulled the mail bundles ML>> just like another node would do... then it unarchived the ML>> messages and you read and replied to them... when done, it ML>> would create a bundle of replies to upload back to the boss ML>> node's mailer... it didn't matter if the message areas ML>> changed or not because it all operated outside the bbs... ML>> the mail was tossed and scanned just like any other fido ML>> node's... it just makes sense OB-) NB> That wasn't Martin Pollard's OMX was it? Dan Ceppa's still NB> using that to do his BW packets... :) i don't recall, actually... i seem to recall that it was out before QWK really got a foothold in fidonet... the biggest problem facing it was that it was incompatible with the QWK readers that many folk were using from the RIME/PCRelay network connected boards and those that just offered offline mail that had compatible doors and software... i'll have to dig into my old 5.25 1.2meg floppies and see if i can locate it... it should still work just fine with today's software barring any y2k and fast processor problems ;) even the, i'm sure that there is existing stuff that can handle that to make it work... if i can locate it, i'll see what i may be able to do to test it out... its definitely not "fancy" like BW > )\/(ark* Origin: (1:3634/12) SEEN-BY: 633/267 270 @PATH: 3634/12 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.