what does that even mean??? we need logs, man... logs of the same session from both sides... these eWAGS* are getting old... fast...
^C:/SBBS/RADIUS/OUT/0000fff9.MO0
Here is the .FLO file after Radius see it and changes it.
^C:\SBBS\radius\OUT\01130064.TMP\/SBBS/RADIUS/OUT/0000fff9.MO0
Maybe the back-slashes vs. forward-slashes are an issue for Radius?
Re: Outgoing Fido Mail
By: Digital Man to DesotoFireflite on Mon Mar 29 2021 04:01 pm
^C:/SBBS/RADIUS/OUT/0000fff9.MO0
Here is the .FLO file after Radius see it and changes it.
^C:\SBBS\radius\OUT\01130064.TMP\/SBBS/RADIUS/OUT/0000fff9.MO0
Maybe the back-slashes vs. forward-slashes are an issue for Radius?
Just curious, and work with me here, was there a change in how sbbsecho would pass this file dir and name in the .clo/.flo, when it comes to forward-slashes and back-slashes when 3.18b came out.
I'm grasping at straws
here, but I've been using radius for about 3 to 4 years, and this all started about the time I did the last update. In sbbsecho.ini, it's listed as:
"outbound = C:\SBBS\RADIUS\OUT\" but it's forward slashes in the .clo/.flo
The logs don't tell me squat, and I can't get the hub to send me their logs, so I'm shooting in the dark. I plan on updating to binkit this weekend, but I really would like to know what is causing this if possable. As always, thanks.
Sysop: | Chris Crash |
---|---|
Location: | Huntington Beach, CA. |
Users: | 577 |
Nodes: | 8 (0 / 8) |
Uptime: | 61:54:37 |
Calls: | 10,734 |
Calls today: | 1 |
Files: | 5 |
Messages: | 442,632 |