docker exec -p 80:8080 -p 443:8484 citadeldotorg/citadel <----
the "-p" is not working for me to change the ports
"docker exec" runs a command inside a container that is already running.
If you want to map ports, you have to do two things:
1. Specify your "-p" command as part of "docker run", not "docker exec"
2. You'll have to map *every* port if you're not going to use the "--network=host" directive. The example given on the web site uses "--network=host" to tell Docker to map the container directly into the host's network namespace, so you'll get port 80 on port 80, port 25 on port 25, etc. etc.
So if you are going to run the container in its own network namespace (which is the Docker default) you will need to "-p" every port that is exposed by Citadel, or at least the ones you intend to use.
<no-reply@vivaslimcbd.ru.com> X-Spam-Level: *** X-Spam-Status: False,
score=3.0 required=5.0 # Set the threshold at which a message
is considered spam (default: 5.0) # # required_score 5.0
In your example, the message has a spam score of 3.0, but it needs a score of at least 5.0 to be considered spam.
That's why it set "X-Spam-Status: False".
If you have Citadel configured to "Flag spam instead of rejecting it" you'll still receive that message, but you can configure it to be redirected or rejected in your inbox rules. But it's not going to do anything for a message that isn't considered spam.
I'm trying to use the "cull" sendcommand but when it runs it gets a
error about the command not being found. Any ideas on this?
Hmm, that documentation might be out of date. The CULL command no longer functions.
The best strategy here is to let the server automatically delete committed database logs. Put it on a filesystem that allows snapshots (btrfs, zfs, etc) and back up a snapshot every night.
I see.. however, every message I get (including all messages I would class as spam, ie fishing emails etc) they dont seem to be getting caught.
<no-reply@vivaslimcbd.ru.com> X-Spam-Level: *** X-Spam-Status: False,
score=3.0 required=5.0 # Set the threshold at which a message
is considered spam (default: 5.0) # # required_score 5.0
In your example, the message has a spam score of 3.0, but it needs a score of at least 5.0 to be considered spam.
That's why it set "X-Spam-Status: False".
If you have Citadel configured to "Flag spam instead of rejecting it" you'll still receive that message, but you can configure it to be redirected or rejected in your inbox rules. But it's not going to do anything for a message that isn't considered spam.
I've only just first-time installed Citadel on Debian 12, using Docker. Many thanks to all those who work on this great software.
All is fine so far, except ...
When I logged into my own server, I created an ordinary user with name and p/w. Then I logged out and logged in as admin. Also no problem.
But when I try to log out as admin so that I can go back to the ordinary user, I hit "Log in again", and it just takes me straight back to "logged in as admin" — there is no opportunity to enter the other credentials.
Am I doing something wrong? I've read the FAQ and Docs ... can't find any help.
No expert here, but id try incognito mode in the browser. to me it sounds like something is being cached.
Many thanks for the suggestion, you're right. I'll have to try to see why that's happening! Regards.
I am running Debian 12, do you know if OPENID is still supported
and what libraries LDAP requires so that the modules are built
during the easy setup process?
OpenID isn't supported anymore, no one was using it and it was becoming a burden to maintain. In the future we are likely to add OAuth and/or SAML because that seems to be what the world is using now.
LDAP is fully supported in every build. If you have Citadel you have LDAP.
Mr. Foobar and Support Team,
If LDAP is fully supported, how do you get rid of the message, "NOTE: This Citadel server has been built without LDAP support. These options will have no effect."
Please also not that my install was partially executed and that i had to manually add some of the "systemctl services"
How do I ENABLE the LDAP support?
I am on debian bookworm.
On a fresh install i am using this
apt install build-essential curl g++ gettext shared-mime-info libssl-dev slapd ldap-utils libical-dev libstdc++6
together with the easy-install script.
Might be too much but is doing the job.
Subject: How to access the admin user with ldap activated
Im on Debian bookworm ( fresh installed )
A fresh install with
apt install build-essential curl g++ gettext shared-mime-info libssl-dev slapd ldap-utils libical-dev libstdc++6
and the easy-install script ends with a working citadel server.
All domain user are pulled in and accessable, BUT not the build in admin user.
So how do i access the bulid in admin user ?
Hello. I've installed Citadel on a Debian 12 VPS using the EasyIntall process. All the compilations, etc, seemed to go without a problem. Eventually, it got to "Restarting Citadel server to apply changes",
which was followed by a line of dots which were replaced by * as the procedure advanced.
When it got to four dots from the end, however, everything hangs. It just sits there, with the last 4 dots unmoving. Eventually, I broke out with a ctrl-C, and ran citadel setup manually, but exactly the same thing happened.
I should add that I accepted all the defaults for the questions that were asked by the setup process, as they seemed reasonable.
All the required ports are open.
I'd appreciate some advice.
Thank you to all those who have put in so much hard work on this project!
Subject: ALL Citadel servers have LDAP. Ignore the warning message.
If LDAP is fully supported, how do you get rid of the message,
"NOTE: This Citadel server has been built without LDAP support.
These options will have no effect."
All right, I just went in to see what the heck is going on with this issue, and here is what I found:
You may IGNORE the message that says "Citadel has been built without LDAP support." There is no such thing. That message displays even if you have a working LDAP setup.
We will work on getting that spurious message removed. In the mean time, the workaround is to ignore it.
Thank you for all of the reports.
Subject: Re: ALL Citadel servers have LDAP. Ignore the warning message.
And to make things a little easier ... we have updated the published Citadel distribution to version 1001, which is now available in source distribution, Docker container, and Easy Install.
There's not much new in this version except for the removal of the erroneous "Citadel has been built without LDAP support" message. Also, the option to switch from self-contained authentication to LDAP authentication has been moved from the "Access" tab to the "Directory" tab. This seems to make a little more sense.
Greetings,
I just visited the Citadel website and found that a link on the website (to the feature list) is broken.
It seems important for new visitors and potential users to be able to find out about the features of Citadel.
From the Web Archive, this link seems broken for a while now.
Link goes to: https://www.citadel.org/doku.php?id=features
Showing this at the destination:
I went back several years and last time this link worked was in 2019:
Suggestion is to fix the broken link.
All the best,
Ernst
... excuse me, 2020.
I guess just the link URL needs to be updated.
All the best,
Ernst
Subject: Re: Website: Broken link to feature list
Hello,
Is it possible to edit a mail in "Drafts" under "My folders"?
Thanks!
I didn't like that general users can see the host location of other visitors. So I made a change (TestUser001 is a non-admin testing account).
Here's the file and location of what you need to edit
- /usr/local/webcit/static/t/who/section.html
- or - /usr/local/webcit/local.static/t/who/section.html
Here's the contents of the file that rendered the above screenshot.
<tr class="<?ITERATE:ODDEVEN>">
<td class="edit_col">
<??("COND:AIDE", 1)><??("WHO:ISME", 2)>
<a href="terminate_session?which_session=<?WHO:SESSION>?template=who" onClick="return ConfirmKill();"><?_("(kill)")></a>
(<a href="display_edituser?username=<?WHO:NAME("U")>&edit_config_button=Edit+configuration&nonce=<?NONCE>"><?_("Edit configuration")></a>)
(<a href="display_edituser?username=<?WHO:NAME("U")>&edit_abe_button=Edit+address+book+entry"><?_("Edit address book entry")></a>)
<??("X", 2)><??("X", 1)>
</td>
<!-- link to page this user -->
<td><a href="display_page?recp=<?WHO:NAME("X")>">
<img src="static/webcit_icons/essen/16x16/chat.png" alt="(p)" title="chat"></a>
| </td>
<!-- idle flag -->
<td>
<?!("WHO:IDLE", 4)>
<img align="middle" src="static/webcit_icons/essen/16x16/user.png" alt="(<?_("idle since")>s <?WHO:IDLESINCE> <?_("Minutes")>)" title="(<?_("idle since")>s <?WHO:IDLESINCE> <?_("Minutes")>)">
<?!("X", 4)>
<??("WHO:IDLE", 5)>
<img align="middle" src="static/webcit_icons/essen/16x16/activeuser.png" alt="(<?_("active")>)">
<?!("X", 5)>
</td>
<!-- username (link to user bio/photo page) -->
<td>
<a href="do_template?template=user_show?who=<?WHO:NAME("U")>"><?WHO:NAME("X")></a>
<??("WHO:NSESSIONS", 6, 1)>[<?WHO:NSESSIONS>]<?!("X", 6)>\
</td>
<!-- room -->
<td>
<?WHO:ROOM>
<?!("WHO:REALROOM", 7)>
<br><i> <?WHO:REALROOM("X")> </i>
<?!("X", 7)>
</td>
<!-- hostname -->
<td class="host_col">
<??("COND:AIDE", 1)><??("WHO:ISME", 2)>
<?WHO:HOST("X")>
<?!("WHO:REALHOST", 8)><br><i> <?WHO:REALHOST("X")></i>
<?!("X", 8)>
<??("X", 2)><??("X", 1)>
</td>
</tr>
Redacting information for the safety of my visitors. 👍
--
- Tumblefluff the Squirrel
I have a server that seems to be keeping the logs forever, and keeps running out of space. How do I force it to remove the logs once they are committed?
Marisa
Would be better posting this over in the support room, will be more likely to be seen. ( and no, i dont have the answer )
I have a server that seems to be keeping the logs forever, and keeps running out of space. How do I force it to remove the logs once they are committed?
Marisa