In the areas section of the config you can point to specific echomail tags
and then point to where their JAM base is.

If I create these entries but the JAM base files I state don't yet exist,
will HPT create the JAM files when it first starts tossing packets for the given echomail tag that does not yet have a JAM file with the name defined in the config?

e.g.

EchoArea FSX_ENG msgs/fsx_eng -d "ENiGMA 1/2 BBS Support/Dev"

if fsx_eng does not exist in the /msg folder will the base be auto created?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Husky Config
By: Avon to All on Mon Jan 11 2021 10:12 am

EchoArea FSX_ENG msgs/fsx_eng -d "ENiGMA 1/2 BBS Support/Dev"

Yes, it will create the msgbase if it doesn't exist already.

If you use a path like msgs/fsx_eng you will have to be sure to always run hpt from the directory below msgs/. If in doubt use an absolute path.

if fsx_eng does not exist in the /msg folder will the base be auto created?

Yes, that is true of message bases and file base directories. You need to have your fileareabasedir set, and it must exist but directories for your file areas will be created if they don't already exist.

Ttyl :-),
Al

... What bug? That's a feature
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 10 Jan 2021 at 02:50p, Al pondered and said...

EchoArea FSX_ENG msgs/fsx_eng -d "ENiGMA 1/2 BBS Support/Dev"

Yes, it will create the msgbase if it doesn't exist already.

Good to know thanks.

If you use a path like msgs/fsx_eng you will have to be sure to always
run hpt from the directory below msgs/. If in doubt use an absolute path.

Ah yep, OK so if I create a root dir called msgs I'll be sure to set things
up as /msgs/fsx_eng - that should do the trick.

Yes, that is true of message bases and file base directories. You need
to have your fileareabasedir set, and it must exist but directories for your file areas will be created if they don't already exist.

Thank you.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Husky Config
By: Avon to Al on Mon Jan 11 2021 12:03 pm

Ah yep, OK so if I create a root dir called msgs I'll be sure to set things up as /msgs/fsx_eng - that should do the trick.

Yep, short and sweet.. :)

Ttyl :-),
Al

... A penny for your thoughts; $200 to act it out.
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

I'm wondering about how best to design/config for multiple networks? Specifically netmail, dupe and bad message bases.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Husky Config
By: Avon to Al on Mon Jan 11 2021 03:17 pm

Howdy,

I'm wondering about how best to design/config for multiple networks? Specifically netmail, dupe and bad message bases.

Easy peasy :)

I use include files. Config for multiple network is in /etc/ftn/net/xxx (eg:sportsnet, fsxnet, videotex, etc)

In each subdir I have an "areas", "nodes" and "routes".

The main config file "includes those files" at the appropriate place.

I do a similar thing for binkd.

...ëîåï

... Any club that would accept me as a member, I wouldn't want to join.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 11 Jan 2021 at 04:03p, deon pondered and said...

Easy peasy :)

I use include files. Config for multiple network is in /etc/ftn/net/xxx (eg:sportsnet, fsxnet, videotex, etc)

In each subdir I have an "areas", "nodes" and "routes".

Do you state specific netmail, bad and dupes for each network or just use one communal base for each that covers all networks?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Husky Config
By: Avon to Al on Mon Jan 11 2021 03:17 pm

I'm wondering about how best to design/config for multiple networks? Specifically netmail, dupe and bad message bases.

I use only one bad, dupe and netmail base. It's possible to use more than one netmail base, one for each network but I have never done that.

If you do that filefix might have trouble finding netmail addressed to it, there are ways to work that out but I haven't gone down that road.

Ttyl :-),
Al

... Is fire supposed to shoot out of it like that!?
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 11 Jan 2021, 08:15p, Avon said the following...

Do you state specific netmail, bad and dupes for each network or just
use onecommunal base for each that covers all networks?

I just use one of each here.

I actually do have multiple netmail areas, but the others are not set up in Mystic as they are *.msg for other uses.


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2021/01/05 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)

On 10 Jan 2021 at 11:47p, Al pondered and said...

I use only one bad, dupe and netmail base. It's possible to use more
than one netmail base, one for each network but I have never done that.

If you do that filefix might have trouble finding netmail addressed to
it, there are ways to work that out but I haven't gone down that road.

