Hexdump of 112702

00000000  6d 73 67 74 65 78 74 7c  31 31 32 37 30 32 7c 2f  |msgtext|112702|/|

00000010  77 41 45 53 54 59 33 4e  30 59 7a 52 6a 55 33 4c  |wAESTY3N0YzRjU3L|

00000020  54 46 43 4f 44 4e 46 51  47 4e 68 61 6e 4e 76 5a  |TFCODNFQGNhanNvZ|

00000030  6e 51 75 59 32 38 75 64  57 73 41 55 48 52 6c 63  |nQuY28udWsAUHRlc|

00000040  33 52 41 59 32 46 71 63  32 39 6d 64 43 35 6a 62  |3RAY2Fqc29mdC5jb|

00000050  79 35 31 61 77 42 55 4d  54 63 7a 4e 6a 4d 35 4d  |y51awBUMTczNjM5M|

00000060  6a 55 7a 4e 51 42 50 4d  44 41 77 4d 44 41 77 4d  |jUzNQBPMDAwMDAwM|

00000070  44 41 78 4e 53 35 54 5a  57 35 30 49 45 6c 30 5a  |DAxNS5TZW50IEl0Z|

00000080  57 31 7a 41 46 5a 6b 61  48 4a 31 64 6d 74 68 64  |W1zAFZkaHJ1dmthd|

00000090  58 4e 6f 61 57 74 41 5a  32 31 68 61 57 77 75 59  |XNoaWtAZ21haWwuY|

000000a0  32 39 74 41 45 31 53 5a  57 4e 6c 61 58 5a 6c 5a  |29tAE1SZWNlaXZlZ|

000000b0  44 6f 67 5a 6e 4a 76 62  53 41 78 4d 43 34 31 4c  |DogZnJvbSAxMC41L|

000000c0  6a 41 75 4d 69 41 6f 4d  54 55 78 4c 6a 59 77 4c  |jAuMiAoMTUxLjYwL|

000000d0  6a 45 34 4d 69 34 78 4f  54 4d 67 57 7a 45 31 4d  |jE4Mi4xOTMgWzE1M|

000000e0  53 34 32 4d 43 34 78 4f  44 49 75 4d 54 6b 7a 58  |S42MC4xODIuMTkzX|

000000f0  53 6b 4b 43 57 4a 35 49  47 4e 68 61 6e 4e 76 5a  |SkKCWJ5IGNhanNvZ|

00000100  6e 51 75 59 32 38 75 64  57 73 37 49 46 52 6f 64  |nQuY28udWs7IFRod|

00000110  53 77 67 4d 44 6b 67 53  6d 46 75 49 44 49 77 4d  |SwgMDkgSmFuIDIwM|

00000120  6a 55 67 4d 44 4d 36 4d  44 41 36 4d 44 51 67 4c  |jUgMDM6MDA6MDQgL|

00000130  54 41 77 4d 44 41 4b 43  67 41 3d 7c 0a 6d 73 67  |TAwMDAKCgA=|.msg|

00000140  6d 65 74 61 7c 31 31 32  37 30 32 7c 32 7c 74 65  |meta|112702|2|te|

00000150  78 74 2f 70 6c 61 69 6e  7c 33 30 33 7c 0a        |xt/plain|30

Hexdump of 112703

00000000  6d 73 67 74 65 78 74 7c  31 31 32 37 30 33 7c 2f  |msgtext|112703|/|

00000010  30 45 45 53 54 59 33 4e  30 59 7a 52 6a 55 33 4c  |0EESTY3N0YzRjU3L|

00000020  54 46 43 4f 44 4e 47 51  47 4e 68 61 6e 4e 76 5a  |TFCODNGQGNhanNvZ|

00000030  6e 51 75 59 32 38 75 64  57 73 41 55 45 4e 70 64  |nQuY28udWsAUENpd|

00000040  47 46 6b 5a 57 77 41 56  44 45 33 4d 7a 59 7a 4f  |GFkZWwAVDE3MzYzO|

00000050  54 49 31 4d 7a 55 41 51  55 4e 70 64 47 46 6b 5a  |TI1MzUAQUNpdGFkZ|

00000060  57 77 41 54 31 39 66 51  32 6c 30 59 57 52 6c 62  |WwAT19fQ2l0YWRlb|

00000070  46 4e 4e 56 46 42 7a 63  47 39 76 62 47 39 31 64  |FNNVFBzcG9vbG91d|

00000080  46 39 66 41 45 70 6b 62  79 42 75 62 33 51 67 61  |F9fAEpkbyBub3Qga|

