I am not sure when it started, but Areafix has not been working properly with the 3.18 version of Synchronet I pulled down & compiled last week or again today.

I have a node that is trying to get a listing of the echos available to him. Instead the messages are being routed to me. I thought that should only
happen if the requester goofed but, having received the netmails I see no issues with them. They are formatted as follows:

From: Christopher Hall (1:2320/200)
To: AreaFix@1:2320/105
Subject: correct-password-here
Body:
%LIST

The password matches exactly what is in sbbsecho.ini for that node. I have also since tried sending netmail to both 'AreaFix' and 'areafix' from my MagickaBBS and am also not getting any responses (meanwhile, both were routed to my user on the synchronet bbs).

I also could not get a response to a message sent to Filefix but, as that is new and not documented yet (last I looked!), I suspect I am missing something somewhere.

Thanks!

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

P.S. Forgot to mention, we are able to exchange netmail otherwise. He receives netmail written by me, and I him.

Also, in case you are curious, here is what his sbbsecho.ini entry looks like. His password is only 7 characters long, if that matters?:

[node:1:2320/200@fidonet]
Name = Christopher Hall
Comment =
Archive = ZIP
PacketType = 2+
PacketPwd =
AreaFix = true
AreaFixPwd = passwrd
SessionPwd = passwrd
TicFilePwd =
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys = FIDO
Status = Normal
GroupHub =
BinkpHost = slasho.me
BinkpPort = 24554
BinkpPoll = true
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = true
BinkpAllowPlainText = true
BinkpTLS = false
BinkpSourceAddress =

He is running Mystic but I don't think that should be an issue since the netmails are getting through.

Thanks!

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Areafix has stopped working
By: Dumas Walker to Digital Man on Sun May 03 2020 15:17:31

I have a node that is trying to get a listing of the echos available
to him. Instead the messages are being routed to me. I thought that should only happen if the requester goofed but, having received the netmails I see no issues with them. They are formatted as follows:

this sounds like you have listed areafix as an alias to your account...

run echocfg and see what you have in the Netmail Settings->Sysop Aliases field... if you have areafix, filefix or similar in there, remove them...

mine has only SYSOP and one other alias that i use for special purposes unrelated to FNT operations...


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR

Re: Areafix has stopped working
By: Dumas Walker to Digital Man on Sun May 03 2020 03:17 pm

I am not sure when it started, but Areafix has not been working properly with the 3.18 version of Synchronet I pulled down & compiled last week or again today.

I have a node that is trying to get a listing of the echos available to him. Instead the messages are being routed to me. I thought that should only happen if the requester goofed but, having received the netmails I see no issues with them. They are formatted as follows:

From: Christopher Hall (1:2320/200)
To: AreaFix@1:2320/105
Subject: correct-password-here
Body:
%LIST

The password matches exactly what is in sbbsecho.ini for that node. I have also since tried sending netmail to both 'AreaFix' and 'areafix' from my MagickaBBS and am also not getting any responses (meanwhile, both were routed to my user on the synchronet bbs).

If you could dump the message header using "smbutil v" or something similar and paste that here, that could be very helpful.

digital man

Sling Blade quote #1:
Karl: I've killed Doyle with a lawn mower blade. Yes, I'm right sure of it. Norco, CA WX: 66.2øF, 72.0% humidity, 3 mph ESE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Areafix has stopped working
By: Dumas Walker to Digital Man on Sun May 03 2020 15:17:31

I have a node that is trying to get a listing of the echos available
to him. Instead the messages are being routed to me. I thought that should only happen if the requester goofed but, having received the netmails I see no issues with them. They are formatted as follows:

this sounds like you have listed areafix as an alias to your account...

run echocfg and see what you have in the Netmail Settings->Sysop Aliases field... if you have areafix, filefix or similar in there, remove them...

mine has only SYSOP and one other alias that i use for special purposes unrelated to FNT operations...

Mine only has SYSOP and an intentional typo that needs to be routed to me. :)

#

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

If you could dump the message header using "smbutil v" or something similar and paste that here, that could be very helpful.

I actually figured out the problem! I keep all of the *.NA files that are set up in sbbsecho.ini in a directory to themselves. The ones for the "othernets" were still there but somehow the BACKBONE.NA file for FIDO had gone missing. So, I guess when an NA file is missing, this is what sbbsecho does. I
replaced the missing file, and sbbsecho started generating the responses for
my other Zone 1 system.

I have asked the other sysop to try again.

