Virtual Private Server (VPS) Hosting provided by Central Point Networking cpnllc.com
For some reason, the "Nodelist" and "Recent Callers" features are not working.
| Sysop: | Ray Quinn |
|---|---|
| Location: | Visalia, CA |
| Users: | 60 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 69:36:51 |
| Calls: | 12 |
| Files: | 12,938 |
| Messages: | 99,240 |
Check out the US 99 menu above for links to information about US Highway 99, after which the US 99 BBS is named.
Be sure to click on the Amateur Radio menu item above for packet BBSes, packet software, packet organizations, as well as packet how-to's. Also included is links to local and some not-so-local Amateur Radio Clubs.
I just tried out the version in subj and found two oddities.
1. The slash switch '/' doesn't seem to work, only the dash '-'.
2. Reports supposed to be sent to e.g. 2:203/0 in region 20 is sent
to 2:20/203.
Doesn't that depend on what you put in the control file for the specific net?
I use exactly the same file as I've been using for almost ten years, except for the allowunup verb.
- = o = o = O = o = o = -
;
; MAKENL.CTL for RC 2:20/0
;
make region 20
outfile <secret>
process Thursday
master .
outpath .
update .\tmp
badfiles .\bad
mailfiles \fd\netfiles
notify receipt
submit 2:292/854 ;ZC2's main address
netaddress 2:20/0
messages \fd\netmail
allowunpub 1
;
data
Region,20,Scandinavia,[...]
,228,HAM-BOX,Mariehamn_Aland,[...]
;
files
Net 201 <secret>
Net 203 <secret>
Net 211 <secret>
Net 230 <secret>
EOF
The can be an extra parameter, e.g.
Net 203 <secret> 2:203/0
threshold 0 -1 ; force compression -- no submittal difference file
;arc 5 ; obsolete, see whatsnew.txt
arccopy z pkzip -ex ; compress with pkzip instead of default arc
arcmove z pkzip -mf ; compress with pkzip instead of default arc
arcopen a arc ew ; accept compressed arced segments
arcopen z pkunzip -eo ; accept compressed zipped segments
Or something like it. This is documented in the whatsnew.txt file.
The can be an extra parameter, e.g.
Net 203 <secret> 2:203/0
I know that, but that doesn't correct the obvious bug, does it?
OpenMSGFile entered
* OpenMSGFile: 2:20/203 filename=(null) *
Nah, I don't use compressed mail.
Or something like it. This is documented in the whatsnew.txt file.
I was the one that changed the arcmail functions in the source originally, so I am fully aware of how it works. 8-)
I just tried out the version in subj and found two oddities.
1. The slash switch '/' doesn't seem to work, only the dash '-'.
2. Reports supposed to be sent to e.g. 2:203/0 in region 20 is
sent to 2:20/203.
O.K. I was never good at history. ;)
1. The slash switch '/' doesn't seem to work, only the dash '-'.
2. Reports supposed to be sent to e.g. 2:203/0 in region 20 is sent
to 2:20/203.
I know that, but that doesn't correct the obvious bug, does
it?
OpenMSGFile entered
* OpenMSGFile: 2:20/203 filename=(null) *
Apparently it doesn't. I think Andrew Leary is in a better position
to dive into the code than I am. If he does not pick it up, I will
have a go at it.
I did fix a problem with incorrect message headers in 3.4.2. I will do some testing to make sure the problem is completely corrected.
Using an explicit address last for each Net line works OK. But
this looks odd:
d 14-Nov-2014 00:14:45 makenl[4000] OpenMSGFile entered
d 14-Nov-2014 00:14:46 makenl[4000] OpenMSGFile: 0:203/0
filename=(null) d 14-Nov-2014 00:14:46 makenl[4000] SearchMaxMSG('S:\FD\netmail')
Zone 0?
How did you specify the notify address in your control file? 2D or 3D?
Incidentally, I found and stomped the bug in generating the destination address when you don't specify it. I need to look into your Zone 0fixes.
issue; once that is taken care of, v3.4.5 will be released with both
How did you specify the notify address in your control file? 2D or 3D?
How did you specify the notify address in your control file? 2D or 3D?
How did you specify the notify address in your control file? 2D
or 3D?
Then again, I've specified
netaddress 2:20/0
So *my* zone is in there, methinks the program should use my_zone
if only 2D for the Net files.
Fixed.