Language:
switch to room list switch to menu My folders
Go to page: First ... 16 17 18 19 [20] 21
[#] Fri Jun 14 2024 03:03:58 EDT from luisgo

Subject: Spamassassin/Citadel problem

[Reply] [ReplyQuoted] [Headers] [Print]

Dear All,

I installed Spamassassin and configured in Citadel.

See here my Logwatch of yesterday:

SpamAssassin

 
Mail Recipients:
  (unknown) :   79 clean,     1 spam
 
Summary:
    Total Clean:    79 ( 99%)
    Total Spam:      1 (  1%)
 
Top 10 Spam Relays:
  : 1 Time(s)
 
"still running as root" error: 80 time(s)
 
Child-related errors
  spamd: cannot send SIGINT to child process [___]: No such process: 1 Time(s)

 



[#] Sat Jun 15 2024 10:54:16 EDT from IGnatius T Foobar

Subject: Re: Citadel Server Setup reconfigure

[Reply] [ReplyQuoted] [Headers] [Print]

Is it possible to RECONFIGURE a Citadel Server once you install the libldap2-dev libraries for LDAP support?

If you used Easy Install, delete /usr/local/ctdlsupport/*.sum and run Easy Install again.

Or just use the container version of Citadel and all the LDAP support is built in for you.



[#] Sat Jun 15 2024 10:57:31 EDT from IGnatius T Foobar

Subject: Re: Spamassassin/Citadel problem

[Reply] [ReplyQuoted] [Headers] [Print]

 

In the default configuration, when SpamAssassin identifies a message as spam, Citadel rejects it.  We believe that this is superior to filing it in a spam folder because when there is a false positive, the sender will receive a bounce and will know what happened.

If you want to change this behavior, there is an option on your Administration screen "Flag spam instead of deleting it" which will simply set the X-Spam-Status header, and this allows you to create an inbox filter rule to handle it as you wish.



[#] Mon Jun 17 2024 02:59:43 EDT from luisgo

Subject: Is this correct? I do not know how to test if SPAM.

[Reply] [ReplyQuoted] [Headers] [Print]



[#] Tue Jun 18 2024 16:40:04 EDT from nickb

Subject: Webcit port 80 to port 8484

[Reply] [ReplyQuoted] [Headers] [Print]

How do you change the port of WEBCIT?

By default it is running on port 80 but I would like to change

HTTP to port 8484 and HTTPS to port 8888

I am using the DOCKER system



[#] Tue Jun 18 2024 21:39:37 EDT from nickb

Subject: changing some settings on Webcit and SMTP

[Reply] [ReplyQuoted] [Headers] [Print]

i need to do two things,

change SMTP port 25 from listening on 127.0.0.1 to 0.0.0.0

and change the webcit from port 443 and port 80 to port 8080 and 8484

how can i do this on debain 12/bookworm

 

root@LAMP2:/etc/default# ss -pltn
State    Recv-Q   Send-Q      Local Address:Port        Peer Address:Port   Process
LISTEN   0        20              127.0.0.1:25               0.0.0.0:*       users:(("exim4",pid=1541,fd=4))
LISTEN   0        128             127.0.0.1:631              0.0.0.0:*       users:(("cupsd",pid=786,fd=7))
LISTEN   0        5                 0.0.0.0:995              0.0.0.0:*       users:(("citserver",pid=7328,fd=31))
LISTEN   0        5                 0.0.0.0:993              0.0.0.0:*       users:(("citserver",pid=7328,fd=27))
LISTEN   0        5                 0.0.0.0:587              0.0.0.0:*       users:(("citserver",pid=7328,fd=34))
LISTEN   0        5                 0.0.0.0:563              0.0.0.0:*       users:(("citserver",pid=7328,fd=29))
LISTEN   0        5                 0.0.0.0:504              0.0.0.0:*       users:(("citserver",pid=7328,fd=25))
LISTEN   0        5                 0.0.0.0:465              0.0.0.0:*       users:(("citserver",pid=7328,fd=33))
LISTEN   0        5                 0.0.0.0:143              0.0.0.0:*       users:(("citserver",pid=7328,fd=26))
LISTEN   0        5                 0.0.0.0:110              0.0.0.0:*       users:(("citserver",pid=7328,fd=30))
LISTEN   0        5                 0.0.0.0:119              0.0.0.0:*       users:(("citserver",pid=7328,fd=28))
LISTEN   0        128               0.0.0.0:22               0.0.0.0:*       users:(("sshd",pid=805,fd=3))
LISTEN   0        4096            127.0.0.1:45853            0.0.0.0:*       users:(("containerd",pid=793,fd=10))
LISTEN   0        5                 0.0.0.0:5222             0.0.0.0:*       users:(("citserver",pid=7328,fd=37))
LISTEN   0        20                  [::1]:25                  [::]:*       users:(("exim4",pid=1541,fd=5))
LISTEN   0        128                 [::1]:631                 [::]:*       users:(("cupsd",pid=786,fd=6))
LISTEN   0        100                     *:443                    *:*       users:(("webcit",pid=7330,fd=5))
LISTEN   0        100                     *:80                     *:*       users:(("webcit",pid=7329,fd=5))
LISTEN   0        128                  [::]:22                  [::]:*       users:(("sshd",pid=805,fd=4))



[#] Wed Jun 19 2024 01:28:11 EDT from nickb

Subject: not able to receive emails

[Reply] [ReplyQuoted] [Headers] [Print]

Is that right? should port 25 be picked up by exim4, or should i delete the exim4 package and try to configure Citadel for port 25

 

 

LISTEN   0        20              127.0.0.1:25               0.0.0.0:*       users:(("exim4",pid=1541,fd=4))
LISTEN   0        5                 0.0.0.0:995              0.0.0.0:*       users:(("citserver",pid=7328,fd=31))
LISTEN   0        5                 0.0.0.0:993              0.0.0.0:*       users:(("citserver",pid=7328,fd=27))
LISTEN   0        5                 0.0.0.0:587              0.0.0.0:*       users:(("citserver",pid=7328,fd=34))
LISTEN   0        5                 0.0.0.0:563              0.0.0.0:*       users:(("citserver",pid=7328,fd=29))
LISTEN   0        5                 0.0.0.0:504              0.0.0.0:*       users:(("citserver",pid=7328,fd=25))
LISTEN   0        5                 0.0.0.0:465              0.0.0.0:*       users:(("citserver",pid=7328,fd=33))
LISTEN   0        5                 0.0.0.0:143              0.0.0.0:*       users:(("citserver",pid=7328,fd=26))
LISTEN   0        5                 0.0.0.0:110              0.0.0.0:*       users:(("citserver",pid=7328,fd=30))
LISTEN   0        5                 0.0.0.0:119              0.0.0.0:*       users:(("citserver",pid=7328,fd=28))



[#] Wed Jun 19 2024 01:40:40 EDT from nickb

Subject: Re: not able to receive emails

[Reply] [ReplyQuoted] [Headers] [Print]

 

Wed Jun 19 2024 01:28:11 EDT from nickb Subject: not able to receive emails

Is that right? should port 25 be picked up by exim4, or should i delete the exim4 package and try to configure Citadel for port 25

 

 

LISTEN   0        20              127.0.0.1:25               0.0.0.0:*       users:(("exim4",pid=1541,fd=4))
LISTEN   0        5                 0.0.0.0:995              0.0.0.0:*       users:(("citserver",pid=7328,fd=31))
LISTEN   0        5                 0.0.0.0:993              0.0.0.0:*       users:(("citserver",pid=7328,fd=27))
LISTEN   0        5                 0.0.0.0:587              0.0.0.0:*       users:(("citserver",pid=7328,fd=34))
LISTEN   0        5                 0.0.0.0:563              0.0.0.0:*       users:(("citserver",pid=7328,fd=29))
LISTEN   0        5                 0.0.0.0:504              0.0.0.0:*       users:(("citserver",pid=7328,fd=25))
LISTEN   0        5                 0.0.0.0:465              0.0.0.0:*       users:(("citserver",pid=7328,fd=33))
LISTEN   0        5                 0.0.0.0:143              0.0.0.0:*       users:(("citserver",pid=7328,fd=26))
LISTEN   0        5                 0.0.0.0:110              0.0.0.0:*       users:(("citserver",pid=7328,fd=30))
LISTEN   0        5                 0.0.0.0:119              0.0.0.0:*       users:(("citserver",pid=7328,fd=28))



 

figured out that one, i just delete exim and then restarted Citadel and the port popped up.

HOWEVER, how do you change the ports for WEBCIT?

to http port 8080 and https port 8484............................

 

LISTEN   0        100                    *:443                  *:*      users:(("webcit",pid=10512,fd=5))      
LISTEN   0        100                    *:80                   *:*      users:(("webcit",pid=10511,fd=5))



[#] Wed Jun 19 2024 03:24:00 EDT from nickb

[Reply] [ReplyQuoted] [Headers] [Print]

This is what I have. How do i change the default port 80/443 to 8080/8484

 

CONTAINER ID   IMAGE                   COMMAND                  CREATED       STATUS         PORTS     NAMES
1374aa8e97ec   citadeldotorg/citadel   "/usr/local/bin/ctdl…"   8 hours ago   Up 4 minutes             citadel

root@LAMP2:/home/nick# docker run
"docker run" requires at least 1 argument.
See 'docker run --help'.

Usage:  docker run [OPTIONS] IMAGE [COMMAND] [ARG...]

Run a command in a new container

LISTEN         0              100                                 *:80                                 *:*             users:(("webcit",pid=1746,fd=5))                         
LISTEN         0              100                                 *:443                                *:*             users:(("webcit",pid=1747,fd=5))



[#] Wed Jun 19 2024 03:46:42 EDT from nickb

[Reply] [ReplyQuoted] [Headers] [Print]

 

Wed Jun 19 2024 03:24:00 EDT from nickb

This is what I have. How do i change the default port 80/443 to 8080/8484

 

CONTAINER ID   IMAGE                   COMMAND                  CREATED       STATUS         PORTS     NAMES
1374aa8e97ec   citadeldotorg/citadel   "/usr/local/bin/ctdl…"   8 hours ago   Up 4 minutes             citadel

root@LAMP2:/home/nick# docker run
"docker run" requires at least 1 argument.
See 'docker run --help'.

Usage:  docker run [OPTIONS] IMAGE [COMMAND] [ARG...]

Run a command in a new container

LISTEN         0              100                                 *:80                                 *:*             users:(("webcit",pid=1746,fd=5))                         
LISTEN         0              100                                 *:443                                *:*             users:(("webcit",pid=1747,fd=5))



 

docker exec -p 80:8080 -p 443:8484 citadeldotorg/citadel   <---- the "-p" is not working for me to change the ports

it would be something like this, but I just can't put y finger on it and wold like some help



[#] Wed Jun 19 2024 04:39:06 EDT from cjonline

Subject: spamassassin - debian

[Reply] [ReplyQuoted] [Headers] [Print]

Hi,

I have citadel and spamassassin set up.. I can see the messages getting marked but the dont seem to be flagged as spam - 

 

Subject: Delta Airline reward - Open immediately!
Message-ID: <eo0fexlcias7oezr-u0jkqocnwg7hx17p-225a5-5e24d@vivaslimcbd.ru.com>
From: "Delta Airlines Opinion Requested" <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 
 
 
I have no idea what's going on here.. please help!
 
Craig.


[#] Wed Jun 19 2024 05:51:10 EDT from Marisa Giancarla <fstltna@yahoo.com> to room_Citadel_Support@uncensored.citadel.org

Subject: Backup database culling

[Reply] [ReplyQuoted] [Headers] [Print]

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?


Marisa

[#] Wed Jun 19 2024 16:48:15 EDT from IGnatius T Foobar

[Reply] [ReplyQuoted] [Headers] [Print]

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.

[#] Wed Jun 19 2024 16:50:24 EDT from IGnatius T Foobar

Subject: Re: spamassassin - debian

[Reply] [ReplyQuoted] [Headers] [Print]

<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.

[#] Wed Jun 19 2024 16:52:39 EDT from IGnatius T Foobar

Subject: Re: Backup database culling

[Reply] [ReplyQuoted] [Headers] [Print]

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.

[#] Thu Jun 20 2024 04:56:42 EDT from cjonline

Subject: Re: spamassassin - debian

[Reply] [ReplyQuoted] [Headers] [Print]

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.

Wed Jun 19 2024 16:50:24 EDT from IGnatius T Foobar Subject: Re: spamassassin - debian
<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.

 



[#] Mon Jun 24 2024 20:36:32 EDT from kdv666

Subject: New installation, can't log out?

[Reply] [ReplyQuoted] [Headers] [Print]

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.

 



[#] Tue Jun 25 2024 07:26:53 EDT from Nurb432

Subject: Re: New installation, can't log out?

[Reply] [ReplyQuoted] [Headers] [Print]

No expert here, but id try incognito mode in the browser.  to me it sounds like something is being cached.



[#] Tue Jun 25 2024 20:37:03 EDT from kdv666

Subject: Re: New installation, can't log out?

[Reply] [ReplyQuoted] [Headers] [Print]

Many thanks for the suggestion, you're right.  I'll have to try to see why that's happening!  Regards.

 



[#] Wed Jun 26 2024 03:44:49 EDT from Mike1700

Subject: Re: LDAP and OPENID

[Reply] [ReplyQuoted] [Headers] [Print]

 

Thu Jun 13 2024 00:12:30 EDT from nickb Subject: Re: LDAP and OPENID

 

Mon Jun 10 2024 09:22:42 EDT from IGnatius T Foobar Subject: Re: LDAP and OPENID
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.

 

 



Go to page: First ... 16 17 18 19 [20] 21