I was mistaken about it not generating for another Zone... for some reason, it just took it longer to process than I expected. I could not just crash the system, wait for the FIDOIN/OUT tasks to run, and then crash again. But it
was generated so all is good!

Sorry for the false alarm!

#

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Re: Areafix has stopped working
By: Dumas Walker to Rampage on Mon May 04 2020 10:39:20

Mine only has SYSOP and an intentional typo that needs to be routed
to me. :)

manually check your sbbsecho.ini file and ensure that any new [robot:blah] entries have a line

attr = 0x0020

it was discovered that this could go missing... if it is missing, add it to all [robot:blah] sections and ensure that you update to the latest .js and binaries...

but that's only for tickfix stuffings... it should not affect areafix if that's messing up, too...


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR

Re: Re: Areafix has stopped working
By: Dumas Walker to Digital Man on Mon May 04 2020 10:44:31

I actually figured out the problem! I keep all of the *.NA files
that are set up in sbbsecho.ini in a directory to themselves. The
ones for the "othernets" were still there but somehow the
BACKBONE.NA file for FIDO had gone missing.

is this the fix for what i was attempting to help you with? if so, glad you found it... but still check for those attr lines in the [robot:blah] section(s) of your sbbsecho.ini file and fix them if they are missing...


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR

Re: Re: Areafix has stopped working
By: Dumas Walker to Digital Man on Mon May 04 2020 10:44 am

If you could dump the message header using "smbutil v" or something similar and paste that here, that could be very helpful.

I actually figured out the problem! I keep all of the *.NA files that are set up in sbbsecho.ini in a directory to themselves. The ones for the "othernets" were still there but somehow the BACKBONE.NA file for FIDO had gone missing. So, I guess when an NA file is missing, this is what sbbsecho does. I
replaced the missing file, and sbbsecho started generating the responses for my other Zone 1 system.

That seems to me to be very unlikely to be the cause.

digital man

This Is Spinal Tap quote #5:
Nigel Tufnel: Authorities said... best leave it... unsolved.
Norco, CA WX: 79.7øF, 46.0% humidity, 6 mph E wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

El 4/5/20 a las 14:57, Rampage escribi¢:

Re: Re: Areafix has stopped working
By: Dumas Walker to Rampage on Mon May 04 2020 10:39:20

Mine only has SYSOP and an intentional typo that needs to be routed
to me. :)

manually check your sbbsecho.ini file and ensure that any new [robot:blah] entries have a line

attr = 0x0020

it was discovered that this could go missing... if it is missing, add it to all [robot:blah] sections and ensure that you update to the latest .js and binaries...

DigitalMan was fixed sbbsecho for that issue

---
þ Synchronet þ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar

Re: Re: Areafix has stopped working
By: Ragnarok to Rampage on Mon May 04 2020 09:10 pm

attr = 0x0020

it was discovered that this could go missing... if it is missing, add it to all [robot:blah] sections and ensure that you update to the latest .js and binaries...

DigitalMan was fixed sbbsecho for that issue

It was actually echocfg that had the bug, but yeah. :-)

digital man

Sling Blade quote #15:
Doyle Hargraves: What'cha doin' with that lawn mower blade Karl?
Norco, CA WX: 72.3øF, 57.0% humidity, 6 mph E wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

On 05-04-20 10:39, Dumas Walker wrote to Rampage <=-

mine has only SYSOP and one other alias that i use for special purposes unrelated to FNT operations...

Mine only has SYSOP and an intentional typo that needs to be routed to
me. :)

I had to add an alias for a mispelling of my name, so I could receive a netmail intended for me.


... Help! I've fallen and can't reach my beer!
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: Areafix has stopped working
By: Ragnarok to Rampage on Mon May 04 2020 21:10:57


Rampage>> manually check your sbbsecho.ini file and ensure that any new
Rampage>> [robot:blah] entries have a line

Rampage>> attr = 0x0020

Rampage>> it was discovered that this could go missing... if it is
Rampage>> missing, add it to all [robot:blah] sections and ensure that
Rampage>> you update to the latest .js and binaries...

Ragnarok> DigitalMan was fixed sbbsecho for that issue

exactly why i was telling Dumas Walker about it... not everyone monitors the cvs log page, irc, or the message area where the cvs commits are posted ;)


BTW: did you see my posting yesterday morning to you in IRC? it was about your hatchit and tickit problem with the hatched files being sent back to your system's inbound from its outbound??