OK thanks, good to know.

Another uncertainty for me. In Fastecho when I first set it up I set up node entries for the HUB aka addresses I fly. It was done way back when I first started setting up FE and I think from memory may have been needed to ensure netmail sent to my AKA addresses for the various network hubs was accepted.

So now in the exported config file from fecfg2conf util it's created all
these extra link entries for my HUB akas, do you think I need to retain them
or will the software know to move netmails to my aka on to the netmail base?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 11 Jan 2021 at 12:49a, Black Panther pondered and said...

Do you state specific netmail, bad and dupes for each network or just use onecommunal base for each that covers all networks?

I just use one of each here.

OK so just one of each that covers all networks, gotcha.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Husky Config
By: Avon to deon on Mon Jan 11 2021 08:15 pm

Howdy,

Do you state specific netmail, bad and dupes for each network or just use one communal base for each that covers all
networks?

I'm not sure you can have one for each network - and if you can I dont know how.

So yes, I just have a single dupe and bad areas. But I've never looked in it!

...ëîåï

... My girlfriend asked me how long I was going to be gone on this tour. I said, "the whole time".
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 11 Jan 2021 at 07:54p, deon pondered and said...

I'm not sure you can have one for each network - and if you can I dont know how.

Coolio, many thanks :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Husky Config
By: Al to Avon on Sun Jan 10 2021 11:47 pm

Howdy,

I use only one bad, dupe and netmail base. It's possible to use more than one netmail base, one for each network but I have
never done that.
If you do that filefix might have trouble finding netmail addressed to it, there are ways to work that out but I haven't
gone down that road.

Yes, I have more than 1 netmail base - I need that for makenl to send segments to upstream hosts.

To get around filefix not finding messages, in my filter (that controls the robot), I move the message into a "robot" message area, since filefix looks into it.

Carbon copy can be used as well - but I havent played with carbon copy, since the filter can do it too...

...ëîåï

... There is no greater loan than a sympathetic ear.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 11 Jan 2021, 07:54p, deon said the following...

Do you state specific netmail, bad and dupes for each network or just

ne communal base for each that covers all

networks?

I'm not sure you can have one for each network - and if you can I dont know how.

You can, but it's a bit of a pain to set up, and keep them separated. I wouldn't recommend it if you don't need them. :)


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2021/01/05 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)

Re: Re: Husky Config
By: Avon to Al on Mon Jan 11 2021 09:11 pm

Another uncertainty for me. In Fastecho when I first set it up I set up node entries for the HUB aka addresses I fly. It was done way back when I first started setting up FE and I think from memory may have been needed to ensure netmail sent to my AKA addresses for the various network hubs was accepted.

Yes, near the top of my config is listed all my AKA's, only three in my case. You may not be using all those AKA's but husky needs to know it is the destination for all your AKA's.

Ttyl :-),
Al

... I didn't claw my way to the top of the food chain to eat vegetables!
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Re: Re: Husky Config
By: deon to Al on Mon Jan 11 2021 08:02 pm

Yes, I have more than 1 netmail base - I need that for makenl to send segments to upstream hosts.

Same here, on my node I can get away with just one netmail base so I have a single *.MSG netmail base that everything can use and be happy with.

If there was a BBS in the mix I might need a Squish or Jam netmail base, or a base per net but I haven't got that going on so my setup is quite simple.

I have an itch to try some different things so that may change and I'll be asking about all that.. :)

Ttyl :-),
Al

... For people who like peace & quiet - A phoneless cord!
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 11 Jan 2021 at 08:02p, deon pondered and said...

Yes, I have more than 1 netmail base - I need that for makenl to send segments to upstream hosts.
To get around filefix not finding messages, in my filter (that controls the robot), I move the message into a "robot" message area, since
filefix looks into it.
Carbon copy can be used as well - but I havent played with carbon copy, since the filter can do it too...

Could you netmail me some details of what your netmail bases setup looks like
/ this filter? I do run makenl

I am running makenl for multiple networks but not clear what the best set up would look like for HPT in this regard. The robots things sounds curious
too...

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Husky Config
By: Avon to deon on Tue Jan 12 2021 03:00 pm

Howdy,

