Hello,

I've managed to connect thunderbird to the calender, using the documented URL: http://<server>/groupdav/calendar/calendar.ics

However, I am struggeling to find a corresponding url for the contacts

/groupdav/Contacts/ does not work, thunderbird does ask for the password, but afterwards reports a "failed to connect" error, when trying to add a caldav addressbook. Contrary to what I could find, it does not matter, wether I provide the port with the server address or not. Also a newly created address room cannot be found 

For news, thunderbird reports, it has connected to the news server, but it does not find any groups to possibly subscribe to.

Since there is no dedicated news option for new rooms, I would have expected the public rooms to be available.  At least those, that have been created by that particular user. Or how would I create a news group, in case this is the more appropiate question

Thanks

Another beginners question: Is there a way to use the text mode client when running the docker image? The client itself is part of the image, but so far there seems to be no way of remotely accessing it.Well, besides "podman exec -it citadel /usr/local/bin/citadel". Obviously not a feasible option.

Neither telnet nor ssh seem to be installed and I am not aware of any remote text client. Hopefully I am just missing the last one? 

Has anyone tried this yet? Any hints I might have missed in the documentation?

Thanks

First of all, thank you very much for your answer. I found the source of the problem and prevented it from recurring. Whatever the PutEmail function used by the Apache NiFi application to send mail was doing, it was avoiding the message processing ID from being added to new messages. You can print the debug log with the "-X 9" parameter when starting the container to get the logs. The emails were falling into the Inbox without any rules working. Sending and receiving mail was working normally. Only the Inbox rules were not working.

Hi!

I use Citadel 2 years ago, but recently, I can't send emails to mailboxes hosted on O2Switch (error 421 with no further explanation).

I can communicate with any mailbox on any host (GMail, Outlook, Orange, etc.) but not with them (I can receive emails from them from two domains hosted with them, but not vice versa).

And for their part, they have no problem communicating with anyone...

Could someone help me? Because this type of problem is really stumping me...

Thanks in advance

Hello!

But recently, I can't send emails to mailboxes hosted on O2Switch (error 421 with no further explanation).

I can communicate with any mailbox on any host (GMail, Outlook, Orange, etc.) but not with them (I can receive emails from them from two domains hosted with them, but not vice versa).

And for their part, they have no problem communicating with anyone, and don't see any SMTP connections...

Could someone help me? Because this type of problem is really stumping me...

Thanks in advance

Hello!

But recently, I can't send emails to mailboxes hosted on O2Switch (error 421 with no further explanation).

I can communicate with any mailbox on any host (GMail, Outlook, Orange, etc.) but not with them (I can receive emails from them from two domains hosted with them, but not vice versa).

And for their part, they have no problem communicating with anyone, and don't see any SMTP connections...

Could someone help me? Because this type of problem is really stumping me...

Thanks in advance

Di Jun 24 2025 02:27:46 UTC von IGnatius T Foobar Betreff: Re: URLs for external clients for contacts & news

However, I am struggeling to find a corresponding url for the contacts

Does the Thunderbird client support accessing the contacts list in that way?
To the best of my knowledge it does not.

When you connect Thunderbird to the Citadel calendar you're basically accessing the calendar "as a whole" which is to say, it downloads the whole calendar, then when you make changes it reuploads the whole calendar.

Thunderbird also supports CalDAV and probably CardDAV, which will be fully supported in the not-yet-released WebCit-NG, but unfortunately the current version does not support those protocols.

Thanks very much. I have just found a post, that claimed to have accomplished just that, so I've assumed, it was simply me. Indeed I was trying to use caldav, as this seemed to be the natural choice. No biggy, I'll stick with LDAP for the time being.  

Di Jun 24 2025 02:23:28 UTC von IGnatius T Foobar Betreff: Re: Textclient and docker

No doubt this is a hacky solution and one that we intend to solve a more elegant way in the future.

Thanks again for the explanation. Good to know, not all is grim for the future!

I've been messing with various BBS's to have on one of the systems at my VCF table this year and, remembering Citadel of long ago, thought maybe I'd give it a shot.

I have a SPARCstation 20 running Solaris 7 and found source for Citadel-UX 5.52 and 6.14, both have various build issues and wondered if there might happen to be some other versions of the source around somewhere. Whatever the latest source release was in the 5.x and 6.x trees might help in building this museum piece.

/TIA

Nothing specifically really other than a text mode BBS, there are many DOS and other options, not many for Solaris (which is one of the machines I have on hand). The only real requirement is that I’m trying to target the year 1999 and have it there at the table so anyone can use it 

Version 6 has more Yacc issues than I care to tackle, but after fixing a couple small bugs in the 5.52 version, and adjusting make options, I have it built and working.

