Hi,
Is there a standard way of handling uuencoded messages in SBBS that I'm missing?
Re: uuencode
By: John Dovey to All on Sat Mar 26 2022 04:16 pm
Hi,
Is there a standard way of handling uuencoded messages in SBBS that I'm
missing?
Like... binary newsgroup articles? I once maintained a whole newsgroup binary decoder thing for Synchronet (exec/binarydecoder.js, it's still there, maybe still works). It would handle the multi-part, uuecodeded and yyenc-encoded files. But I think I'm the only one that used it regularly and then stopped.
What exactly are you looking for?
--
digital man (rob)
Re: uuencode
By: John Dovey to All on Sat Mar 26 2022 04:16 pm
Hi,
Is there a standard way of handling uuencoded messages in SBBS that I'm
missing?
Like... binary newsgroup articles? I once maintained a whole newsgroup binary decoder thing for Synchronet (exec/binarydecoder.js, it's still there, maybe still works). It would handle the multi-part, uuecodeded and yyenc-encoded files. But I think I'm the only one that used it regularly and then stopped.
What exactly are you looking for?
--
digital man (rob)
Awesome. I'll take a look.
I was hopibg to have something which for specific exhos would uudecode anything it found and then add the results to a file area automatically. I'll play with that and see if I can tweak it.
I do have built-in support for MIME-encoded attached file decoding (for Internet-emailed attachments, primariliy). I could likely enhance that support to auto-decode uuencoded embedded files. I just don't see such attachments in echoes... ever. Are you? --
digital man (rob)
I do have built-in support for MIME-encoded attached file decoding (for Internet-emailed attachments, primariliy). I could likely enhance that support to auto-decode uuencoded embedded files. I just don't see such attachments in echoes... ever. Are you? --
digital man (rob)
As usual, porn leads the way. RU.SEX.SiMVOL
UUencoded files as the entire body of the message.
I'm only seeing multi-part files in there, e.g.
section 1 of 5 of file Natik08.jpg < MxUUE v0.6.4 (c) 1999-2001 Maxxi >
begin 644 Natik08.jpg
so... yeah, binarydecoder.js is what you'd use.
--
digital man (rob)
I'm only seeing multi-part files in there, e.g.
section 1 of 5 of file Natik08.jpg < MxUUE v0.6.4 (c) 1999-2001 Maxxi
begin 644 Natik08.jpg
so... yeah, binarydecoder.js is what you'd use.
Any hints about how to set that up to run automatically?
Any hints about how to set that up to run automatically?
As a timed event (in SCFG->External Programs) with a command-line of "?binarydecoder"
You'll need to create your ctrl/binarydecoder.ini file based on the instructions at the top of exec/binarydecoder.js.
At minimum, you'd just have:
[usenet_rusexsim]
or whatever the correct internal code is for the sub-board. Of course you can add more.
This won't put the files in the filebase automatically, but that wouldn't be a difficult feature to add if you want it. --
Any hints about how to set that up to run automatically?
As a timed event (in SCFG->External Programs) with a command-line of "?binarydecoder"
You'll need to create your ctrl/binarydecoder.ini file based on the instructions at the top of exec/binarydecoder.js.
At minimum, you'd just have:
[usenet_rusexsim]
or whatever the correct internal code is for the sub-board. Of course you can add more.
This won't put the files in the filebase automatically, but that wouldn't be a difficult feature to add if you want it. --
Thank you. I was thinking a seperate external event to file add all files in the extraction directory, but if that could be included in the script as an option, that would be pretty cool.
Yeah, it could. I ran on test on that "echo" and I see that the resulting decoded files are not correct. There are at least a couple of issues:
1. The subject name of "[#/#] filename" throws off my subject comparison logic which assumes that "[#/#]" or "(#/#)" would come *after* the filename in the subjec, not before. This was the common practice of the day, 18 years ago, when I last worked on that script.
2. The secondary parts of UUencoded message bodies are decoded wrong as my script assumes the message would not have any additional text and decodes it all as UUencoded content.
Yeah, it could. I ran on test on that "echo" and I see that the resulting decoded files are not correct. There are at least a couple of issues:
1. The subject name of "[#/#] filename" throws off my subject comparison logic which assumes that "[#/#]" or "(#/#)" would come *after* the filename in the subjec, not before. This was the common practice of the day, 18 years ago, when I last worked on that script.
Maybe we're. looking at different things. I'm looking at the Fido echo not the newsgroup.
I ran it here and it worked perfectly.
2. The secondary parts of UUencoded message bodies are decoded wrong as my script assumes the message would not have any additional text and decodes it all as UUencoded content.
Each message contains the entirety of the uuencoded file so there are no part numbers.
| Sysop: | Nelgin |
|---|---|
| Location: | Plano, TX |
| Users: | 513 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 20:34:18 |
| Calls: | 8,290 |
| Calls today: | 3 |
| Files: | 15,520 |
| Messages: | 928,815 |