Could you netmail me some details of what your netmail bases setup looks like
/ this filter? I do run makenl

I am running makenl for multiple networks but not clear what the best set up would look like for HPT in this regard. The robots things sounds curious
too...

OK, here is my netmail config:

root@fidohub:/# grep -i netmail /etc/ftn/config /etc/ftn/net/*/areas /etc/ftn/config:netmailarea netmail /fido/msgbase/netmail -b Jam
/etc/ftn/config:netmailarea robots /fido/msgbase/robots -b Jam -p 30
/etc/ftn/net/fsxnet/areas:netmailarea FSX_NETMAIL /fido/makenl/21/netmail -b Msg -a 21:3/100
/etc/ftn/net/happynet/areas:#netmailarea HPY_NETMAIL /fido/msgbase/happynet/netmail -b Jam -a 637:1/103
/etc/ftn/net/micronet/areas:netmailarea MIN_NETMAIL /fido/makenl/618/netmail -b Msg -a 618:510/1
/etc/ftn/net/sportnet/areas:netmailarea SPT_NETMAIL /fido/makenl/24/netmail -b Msg -a 24:24/1
/etc/ftn/net/videotex/areas:#netmailarea VTX_NETMAIL /fido/msgbase/videotex/netmail -b Jam -a 516:516/0

Where I dont have a netmailarea defined for a network, the netmail falls into /fido/msgbase/netmail. (Actually in theory nothing would flow into there at all, because I have the hub "unattended" and if you netmail anybody at the hub, you'll get a "bounce message" saying "nobody at the hub". But what does end up there are the pings and any messages from husky about areas being autocreated - which I need to re-direct...)

For makenl to work, it creates a MSG netmail in the "messages" path of makenl.ctl, so with this area configured as a "-b Msg" for husky, it sees those outgoing messages in hpt pack and sends them out. (I have a makenl.ctl for each zone in it's own subdirectory, and in that subdirectory is a "netmail" area.)

Incoming messages to areafix make it to the robots area on receipt (and are actioned immediately with hpt toss).

Filefix messages are "posted" to the robots area with my filter in husky's config file "hptperlfile /usr/local/tools/filter.pl"

} elsif ($toname =~ /^(area|file)fix$/i) {
w_log('L',"Netmail: *FIX. [$fromaddr]");

if ($attr & $MSG_RRCT) {
putMsgInArea('BADMAIL',$fromname,$toname,$fromaddr,$toaddr,$subject,$date,($MSG_SENT | $MSG_READ | $MSG_PRIVATE),
"hpt> $toname request with RRC\r" . $text, 0);

if ($DEBUG_MODE) {
return '';
}

$kill = 1;
return "$toname request with RRC";
}

if (lc($toname) eq 'filefix')
{
putMsgInArea('robots',$fromname,$toname,$fromaddr,$toaddr,$subject,$date,($MSG_PRIVATE),
$text, 0);
w_log('L',"Netmail: *FIX. Copied to robots [$fromaddr]");

$newhtick = 1;

$kill = 1;
}

# Messages to *fix are OK
return '';

}

...ëîåï

... I have an existential map. It has 'You are here' written all over it.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 12 Jan 2021 at 04:35p, deon pondered and said...

/etc/ftn/config:netmailarea robots /fido/msgbase/robots
-b Jam -p 30

is robots netmail area defined in config using some additional keyword(s)?
I'm guessing yes. Just wondering how it knows to drop areafix messages there?

/etc/ftn/net/fsxnet/areas:netmailarea FSX_NETMAIL
/fido/makenl/21/netmail -b Msg -a 21:3/100

So only fsx is set to Msg base type but the others all seem to be JAM so I'm picking only fsx is getting that makenl treatment you mentioned?

there at all, because I have the hub "unattended" and if you netmail anybody at the hub, you'll get a "bounce message" saying "nobody at the hub". But what does end up there are the pings and any messages from
husky about areas being autocreated - which I need to re-direct...)

..and that's due to some other scripting you have in place - right?

