I came to conclusion that the database was compromised so I decided to install Citadel completely new and deleted the three folders (ctdlsupport, citadel, webcit) and issued the command "curl https://easyinstall.citadel.org/install | bash."

Installation went smoothly and it asked the ports for webcit and I gave port 3010 (http) and 3011 (https).
After the installation there were two webcits but with ports 4433 and 3344 which were the ports of the "totally" deleted installation! Where the heck could these be found?
I run the setup in the folder webcit and gave the new ports and the webcits were started with the correct ports.

Connection to port 3011 (Firefox, (https://sepegp.fi:3011) gave:
"Secure Connection Failed
An error occurred during a connection to sepegp.fi:3011. You are attempting to import a cert with the same issuer/serial as an existing cert, but that is not the same cert.
Error code: SEC_ERROR_REUSED_ISSUER_AND_SERIAL"

Connection to port 3010 (Firefox, (https://sepegp.fi:3010) worked and I was able to create the old users and sending and receiving emails from internet and locally worked well as usual.
                 
Trying to send email using thunderbird gave:
"Your certificate contains the same serial number as another certificate issued by the certificate authority.  Please get a new certificate containing a unique serial number.
The configuration related to smtp.sepegp.fi must be corrected."

My problem is that I know very little about certificates so can the above cert problems solved easily? Are those certificates are generated by Citadel? Could I use e.g. Let's encrypts certificates?

Anyway I wander how those old things can haunt the "completely" new installation. Some undocumented features here :). But I am happy I can handle the emails again trough the web client.

I'm not a Certificate expert - but removing your bad certs and replacing them with new self-signed certs is pretty easy. 

I discuss it a ways back up in this room. 

I'd give a better answer right now - but I've got to get to work, and then I am travelling all weekend. 

If you can wait until next Tuesday, if no one answers, I may be able to assist with this. 

Tue Jun 29 2021 16:47:12 EDT from sepegp Subject: Re: no header in received emails

I came to conclusion that the database was compromised so I decided to install Citadel completely new and deleted the three folders (ctdlsupport, citadel, webcit) and issued the command "curl https://easyinstall.citadel.org/install | bash."

Installation went smoothly and it asked the ports for webcit and I gave port 3010 (http) and 3011 (https).
After the installation there were two webcits but with ports 4433 and 3344 which were the ports of the "totally" deleted installation! Where the heck could these be found?
I run the setup in the folder webcit and gave the new ports and the webcits were started with the correct ports.

Connection to port 3011 (Firefox, (https://sepegp.fi:3011) gave:
"Secure Connection Failed
An error occurred during a connection to sepegp.fi:3011. You are attempting to import a cert with the same issuer/serial as an existing cert, but that is not the same cert.
Error code: SEC_ERROR_REUSED_ISSUER_AND_SERIAL"

Connection to port 3010 (Firefox, (https://sepegp.fi:3010) worked and I was able to create the old users and sending and receiving emails from internet and locally worked well as usual.
                 
Trying to send email using thunderbird gave:
"Your certificate contains the same serial number as another certificate issued by the certificate authority.  Please get a new certificate containing a unique serial number.
The configuration related to smtp.sepegp.fi must be corrected."

My problem is that I know very little about certificates so can the above cert problems solved easily? Are those certificates are generated by Citadel? Could I use e.g. Let's encrypts certificates?

Anyway I wander how those old things can haunt the "completely" new installation. Some undocumented features here :). But I am happy I can handle the emails again trough the web client.

Hello

i still have that Problem with the autopurger

are there characters or sign not allowed for a Room name in ,,My folders,, ?

greetings

I was able to send and receive emails using citadel on linux, and I was also able to receive an email with a file attachment from gmail. However I was unable to send an email with a file attachment to gmail (have not tested others). An error message saying "The connection to the server was reset while the page was loading" was received. Please let me know if this issue can be resolved. Thanks

hello

i have thunderbird on a Linux system running

the thunderbird client is connected to Citadel with IMAP

when a user renames a folder in ,,my Folders,, it works oneth or twice 

but then thunderbird client keeps the old name while citadel gets the new name

in thunderbird then i get the message

,, no such room ,,

when i click on the Folder

is it not allowed to rename folders/rooms with the thunderbird client ??

greetings

kp

hello

i do not know how to change the baseroom

does anybody know how to change it ?

Hello

does anybody know a Company

where to get support for the Citadel Mailserver?

greetings

kp

Having deleted a user I now cannot recreate that user as it says it already exists

Just wait untill tomorrow, user should be purged an you can create it again.

Sun Jul 11 2021 16:17:54 EDT from johno Subject: user deletion

Having deleted a user I now cannot recreate that user as it says it already exists

hey i have a error when i install citadel on a raspberry 4.

Setup could not connect to a running Citadel server.: Connection refused citadel-admin.socket

everyone a idea?

Greeting to all citadel users.  I just completed an easy-install on a CentOS 8 system and I am having an issue with the cli client.  When I run ./citadel I am prompted to log in and that works, but once i get to the Lobby> prompt then it no longer accepts any input. No matter what commands I try to type, it does nothing.  I cannot even (T)erminate.  The only thing I can do is open another session and do a "killall citadel" to close the client.  I was really hoping for the text client option for use as a legacy BBS style setup.

Thanks in advance for any help!

Never mind... I figured it out.  Finally found that the generated citadel.rc file was placed in the root instead of /usr/local/citadel.  Once i moved it everything works as expected.

Wed Jul 28 2021 22:58:44 EDT from jbach34 Subject: text client not accepting input after logion

Greeting to all citadel users.  I just completed an easy-install on a CentOS 8 system and I am having an issue with the cli client.  When I run ./citadel I am prompted to log in and that works, but once i get to the Lobby> prompt then it no longer accepts any input. No matter what commands I try to type, it does nothing.  I cannot even (T)erminate.  The only thing I can do is open another session and do a "killall citadel" to close the client.  I was really hoping for the text client option for use as a legacy BBS style setup.

Thanks in advance for any help!

Hi all!

I‘ve been running a Citadel server happily for around a year now on a Pi4 under Raspbian Buster, using it as an IMAP and SMTP server.

One of my users needs to change his password due to a potential breach.

When either he changes it or I change it (as admin) it seems to change it ok on the IMAP side but doesn’t change the SMTP side. I‘ve tried both Thunderbird and Microsoft mail as clients.

I think I can probably get around it by creating a temporary new account (say usertemp), copy all of his emails into that on the client, delete his original account, then reply-create the original account the next day with the new password after the auto-purge, then copy everything back from the temp account.

Any ideas about my problem though? 

Appreciate any help,

thanks

Col 

Sat Jul 31 2021 10:19:42 EDT from IGnatius T Foobar Subject: Re: Changing a user password - only changes imap, not smtp

Interesting. I hate to be the one to say "the problem is on your end" but ... Citadel does not have any concept of different passwords for different protocols. The password for an account is the password for all protocols -- IMAP, SMTP, web client access, etc.

The only thing I can think of is perhaps the client is caching old credentials?
Or maybe you have something other than Citadel listening on port 587?

Thanks for replying, what you say makes sense.

I’ll try to set up his client on a fresh device so no there‘s no possibility of the passwords being cached.

There’s definitely only Citadel listening on 587 (goes away to hastily check!) :)

Hi,

tried to use your "AppImage" today to install a fresh Raspberry Pi 4 with 4GB running following Raspian:

lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

cat /etc/debian_version
10.9

Used following image: citadel-932-armv7l.appimage

Independant using citadel-932-armv7l.appimage with run or install, the citadel start crashes with the following information and loops the start every second:

 ./citadel-932-armv7l.appimage -p 8088 -s 8444 run
ctdlvisor: Welcome to the Citadel System, brought to you using AppImage.
ctdlvisor: LD_LIBRARY_PATH = /tmp/.mount_citadeXGtRbm/usr/lib
ctdlvisor:            PATH = /tmp/.mount_citadeXGtRbm/usr/bin
ctdlvisor:          APPDIR = /tmp/.mount_citadeXGtRbm
ctdlvisor:  data directory = /usr/local/citadel
ctdlvisor:       HTTP port = 8088
ctdlvisor:      HTTPS port = 8444
ctdlvisor: citserver running on pid=4882
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel
ctdlvisor: webcit (HTTP) running on pid=4883
ctdlvisor: webcit (HTTPS) running on pid=4884
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/webcit/webcit
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/webcit/webcit
ctdlvisor: pid=4882 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=4885
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel
ctdlvisor: pid=4885 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=4888
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel
ctdlvisor: pid=4888 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=4892
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel
ctdlvisor: pid=4892 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=5019
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel
ctdlvisor: pid=5019 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=5026
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel
ctdlvisor: pid=5026 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=5028
ctdlvisor: executing /tmp/.mount_citadeXGtRbm/usr/local/citadel/citserver with data directory /usr/local/citadel

After CTRL-C the following output appears:
^Cctdlvisor: caught signal 2
ctdlvisor: waiting for all child process to exit...
ctdlvisor: 5029 (Citadel Server) ended, status=139
ctdlvisor: waiting for all child process to exit...
ctdlvisor: 4883 (WebCit HTTP) ended, status=15
ctdlvisor: waiting for all child process to exit...
ctdlvisor: 4884 (WebCit HTTPS) ended, status=15
ctdlvisor: waiting for all child process to exit...
ctdlvisor: exit code 0

ps -ef | grep cit shows:
ps -ef | grep -i cit
root     13683     1 25 21:51 ?        00:00:00 /usr/local/citadel/citadel.appimage run -h /usr/local/citadel -p 8088 -s 8444
root     13688 13681  4 21:51 ?        00:00:00 webcit -x9 -h/tmp/.mount_citadeKf63qY/usr/local/webcit -p 8088 uds /usr/local/citadel
root     13689 13681 34 21:51 ?        00:00:00 webcit -x9 -h/tmp/.mount_citadeKf63qY/usr/local/webcit -s -p 8444 uds /usr/local/citadel
root     13694 13681  4 21:51 ?        00:00:00 [citserver] <defunct>
root     13696  3876  0 21:51 pts/0    00:00:00 grep -i cit

ps -ef | grep 13681
root     13681     1  0 21:51 ?        00:00:00 ctdlvisor run
root     13688 13681  0 21:51 ?        00:00:00 webcit -x9 -h/tmp/.mount_citadeKf63qY/usr/local/webcit -p 8088 uds /usr/local/citadel
root     13689 13681  2 21:51 ?        00:00:00 webcit -x9 -h/tmp/.mount_citadeKf63qY/usr/local/webcit -s -p 8444 uds /usr/local/citadel
root     14047 13681  5 21:51 ?        00:00:00 [citserver] <defunct>
root     14103  3876  0 21:51 pts/0    00:00:00 grep 13681

Using Citadel for several years meanwhile. Running one instance on a Rasperry Pi 3b that I installed with "Easy Install". But as you also provide an Image version, I thought giving this one a try. But it seems not to work for me.

If you need any furhter information, give me a note.

Cheers,
Garfield73

Just to give you a bit more information. After running systemctl stop citadel, the defunc pid disappears - as all the other citadel ones.

If I use then either ...run or do systemctl start citadel, the ps output looks similar to the one I pasted earlier - with different pid´s for sure.

Cheers,
Garfield73