On 12/12/18, g00r00 pondered and said...
There are instructions to place your original users.dat in and rerun the upgrade, so hopefully that would resolve any issues. Should also be running the latest build Dec 11 I think?
I have tried this and seemed to have issues still with an account that the problem of a blank/missing pw was picked up on. I moved copies of mystic.dat
in /mystic and also users.dat in /data over
Then ran the upgrade process also tried upgrade passwords... problem
continued with the identified account. In the end I did a manual PW reset on it. I also had to update the SMTP settings again as they went west with the mystic.dat update
I'm thinking about just setting up a mandatory password change every 45 days
to pick up these rogue issues as there's just no way to know which accounts
are impacted and which are not.
--- Mystic BBS v1.12 A40 2018/12/11 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)