Hiya DM....

OK... forget the last message... I figured out a work-around. Instead of creating a semaphore, I used binkd's 'EXEC' section to run ./sbbsecho on incoming pkts/ and it's working fine. I just couldn't understand how it
was working one day and not the next. Gremlins... lol

Thanks for everything...


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net:81
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: 6697
Radio: radio.tequilamockingbirdonline.net:8010/live

... Look TWICE.... Save a life.... Motorcycles are EVERYWHERE!!

---
* Synchronet * TequilaMockingbird Online - Toms River, NJ
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hello Bill,

On Wed Feb 08 2017 10:52:42, Bill McGarrity wrote to Digital Man:

OK... forget the last message... I figured out a work-around. Instead
of creating a semaphore, I used binkd's 'EXEC' section to run
./sbbsecho on incoming pkts/ and it's working fine. I just couldn't understand how it was working one day and not the next. Gremlins...
lol

Did you take a look at your sbbsecho logs when that timed event runs? Is there a "fidoin.now" that exists in your data directory already? If so, you may have to remove it and restart sbbs.

In order for semaphores to work properly, I would imagine you would at least need the sbbs daemon running, ie: ./sbbs -d (even though you can probably disable some services in services.ini).

Regards,
Nick

... "-Y-| -+-+-#-A. -> -+-|-|-U-i -e-+-+-i-|-+ -C-#-#-+-e-#-A."
--- GoldED+/LNX 1.1.5-b20161221
# Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
* Synchronet * thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hiya Nick..

Accession wrote to Bill McGarrity <=-

On Wed Feb 08 2017 10:52:42, Bill McGarrity wrote to Digital Man:

OK... forget the last message... I figured out a work-around. Instead
of creating a semaphore, I used binkd's 'EXEC' section to run
./sbbsecho on incoming pkts/ and it's working fine. I just couldn't understand how it was working one day and not the next. Gremlins...
lol

Did you take a look at your sbbsecho logs when that timed event runs?
Is there a "fidoin.now" that exists in your data directory already? If
so, you may have to remove it and restart sbbs.

I did everything, three times I complete deleted SBBS and reinstalled/compiled it. It does take awhile to compile... :)

In order for semaphores to work properly, I would imagine you would at least need the sbbs daemon running, ie: ./sbbs -d (even though you can probably disable some services in services.ini).

Yes, it was running but after many head bumps on the kb I finally came up with a solution and that was to toss the semapohe binkd creates and just yse it's 'EXEC" section. now I don't even have to run the daemon, sbbsecho can be run standalone... :)

Thanks!!


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net:81
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
--- MultiMail/Win32 v0.50
* Synchronet * TequilaMockingbird Online - Toms River, NJ
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hiya DM....

OK, I updated off the cvs this afternoon and followed all the update steps
off the wiki. Nick even sent me his update bash script and it showed it updated everything correctly. One issue, doesn't seem to have updated sbbsecho.

From my logs...

SBBSecho v3.00-Linux (rev 3.28)

It's still dated Feb 8 2017 as well....

For now I removed the Additional echolist.

Let me know...

Thanks...


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net:81
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: 6697
Radio: radio.tequilamockingbirdonline.net:8010/live

... Look TWICE.... Save a life.... Motorcycles are EVERYWHERE!!
--- SBBSecho 3.00-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Re: sbbsecho
By: Bill McGarrity to digital man on Fri Feb 24 2017 11:35 pm

Hiya DM....

OK, I updated off the cvs this afternoon and followed all the update steps off the wiki. Nick even sent me his update bash script and it showed it updated everything correctly. One issue, doesn't seem to have updated sbbsecho.

You missed a step somewhere then.

digital man

Synchronet/BBS Terminology Definition #39:
REP = QWK Reply
Norco, CA WX: 61.1oF, 41.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Digital Man wrote to Bill McGarrity on 02-25-17 12:29 <=-

@VIA: VERT
@MSGID: <58B1E91A.39461.sync_sys@vert.synchro.net>
@REPLY: <58B10A25.39458.sync_sys@vert.synchro.net>
@TZ: 41e0
Re: sbbsecho
By: Bill McGarrity to digital man on Fri Feb 24 2017 11:35 pm

Hiya DM....

OK, I updated off the cvs this afternoon and followed all the update steps off the wiki. Nick even sent me his update bash script and it showed it updated everything correctly. One issue, doesn't seem to have updated sbbsecho.

