Hello,

Is there anybody out there? I am having an issue importing an echolist on 1.46 & 1.46.1. Any words??



Regards,
Phil
t1b.bayhaus.org

... An Elephant; A Mouse built to government specifications.

--- MBSE BBS v0.95.6 (FreeBSD-i386)
* Origin: bayhaus.org >> Serving the Front Range (1:128/2)

Hi! Phil,

In a message to All you wrote:

Is there anybody out there? I am having an issue importing an
echolist on 1.46 & 1.46.1. Any words??

Show us yer legs... ermm, logs. ;-)

Frankly it's been so l-o-n-g since I last used that function that when I saw your question I thought that the operation was impossible. Thanks for reminding me.

Here's what the manual says on the matter...

-----8<-----C-U-T--H-E-R-E----->8-----
FESetup -IE<File> [-O]

This switch is provided in order to simplify the operation of
import the EchoMail area description from a standard fidonet echo area
descriptions called Echolist (FIDONET.NA). You can do the same opera-
tion internally, by means of the "Import" DropDown-menu. If used in
conjunction with the -O switch, the already-existent description pre-
sents in FastEcho.cfg will be automatically overwritten. I.E. assuming
that you want automatic import in your FastEcho configuration the
description present in standard file FIDONET.NA overwriting all the
existing descriptions, you have to layout the following command:

FESetup -IEFIDONET.NA -O

Note that there isn't -any space- between the -IE switch and the file-
name FIDONET.NA (that's mandatory).
-----8<-----C-U-T--H-E-R-E----->8-----

What's -not- happening, Phil?

Cheers,
Paul.

---
* Origin: Gotta go! HAL shut off the life support system again!! (3:640/384)

Paul Quinn wrote to Phil Kimble:

Hi! Phil,

Hi Paul!! Thansk for the fast response.

Show us yer legs... ermm, logs. ;-)

Only for a pint of yer finest ale!

Frankly it's been so l-o-n-g since I last used that function that when I saw your question I thought that the operation was impossible. Thanks for reminding me.

Here's what the manual says on the matter...

Read it, performed it, as a command on the command line & drop-down menu. Exported the existing areas to research format & no luck.

What's -not- happening, Phil?

It no workie-workie. The fidonet.na file exists in the \FE directory & when I atempt to import it regardless of method, it reports "0 descriptions imported".
It fails to create the areas or import descriptions.

So before I trudge through the manual creation of 300 echo areas, I would like to investigate to see if anyone else has the same problem & possible solution.




Regards,
Phil
t1b.bayhaus.org

... (A)bort, (R)etry, (P)retend this never happened...

--- MBSE BBS v0.95.6 (FreeBSD-i386)
* Origin: bayhaus.org >> Serving the Front Range (1:128/2)

Paul Quinn wrote to Phil Kimble:

-----8<-----C-U-T--H-E-R-E----->8-----
FESetup -IE<File> [-O]

This switch is provided in order to simplify the operation of
import the EchoMail area description from a standard fidonet echo area
descriptions called Echolist (FIDONET.NA). You can do the same
-----8<-----C-U-T--H-E-R-E----->8-----

Is this to say it wont import the echolist & 'automagically' create the areas? In other words, I have to create the areas & this will only import the descriptions?

I havent used FastEcho since about 1996 so I am a little foggy... More than noral, that is.

m

Regards,
Phil
t1b.bayhaus.org

... "Build a watch in 179 easy steps" by C. Forsberg.

--- MBSE BBS v0.95.6 (FreeBSD-i386)
* Origin: bayhaus.org >> Serving the Front Range (1:128/2)

Hi! Phil,

On Tue, 09 Aug 11, you wrote to me:

FESetup -IE<File> [-O]

Is this to say it wont import the echolist & 'automagically' create
the areas? In other words, I have to create the areas & this will
only import the descriptions?

That's probably true. Though the import of an Areas.Bbs file looks promising as a way to actually create the areas. It looks to be a two-step process to auto-create areas: import Areas.Bbs, then import the echolist.

You still have the option to have an _uplink_ (in FEsetup) send you new echoes with the auto-create option set, so that areas are created as traffic for those
areas comes through. You can always generate traffic by sending an areafix "rescan" netmail to the uplink. Later, as a second step, then import the echolist/backbone.na descriptions.

The second method works. I'm not sure of the Areas.Bbs & echolist import thingamajig.

I havent used FastEcho since about 1996 so I am a little foggy...
More than normal, that is.

I'm having the same trouble (remembering), Phil; my config started in mid-94, as a point. BTW, I was feeling brave (haven't finished my first coffee) when I
read your replies, and did an import using the (FEsetup) menu option with the latest Backbone.Na file: "124 descriptions imported" fine. There's a lot of areas that still don't have descriptions in them but at the least the existing ones weren't harmed.

Cheers,
Paul.

---
* Origin: "Yeah, I wrote it but it's Jimi's song." - Dylan. (3:640/384)

Is there anybody out there? I am having an issue importing an
echolist on 1.46 & 1.46.1. Any words??