----->8 snip 8<-----
[20200504 0526-0400] <rampage> ragnarok: is this circular connection
happening only when you hatch a file?

[20200504 0530-0400] <rampage> ragnarok: i think i see the problem...
when you hatch a file, you are the
uplink... when tickit processes the
file, it does not see your address in
the links line so it tries to send the
file to yourself...

[20200504 0530-0400] <rampage> ragnarok: there are at least two solutions
i can think of... one is to add your
address to your links line... the second
is that tickit should maybe check to see
if you are the sending system...

[20200504 0531-0400] <rampage> ragnarok: one of these should fix the
problem but not totally sure
----->8 snip 8<-----



)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR

El 5/5/20 a las 08:51, Rampage escribi¢:

Ragnarok> DigitalMan was fixed sbbsecho for that issue

exactly why i was telling Dumas Walker about it... not everyone

monitors the cvs log page, irc, or the message area where the cvs
commits are posted ;)

yes i know.. i am these people that follow the development sometimes.

BTW: did you see my posting yesterday morning to you in IRC? it was about your hatchit and tickit problem with the hatched files being sent back to your system's inbound from its outbound??

sorry, i think that i don't see it.

----->8 snip 8<-----
[20200504 0526-0400] <rampage> ragnarok: is this circular connection
happening only when you hatch a file?

Yes, i notice this behavior only when hat a file to my points.

[20200504 0530-0400] <rampage> ragnarok: i think i see the problem...
when you hatch a file, you are the
uplink... when tickit processes the
file, it does not see your address in
the links line so it tries to send the
file to yourself...

yeah, i see..when i hatchit the file, my node are not in the seenby list
on outbound:

Area POINTS
Origin 4:902/26
From 4:902/26
To 4:902/26.4
File n16d408.exe
Size 9093595
Date 1387772993
Desc n16d408.exe Netscape Navigator 16Bits 4.08
Created by TickIT 1.6
Crc 53478AB4
Path 4:902/26
Seenby 4:902/26.3
Pw

[20200504 0530-0400] <rampage> ragnarok: there are at least two solutions
i can think of... one is to add your
address to your links line... the second
is that tickit should maybe check to see
if you are the sending system...

i manual add the Seenby 4:902/26 line editing outbound tic files, but i
have same behavior. i will test using tickitcfg

[20200504 0531-0400] <rampage> ragnarok: one of these should fix the
problem but not totally sure

i will try more debugging tickit/binkit logic.

i see that sbbs is near to work as complete/working hub/boos system, my
goal is give points and use all sbbs embed tools whitout external like areafix/tinytic/binkd

thanks!

---
þ Synchronet þ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar

El 5/5/20 a las 13:08, Ragnarok escribi¢:

El 5/5/20 a las 08:51, Rampage escribi¢:

i see that sbbs is near to work as complete/working hub/boos system, my
goal is give points and use all sbbs embed tools whitout external like areafix/tinytic/binkd

thanks!

I want to append comment that tic files that come from my boos (4:90/1)
are correctly fowarded to the points (4:902/26.xxx) ex: NODELIST, ZSEGS, BACKBONE, etc

---
þ Synchronet þ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar

Re: Re: Areafix has stopped working
By: Dumas Walker to Rampage on Mon May 04 2020 10:39:20

Mine only has SYSOP and an intentional typo that needs to be routed
to me. :)

manually check your sbbsecho.ini file and ensure that any new [robot:blah] entries have a line

attr = 0x0020

it was discovered that this could go missing... if it is missing, add it to all [robot:blah] sections and ensure that you update to the latest .js and binaries...

but that's only for tickfix stuffings... it should not affect areafix if that's messing up, too...

That is in there. file/tickfix was not working initially because I miseed the jsexec install step. Figured that out reading the code.

The system is still not responding to filefix netmails, though, so something else is amiss. I pulled the latest version of tickfix.js about 12 hours ago (~2200 GMT).

#

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

is this the fix for what i was attempting to help you with? if so, glad you found it... but still check for those attr lines in the [robot:blah] section(s) of your sbbsecho.ini file and fix them if they are missing...

I only have a robots entry for filefix, that attribute is there and it is *not* working. Should there be other robot entries for other functions, or is tickfix
the only one?

The jsexec install step created it as 'filefix' and not 'tickfix' if that matters. The netmails that are being ignored are addressed to filefilx.

#

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