As I said, Nick gave me his bash script to run after I didn't have any luck. That really didn't work probably because I already started the process and it was fubar'd so I just did a rm -R sbbs and started all over... lol. Whats an hour among friends... :)

Thanks again...


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net:81
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
--- MultiMail/Win32 v0.50
* Synchronet * TequilaMockingbird Online - Toms River, NJ
* Origin: Vertrauen - vert.synchro.net (1:103/705)

On 2017 May 02 09:23:24, you wrote to All:

When I run SBBSECHO -LINF, it complains "unrecognized internal code, assumed passthrough".

have you added FIDO to your area definitions as the internal code??

eg: (hand typed since i can't copy'n'paste the scfg screen)

================================================
Fidonet Group
================================================
Long Name Fidonet Backbone Areas
Short Name Fidonet

Internal Code Prefix FIDO-

Access Requirements LEVEL 50
Clone Options
Export Areas...
Import Areas...
Message Sub-Boards...
================================================

FIDO_SYNCSYSO SYNC_SYSOPS 1:3828/7

looks like you are using FIDO_ as your Internal Code Prefix

then there's the Sub-Board definitions which also contain an Internal Code... that code is made of the above Internal Code Prefix and the Sub-Board's Short Name...

eg: (hand typed again)

================================================
10th AMD Sub-Board
================================================
Long Name 10th Amendent
Short Name 10TH AMD
QWK Name 10TH AMD

Internal Code FIDO-10TH_AMD

[...]
================================================

This appears to have been imported to c:\sbbs\ctrl and now reads:

/sbbs/echomail\FIDO_SYNCSYSO SYNC_SYSOPS 1:3828/7

What am I missing that will get sbbsecho to scan, pack and unpack?

i don't know why you have the mixed slashes in your AREAS.BBS file... check your path to your areas... my understanding is that they are stored on disk in /sbbs/data/subs...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... We are what we are.
---
* Origin: (1:3634/12.73)

Joe wrote to All on 05-02-17 09:23 <=-

mark lewis seems to ahve covered most in his post but I'll add my two cents.

I am setting up Fidonet on SBBS. I hav successfully imported areas.bbs
and all looks good in the BBS. I have Binkdwin setup and it polls my uplink ok. My problem appears to be packing/unpacking mail.

When I run SBBSECHO -LINF, it complains "unrecognized internal code, assumed passthrough".

IF you are using version 3 of sbbsecho, you no longer need to use the -LINF as everything those options do is not defaulted. To get a list of the options now, in a cmd prompt, type: sbbsecho -?

Here is the format of one echoarea in c:\sbbs\exec\areas.bbs:

Your areas.bbs should be in the ../sbbs/data folder.

FIDO_SYNCSYSO SYNC_SYSOPS 1:3828/7

This appears to have been imported to c:\sbbs\ctrl and now reads:

/sbbs/echomail\FIDO_SYNCSYSO SYNC_SYSOPS 1:3828/7

When you create the different echomail folders in SCFG, they are saved to the folder ../sbbs/data/subs

What am I missing that will get sbbsecho to scan, pack and unpack?

So in review, make sure you created the correct echo group using SCFG under Message Areas, Set the internal code (which as mark pointed out seems to be FIDO), inport the *.NA file and then edit each of the sub-boards that were imported...

Here are my screens..

Group (notice the internal code. I use 2, you use Fido)

+[a][?]----------------------------------------------------+
a Fidonet Group a a----------------------------------------------------------a
a aLong Name Fidonet a
a aShort Name Fidonet a
a aInternal Code Prefix 2 a
a aAccess Requirements LEVEL 50 a
a aClone Options a
a aExport Areas... a
a aImport Areas... a
a aMessage Sub-boards... a

Message Sub-boards

+[a][?]-------------------------------------+
a Fidonet Sub-boards a a-------------------------------------------a
a aAllfix File Announce a
a aI'ntl ALLFIX Support a
a aWhacko Teabagger Politics - Dangerous! a
a aAMATEUR / HAM Radio a
a aAutomotive a
a aBASH Discussion Forum a
a aInternational Bible Conference a
a aThe ubiquitous BinkD TCP/IP Mailer a
a aConspiracy Discussions a
a aControversial Topics, Current Events a
a aPolitics and Current Events a
a aDads a
a aDEBATE Conference a
a aInternational Dog Lovers a
a aBBS Doorgames and Discussions a
a .aAdvertise FIDONet Echos Here a +-------------------------------------------+

Individual Sub-board:

+[a][?]----------------------------------------------------+
a ALLFIX_FILE Sub-board a a----------------------------------------------------------a
a aLong Name Allfix File Announce a
a aShort Name ALLFIX_FILE a
a aQWK Name Allfix a
a aInternal Code 2ALLFIXFI a
a aNewsgroup Name a
a aAccess Requirements LEVEL 50 a
a aReading Requirements a
a aPosting Requirements a
a aOperator Requirements a
a aModerated Posting User a
a aMaximum Messages 10000 a
a aPurge by Age Disabled a
a aDuplicate Checking Enabled (10000 message CRCs) a
a aToggle Options... a
a aNetwork Options... a
a aAdvanced Options... a


Now notice the Internal code now. Here is saYs 2ALLFIXFI and the short name: ALLLFIX_FILE.

An exported areas.bbs would look like this:

2ALLFIXFI..ALLFIX_FILE..X:XXX:XXX

Network Options:

+[a][?]----------------------------------------------------+
a Network Options a a----------------------------------------------------------a
a aAppend Tag/Origin Line Yes a
a aExport ASCII Only Yes a
a aGate Between Net Types No a
a aQWK Networked No a
a aQWK Tagline a
a aInternet (UUCP/NNTP) No a
a aPostLink or PCRelay No a
a aFidoNet EchoMail Yes a
a aFidoNet Address Your address here a
a aEchoMail Origin Line a +----------------------------------------------------------+

Make sure in ECHOCFG you tell it where ALL the netmail, incoming and outgoing folders are.

That should do it..

Enjoy...






--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
=== MultiMail/Win32 v0.50
--- SBBSecho 3.00-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Hello All

I am setting up Fidonet on SBBS. I hav successfully imported areas.bbs and all looks good in the BBS. I have Binkdwin setup and it polls my uplink ok. My problem appears to be packing/unpacking mail.

When I run SBBSECHO -LINF, it complains "unrecognized internal code, assumed passthrough".

Here is the format of one echoarea in c:\sbbs\exec\areas.bbs:

FIDO_SYNCSYSO SYNC_SYSOPS 1:3828/7

This appears to have been imported to c:\sbbs\ctrl and now reads:

/sbbs/echomail\FIDO_SYNCSYSO SYNC_SYSOPS 1:3828/7

What am I missing that will get sbbsecho to scan, pack and unpack?

Thank you.

Joe Bruchis

---
* Synchronet * Fire on the Bayou - bayouflames.ddns.net
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Joe wrote to All <=-

When I run SBBSECHO -LINF, it complains "unrecognized internal code, assumed passthrough".

That means that the internal code doesn't match any you have on the system. The internal code includes both the internal code prefix for the group, and the internal code suffix setup in the individual sub configuration.

Here is the format of one echoarea in c:\sbbs\exec\areas.bbs:

FIDO_SYNCSYSO SYNC_SYSOPS 1:3828/7

Here's mine, for comparison.

FIDO-SYNCSYSO SYNC_SYSOPS 3:633/280

Now, I have an internal code prefix of "FIDO-", which gets prepended to all of my Fidonet subs, which is a handy way to avoid internal code conflicts when importing echoes in bulk for a new network.

This appears to have been imported to c:\sbbs\ctrl and now reads:

/sbbs/echomail\FIDO_SYNCSYSO SYNC_SYSOPS 1:3828/7

FIDO-SYNCSYSO SYNC_SYSOPS 3:633/280

What am I missing that will get sbbsecho to scan, pack and unpack?

You need to make sure that AREAS.BBS matches your configuration exactly. Easiest way to do that is to export AREAS.BBS when all of your message ares are setup in scfg.


... A life? Where can I download that?
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

When I run SBBSECHO -LINF, it complains "unrecognized internal code, assumed passthrough".

Here is the format of one echoarea in c:\sbbs\exec\areas.bbs:

FIDO_SYNCSYSO SYNC_SYSOPS 1:3828/7

I think your internal code tag is too long. I think you are limited to 8 or
10 characters. So, it is not able to match the internal code on that line
with any of the internal message area codes you set up in SCFG.

Your first entry there, FIDO_SYNCSYSO, is too long to be a proper internal message area code. Make sure it matches what you have set up in SCFG for
that area and it should recognize it.

Mike

---
* SLMR 2.1a * If you chose not to decide, you still have made a choice!
* Synchronet * CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Mike Powell wrote to JOE <=-

I think your internal code tag is too long. I think you are limited to
8 or 10 characters. So, it is not able to match the internal code on
that line with any of the internal message area codes you set up in
SCFG.

Not if you're using a prefix. My internal code is exactly the same length and only one character different, and works perfectly.


... If something is confidential, it'll be left in the copier.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Bill McGarrity wrote in a message to Joe:

Joe wrote to All on 05-02-17 09:23 <=-

mark lewis seems to ahve covered most in his post but I'll add my
two cents.

Yes. Mark's comments were helpful.

I am setting up Fidonet on SBBS. I hav successfully imported areas.bbs
and all looks good in the BBS. I have Binkdwin setup and it polls my uplink ok. My problem appears to be packing/unpacking mail.

When I run SBBSECHO -LINF, it complains "unrecognized internal code, assumed passthrough".

IF you are using version 3 of sbbsecho, you no longer need to use
the -LINF as everything those options do is not defaulted. To get
a list of the options now, in a cmd prompt, type: sbbsecho -?

I will download version 3.

Network Options:

This is where my problem was found. I had not configured the line that required
my node number.

Make sure in ECHOCFG you tell it where ALL the netmail, incoming
and outgoing folders are.

That should do it..

Yes that did it. Thank you!

Regards,

Joe
--- timEd/386 1.10+
* Origin: Fire on the Bayou BBS:telnet/http:bayouflames.ddns.net (1:3828/12)

mark lewis wrote in a message to Joe:

FIDO_SYNCSYSO SYNC_SYSOPS 1:3828/7

looks like you are using FIDO_ as your Internal Code Prefix

i don't know why you have the mixed slashes in your AREAS.BBS
file... check your path to your areas... my understanding is that
they are stored on disk in /sbbs/data/subs...

When I imported an AREAS.BBS file, they appeared there after import. In any event, I have it corrected to the correct path now.

The actual problem of not being able to scan/pack was an overlooked line in the
network config portion in sbbsecho.cfg. Bill posted his config and there I noted my error.

Thank you and to everyone that replied with assitance.

Regards,

Joe
--- timEd/386 1.10+
* Origin: Fire on the Bayou BBS:telnet/http:bayouflames.ddns.net (1:3828/12)

Joe Bruchis wrote to Bill McGarrity on 05-04-17 06:02 <=-

Bill McGarrity wrote in a message to Joe:

Joe wrote to All on 05-02-17 09:23 <=-

mark lewis seems to ahve covered most in his post but I'll add my
two cents.

Yes. Mark's comments were helpful.

They usually are.. :)