importing an echolist? what problems?

)\/(ark
member, FastEcho Beta Team


* Origin: (1:3634/12)

mark lewis wrote to Phil Kimble:

Is there anybody out there? I am having an issue importing an
echolist on 1.46 & 1.46.1. Any words??

importing an echolist? what problems?

I wouldnt call it a problem with FE as much as it is my misunderstanding of the
import function. Under FE, the import echlist only imports the descriptions. It does not import the areas & auto-create them based on a templatte area.

Using Paul's recommendation & some testing to re-learn how it really does work,
I use my mail hub to import & auto-create the message areas. Them import the echolist to populate the descriptions. Works pretty well.



Regards,
Phil
t1b.bayhaus.org

... A Smith & Wesson *ALWAYS* beats 4 Aces.

--- MBSE BBS v0.95.6 (FreeBSD-i386)
* Origin: Serving the Front Range (1:128/2)

mark lewis wrote to Phil Kimble:

Is there anybody out there? I am having an issue importing an
echolist on 1.46 & 1.46.1. Any words??

importing an echolist? what problems?

I wouldnt call it a problem with FE as much as it is my
misunderstanding of the import function. Under FE, the import
echlist only imports the descriptions. It does not import the
areas & auto-create them based on a templatte area.

ahhh, yes... this is correct... bringing in the areatags is done by importing an areas.bbs, IIRC... but a long long long time ago, i found it easier to allow
FE to automatically add areas from my main feed(s) which are seperated by groups... then, if i want to pull the descriptions in, i can... however, i've also found that the descriptions leave a bit to be desired so i basically use only the areatag any more...

for example, i can now tell when i'm in COFFEE_KLATSCH instead of trying to figure out what area "Gossip and chit-chat echo" represents... especially when CHATTER ("Mindless Chatter Conference") and MEMORIES ("NOSTALGIA") exist and carry similar traffic... well, CHATTER really does carry "mindless" chit-chat ;) it always takes me a minute to remember that the description "NOSTALGIA" is
the MEMORIES echo...

Using Paul's recommendation & some testing to re-learn how it
really does work, I use my mail hub to import & auto-create the
message areas. Them import the echolist to populate the
descriptions. Works pretty well.

yup... and then you get those areas with long descriptions and some tools that use them (ie: sysop message reader, BBS areas that are imported in the same way) chop off the descriptions because they have a 45 character limit or such... all in all, it is a decent idea and it was fulfilled by authors at the requests of their customers but somewhere along the lines, someone forgot to create some type of spec document for everyone (ie code authors and echoarea moderators) to follow so that no descriptions were too long ;)

)\/(ark
member, FastEcho Beta Team


* Origin: (1:3634/12)

I've configured FastEcho I think as it should be but I keep getting this
error message when I run fastecho scan.

"Can't export message in area FIDOTEST without active downlinks."

I went to node configuration and entered info for my uplink, But I will not have any downlinks.

Any help and is this still registerable?

Ruben Figueroa aka Zazz
Mystic Prison Board Sysop
telnet://pbmystic.rdfig.net:24
Web: www.rdfig.net

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Mystic Prison Board*Mesquite Tx*pb.darktech.org:24 (1:124/5014)

On 2019 Jul 16 18:03:54, you wrote to All:

"Can't export message in area FIDOTEST without active downlinks."

I went to node configuration and entered info for my uplink, But I will

not

have any downlinks.

a link is both up and down... you must have at least one system linked... generally this will be the one link you get your mail for the area from... thus
"downlink" since you are "down stream" from them...

Any help and is this still registerable?

yes... fill out the application form and send it to toby...

https://www.softeq.de/old/Products/FastEcho/fastecho.html

use the author link at the top of the page in the first paragraph... he does have a fidonet address but the web/email will likely work better/faster...

)\/(ark

And to this end they built themselves a stupendous super-computer which was
so amazingly intelligent that even before its data banks had been connected
up it had started from "I think therefore I am" and got as far as deducing
the existence of rice pudding and income tax before anyone managed to turn
it off.
... It is further to Chicago than by bus.
---
* Origin: (1:3634/12.73)

a link is both up and down... you must have at least one system linked... generally this will be the one link you get your mail for the area
from... thus "downlink" since you are "down stream" from them...

Found out where to link messages to the uplink so traffic is flowing.

yes... fill out the application form and send it to toby...

https://www.softeq.de/old/Products/FastEcho/fastecho.html

use the author link at the top of the page in the first paragraph... he does have a fidonet address but the web/email will likely work better/faster...

Well I did email, a couple of times, been a few days, but I didn't send in
the application so I'll do that now.

Thanks

Ruben Figueroa aka Zazz
Mystic Prison Board Sysop
telnet://pbmystic.rdfig.net:24
Web: www.rdfig.net

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Mystic Prison Board*Mesquite Tx*pb.darktech.org:24 (1:124/5014)

I use fastecho to toss my mail after Irex receievees the packets.
It toss toss them just find according to FE.LOG file. But I do not see them in ProBoard.

I check ProBoard logs but they do not show if any echo mail is tossed

How can I figure out what is happening?

--- ProBoard v2.30-A1u4
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)

On 28 Jul 2023 at 06:38p, Zazz pondered and said...

I use fastecho to toss my mail after Irex receievees the packets.
It toss toss them just find according to FE.LOG file. But I do not see them in ProBoard.

I check ProBoard logs but they do not show if any echo mail is tossed

How can I figure out what is happening?

could it be a packet password thing?

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

I use fastecho to toss my mail after Irex receievees the packets.
It toss toss them just find according to FE.LOG file. But I do not

see

No, I had to set netmail message board

The I saw in inbound folder archives not recognized

--- ProBoard v2.30-A1u5
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)