Please wait...
0 files
so, after trying commands to unset the email (there was no straight up delete user command), i tried AGUP/ASUP and that failed saying user didn't exist so i couldn't change the email. here's the connundrum: GETU says it exists, but QUSR says it doesn't exist.. i can't query the user, but i can just get the user and it exists. doesn't appear in LIST... i'm not sure what to do. i did run TDAP which i assume is as close to IGAB as i can get, but that hasn't done anything useful just yet... says it started and its been an hour and the issue still exists, so i dont think it helped any.
root@Mail:/usr/local/citadel# ./sendcommand "GETU Use R. Name"
sendcommand: started (pid=3213) connecting to Citadel server with data directory /usr/local/citadel
200 furryrefuge.com Citadel server ADMIN CONNECTION ready.
GETU Use R. Name
200 80|24|0|
sendcommand: processing ended.
root@Mail:/usr/local/citadel# ./sendcommand "QUSR Use R. Name"
sendcommand: started (pid=3214) connecting to Citadel server with data directory /usr/local/citadel
200 furryrefuge.com Citadel server ADMIN CONNECTION ready.
QUSR Use R. Name
570 No such user.
root@Mail:/usr/local/citadel# ./sendcommand "CHEK Use R. Name"
sendcommand: started (pid=3208) connecting to Citadel server with data directory /usr/local/citadel
200 furryrefuge.com Citadel server ADMIN CONNECTION ready.
CHEK Use R. Name
200 0|0|0||
i've tried looking for a table in the documentation that shows what the GETU output "80|24|0" means as i assumed it was UID, permissions, and whatever else... but apparently i'm wrong as every user i've tried GETU with returns 80|24|0. there doesn't seem to be any clear documentation on what exactly that means. documentation on both GETU and SETU below. according to this, the SETU command also takes inputs on screen as the 2nd and third arguments? even if it ignores them i'd have to use a placeholder like 0 so.. if the GETU output was like "something | permissions | something" then SETU would be "SETU Use R. Name|0|0|something|0|something" correct?
"GETU (GET User configuration)
This command retrieves the configuration options for the currently logged in account. ERROR+NOT_LOGGED_IN will be returned if no user is logged in, of course. Otherwise, OK will be returned, followed by four parameters. The first two parameters in the past conveyed the stored screen dimensions for the user, but since modern displays are able to communicate their screen dimensions back to the system this is no longer needed, so the server always returns 80x24 as a placeholder. The third parameter is a bag of bits with the following meanings: US_LASTOLD 16 Print last old message with new US_EXPERT 32 Experienced user (suppress some of the help blurbs) US_UNLISTED 64 Unlisted userlog entry US_NOPROMPT 128 Don't prompt after each message US_DISAPPEAR 512 Use "disappearing msg prompts" US_PAGINATOR 2048 Pause after each screen of text There are other bits, too, but they can't be changed by the user (see below). SETU (SET User configuration) This command does the opposite of GETU: it takes the screen dimensions and user options (which were probably obtained with a GETU command, and perhaps modified by the user) and writes them to the user account. This command should be passed three parameters: the screen width, the screen height, and the option bits (see above). It returns ERROR+NOT_LOGGED_IN if no user is logged in, and ERROR+ILLEGAL_VALUE if the parameters are incorrect. Note that there exist bits here which are not listed in this document. Some are flags that can only be set by administrators. SETU will ignore attempts to toggle these bits. There also may be more user settable bits added at a later date. To maintain later downward compatibility, the following procedure is suggested: * Execute GETU to read the current flags * Toggle the bits that we know we can toggle * Execute SETU to write the flags If we are passed a bit whose meaning we don't know, it's best to leave it alone, and pass it right back to the server. That way we can use an old client on a server that uses an unknown bit without accidentally clearing it every time we set the user's configuration. As noted above, we no longer store per-user screen dimensions, so any value supplied will be ignored.
Doesnt the 80 & 24 refer to screen width and number of lines?
Marisa
i've tried looking for a table in the documentation that shows what the GETU output "80|24|0" means as i assumed it was UID, permissions, and whatever else... but apparently i'm wrong as every user i've tried GETU with returns 80|24|0. there doesn't seem to be any clear documentation on what exactly that means. documentation on both GETU and SETU below. according to this, the SETU command also takes inputs on screen as the 2nd and third arguments? even if it ignores them i'd have to use a placeholder like 0 so.. if the GETU output was like "something | permissions | something" then SETU would be "SETU Use R. Name|0|0|something|0|something" correct?
"GETU (GET User configuration)
This command retrieves the configuration options for the currently logged in account. ERROR+NOT_LOGGED_IN will be returned if no user is logged in, of course. Otherwise, OK will be returned, followed by four parameters. The first two parameters in the past conveyed the stored screen dimensions for the user, but since modern displays are able to communicate their screen dimensions back to the system this is no longer needed, so the server always returns 80x24 as a placeholder. The third parameter is a bag of bits with the following meanings: US_LASTOLD 16 Print last old message with new US_EXPERT 32 Experienced user (suppress some of the help blurbs) US_UNLISTED 64 Unlisted userlog entry US_NOPROMPT 128 Don't prompt after each message US_DISAPPEAR 512 Use "disappearing msg prompts" US_PAGINATOR 2048 Pause after each screen of text There are other bits, too, but they can't be changed by the user (see below). SETU (SET User configuration) This command does the opposite of GETU: it takes the screen dimensions and user options (which were probably obtained with a GETU command, and perhaps modified by the user) and writes them to the user account. This command should be passed three parameters: the screen width, the screen height, and the option bits (see above). It returns ERROR+NOT_LOGGED_IN if no user is logged in, and ERROR+ILLEGAL_VALUE if the parameters are incorrect. Note that there exist bits here which are not listed in this document. Some are flags that can only be set by administrators. SETU will ignore attempts to toggle these bits. There also may be more user settable bits added at a later date. To maintain later downward compatibility, the following procedure is suggested: * Execute GETU to read the current flags * Toggle the bits that we know we can toggle * Execute SETU to write the flags If we are passed a bit whose meaning we don't know, it's best to leave it alone, and pass it right back to the server. That way we can use an old client on a server that uses an unknown bit without accidentally clearing it every time we set the user's configuration. As noted above, we no longer store per-user screen dimensions, so any value supplied will be ignored."
-- --- https://msbob.org - Support for MS Bob user interface --- https://pocketmud.com - Support and hosting for CoffeeMUD MUDs --- https://minecity.online - Support and hosting for Minetest/Multicraft2 --- https://synchronetbbs.org - Support and hosting for Synchronet BBS software
i tried this command and then TDAP but it doesn't look like it did anything. GETU still sees it. i'm not sure how to log into the other tool you suggested though
root@Mail:/usr/local/citadel# ./sendcommand "SETU Use R. Name|80|24|0|0|0|0|0|0|0|0"
sendcommand: started (pid=7077) connecting to Citadel server with data directory /usr/local/citadel
200 furryrefuge.com Citadel server ADMIN CONNECTION ready.
SETU Use R. Name|80|24|0|0|0|0|0|0|0|0
200 Ok
sendcommand: processing ended.
This is hands-down the best email server and networking server for groups and small businesses. i use this daily for my community where we have a support room that support@example.com goes to, all server logs that need looking at go to admin@example.com which is an alias for room_Admin@example.com and doing that is so insanely useful and also very unique. after extensively testing out which servers i would want to use personally, i knew this was the one. so switching just because of an issue isn't a problem.. but conversely, i figure the harder the problem, the more you learn. and i got my buddies who run communities of their own to try it too. i figure if i learn more, i can help out more. so in honesty, thank YOU for being willing to help me.
back to the issue though, running the command gave me the error "no citadel.rc" so i made one and now its saying the server is to old for MSG4. so i imagine i should update and i figure (but want to ask first to make sure its ok because it doesn't really flat out say it on the documentation) but since i installed with the script, i should be able to run it again and have it update everything, right? after updating i'll see if the issue persists then try those commands again
i've still got the issue i had with the user and havent been able to try the fix you told me yet due to updating. i backed it up so i could just revert if things don't go well.. and i've not been able to successfully update yet. it seems to go ok but when it goes to "connecting to citadel server" the green [**----------------] loading bar disappears and it just sits there while the website gives me a 503 error. not quite sure what i should check.
it took a while for me to update but i finally figured out how to rebuild the database and all that. so its updated now but when i go into the console with that command it allows me to login and shows me lobby messages, i get to the lobby prompt but it freezes, not allowing any input. it doesn't seem to be taking up any cpu or anything. looking into that issue now, but its running pretty well with the updates and all. no issues and everything's intact after rebuilding the database. going to dig around for logs and see why it would just hang up without doing or saying anything.