Running the docker image on arch/podman 5.5.1 (unpriviledged) seems to crash rather happily, after some light use:

Just in case, this output is of any use, meanthile I'll try a complete reboot:

Jun 26 18:16:58 podhost systemd-coredump[72142]: Process 71754 (citserver) of user 666 terminated abnormally with signal 11/SEGV, processing...
Jun 26 18:16:58 podhost systemd[1]: Started Process Core Dump (PID 72142/UID 0).
Jun 26 18:16:58 podhost systemd-coredump[72143]: Process 71754 (citserver) of user 666 dumped core.
                                                            
                                                            Stack trace of thread 268:
                                                            #0  0x000077723f430ad9 n/a (/lib/x86_64-linux-gnu/libc-2.31.so + 0x16aad9)
                                                            #1  0x000077723b453630 n/a (n/a + 0x0)
                                                            ELF object binary architecture: AMD x86-64
Jun 26 18:16:58 podhost systemd[1]: systemd-coredump@1-72142-0.service: Deactivated successfully.
Jun 26 18:16:58 podhost citadel[614]: ctdlvisor: pid=265 exited, status=139, exitcode=0
Jun 26 18:16:58 podhost citadel[614]: ctdlvisor: citserver crashed on signal 11
Jun 26 18:16:58 podhost citadel[614]: ctdlvisor: citserver running on pid=274
Jun 26 18:16:58 podhost citadel[614]: ctdlvisor: executing citserver
Jun 26 18:17:40 podhost systemd-coredump[72187]: Process 72149 (citserver) of user 666 terminated abnormally with signal 11/SEGV, processing...
Jun 26 18:17:40 podhost systemd[1]: Started Process Core Dump (PID 72187/UID 0).
Jun 26 18:17:40 podhost systemd-coredump[72188]: Process 72149 (citserver) of user 666 dumped core.
                                                            
                                                            Stack trace of thread 275:
                                                            #0  0x00007915a0fdaad9 n/a (/lib/x86_64-linux-gnu/libc-2.31.so + 0x16aad9)
                                                            #1  0x000079159e009630 n/a (n/a + 0x0)
                                                            ELF object binary architecture: AMD x86-64
Jun 26 18:17:40 podhost citadel[614]: ctdlvisor: pid=274 exited, status=139, exitcode=0
Jun 26 18:17:40 podhost citadel[614]: ctdlvisor: citserver crashed on signal 11
Jun 26 18:17:40 podhost citadel[614]: ctdlvisor: executing citserver
Jun 26 18:17:40 podhost citadel[614]: ctdlvisor: citserver running on pid=280
Jun 26 18:17:40 podhost systemd[1]: systemd-coredump@2-72187-0.service: Deactivated successfully.
Jun 26 18:18:28 podhost systemd-coredump[72202]: Process 72192 (citserver) of user 666 terminated abnormally with signal 11/SEGV, processing...
Jun 26 18:18:28 podhost systemd[1]: Started Process Core Dump (PID 72202/UID 0).
Jun 26 18:18:29 podhost systemd-coredump[72203]: Process 72192 (citserver) of user 666 dumped core.
                                                            
                                                            Stack trace of thread 281:
                                                            #0  0x00007f8ad0c30ad9 n/a (/lib/x86_64-linux-gnu/libc-2.31.so + 0x16aad9)
                                                            #1  0x00007f8acdc5d630 n/a (n/a + 0x0)
                                                            ELF object binary architecture: AMD x86-64
Jun 26 18:18:29 podhost citadel[614]: ctdlvisor: pid=280 exited, status=139, exitcode=0
Jun 26 18:18:29 podhost citadel[614]: ctdlvisor: citserver crashed on signal 11
Jun 26 18:18:29 podhost citadel[614]: ctdlvisor: citserver running on pid=283
Jun 26 18:18:29 podhost systemd[1]: systemd-coredump@3-72202-0.service: Deactivated successfully.
Jun 26 18:18:29 podhost citadel[614]: ctdlvisor: executing citserver
Jun 26 18:19:21 podhost systemd-coredump[72214]: Process 72207 (citserver) of user 666 terminated abnormally with signal 11/SEGV, processing...
Jun 26 18:19:21 podhost systemd[1]: Started Process Core Dump (PID 72214/UID 0).
Jun 26 18:19:21 podhost systemd-coredump[72215]: Process 72207 (citserver) of user 666 dumped core.
                                                            
                                                            Stack trace of thread 284:
                                                            #0  0x0000742305acbad9 n/a (/lib/x86_64-linux-gnu/libc-2.31.so + 0x16aad9)
                                                            #1  0x0000742302af9620 n/a (n/a + 0x0)
                                                            ELF object binary architecture: AMD x86-64