For makenl to work, it creates a MSG netmail in the "messages" path of makenl.ctl, so with this area configured as a "-b Msg" for husky, it
sees those outgoing messages in hpt pack and sends them out. (I have a makenl.ctl for each zone in it's own subdirectory, and in that subdirectory is a "netmail" area.)

..and these netmail areas are also used by you to reply to any netmails sent
to your HUB addresses? I can understand why you may place them as sub dirs in makenl... I'm not sure I will but rather place them as sub dirs in a /msgs/nmail folder instead I think... not 100% sure.. will keep pondering.

In my current makenl setup the software exports the messages to my hub echomail\in folder and Fastecho picks them up, processes them and sends info either to me or my Fido uplink.

Filefix messages are "posted" to the robots area with my filter in
husky's config file "hptperlfile /usr/local/tools/filter.pl"

how is this file run? is it each time on incoming toss etc. can called within
a .sh file somehow?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Hi Al

In the route file that dictates netmail rules. I read the following in the manual

[snip]

Route statements are parsed in descending order: Pseudo-code:

1) actual = first statement
2) if linkWWW = msg-destination using pattern matching
2a) take this routing and return
2b) else actual = next statement
3) jump to 2)

[snip]

Based on this I take it that rules that set noroute instructions for a given node should be stated above rules that set more catch-all/blanket routing statements?

e.g.

route crash noroute 3:770/100
route crash 3:712/848 3:*

I think should work OK.. but if I reversed those lines... would HPT route all netmail intended to 3:770/100 via 3:712/848?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 12 Jan 2021 at 08:12p, Avon pondered and said...

is robots netmail area defined in config using some additional
keyword(s)? I'm guessing yes. Just wondering how it knows to drop
areafix messages there?

Yep sussed this one.

[snip]

robotsArea SecondNetMail

Specifies area used for areafix and filefix scanning. Replies from robots
will also be stored here. RobotsArea must be NetmailArea for security
purposes!

[snip]

But looking at this manual description I'm not 100% clear on why you run a separate netmail base for Filefix? It appears netmails sent to both commands would land in your defined 'robots' base using the one keyword.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Husky Config
By: Avon to deon on Tue Jan 12 2021 08:12 pm

Howdy,

/etc/ftn/net/fsxnet/areas:netmailarea FSX_NETMAIL
/fido/makenl/21/netmail -b Msg -a 21:3/100

So only fsx is set to Msg base type but the others all seem to be JAM so I'm picking only fsx is getting that makenl treatment you mentioned?

No, micronet and sportnet as well...

there at all, because I have the hub "unattended" and if you netmail anybody at the hub, you'll get a "bounce message" saying "nobody at the hub". But what does end up there are the pings and any messages from
husky about areas being autocreated - which I need to re-direct...)

..and that's due to some other scripting you have in place - right?

That's all due to my perl filter which is part of the hptperlfilter /usr/local/tools/filter.pl

For makenl to work, it creates a MSG netmail in the "messages" path of makenl.ctl, so with this area configured as a "-b Msg" for husky, it
sees those outgoing messages in hpt pack and sends them out. (I have a makenl.ctl for each zone in it's own subdirectory, and in that subdirectory is a "netmail" area.)

..and these netmail areas are also used by you to reply to any netmails sent
to your HUB addresses? I can understand why you may place them as sub dirs in makenl... I'm not sure I will but rather place them as sub dirs in a /msgs/nmail folder instead I think... not 100% sure.. will keep pondering.

I could reply, yes - but I dont (since the bounce tells folks where to send their message - and it secretly sends it to my BBS anyway in a private echomail area - so I reply from Alterant).

Filefix messages are "posted" to the robots area with my filter in
husky's config file "hptperlfile /usr/local/tools/filter.pl"

how is this file run? is it each time on incoming toss etc. can called within
a .sh file somehow?

filter.pl is executed for every packet processed, and can do something before the packet is stored, or after it is stored, or even after the onward packet is created.

...ëîåï

... Mary had a little RAM -- only about a MEG or so.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: Husky Config
By: Avon to Al on Tue Jan 12 2021 08:26 pm

Based on this I take it that rules that set noroute instructions for a given node should be stated above rules that set more catch-all/blanket routing statements?
route crash noroute 3:770/100
route crash 3:712/848 3:*
I think should work OK.. but if I reversed those lines... would HPT route all netmail intended to 3:770/100 via 3:712/848?

Right. First match wins.

...ëîåï

... I belong to no organized party - I am a democrat.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: Husky Config
By: Avon to Deon on Tue Jan 12 2021 09:02 pm

But looking at this manual description I'm not 100% clear on why you run a separate netmail base for Filefix? It appears netmails sent to both commands would land in your defined 'robots' base using the one keyword.

areafix messages are processed during the run of "hpt toss", however hpt doesnt process filefix messages, so they need to be stored, so that "htick scan" can find them and process them.

"htick" only looks for robot messages (areafix/filefix) in the "robots" area (or the first netmail configuration), but hpt puts filefix messages in the netmail area that is defined for the zone (or the global catch all). Sometimes there is a mismatch (as in my case), so I have to move filefix messages to the robots area manually (or rather programmatically) for htick scan to find them.

...ëîåï

... No one can guarantee the actions of another. Spock, stardate unknown.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 12 Jan 2021 at 04:35p, deon pondered and said...

/etc/ftn/net/fsxnet/areas:netmailarea FSX_NETMAIL
/fido/makenl/21/netmail -b Msg -a 21:3/100

For makenl to work, it creates a MSG netmail in the "messages" path of

How many files do you end up with in this base when people send netmails to 21:3/100 ?

I'm thinking (and it's been some time since I used them) with the MSG style base you can end up with hundreds of files in a dir, one for each message. Sound right? Al? And how to purge such files when I think the only utils
I've looked at so far seem to handle just JAM and Squish bases?

