Please wait...
0 files
Go to freeipa.org and check out their demo server. Point your Citadel LDAP to it and go !
Better yet, I'll give you a cheat code :)
Go to freeipa.org and check out their demo server. Point your Citadel LDAP to it and go !
I want use my own local LDAP. Its a very secure setup and productive server. I'll wait for a schema down build it inside my lldap.
Dear All,
I am having the following problem with purge. During the processing after purge (where there are generated temporary files that can ocuppy more than 30GBytes. In my case until exaust my free disk space of 52GBytes) there happens several core dumps (each 2 minutes) that citadel recovers every time (until now). Can I infer that the data files are corrupt or are valid after the processing?
Thank you,
Luís Gonçalves.
I am having the following problem with purge. During the processing after purge (where there are generated temporary files that can ocuppy more than 30GBytes. In my case until exaust my free disk space of 52GBytes) there happens several core dumps (each 2 minutes) that citadel recovers every time (until now). Can I infer that the data files are corrupt or are valid after the processing?
Luis, this seems to happen to you a lot. Are you sending large amounts of unusually large messages through your system? If so, and you are limited on disk space, perhaps you should purge more than once per day, so the database can clean up its log files multiple times per day.
To do so, run the following command from your Citadel Server directory:
./sendcommand TDAP
Furthermore, in the next release of Citadel Server we will have support for LMDB, and you might want to convert your database from Berkeley DB to LMDB. This is because LMDB doesn't write separate journal files and will manage your space better.
Hello,
I'm using Citadel 917 and I know I should upgrade but I have a question concerning DKIM keys. I read the thread on DKIM in support and it suggested deleting the domain and re-creating it and the should be in the Aide room. That is not happening. So here are my questions:
1) Does version 917 support the DKIM key?
2) If so, I've manually generated the keys so how do I get Citadel to load them?
Thanks,
Allen
Dear Foobar,
The new Citadel Version is out.
How to convert the database from Berkeley DB to LMDB?
Thank you,
Luís Gonçalves.
I am having the following problem with purge. During the processing after purge (where there are generated temporary files that can ocuppy more than 30GBytes. In my case until exaust my free disk space of 52GBytes) there happens several core dumps (each 2 minutes) that citadel recovers every time (until now). Can I infer that the data files are corrupt or are valid after the processing?
Luis, this seems to happen to you a lot. Are you sending large amounts of unusually large messages through your system? If so, and you are limited on disk space, perhaps you should purge more than once per day, so the database can clean up its log files multiple times per day.
To do so, run the following command from your Citadel Server directory:
./sendcommand TDAP
Furthermore, in the next release of Citadel Server we will have support for LMDB, and you might want to convert your database from Berkeley DB to LMDB. This is because LMDB doesn't write separate journal files and will manage your space better.
Hello,
I'm using Citadel 917 and I know I should upgrade but I have a question concerning DKIM keys. I read the thread on DKIM in support and it suggested deleting the domain and re-creating it and the should be in the Aide room. That is not happening. So here are my questions:
1) Does version 917 support the DKIM key?
2) If so, I've manually generated the keys so how do I get Citadel to load them?
Thanks,
Allen
I don’t want to convert to LMDB. Berkeley is not up to date, but it’s bulletproof. First, I need to know how to build the group schemas for LDAP on my own.
Dear Foobar,
The new Citadel Version is out.
How to convert the database from Berkeley DB to LMDB?
Thank you,
Luís Gonçalves.
I am having the following problem with purge. During the processing after purge (where there are generated temporary files that can ocuppy more than 30GBytes. In my case until exaust my free disk space of 52GBytes) there happens several core dumps (each 2 minutes) that citadel recovers every time (until now). Can I infer that the data files are corrupt or are valid after the processing?
Luis, this seems to happen to you a lot. Are you sending large amounts of unusually large messages through your system? If so, and you are limited on disk space, perhaps you should purge more than once per day, so the database can clean up its log files multiple times per day.
To do so, run the following command from your Citadel Server directory:
./sendcommand TDAP
Furthermore, in the next release of Citadel Server we will have support for LMDB, and you might want to convert your database from Berkeley DB to LMDB. This is because LMDB doesn't write separate journal files and will manage your space better.
1) Does version 917 support the DKIM key?
2) If so, I've manually generated the keys so how do I get Citadel to
Citadel 917 was released in 2018. I'm happy to hear it has served you so well without upgrading it but we did not add DKIM support until 2024. As it so happens, we actually just published a new version of Citadel Server just yesterday that improves the DKIM signing algorithm even more.
Please upgrade to the newest version. As soon as you do so, the server will automatically generate your DKIM keys, and the helpful Citadel Aide will automatically post a system bulletin telling you what TXT records to put in your DNS.
It's not just easy, it's "Citadel Easy". But you have to do the upgrade.
I don’t want to convert to LMDB. Berkeley is not up to date, but it’s
bulletproof. First, I need to know how to build the group schemas for
LDAP on my own.
Motobike: the LMDB remark was not directed to you, that was for someone else.
Berkeley DB is just fine.
The most recent version of Citadel Server has additional prompts during system setup. Should you choose to use LDAP, just as before, you'll be asked whether your LDAP directory is using the POSIX schema (OpenLDAP, FreeIPA, 389 Directory, etc) or the Microsoft schema (Microsoft Active Directory). You'll be asked for your Base DN, Bind DN, and Bind Password, just as before.
What's new is that you will now also be asked for the LDAP group name for Citadel Administrators. You should supply the name of the group (just its name should work, you probably don't need to specify it by DN) you're using for this. Any user who logs in to Citadel and is a member of that group will automatically have Admin privileges for the duration of that session.
1) Does version 917 support the DKIM key?
2) If so, I've manually generated the keys so how do I get Citadel to
Citadel 917 was released in 2018. I'm happy to hear it has served you so well without upgrading it but we did not add DKIM support until 2024. As it so happens, we actually just published a new version of Citadel Server just yesterday that improves the DKIM signing algorithm even more.
Please upgrade to the newest version. As soon as you do so, the server will automatically generate your DKIM keys, and the helpful Citadel Aide will automatically post a system bulletin telling you what TXT records to put in your DNS.
It's not just easy, it's "Citadel Easy". But you have to do the upgrade.
Thanks!
How to convert the database from Berkeley DB to LMDB?
For starters, you have to be running the Docker version; we haven't added LMDB support to the Easy Install build yet.
Start by running it on a test system, and set the environment variable "BACKEND" to the value "lmdb" when starting the container; for example, "-e BACKEND=lmdb"
If it looks like it's working, wipe that out and export your BDB with a command like:
docker run -i --network host --rm -e BACKEND=bdb --volume=/usr/local/citadel-old:/citadel-data citadeldotorg/citadel -e >dump.dat
That'll dump your old database. Then import it:
docker run -i --network host --rm -e BACKEND=lmdb --volume=/usr/local/citadel-new:/citadel-data citadeldotorg/citadel -i <dump.dat
Once your data is imported, just start the container as normal with the new data directory. It will detect the correct database and start up.
I have a VPS with citadel. I will wait for the Easy Install with the feature.
How to convert the database from Berkeley DB to LMDB?
For starters, you have to be running the Docker version; we haven't added LMDB support to the Easy Install build yet.
Start by running it on a test system, and set the environment variable "BACKEND" to the value "lmdb" when starting the container; for example, "-e BACKEND=lmdb"
If it looks like it's working, wipe that out and export your BDB with a command like:
docker run -i --network host --rm -e BACKEND=bdb --volume=/usr/local/citadel-old:/citadel-data citadeldotorg/citadel -e >dump.dat
That'll dump your old database. Then import it:
docker run -i --network host --rm -e BACKEND=lmdb --volume=/usr/local/citadel-new:/citadel-data citadeldotorg/citadel -i <dump.dat
Once your data is imported, just start the container as normal with the new data directory. It will detect the correct database and start up.
Be sure to back everything up because this is destructive.
Just tried to plug in Home Assistant's CalDAV support to Citadel, and discovered that it wants to use the "REPORT" command, which based on what I'm seeing in the current source code, looks like it just dumps an "Error 500". Any chance this might end up being supported at some point?
... also, there are several better options for it to return than "500 Internal Server Error" --
- 501 Not Implemented
- 405 Method Not Allowed (include an Allow header that says what methods are implemented)
- 403 Forbidden with a body indicating <D:supported-report/> being an empty set, showing that it doesn't support any kinds of reports
Then a proper client implementation would know not to send it again (although i don't know if the HA implementation would degrade properly)
... also calendar event entry and ICS appear to be broken pretty badly .. I tried to enter a test entry for 22:00 to 23:00 tonight (it's 21:47 right now), and it shows up for 01:00 to 02:00 tomorrow. I didn't set it as recurring, but it gets exported as a broken recurring event in ICS format:
> Value error, RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware
Just tried to plug in Home Assistant's CalDAV support to Citadel, and discovered that it wants to use the "REPORT" command, which based on what I'm seeing in the current source code, looks like it just dumps an "Error 500".
Bad news: WebCit does not support CalDAV. At all.
Any chance this might end up being supported at some point?
Good news: it's already been completed. WebCit-NG has full CalDAV and CardDAV support. It's working with several different clients, including DAVx5 on Android and Thunderbird on desktop. Even the WebCit-NG user interface itself is using CalDAV and CardDAV on the back end to access its own data stores.
We're aiming for general availability late this year.