Jun 26 18:19:21 podhost systemd[1]: systemd-coredump@4-72214-0.service: Deactivated successfully.
Jun 26 18:19:21 podhost citadel[614]: ctdlvisor: pid=283 exited, status=139, exitcode=0
Jun 26 18:19:21 podhost citadel[614]: ctdlvisor: citserver crashed on signal 11
Jun 26 18:19:21 podhost citadel[614]: ctdlvisor: executing citserver
Jun 26 18:19:21 podhost citadel[614]: ctdlvisor: citserver running on pid=287
Jun 26 18:19:55 podhost systemd-coredump[72227]: Process 72219 (citserver) of user 666 terminated abnormally with signal 11/SEGV, processing...
Jun 26 18:19:55 podhost systemd[1]: Started Process Core Dump (PID 72227/UID 0).
Jun 26 18:19:55 podhost systemd-coredump[72228]: Process 72219 (citserver) of user 666 dumped core.
                                                            
                                                            Stack trace of thread 289:
                                                            #0  0x000077fca9a75ad9 n/a (/lib/x86_64-linux-gnu/libc-2.31.so + 0x16aad9)
                                                            #1  0x000077fca62a0630 n/a (n/a + 0x0)
                                                            ELF object binary architecture: AMD x86-64
Jun 26 18:19:55 podhost systemd[1]: systemd-coredump@5-72227-0.service: Deactivated successfully.
Jun 26 18:19:55 podhost citadel[614]: ctdlvisor: pid=287 exited, status=139, exitcode=0
Jun 26 18:19:55 podhost citadel[614]: ctdlvisor: citserver crashed on signal 11
Jun 26 18:19:55 podhost citadel[614]: ctdlvisor: citserver running on pid=290
Jun 26 18:19:55 podhost citadel[614]: ctdlvisor: executing citserver
Jun 26 18:20:29 podhost systemd-coredump[72237]: Process 72232 (citserver) of user 666 terminated abnormally with signal 11/SEGV, processing...
Jun 26 18:20:29 podhost systemd[1]: Started Process Core Dump (PID 72237/UID 0).
Jun 26 18:20:29 podhost systemd-coredump[72238]: Process 72232 (citserver) of user 666 dumped core.
                                                            
                                                            Stack trace of thread 292:
                                                            #0  0x0000778b2f4faad9 n/a (/lib/x86_64-linux-gnu/libc-2.31.so + 0x16aad9)
                                                            #1  0x0000778b2bd7f630 n/a (n/a + 0x0)
                                                            ELF object binary architecture: AMD x86-64
Jun 26 18:20:29 podhost systemd[1]: systemd-coredump@6-72237-0.service: Deactivated successfully.
Jun 26 18:20:29 podhost citadel[614]: ctdlvisor: pid=290 exited, status=139, exitcode=0
Jun 26 18:20:29 podhost citadel[614]: ctdlvisor: citserver crashed on signal 11
Jun 26 18:20:29 podhost citadel[614]: ctdlvisor: citserver running on pid=293
Jun 26 18:20:29 podhost citadel[614]: ctdlvisor: executing citserver

Sa Jun 28 2025 18:11:05 UTC von IGnatius T Foobar Betreff: Re: docker image keeps crashing

Running the docker image on arch/podman 5.5.1 (unpriviledged) seems to
crash rather happily, after some light use:

If you could run the container in the foreground with full logging turned on, it would be great if you could capture the last screenful of log messages before a crash.

As your previous log capture shows, we've been trying to get it to be better about showing where it crashed, but all we're able to get so far is a program name and memory offset.

I am having trouble getting podmal to be ba any verbose at all, and running in the foreground does not talk much either:

$ podman run --systemd=true --rm --cpus=2 --memory=1g --name=citadel --hostname=hello.world.net --mount=type=bind,source=/daten/podman/data/citadel,destination=/citadel-data,ro=false,U=true --network=pasta:--interface,dummy.pod,--ns-ifname,tap15.pod,--ns-mac-addr,2a:00:00:00:00:15,--address,192.168.89.15,--netmask,255.255.255.0,--gateway,192.168.89.1,--outbound,192.168.89.15,--outbound-if4,dummy.pod,--fqdn,hello.world.net,--no-dhcpv6,--no-dhcp,--dns,none,--no-map-gw,--tcp-ports,192.168.89.1/25,--tcp-ports,192.168.89.1/80,--tcp-ports,192.168.89.1/110,--tcp-ports,192.168.89.1/119,--tcp-ports,192.168.89.1/143,--tcp-ports,192.168.89.1/443,--tcp-ports,192.168.89.1/465,--tcp-ports,192.168.89.1/504,--tcp-ports,192.168.89.1/563,--tcp-ports,192.168.89.1/587,--tcp-ports,192.168.89.1/993,--tcp-ports,192.168.89.1/995,--tcp-ports,192.168.89.1/5222 docker.io/citadeldotorg/citadel
ctdlvisor: Welcome to the Citadel System running in a container.
ctdlvisor: command line arguments: /usr/local/bin/ctdlvisor 
ctdlvisor: /citadel-data is writable
ctdlvisor: /citadel-data/data is writable
ctdlvisor: /citadel-data/files is writable
ctdlvisor: /citadel-data/keys is writable
ctdlvisor: citserver running on pid=2
ctdlvisor: webcit (HTTP) running on pid=3
ctdlvisor: executing citserver
ctdlvisor: executing webcit (http) on port 80
ctdlvisor: executing webcit (https) on port 443
ctdlvisor: webcit (HTTPS) running on pid=4
ctdlvisor: pid=2 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=10
ctdlvisor: executing citserver
ctdlvisor: pid=10 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=19
ctdlvisor: executing citserver

I have however, attached a coredumd for each of above crashes. Those came from a fresh install (empty citadel-data), so nothing secret in there. I hope. Maybe these help. In case you have any more hints for verbosity, just let me know, please. 

Fr Jul 04 2025 00:47:30 UTC von IGnatius T Foobar Betreff: Re: docker image keeps crashing

I am having trouble getting podmal to be ba any verbose at all, and
running in the foreground does not talk much either:

Ok, let's try this. I added some code to the server and to the supervisor, and now when it crashes it will make its best effort to produce a stack trace that has some filenames and line numbers in it.

Go ahead and update your container with the latest image.

Not too chatty, either. But maybe it is still helpful. As you may see, this is the very first start and it crashes (as it usually does), when loading the page, before the login screen is being presented. Hence, no timezone yet. Another instance, where it regulary chrashes, is, when editing certain parameters of rooms.  But this one is the crash from before the login screen:

$ podman run --systemd=true --rm --cpus=2 --memory=1g --name=citadel --hostname=hello.world.net --mount=type=bind,source=/daten/podman/data/citadel,destination=/citadel-data,ro=false,U=true --network=pasta:--interface,dummy.pod,--ns-ifname,tap15.pod,--ns-mac-addr,2a:00:00:00:00:15,--address,192.168.89.15,--netmask,255.255.255.0
,--gateway,192.168.89.1,--outbound,192.168.89.15,--outbound-if4,dummy.pod,--fqdn,hello.world.net,--no-dhcpv6,--no-dhcp,--dns,none,--no-map-gw,--tcp-ports,192.168.89.1/25,--tcp-ports,192.168.89.1/80,--tcp-ports,192.168.89.1/110,--tcp-ports,192.168.89.1/119,--tcp-ports,192.168.89.1/143,--tcp-ports,192.168.89.1/443,--tcp-ports,192.168.89.1/465,--tcp-ports,192
.168.89.1/504,--tcp-ports,192.168.89.1/563,--tcp-ports,192.168.89.1/587,--tcp-ports,192.168.89.1/993,--tcp-ports,192.168.89.1/995,--tcp-ports,192.168.89.1/5222 docker.io/citadeldotorg/citadel
Trying to pull docker.io/citadeldotorg/citadel:latest...
Getting image source signatures
Copying blob cf1db188696b done   |  
Copying blob cc41ef31545f done   |  
Copying blob ff44dcceb233 done   |  
Copying blob 36fc4513d1bb done   |  
Copying blob 4f4fb700ef54 done   |  
Copying blob 2ae7966dbe43 done   |  
Copying blob ae1048e58da0 done   |  
Copying blob 86d5ae05b3a0 done   |  
Copying blob ccbf3b9f7451 done   |  
Copying config 1c45cdb189 done   |  
Writing manifest to image destination
ctdlvisor: Welcome to the Citadel System running in a container.
ctdlvisor: command line arguments: /usr/local/bin/ctdlvisor  
ctdlvisor: /citadel-data is writable
ctdlvisor: /citadel-data/data is writable
ctdlvisor: /citadel-data/files is writable
ctdlvisor: /citadel-data/keys is writable
ctdlvisor: citserver running on pid=2
ctdlvisor: executing citserver
ctdlvisor: webcit (HTTP) running on pid=3
ctdlvisor: webcit (HTTPS) running on pid=4
ctdlvisor: executing webcit (http) on port 80
ctdlvisor: executing webcit (https) on port 443
/usr/local/citadel/guesstimezone.sh: 350: echo: echo: I/O error
ctdlvisor: pid=2 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
/citadel/server/session.c:64
??:0
sequence.c:?
/citadel/server/modules/expire/serv_expire.c:142 (discriminator 1)
/citadel/server/modules/imap/serv_imap.c:1130
??:0
ctdlvisor: citserver running on pid=1047
ctdlvisor: executing citserver