Hmm

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 12 Jan 2021 at 07:55p, deon pondered and said...

Right. First match wins.

Thanks :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 12 Jan 2021 at 07:54p, deon pondered and said...

anybody at the hub, you'll get a "bounce message" saying "nobody at
hub". But what does end up there are the pings and any messages from
husky about areas being autocreated - which I need to re-direct...)

..and that's due to some other scripting you have in place - right?

That's all due to my perl filter which is part of the hptperlfilter /usr/local/tools/filter.pl

I can see a little bit down the track I'm going to want to do something like this also, it's sounds very good. I'm glad I built my copy with PERL enabled.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 12 Jan 2021 at 07:58p, deon pondered and said...

areafix messages are processed during the run of "hpt toss", however hpt doesnt process filefix messages, so they need to be stored, so that
"htick scan" can find them and process them.

That makes sense.

"htick" only looks for robot messages (areafix/filefix) in the "robots" area (or the first netmail configuration), but hpt puts filefix messages in the netmail area that is defined for the zone (or the global catch all). Sometimes there is a mismatch (as in my case), so I have to move filefix messages to the robots area manually (or rather
programmatically) for htick scan to find them.

This I had to re-read twice :) But I understand because of complexity it
makes sense (and works) to copy filefix incoming to a dedicated bots base.

My original config has a

robotsarea NETMAIL

but I updated it to

robotsarea BOTMAIL

The later defined

NetmailArea NETMAIL /msgs/netmail/netmail -b Jam -g Z -dupehistory 1100 -d "Netmail Catch-all"
NetmailArea BOTMAIL /msgs/netmail/botmail -b Jam -g Z -dupehistory 1100 -d
"BOT Netmail"

I'm hoping along with some scripting you have provided I will be OK.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Husky Config
By: Avon to deon on Tue Jan 12 2021 10:01 pm

For makenl to work, it creates a MSG netmail in the "messages" path of

How many files do you end up with in this base when people send netmails to 21:3/100 ?
I'm thinking (and it's been some time since I used them) with the MSG style base you can end up with hundreds of files in a
dir, one for each message. Sound right? Al? And how to purge such files when I think the only utils
I've looked at so far seem to handle just JAM and Squish bases?

Not many.

Nobody netmails the hub (they get a bounce if they do). And *fix messages go into the "robots" netmail area which is Jam.

...ëîåï

... Construct a system that even a fool can use and only a fool will want to. --- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: Husky Config
By: Avon to Al on Tue Jan 12 2021 08:26 pm

Based on this I take it that rules that set noroute instructions for a given node should be stated above rules that set more catch-all/blanket routing statements?

Yes, I have all my links (for the most part) listed at the beginning of the route file and the catch-all's down at the bottom.

route crash noroute 3:770/100
route crash 3:712/848 3:*

I think should work OK.. but if I reversed those lines... would HPT route all netmail intended to 3:770/100 via 3:712/848?

Yes, if "route crash 3:712/848 3:*" was listed first, netmail for 3:770/100 would be routed there. Your example above is what you want.

Ttyl :-),
Al

... 75%, no, 72% of all statistics are made up on the spot.
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Hey Avon,

route crash noroute 3:770/100
route crash 3:712/848 3:*

What no love for the other nets in z3 that you have connections to? %-(




\/orlon
VK3HEG


--- MagickaBBS v0.15alpha (Linux/armv6l)
* Origin: \/orlon Empire: Sector 550 (21:1/195.1)

On 12 Jan 2021 at 02:03a, Al pondered and said...

Yes, if "route crash 3:712/848 3:*" was listed first, netmail for 3:770/100 would be routed there. Your example above is what you want.

Thanks. I have been working on this file tonight :)

I've also hit a snag with Tparser whereby the suggested config file syntax generated by the converter script from Fastecho to Husky had the following commands in it for some links

AutoAreaCreate on
AutoAreaCreateDefaults -g A -lr 100 -lw 100 -p 999 -$m 5000

this is for some links that are allowed to created echos as they are an upstream feed..

But running tparser I get this

tparser/lnx 1.9.0-cur 2020-10-16
Test /hub/husky/config for all modules
"/hub/husky/links", line 80: unrecognized: AutoAreaCreate on "/hub/husky/links", line 81: unrecognized: AutoAreaCreateDefaults -g B -lr 100 -lw 100 -p -1 -$m -1
Please correct above error(s) first!

Do you know what the correct keywords are for a given link to allow echomail area creation and the defaults that should be used?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 13 Jan 2021 at 04:22p, vorlon pondered and said...

What no love for the other nets in z3 that you have connections to? %-(

Now now, thus far I have you listed four times in that file and I think you
may be in the lead :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Husky Config
By: Avon to Al on Wed Jan 13 2021 09:42 pm

But running tparser I get this

tparser/lnx 1.9.0-cur 2020-10-16
Test /hub/husky/config for all modules
"/hub/husky/links", line 80: unrecognized: AutoAreaCreate on "/hub/husky/links", line 81: unrecognized:
AutoAreaCreateDefaults -g B -lr 100 -lw 100 -p -1 -$m -1
Please correct above error(s) first!

It might be in the wrong location.

Its a "node" command, so it should follow a "Link" or a "LinkDefaults".

...ëîåï

... A fertile imagination is no compensation for vasectomy.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: Husky Config
By: Avon to Al on Wed Jan 13 2021 09:42 pm

I've also hit a snag with Tparser whereby the suggested config file syntax generated by the converter script from Fastecho to Husky had the following commands in it for some links

AutoAreaCreate on
AutoAreaCreateDefaults -g A -lr 100 -lw 100 -p 999 -$m 5000

Looks like the FE -> Husky config tool has used hpt 1.4 keywords, I hope you don't run into more of that.

Quite possibly that tool could use a bug report and an update.

But running tparser I get this

tparser/lnx 1.9.0-cur 2020-10-16
Test /hub/husky/config for all modules
"/hub/husky/links", line 80: unrecognized: AutoAreaCreate on "/hub/husky/links", line 81: unrecognized: AutoAreaCreateDefaults -g B -lr 100 -lw 100 -p -1 -$m -1
Do you know what the correct keywords are for a given link to allow echomail area creation and the defaults that should be used?

I don't use AutoAreaCreate so I am not sure but I know some keywords have changed. I think you need AreafixAutoAreaCreate and AreafixAutoAreaCreateDefaults now. Try that and see if tparser likes that better.

I think Deon or BP might know what these keywords are for hpt 1.9.

Ttyl :-),
Al

... This login session: $13.99, but for you $11.88
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Re: Re: Husky Config
By: Al to Avon on Wed Jan 13 2021 04:34 am

Looks like the FE -> Husky config tool has used hpt 1.4 keywords, I hope you don't run into more of that.

Ahh, I hadnt picked up on that.

Indeed, that keyword doesnt work with 1.9. Those keywords are now
- AreaFixAutoCreate
- FileFixAutoCreate

...ëîåï

... Bend the facts to fit the conclusion. It's easier that way.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 13 Jan 2021 at 04:34a, Al pondered and said...

I don't use AutoAreaCreate so I am not sure but I know some keywords have changed. I think you need AreafixAutoAreaCreate and AreafixAutoAreaCreateDefaults now. Try that and see if tparser likes that better.

tparser/lnx 1.9.0-cur 2020-10-16
Test /hub/husky/config for all modules
"/hub/husky/links", line 80: unrecognized: AreafixAutoAreaCreate on "/hub/husky/links", line 81: unrecognized: AreafixAutoAreaCreateDefaults -g
B -lr 100 -lw 100 -p -1 -$m -1
"/hub/husky/links", line 127: unrecognized: AutoAreaCreate on "/hub/husky/links", line 128: unrecognized: AutoAreaCreateDefaults -g G -lr 100 -lw 100 -p 730 -$m 5000

Hmm

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 14 Jan 2021 at 01:02a, deon pondered and said...

Indeed, that keyword doesnt work with 1.9. Those keywords are now
- AreaFixAutoCreate
- FileFixAutoCreate

Thanks that worked :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 14 Jan 2021, 09:48a, Avon said the following...

tparser/lnx 1.9.0-cur 2020-10-16
Test /hub/husky/config for all modules
"/hub/husky/links", line 80: unrecognized: AreafixAutoAreaCreate on "/hub/husky/links", line 81: unrecognized: AreafixAutoAreaCreateDefaults
-gB -lr 100 -lw 100 -p -1 -$m -1
"/hub/husky/links", line 127: unrecognized: AutoAreaCreate on "/hub/husky/links", line 128: unrecognized: AutoAreaCreateDefaults -g
G -lr100 -lw 100 -p 730 -$m 5000

Hey Paul,

In my setup here, I have the auto create set as:

AutoCreate on
AutoCreateSubdirs off
AutoFileCreateSubdirs off
areafixAutoCreateFile ~/husky/areas
filefixAutoCreateFile ~/husky/fileareas

Above is set up in my link defaults for uplinks. Downlinks do not have the ability to auto create areas.

areafixAutoCreateDefaults -b Jam -g F -a 1:317/3 -dupCheck Move -lw 100 filefixAutoCreateDefaults -g F

These lines are included in the individual uplinks.

It looks like you might just have to rename some of the keywords.


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2021/01/05 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)

-killsb
no seen-by & path kludges stores in message base (*)
-nokillsb
seen-by & path kludges stores in message base (*) if echoareadefaults set -killsb;

Al (and others) I read this and it looks like I need to set both switches if
I want seen-by and path kludges to be stored in message bases. Seems like a good idea to me - thoughts?


Al I noticed you run

-sbkeepAll
Keep all seen-bys when zone-gating (prevails over -sbkeep).

If I used the two earlier switches and this one as well, do you think all would be fine?

-tooOld <number of days>
Move incoming echomail older than the given number of days to BadMail

I'm wondering what everyone is using for this setting? I'm thinking 60 days, a value too low could filter legitimate traffic.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Husky Config
By: Avon to Al on Thu Jan 14 2021 09:48 am

"/hub/husky/links", line 127: unrecognized: AutoAreaCreate on "/hub/husky/links", line 128: unrecognized: AutoAreaCreateDefaults -g G -lr 100 -lw 100 -p 730 -$m 5000

Hmm

My thoughts exactly.. ;)

I'm not sure what the correct keywords are.. a little experimentation might be needed, or help from someone who uses the auto create features.

I did actually use the auto create features back in the hpt 1.4 days but I haven't used it recently since there isn't a need for it. I have just been manually adding areas if the need arises.

Ttyl :-),
Al

... Enter that again, just a little slower.
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Re: Re: Husky Config
By: Avon to Al on Thu Jan 14 2021 11:14 am

-killsb
no seen-by & path kludges stores in message base (*)
-nokillsb
seen-by & path kludges stores in message base (*) if echoareadefaults set -killsb;

Al (and others) I read this and it looks like I need to set both switches if I want seen-by and path kludges to be stored in message bases. Seems like a good idea to me - thoughts?

You only need those if your echoareadefaults set them and you want to turn them off or vice versa. I don't use it here.

