I've been testing SBBSecho at another level, trying to determine if it's capable of this like I'd hope it to be.
I'm acting NC for FidoNet for my network now, and as a result, I'm also the middle man for handling netmail routing.
I had one of my downlinks send a netmail to a PING endpoint I know works, and what results I saw was very disturbing.
SBBSecho gets the netmail, and exports it to my netmail directory. That's it. It doesn't try to route it or send it to my uplink as I would hope for it to do. It just sits there in my netmail directory as a raw *.msg file.
Why would it do this, and why will it not pass it on?
Is it expected that
some other tosser be required to be configured in order to get things like this to route?
I'm wondering because I notice it didn't try to import it to Synchronet, because the address is not mine, but it did export it at the least, it just didn't and won't seem to export it out the next route-hop.
The way I'm calling sbbsecho on inbound packets is:
sbbsecho -lesrfd!
htick toss scan ffix
sbbsecho -linefs
Furthermore, it's possible that sbbsecho may be rewriting the netmail it exports?
I'm confirming with the sender of it to validate this, but they
were asked to send a netmail to PING@1:3634/12 (Mark Lewis's system, which I know works well with PING), but looking at the netmail message it exported, using GoldEd+, I see the To address is mine, 1:135/371. Again, I'm double-checking if they sent it to me or to the correct adress or not. :)
I've been testing SBBSecho at another level, trying to determine if it's capable of this like I'd hope it to be.
I'm acting NC for FidoNet for my network now, and as a result, I'm also the middle man for handling netmail routing.
I had one of my downlinks send a netmail to a PING endpoint I know works, and what results I saw was very disturbing.
SBBSecho gets the netmail, and exports it to my netmail directory. That's it. It doesn't try to route it or send it to my uplink as I would hope for it to do. It just sits there in my netmail directory as a raw *.msg file.
Re: SBBSEcho and NetMail Routing?
By: Psi-Jack to All on Mon Sep 21 2015 03:11 pm
I've been testing SBBSecho at another level, trying to determine if
it's capable of this like I'd hope it to be.
Okay. Any feedback on the last set of changes you requested (in regards to the file request/.req file stuff)?
I'm acting NC for FidoNet for my network now, and as a result, I'm
also the middle man for handling netmail routing.
I had one of my downlinks send a netmail to a PING endpoint I know
works, and what results I saw was very disturbing.
SBBSecho gets the netmail, and exports it to my netmail directory.
That's it. It doesn't try to route it or send it to my uplink as I
would hope for it to do. It just sits there in my netmail directory as
a raw *.msg file.
The .msg file phase is required for all received netmail, even netmail destined for other nodes.
Why would it do this, and why will it not pass it on?
An export run with the 'F' command-line option should have SBBSecho then export the .msg to an outbound packet for the destination node.
Is it expected that
some other tosser be required to be configured in order to get things
like this to route?
No, but is expected that a second run of SBBSecho is required to get the netmail routed to a new outbound packet for the destination node (or route hop).
I'm wondering because I notice it didn't try to import it to
Synchronet, because the address is not mine, but it did export it at
the least, it just didn't and won't seem to export it out the next
route-hop.
What does SBBSecho display when the export command-line is run and the .msg file(s) in question are processed?
The way I'm calling sbbsecho on inbound packets is:
sbbsecho -lesrfd!
htick toss scan ffix
sbbsecho -linefs
Furthermore, it's possible that sbbsecho may be rewriting the netmail
it exports?
I'm not really sure what you're asking. SBBSecho doesn't actually export netmail. It can packetize netmail (from .msg to .pkt format), and by definition, that is "rewriting the netmail". If the netmail is to be routed, then the packet header may contain a different destination address than the "packed message" header.
I'm confirming with the sender of it to validate this, but they
were asked to send a netmail to PING@1:3634/12 (Mark Lewis's system,
which I know works well with PING), but looking at the netmail message
it exported, using GoldEd+, I see the To address is mine, 1:135/371.
Again, I'm double-checking if they sent it to me or to the correct
adress or not. :)
There certainly could be a bug or two somewhere, but without more details (e.g. display or log output pointing out exactly what the problem is), I can't really determine that.
In a reply from Psi-Jack on 15:11 about SBBSEcho and NetMail Rout
I've been testing SBBSecho at another level, trying to determine if
it's capable of this like I'd hope it to be.
I'm acting NC for FidoNet for my network now, and as a result, I'm
also the middle man for handling netmail routing.
I had one of my downlinks send a netmail to a PING endpoint I know
works, and what results I saw was very disturbing.
SBBSecho gets the netmail, and exports it to my netmail directory.
That's it. It doesn't try to route it or send it to my uplink as I
would hope for it to do. It just sits there in my netmail directory
as a raw *.msg file.
I don't use the sbbs netmail dir. or my ftn netmail, it goes to the right outbound dir. for each zone
I've been testing SBBSecho at another level, trying to determine if
it's capable of this like I'd hope it to be.
I'm acting NC for FidoNet for my network now, and as a result, I'm
also the middle man for handling netmail routing.
I had one of my downlinks send a netmail to a PING endpoint I know
works, and what results I saw was very disturbing.
SBBSecho gets the netmail, and exports it to my netmail directory.
That's it. It doesn't try to route it or send it to my uplink as I
would hope for it to do. It just sits there in my netmail directory
as a raw *.msg file.
I don't use the sbbs netmail dir. or my ftn netmail, it goes to the right outbound dir. for each zone
What? SBBSecho doesn't support 5D, only 4D.
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 09:22:05 |
Calls: | 510 |
Messages: | 220571 |