I actually figured out the problem! I keep all of the *.NA files that are set up in sbbsecho.ini in a directory to themselves. The ones for the "othernets" were still there but somehow the BACKBONE.NA file for FIDO had gone missing. So, I guess when an NA file is missing, this is what sbbsecho does. I
replaced the missing file, and sbbsecho started generating the responses for my other Zone 1 system.

That seems to me to be very unlikely to be the cause.

I was afraid of that, but areafix is working now that the NA file is back in place. I have received consistent responses from it, and the other sysop has reported that they are now getting responses, too.

Filefix, OTOH, is still not responding. I read the code and realized I needed to run the jsexec install for it. Did that. Robots entry is now in the sbbsecho.ini file (the only robots entry), and the event is active but it is still not doing anything (aside from exiting with 0) when the event does run.
I have sent netmails both to FileFix and TickFix. All are routed to my
account when they arrive.

Are there any changes required to the tickit.ini file? Is the TO case sensitive? I am using my areafix password... is that right?

Thanks!
#

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Re: Areafix has stopped working
By: Dumas Walker to Rampage on Tue May 05 2020 06:53 am

The system is still not responding to filefix netmails, though, so something else is amiss. I pulled the latest version of tickfix.js about 12 hours ago (~2200 GMT).

An 'smbutil v' dump of the message headers of the problem request netmails (in your data/mail base) would be helpful in debugging the issue.

digital man

Synchronet/BBS Terminology Definition #73:
SSL = Secure Sockets Layer (precursor to TLS)
Norco, CA WX: 88.1øF, 26.0% humidity, 1 mph NNW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Tickfix not working
By: Dumas Walker to Rampage on Tue May 05 2020 06:55 am

is this the fix for what i was attempting to help you with? if so, glad you found it... but still check for those attr lines in the [robot:blah] section(s) of your sbbsecho.ini file and fix them if they are missing...

I only have a robots entry for filefix, that attribute is there and it is *not* working. Should there be other robot entries for other functions, or is tickfix
the only one?

Right now, filefix/tickfix is the only sbbs netmail robot I know of.

The jsexec install step created it as 'filefix' and not 'tickfix' if that matters. The netmails that are being ignored are addressed to filefilx.

'filefix' is the correct name. That should be all that is needed.

digital man

Synchronet/BBS Terminology Definition #29:
FOSSIL = Fido/Opus/SEAdog Standard Interface Layer
Norco, CA WX: 88.6øF, 26.0% humidity, 3 mph ENE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: Areafix has stopped working
By: Dumas Walker to Digital Man on Tue May 05 2020 07:02 am

I actually figured out the problem! I keep all of the *.NA files that are set up in sbbsecho.ini in a directory to themselves. The ones for the "othernets" were still there but somehow the BACKBONE.NA file for FIDO had gone missing. So, I guess when an NA file is missing, this is what sbbsecho does. I
replaced the missing file, and sbbsecho started generating the responses for my other Zone 1 system.

That seems to me to be very unlikely to be the cause.

I was afraid of that, but areafix is working now that the NA file is back in place. I have received consistent responses from it, and the other sysop has reported that they are now getting responses, too.

Filefix, OTOH, is still not responding. I read the code and realized I needed to run the jsexec install for it. Did that. Robots entry is now in the sbbsecho.ini file (the only robots entry), and the event is active but it is still not doing anything (aside from exiting with 0) when the event does run.
I have sent netmails both to FileFix and TickFix. All are routed to my account when they arrive.

Netmail should not be sent to 'tickfix'. If you netmail sent to the robot name (e.g. "filefix") are going to "your account", that sounds like you're not running SBBSecho v3.11.

Are there any changes required to the tickit.ini file?

No.

Is the TO cas sensitive?

No.

I am using my areafix password... is that right?

Yes.

digital man

Sling Blade quote #16:
Karl Childers (to Doyle, re: lawn mower blade): I aim to kill you with it. Mmm. Norco, CA WX: 88.6øF, 26.0% humidity, 3 mph ENE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Tickfix not working
By: Dumas Walker to Rampage on Tue May 05 2020 06:55:41

The jsexec install step created it as 'filefix' and not 'tickfix' if
that matters. The netmails that are being ignored are addressed to filefilx.

filefix is the correct default... i also added allfix to mine...

i don't have any idea why the netmails are not being handled by sbbsecho, though... it should see them and trigger tickfix to do the thing...


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR

I actually figured out the problem! I keep all of the *.NA files
that are set up in sbbsecho.ini in a directory to themselves. The
ones for the "othernets" were still there but somehow the
BACKBONE.NA file for FIDO had gone missing.

is this the fix for what i was attempting to help you with? if so, glad you fou
d it... but still check for those attr lines in the [robot:blah] section(s) of >our sbbsecho.ini file and fix them if they are missing...

It is the fix for areafix not working. Areafix does not have a robot
section here. File/tickfix does. It is still not working.

---
þ SLMR 2.1a þ A distant ship, smoke on the horizon....
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Mine only has SYSOP and an intentional typo that needs to be routed to me. :)

I had to add an alias for a mispelling of my name, so I could receive a netmail
intended for me.

Yep, that is the reason. Now that I also have anything addressed to an apparently non-existent user routed to me I guess that is redundant.

---
þ SLMR 2.1a þ ....we came in?
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Re: Areafix has stopped w
By: Dumas Walker to RAMPAGE on Tue May 05 2020 13:07:00


Rampage>> is this the fix for what i was attempting to help you with? if
Rampage>> so, glad you found it... but still check for those attr lines
Rampage>> in the [robot:blah] section(s) of >our sbbsecho.ini file and
Rampage>> fix them if they are missing...

It is the fix for areafix not working. Areafix does not have a
robot section here. File/tickfix does. It is still not working.

yeah, i've read that... have you updated to the latest sbbsecho and echocfg, too? can't tell from here or the fidonet side of the gateway... i think 3.11 is the latest but there may have been another update since i updated early today or yesterday...


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR

On 05-05-20 13:08, Dumas Walker wrote to TONY LANGDON <=-

Mine only has SYSOP and an intentional typo that needs to be routed to me. :)

I had to add an alias for a mispelling of my name, so I could receive a

netmail

intended for me.

Yep, that is the reason. Now that I also have anything addressed to an apparently non-existent user routed to me I guess that is redundant.

Good point there! :)


... Stop picking your nose and go to the next message
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

On 05-05-20 12:13, Digital Man wrote to Dumas Walker <=-

Netmail should not be sent to 'tickfix'. If you netmail sent to the
robot name (e.g. "filefix") are going to "your account", that sounds
like you're not running SBBSecho v3.11.

Interestingly, someone sent a netmail to tickfix on my system recently. :/ Odd, because my Synchronet system is not a FTN hub, it's a QWK hub and a FTN leaf node.


... Oxymoron: 10K Fun Run.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Netmail should not be sent to 'tickfix'. If you netmail sent to the robot name >e.g. "filefix") are going to "your account", that sounds like you're not runnin
SBBSecho v3.11.

I have been trying it both ways to see if I can get it to work. I should
have the latest of everything as I pulled a clean copy the last time I
pulled it. I also pulled a newer version of tickfix.js a couple of days
ago when I saw the message saying that it had been updated.

I will have to check it when I am sitting at that box. I cannot find
anywhere in this packet where someone has quoted my ftn origin back to me.
:)

Thanks!

---
þ SLMR 2.1a þ This message brought to you by JAMMITIN (tm)!!
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Re: Areafix has stopped w
By: Dumas Walker to DIGITAL MAN on Wed May 06 2020 11:37:00

I will have to check it when I am sitting at that box. I cannot find anywhere in this packet where someone has quoted my ftn origin back to me. :)

you have to post from the fidonet side of the gateway for us to see that... that means carrying the fidonet side's echo which mean two identical message areas but in two different groups fed by two different technologies ;)

like this one coming from the fidonet side on my system whereas most of my others have been posted from my dove-net side via QWK-networking...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Nevermind... I just checked on the other system and it did respond to the most-recent attempt! Thanks!

Netmail should not be sent to 'tickfix'. If you netmail sent to the

robot

name (e.g. "filefix") are going to "your account", that sounds like you're not running SBBSecho v3.11.

sbbsecho.c:
/* Synchronet FidoNet EchoMail Scanning/Tossing and NetMail Tossing Utility */

/* $Id: sbbsecho.c,v 3.172 2020/05/02 23:04:49 rswindell Exp $ */

tickfix.js:
// $Id: tickfix.js,v 1.7 2020/05/03 20:00:45 rswindell Exp $

sbbsecho.ini:
[robot:filefix]
SemFile=../data/tickfix.now
attr=0x0020

Msg Header:
unfortunately I am not literate on how to find that. I thought it showed

up

in the web interface somewhere, but it does not.

#

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP