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:
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).
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...
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.
Mine only has SYSOP and an intentional typo that needs to be routed
to me. :)
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.
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...
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
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. :)
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...
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.
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).
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 cas sensitive?
I am using my areafix password... is that right?
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.
robot
Netmail should not be sent to 'tickfix'. If you netmail sent to the
name (e.g. "filefix") are going to "your account", that sounds like you're not running SBBSecho v3.11.
sbbsecho.c:up
/* 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
in the web interface somewhere, but it does not.
#
| Sysop: | Chris Crash |
|---|---|
| Location: | Huntington Beach, CA. |
| Users: | 557 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 232:23:48 |
| Calls: | 10,378 |
| Files: | 5 |
| Messages: | 358,578 |