I am setting up Fidonet on SBBS. I hav successfully imported areas.bbs
and all looks good in the BBS. I have Binkdwin setup and it polls my uplink ok. My problem appears to be packing/unpacking mail.

When I run SBBSECHO -LINF, it complains "unrecognized internal code, assumed passthrough".

IF you are using version 3 of sbbsecho, you no longer need to use
the -LINF as everything those options do is not defaulted. To get
a list of the options now, in a cmd prompt, type: sbbsecho -?

I will download version 3.

Just remember, there is a javascript 'upgrade" that needs to be run as well. It will convert your sbbsecho.cfg to sbbsecho.ini.

Network Options:

This is where my problem was found. I had not configured the line that required my node number.

Make sure in ECHOCFG you tell it where ALL the netmail, incoming
and outgoing folders are.

That should do it..

Yes that did it. Thank you!

Great!!!

Enjoy!!


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
=== MultiMail/Win32 v0.50
--- SBBSecho 3.00-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

On 2017 May 04 07:57:00, you wrote to me:

Thank you and to everyone that replied with assitance.

you are welcome, joe... it is good to see you back :)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Never park your hard drive in a sleazy joint.
---
* Origin: (1:3634/12.73)

Re: sbbsecho
By: Joe to All on Tue May 02 2017 09:23 am

