Doesn't that depend on what you put in the control file for the specific net?
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.
O.K. I was never good at history. ;)
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.
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?
Fixed.
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 510 |
Nodes: | 10 (1 / 9) |
Uptime: | 115:22:31 |
Calls: | 8,197 |
Calls today: | 4 |
Files: | 15,442 |
Messages: | 913,356 |
Posted today: | 8 |