00000090  6d 39 31 63 6d 35 68 62  41 42 56 55 55 31 54 52  |m91cm5hbABVUU1TR|

000000a0  77 42 4e 51 32 39 75 64  47 56 75 64 43 31 30 65  |wBNQ29udGVudC10e|

000000b0  58 42 6c 4f 69 42 68 63  48 42 73 61 57 4e 68 64  |XBlOiBhcHBsaWNhd|

000000c0  47 6c 76 62 69 39 34 4c  57 4e 70 64 47 46 6b 5a  |Glvbi94LWNpdGFkZ|

000000d0  57 77 74 5a 47 56 73 61  58 5a 6c 63 6e 6b 74 62  |WwtZGVsaXZlcnktb|

000000e0  47 6c 7a 64 41 6f 4b 62  58 4e 6e 61 57 52 38 4d  |GlzdAoKbXNnaWR8M|

000000f0  54 45 79 4e 7a 41 79 43  6e 4e 31 59 6d 31 70 64  |TEyNzAyCnN1Ym1pd|

00000100  48 52 6c 5a 48 77 78 4e  7a 4d 32 4d 7a 6b 79 4e  |HRlZHwxNzM2MzkyN|

00000110  54 4d 31 43 6d 4a 76 64  57 35 6a 5a 58 52 76 66  |TM1CmJvdW5jZXRvf|

00000120  48 52 6c 63 33 51 4b 63  6d 56 74 62 33 52 6c 66  |HRlc3QKcmVtb3Rlf|

00000130  47 52 6f 63 6e 56 32 61  32 46 31 63 32 68 70 61  |GRocnV2a2F1c2hpa|

00000140  30 42 6e 62 57 46 70 62  43 35 6a 62 32 31 38 4d  |0BnbWFpbC5jb218M|

00000150  48 78 38 43 67 41 3d 7c  0a 6d 73 67 6d 65 74 61  |Hx8CgA=|.msgmeta|

00000160  7c 31 31 32 37 30 33 7c  31 7c 61 70 70 6c 69 63  ||112703|1|applic|

00000170  61 74 69 6f 6e 2f 78 2d  63 69 74 61 64 65 6c 2d  |ation/x-citadel-|

00000180  64 65 6c 69 76 65 72 79  2d 6c 69 73 74 7c 32 38  |delivery-list|28|

00000190  37 7c 0a                                          |7|.|

00000193

So, on the plus side, doing my daily lunchtime check of code.citadel.org, I saw that Citadel 1008 has been built.

On the negative side, Easyinstall still gives 1007.

Am I just early to the party? I feel like I might well be, but I just wanted to mention it in case something didn't get updated like it should have down the line.

Wed Jan 15 2025 23:00:26 UTCfrom IGnatius T Foobar Subject: Re: Citadel Protocol binding for Dart Native?

Thanks for your help :)

its finally up and running and not crashing anymore..

How can I bulk delete messages in the smtp queue.. ? there is thousands.

Craig.

Fri Jan 17 2025 03:13:12 UTC from IGnatius T Foobar Subject: Re: citdel db issues (Log)

cjonline: I have successfully reproduced your crash and can confirm that the hotfix in Citadel 1008 will prevent the server from crashing.

However, I should warn you that if your queue contains thousands of spams, you definitely don't want to just install the fix and go right back online, because that will cause all of the spams to be delivered (minus the corrupted one that's crashing the server).

If you don't have a backup that was taken before the spams arrived, may I suggest this course of action:

0. Start taking backups in the future. Please.
1. Upgrade the Citadel installation, but don't start it yet.
2. Disconnect your server from the network, *or* if you're proficient with iptables, block outgoing connections on port 25.
3. Start the Citadel Server and log in.
4. Go to the hidden room called __CitadelSMTPspoolout__ (the text client might be good for this)
5. DELETE EVERY MESSAGE IN THAT ROOM. That's the queue.
6. Shut down Citadel Server, take a backup, start it up again, and go back online.

Obviously you're also going to want to audit your system and find the account that was compromised, and change the password.

I hope this is helpful!

thanks, but I had message in there that I needed to keep... therefore I managed to change the view of the folder to mailbox view and deleted all the messages..

site is back up and mail is working again.. 

thanks again.

you Rock!

Fri Jan 17 2025 14:05:26 UTC from IGnatius T Foobar Subject: Re: citdel db issues (Log)

How can I bulk delete messages in the smtp queue.. ? there is
thousands.

The rude-and-crude way would be to go to the room called __CitadelSMTPspoolout__ and delete the room, then restart Citadel Server. When you restart it a new queue will be created.

When you delete a room its contents are moved to a hidden namespace and resources are reclaimed the next time the auto-purger is run, so you won't see a change in disk space immediately.

The default docker ran with the command from the docs

mkdir /usr/local/citadel
docker run -i --rm --network host --volume=/usr/local/citadel:/citadel-data citadeldotorg/citadel

opens starttls ports, but not tls ports. Why would this be?

I've figured it out, the ports are set to -1 by default and the documentation on default opened ports is wrong. You can edit them with this: citadel.org

If you're a user of the text mode client, there has been some significant refactoring of that code. Not a lot of what we did is readily visible but we had a few people who wanted to build on top of it so we did some very nice cleaning up in that part of the system. It was really old code, full of gotos and other horrors, so it needed some love :)

 

 

 

Yep, I saw the code improvements being made (I legitimately look at the code page once a day as a matter of interest) and am honestly quite pleased with the text mode client currently.  Behaves fine as far as auto color detection for any reasonable terminal -- gives only monochrome in Syncterm but I kind of like that (use a real terminal for citadel amirite?.) and doesn't have the usual code spillover for color detection like it used to in any situation I've been able to test except for one condition: if the baud rate is too low and the logon screen doesn't finish before the auto-detect threshold (I'm presuming that's the time criteria) then you will get said spillover. Honestly, not that big a concern as even my C128 wifi modem does 9600 normally (too bad I don't have access to it to test right now) but it is a case where such can happen. I would hope anyone crazyenough to access my BBS with a 300 baud modem would also be smart enough to just backspace before putting in their name. ;)

Secondly, I have to applaud that the formatting of text in the messages folder is now respected by the text client -- something I was meaning to ask about but didn't as I don't want to be annoying and at this stage everything I think could be improved seems to be improved in the next build. Really makes my logon screen work well, and I can use an ASCI banner on the logon and know it will print correctly on screens larger than 80 columns wide!

Screenshot from a Windows 2000 VM, for that Y2K authenticity.

PS: Also working perfectly in the telnet client that comes with FreeDOS, for what that's worth. :D

Fri Jan 17 2025 03:19:34 UTCfrom IGnatius T Foobar Subject: Re: Citadel Protocol binding for Dart Native?

Your project sounds interesting and fun. Looking forward to seeing it.

You can monitor the progress at my CodeBerg.org repo. So far it's a mockup of some of the screens with placeholder text. Once I started getting the hang of the Dart language, it's turning out to be pretty easy to work with. Every now and then I have to look up a command syntax on the webs but as long as I'm using Intellisense on OSS (VS Code with the snooping taken out), it's starting to go pretty smoothly even.

I looked through the C source file you indicated on the text client. It's clean code for C and I have no trouble reading it. At this point the only reason I'd reinvent the protocol source is if I wanted it to be the same license as the client itself.

Of course, making the C client code into an LGPL shared object would tip the scales fully in favor of using the C client code. On the other side of the scale, Dart makes code that's portable across 5 platforms plus 2 in the browser itself (standard web page with JavaScript or compiled web page with WebAssembly). If one platform didn't support such a shared object, I'd probably translate the code into MIT licensed Dart.

I noticed a few bugs in the web interface or the underlying infrastructure. If they are all in WebCit, I wouldn't be surprised.

1. I entered an event in the calendar here and it translated the times into a different timezone. I don't mind if it's stored in the server as GMT because the server uses Linux. When it gets sent back to my browser it shows in GMT still instead of my native timezone, though.
2. I've noticed some of the HTML formatting in the editor is not as flexible as raw HTML in the respective mode of the editor. In other words, I can edit paragraph tags into header tags and it shows headers right after I submit the changes. It's probably a minor matter as the text editor upstream hasn't been updated. 
3. The only way I've found to enter links on this page is to do it manually in HTML mode as well. Once entered, the ghosted link icon springs to life and lets me edit the link I've just created.
4. Once a message is saved to drafts, there is no way to make it post. Even moving the message to a room is typically unsuccessful. (This is on a system a few versions back.)

I wouldn't be surprised if this is all WebCit standard bugs, so I just would like to know if these are known bugs or not?

Dear all,

Is this settings enouth for a citadel email server co-sited with Apache to be deployed?

Email server with only two active users. Apache with less than 10GBytes/month activity.

VPS with 2 CPU cores, 3 GB RAM. I am doubting about 2CPU cores as the minimum number of threads of citadel is 5. Must I limit the number maximum number of threads? I have now 16.

Thanks,

Luís Gonçalves. 

I have a fair number of users in DE and FR who would like the interface to be in their native language.

How do I do that?