Hello All

I am setting up Fidonet on SBBS. I hav successfully imported areas.bbs and all looks good in the BBS. I have Binkdwin setup and it polls my uplink ok. My problem appears to be packing/unpacking mail.

When I run SBBSECHO -LINF, it complains "unrecognized internal code, assumed passthrough".

Here is the format of one echoarea in c:\sbbs\exec\areas.bbs:

FIDO_SYNCSYSO SYNC_SYSOPS 1:3828/7

This appears to have been imported to c:\sbbs\ctrl and now reads:

/sbbs/echomail\FIDO_SYNCSYSO SYNC_SYSOPS 1:3828/7

What am I missing that will get sbbsecho to scan, pack and unpack?

The area file that SBBSecho uses by default is data/areas.bbs.

If you have "paths" in the first field on lines in your areas.bbs file, that indicates that you exported it from SCFG using "AREAS.BBS (MSG)" rathr than the "AREAS.BBS (SBBSecho)" format option.

digital man

Synchronet "Real Fact" #24:
1584 Synchronet BBS Software registrations were sold between 1992 and 1996. Norco, CA WX: 83.8oF, 46.0% humidity, 17 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Rob,

When I run SBBSECHO -LINF, it complains "unrecognized internal code, assu passthrough".

I've gotten the same thing. I was told the other day that SBBSECHO
3.00 was a FLO mailer ONLY, and that the Attach option did not work
right...so, I went in, and made changes. I gather the syntax is -LINF
for exporting, and -LESR! for importing, correct??