Al I noticed you run

-sbkeepAll
Keep all seen-bys when zone-gating (prevails over -sbkeep).

Yes, this is to keep seen bys regardless of zone. This is what you want in fido. I actually saw something that made me wonder if this was working properly but haven't gone in for a better look.

I need to check this with an out of zone node so possibly I could check path and seen bys from your node and you could also check mine in a test area.

I did check this at one time and it was working properly.

If I used the two earlier switches and this one as well, do you think all would be fine?

I don't think you need the first two switches but I don't know your setup. Path and seen bys are stored by default. But go ahead and try things, you can't hurt anything. You will want -sbkeepAll in fido areas.

-tooOld <number of days>
Move incoming echomail older than the given number of days to BadMail

I'm wondering what everyone is using for this setting? I'm thinking 60 days, a value too low could filter legitimate traffic.

I recently added -tooOld 60 to my setup and it is doing what I want. I just got a couple old messages in my bad area this morning. My Synchronet setup has a similar setting and it'll save you in case something burps up in the net.

Ttyl :-),
Al

... Never mind the Titanic - is there any news of the iceberg?
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 13 Jan 2021 at 02:54p, Al pondered and said...

I'm not sure what the correct keywords are.. a little experimentation might be needed, or help from someone who uses the auto create features.

Yep I think I have sorted that one now... thanks to Deon's suggestion.

Now working on echoareadefaults and trimming a ton of stuff the fe2config parsed into the areas file.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Do see benefit in using these keywords?

echotosslog
importlog
linkwithimportlog

Despite reading up on them I'm not 100% clear in the merits of using them or
if it's going to be fine to do without?

There's also seqdir , again not sure on that one as it also seems linked to seqoutrun ... which if not set, I'm not sure what the worth of setting just
the dir would be? I'm picking leave both off and msgid would still be fine?

When you setting up a lockfile (LockFile) be needed? Do you run multiple
copies of this software and use some monitoring script?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Husky Config
By: Avon to Al on Thu Jan 14 2021 02:24 pm

Do see benefit in using these keywords?

echotosslog
importlog
linkwithimportlog

Yes, I use all those here.

Echotoss.log is where areas with new mail are listed. It's used when you run "hpt scan" if you want it to be. Golded writes that file when I save messages.

Importlog is created when new mail is tossed, it lists the tags of areas that have been tossed.

"linkwithimportlog kill" will cause "hpt link" to link those areas and then kill the import.log. It will be created on the next toss and the next link will link those area and kill the log again.

Despite reading up on them I'm not 100% clear in the merits of using them or if it's going to be fine to do without?

You are fine without them. If there is no echotoss.log "hpt scan" will scan all your areas. I would use the importlog and "linkwithimportlog kill" options but it will still work without them.

There's also seqdir , again not sure on that one as it also seems linked to seqoutrun ... which if not set, I'm not sure what the worth of setting just the dir would be? I'm picking leave both off and msgid would still be fine?

I have an seqdir, it contains one zero byte .seq file. Seqoutrun is not set so it is using the default value, 3y. I think you'll be OK without it. The doc says seqdir is used to prevent surprises, so I set it.. ;)

When you setting up a lockfile (LockFile) be needed? Do you run multiple copies of this software and use some monitoring script?

Normally binkd will run hpt when new mail arrives or I may run it from the command line too. I have LockFile and AdvisoryLock set in my config so you don't get 2 copies running at the same time although I think there is little change of that but it's best to set them.

Ttyl :-),
Al

... My modem isn't slow- it's "baudily challenged!"
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

What no love for the other nets in z3 that you have
connections to? %-(

Now now, thus far I have you listed four times in that file and I
think you may be in the lead :)

Yah. For onece I'm not in the niddle or last. %-)




\/orlon
VK3HEG


--- MagickaBBS v0.15alpha (Linux/armv6l)
* Origin: \/orlon Empire: Sector 550 (21:1/195.1)

On 21 Jan 2021 at 11:35a, vorlon pondered and said...

Yah. For onece I'm not in the niddle or last. %-)
\/orlon
VK3HEG

:) It's important to savour the wins I think :)

If I had an ASCII trophy I'd post it here.

Someone may have one, anyone? ? ?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)