Commits (3)
-
Rob Swindell authored
Before commit 5da26eca, you could pass Msgbase() the path to an SMB on the disk and open() it, no configuration needed. As of 2 years ago, I broke that, and passing a path to an SMB would open the "mail" base instead - most unexpected. This is a feature of smb_open_sub() which we switched to using (from smb_open()), so go back to using smb_open() when an unrecognized code is pass to the constructor. This has the negative consequence that the "mail" base can't be created via JS. Probably should fix that.
1e62752a -
Rob Swindell authored
This restores the ability for JS MsgBase() to be used to create the initial mail message base properly, if needed. This means that the 'subnum' should now be equal to scfg.total_subs when referencing an arbitrary SMB via path (not in the configuration).
dc4b1bd9 -
Rob Swindell authored
This is a weird one: sbbsecho ran right as I was saving msgs.cnf via SCFG and it seems like it loaded 0-byte msgs.cnf into memory and this segfault was a result of trying to print sub[INVALID_SUB]->code. The use of [f]nopen() with proper share perms should have prevented this (truncated msgs.cnf read) from happening, so there's something else afoot here.
2962e4a5