What I did with the AREAS.BBS (in c:\sbbs\data) was set up an internal
tag for all the FIDONet style areas, since some of the "tags" from
other networks are identical. So, in mine, it looks like this (I'll use
the FIDONet Region 19 Sysops echo as an example):

FIDONET-R19SYSOP R19SYSOP 1:261/38

Yet in checking the log file, it seemed that SBBSECHO wasn't
processing outgoing packets right, if it had the internal tag, specific
to the BBS...and I thought I'd need 2 different AREAS.BBS files, but
that doesn't seem necessary. In other words, the first entry and the
second entry were identical...but as of now, they look like what I noted
above.

Also, I tried using the ZIP and UNZIP, but was getting messages that
they didn't know how to handle the packets (I assume done with
PKZIP/PKUNZIP). Along that line, I have registered copies of 2.04g and
2.50 -- which would be better?? I also disabled the other archivers for
now, but I could put them back in, below ZIP, if it's necessary.

I'm running SBBS 3.16 with SBBSEcho 3.00 and EchoCfg 3.00 under
Windows 7 32-bit.

At least I have all the QWK Networking sorted out...but the issues
with SBBSECHO are the last ones I need to get completed. I came back to
SBBS because of tosser issues with VADV32's FIDONet Tosser, and the
MSGID data. Basically, most all my replies uploaded to Synchronet
systems under VADV32 were getting zapped as duplicates. I hope I won't
have that problem now.

Daryl, WX1DER

---
* OLX 1.53 * Yesterday was the deadline for all complaints.
* Synchronet * The Thunderbolt BBS - wx1der.dyndns.org
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Daryl Stout wrote to DIGITAL MAN on 06-13-17 17:58 <=-

When I run SBBSECHO -LINF, it complains "unrecognized internal code,

ssu

passthrough".

I've gotten the same thing. I was told the other day that SBBSECHO
3.00 was a FLO mailer ONLY, and that the Attach option did not work right...so, I went in, and made changes. I gather the syntax is -LINF
for exporting, and -LESR! for importing, correct??

You no longer need to use the 'options'. Just use sbbsecho alone. One suggestion. If you're running htick, you're going to have to use the -d option. This will prevent the deletion of incoming netmail as to allow it to process any filefix requests.

