i've just spent some time to locate and grab a copy of the radius source code... it is, indeed, doing that xxxxxxxx.TMP thing and i think i have figured out why... somewhere in your settings, have you enabled something called "Dynamic Outbounds"?? if so, turn that off and see what happens...
Ok, I cut off Dynamic Outbounds, and mail went out, but now the hub is getting "Invalid File Name Kickbacks",
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: | Weed Hopper |
|---|---|
| Location: | Clearwater, FL |
| Users: | 16 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 18:03:05 |
| Calls: | 133 |
| Files: | 50,534 |
| D/L today: |
107 files (17,165K bytes) |
| Messages: | 323,318 |