D
Deleted member 5784
Don't know the history of Sab internals, or what assumptions the devs had in this area; i'm just suggesting a possible cause of your error.yes they do already exist, have existed for quite some time, as other containers refer to them.
is this a recent change as surely it should be clever enough to check if they exist before trying to create them again.
I've no idea; it depends what those other containers are & what they're expecting etc. You'll have to run this scenario for yourself.won't that then create issues with other containers that need them?
Just rename the top level /usenet/ folder to, say, /xusenet/ temporarily while you try my suggestion; then just rename it back when you're done testing. Or even simpler, specify a non-existing new folder in the Sab dialogue, just as a test of my suggestion. Specify it as '/foo/bar' and see if this works...