What I did with the AREAS.BBS (in c:\sbbs\data) was set up an
internal tag for all the FIDONet style areas, since some of the "tags" from other networks are identical. So, in mine, it looks like this
(I'll use the FIDONet Region 19 Sysops echo as an example):

FIDONET-R19SYSOP R19SYSOP 1:261/38

In the Fidonet Group box, what did you put in for the Internal Code? In order for the above to work, FIDONET- would be needed and in the Sub Group, under 'Short Name', R19SYSOP. When you export to your areas.bbs file, just tell it your uplink, in this case Janis and either overwrite or append. Personally, for my Internal Code, each network has a #. Fidonet is #1 so my areas.bbs entry would look like this...

Internal ShortName Uplink
----------------------------.
1R19SYSOP R19SYSOP 1:261/38

Yet in checking the log file, it seemed that SBBSECHO wasn't
processing outgoing packets right, if it had the internal tag, specific
to the BBS...and I thought I'd need 2 different AREAS.BBS files, but
that doesn't seem necessary. In other words, the first entry and the second entry were identical...but as of now, they look like what I
noted above.

Also, I tried using the ZIP and UNZIP, but was getting messages that they didn't know how to handle the packets (I assume done with PKZIP/PKUNZIP). Along that line, I have registered copies of 2.04g and 2.50 -- which would be better?? I also disabled the other archivers for now, but I could put them back in, below ZIP, if it's necessary.

Do you have ZIP and UNZIP in your ../sbbs/exec folder or in your PATH
tatement?




--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
--- MultiMail/Win32 v0.50
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Re: sbbsecho
By: Daryl Stout to DIGITAL MAN on Tue Jun 13 2017 05:58 pm

Rob,

When I run SBBSECHO -LINF, it complains "unrecognized internal code, assu passthrough".

I've gotten the same thing.

Then the internal codes you have in your area file (AREAS.BBS) don't match what you have configured in SCFG->Message Areas.

I was told the other day that SBBSECHO
3.00 was a FLO mailer ONLY, and that the Attach option did not work
right...

Well it's untested. I asked for volunteers to test the FD/Attach mode and could find any.

so, I went in, and made changes. I gather the syntax is -LINF
for exporting, and -LESR! for importing, correct??

That'll work, but the command-line options in SBBSecho v3 are completely new. I attempted to maintain some backward compatibility, but many of the option flags you're not using will be ignored by SBBSecho v3. I suggest you look at the output from SBBSecho -? and choose the options that meet your needs. The simplest command-lines:

export (only): sbbsecho -inp
import (only): sbbsecho -ce

If you just run "sbbsecho" it'll import and export (and all the other stuff it does by default).

What I did with the AREAS.BBS (in c:\sbbs\data) was set up an internal
tag for all the FIDONet style areas, since some of the "tags" from
other networks are identical. So, in mine, it looks like this (I'll use
the FIDONet Region 19 Sysops echo as an example):

FIDONET-R19SYSOP R19SYSOP 1:261/38

The syntax for the area file (areas.bbs) is supposed to be:

<code> <tag> [link] [link] [...]

Where <code> is the local sub-board's internal code (as you see it in SCFG->Message Areas), <tag> is the network's agreed-upon 'echo tag' for the ara, and the [link]'s are obvious I guess. Do you have a sub-board with an internal code of "FIDONET-R19SYSOP" in SCFG->Message Areas?

Yet in checking the log file, it seemed that SBBSECHO wasn't
processing outgoing packets right, if it had the internal tag, specific
to the BBS...and I thought I'd need 2 different AREAS.BBS files, but
that doesn't seem necessary. In other words, the first entry and the
second entry were identical...but as of now, they look like what I noted above.

Synchronet sub-board internal codes are made up on the message group prefix (if you have one) and the sub's internal code suffix, combined, for a total maximum of 16 characters. Echo tags on the other hand can be up to 34 chars total. So while it may be true that some of your echo tags and internal codes may match, many may not.

Also, I tried using the ZIP and UNZIP, but was getting messages that
they didn't know how to handle the packets (I assume done with PKZIP/PKUNZIP).

What was the message? How do you have your archivers configured in SBBSecho? You should really use info-zip (zip and unzip) and get that resolved.

Along that line, I have registered copies of 2.04g and
2.50 -- which would be better??

2.50 would be better, but it uses a completely different command-line from pkzip/unzip v2.04g which is also different from Info-zip. I recommend using Info-zip.

digital man

Synchronet/BBS Terminology Definition #41:
SBBS = Synchronet Bulletin Board System
Norco, CA WX: 85.6oF, 31.0% humidity, 5 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.01-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Bill,

You no longer need to use the 'options'. Just use sbbsecho alone. One BM>suggestion. If you're running htick, you're going to have to use the -d BM>option. This will prevent the deletion of incoming netmail as to allow it t BM>process any filefix requests.

Does that work for whether it's incoming or outgoing??

In the Fidonet Group box, what did you put in for the Internal Code? In orde BM>for the above to work, FIDONET- would be needed and in the Sub Group, under BM>'Short Name', R19SYSOP. When you export to your areas.bbs file, just tell it BM>your uplink, in this case Janis and either overwrite or append.

I'm using FIDONET- as the code for the board, then it appends the
FIDOTag to it, to make the first entry in the AREAS.BBS file. Of note,
only the first 8 characters of the tag are used.

As an example the AARP Fraud echo has the FIDOTag of AARP_FRAUD -- but
with the FIDONET- internal code, the first column shows
as FIDONET-AARPFRAU in the AREAS.BBS file. So, that entry looks like:

FIDONET-AARPFRAU AARP_FRAUD 1:261/38

Do you have ZIP and UNZIP in your ../sbbs/exec folder or in your PATH BM>tatement?

Both.

Daryl

---
* OLX 1.53 * If Barbie's so popular, why must you buy her friends??
* Synchronet * The Thunderbolt BBS - wx1der.dyndns.org
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Rob,

Then the internal codes you have in your area file (AREAS.BBS) don't match w DM>you have configured in SCFG->Message Areas.

I thought I had them right.

Well it's untested. I asked for volunteers to test the FD/Attach mode and co DM>find any.

It's like folks believe in N.A.V.Y. -- N)ever A)gain V)olunteer
Y)ourself. I see a lot of that in amateur radio. <G>

export (only): sbbsecho -inp
import (only): sbbsecho -ce

If you just run "sbbsecho" it'll import and export (and all the other stuff DM>does by default).

That makes it easier.

Where <code> is the local sub-board's internal code (as you see it in DM>SCFG->Message Areas), <tag> is the network's agreed-upon 'echo tag' for the DM>ara, and the [link]'s are obvious I guess. Do you have a sub-board with an DM>internal code of "FIDONET-R19SYSOP" in SCFG->Message Areas?

Yes.

Synchronet sub-board internal codes are made up on the message group prefix DM>you have one) and the sub's internal code suffix, combined, for a total maxi DM>of 16 characters. Echo tags on the other hand can be up to 34 chars total. S DM>while it may be true that some of your echo tags and internal codes may matc DM>many may not.

OK, that explains why the tag for AARP_FRAUD shows in my AREAS.BBS
file as FIDONET-AARPFRAU as the first column, then AARP_FRAUD in the
second column, then my link for it (and all my FIDONet stuff) is
1:261/38. I have other hubs for other FTN networks.

2.50 would be better, but it uses a completely different command-line from DM>pkzip/unzip v2.04g which is also different from Info-zip. I recommend using DM>Info-zip.

I'll set up infozip again, and see what happens.

Daryl

---
* OLX 1.53 * I'm speeding because I have to go poop.
* Synchronet * The Thunderbolt BBS - wx1der.dyndns.org
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Daryl Stout wrote to BILL MCGARRITY on 06-14-17 19:09 <=-

You no longer need to use the 'options'. Just use sbbsecho alone. One
suggestion. If you're running htick, you're going to have to use the -d
option. This will prevent the deletion of incoming netmail as to allow it

process any filefix requests.

Does that work for whether it's incoming or outgoing??

Using the -d switch will not delete netmail on incoming. The batch file I use runs sbbsecho twice, once for incoming and once for any posted messages made to the board for outbound. The 2nd instance doesn't use the -d switch but I did notice it will not delete the netmail from the incoming... so I added a del ../secure/*.msg.

In the Fidonet Group box, what did you put in for the Internal Code? In

rde

for the above to work, FIDONET- would be needed and in the Sub Group, under
'Short Name', R19SYSOP. When you export to your areas.bbs file, just tell

t

your uplink, in this case Janis and either overwrite or append.

I'm using FIDONET- as the code for the board, then it appends the FIDOTag to it, to make the first entry in the AREAS.BBS file. Of note, only the first 8 characters of the tag are used.

That's perfect.

As an example the AARP Fraud echo has the FIDOTag of AARP_FRAUD --
but with the FIDONET- internal code, the first column shows
as FIDONET-AARPFRAU in the AREAS.BBS file. So, that entry looks like:

FIDONET-AARPFRAU AARP_FRAUD 1:261/38

Do you have ZIP and UNZIP in your ../sbbs/exec folder or in your PATH
tatement?

Both.

Mmmm... well, DM gave you a resolve for that issue. If you need either the ZIP or UNZIP, as they work perfectly here, let me know.


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
--- MultiMail/Win32 v0.50
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)