May not be "the" answer but it seems this is not uncommon in docker.  Down towards bottom of this thread are a couple of manual fixes.

 

https://stackoverflow.com/questions/60959274/time-in-docker-container-out-of-sync-with-host-machine

Try increasing the message limit (20 -> 25mb).
Attachments increase in size when encoded to base64; I think they increase by 20 to 40% of their original size or less but...

From my own experience, if the attachment makes it to the mailbox but the limit is insufficient to contain it, the attachment will arrive corrupted.

Hello,

Fair enough, sorry haha.

Its running on raspbian, build 939.

I've tried several attachments, images, a mp3, pdf files, text files. All of them are under the maximum message limit (I have set to 20 mb i believe).

The email shows up fine, it shows there's an attachment, and it has the file-size correct. When you go to view or download it, the file contains no data.

I'm assuming its not downloading the attachment with the message for some reason?

 

Thanks for your fast reply.

 

Fri Dec 03 2021 17:02:04 EST from IGnatius T Foobar Subject: Re: Mail attachments

Well, you could start by providing enough details for us to help you troubleshoot.
Citadel version, operating system and hardware architecture, what type and size attachments you are trying to deal with, whether you are trying to open them in WebCit or a client software, etc. Don't make us play 20 Questions.

 

Thank you very much! It's more than what I had before, and will dig a bit deeper. I am also thankful that no one said rude things about me. <LOL>

 

Kevin -- KD9EFV

Docker Citadel Server, running Citadel 940 with WebCit 940, server build 940running in Raspbian Bullseye (fully updated) and Docker.io

Trying to figure out how to get Jabber/Pidgin/XMPP clients to connect.

nmap shows port 5222 open.

Cannot connect with any XMPP/Jabber client.

Hostname: blah   Node Name: blah    FQDN: blah   Human Readable Node Name: Citadel Server

Username within Citadel rudeuser

Authentication Mode: Self Contained

Ive tried every combination for JID or username or whatever I can think of:

rudeuser, rudeuser@blah rudeuser@<ip_address> etc... Nothing allows me to connect. I've tried a CLI tool to get any response, tried telnet, all zippo.

What am I missing?

 

KD9EFV -- Kevin

OK, nevermind. I figured out how to fix the XMPP issue, it was a broken certificate.

I spun up a VM, installed Debian Buster, installed the Easy Install version.

Connected to https://ip address, and got the 'no_overlap' error, which led me to a 'bad'

certificate, and led me to creating a new self-signed certificate. Link from web-cit to new

certificate files and viola, working. Now, for a 'new' issue. How do you link the files to

/citadel-data/keys/citadel.* and the necessary stuff to enable the rest of Citadel?

for the previous message, it refers to the Docker container files that you can't get to.

 

Time traveler perhaps? :)

Kinda realized that. So the docker version is broken for secure connections?Unable to link them to the internal location?

 

Sun Dec 05 2021 07:16:03 PM EST from StarbaseSSD Subject: Re: Citadel Docker XMPP client

for the previous message, it refers to the Docker container files that you can't get to.

 

 

Before creating new certificate:

root@bap-test:/usr/local/citadel/keys# ls -la
total 8
drwx------ 2 root root 4096 Dec  9 11:27 .
drwxr-xr-x 6 root root 4096 Dec  9 11:27 ..
lrwxrwxrwx 1 root root   30 Dec  9 11:27 citadel.cer -> /citadel-data/keys/citadel.cer
lrwxrwxrwx 1 root root   30 Dec  9 11:27 citadel.csr -> /citadel-data/keys/citadel.csr
lrwxrwxrwx 1 root root   30 Dec  9 11:27 citadel.key -> /citadel-data/keys/citadel.key

after new key but before restarting citadel docker instance:

openssl genrsa -out citadel.key 2048
openssl req -new -key citadel.key -out citadel.csr
openssl x509 -req -days 365 -in citadel.csr -signkey citadel.key -out citadel.cer

root@bap-test:/usr/local/citadel/keys# ls -la
total 20
drwx------ 2 root root 4096 Dec  9 11:39 .
drwxr-xr-x 6 root root 4096 Dec  9 11:27 ..
-rw-r--r-- 1 root root 1359 Dec  9 11:39 citadel.cer
-rw-r--r-- 1 root root 1147 Dec  9 11:38 citadel.csr
-rw------- 1 root root 1679 Dec  9 11:36 citadel.key

Restart docker container
docker restart citadel
root@bap-test:/usr/local/citadel/keys# ls -la
total 20
drwx------ 2 root root 4096 Dec  9 11:39 .
drwxr-xr-x 6 root root 4096 Dec  9 11:41 ..
-rw-r--r-- 1 root root 1359 Dec  9 11:39 citadel.cer
-rw-r--r-- 1 root root 1147 Dec  9 11:38 citadel.csr
-rw------- 1 root root 1679 Dec  9 11:36 citadel.key
stop docker container
chmod 777 citadel.*

root@bap-test:/usr/local/citadel/keys# ls -la
total 20
drwx------ 2 root root 4096 Dec  9 11:39 .
drwxr-xr-x 6 root root 4096 Dec  9 11:43 ..
-rwxrwxrwx 1 root root 1359 Dec  9 11:39 citadel.cer
-rwxrwxrwx 1 root root 1147 Dec  9 11:38 citadel.csr
-rwxrwxrwx 1 root root 1679 Dec  9 11:36 citadel.key

Stop docker container.
delete citadel.key
restart citadel container
root@bap-test:/usr/local/citadel/keys# ls -la
total 16
drwx------ 2 root root 4096 Dec  9 11:44 .
drwxr-xr-x 6 root root 4096 Dec  9 11:44 ..
-rwxrwxrwx 1 root root 1359 Dec  9 11:39 citadel.cer
-rwxrwxrwx 1 root root 1147 Dec  9 11:38 citadel.csr
lrwxrwxrwx 1 root root   30 Dec  9 11:44 citadel.key -> /citadel-data/keys/citadel.key

Key is now linked but back to broken.

Found a work-around / fix.

=====

sudo apt install docker.io -y
sudo usermod -aG docker pi
sudo mkdir /citadel-data
reboot
docker run -d --restart=unless-stopped --network host \
--volume=/citadel-data:/citadel-data \
--name=citadel citadeldotorg/citadel

docker stop citadel

sudo cd /citadel-data/keys
sudo rm -f citadel.*
sudo openssl genrsa -out citadel.key 2048
sudo openssl req -new -key citadel.key -out citadel.csr
     Answer the questions to the best of your ability
sudo openssl x509 -req -days 365 -in citadel.csr -signkey citadel.key -out citadel.cer
sudo chmod 777 citadel.*
docker start citadel
Connect to Citadel:
https://<ip_address>
username: admin
password: citadel

You get the warning about a self-signed certificate, and you can accept the exception
now, and all the ssl functionality now works in the other connections with the same limitation.

Feel free to use it, update docs, fix the issue for real.

I've tried increasing the maximum message length to 40485760, still wont load a image attached, file size is 43.6 kB (43,551 bytes). It shows up, just has a broken image icon and doesn't load the attachment still. I cant figure it out.

Sat Dec 04 2021 15:06:19 EST from s3cr3to Subject: Re: Mail attachments

Try increasing the message limit (20 -> 25mb).
Attachments increase in size when encoded to base64; I think they increase by 20 to 40% of their original size or less but...

From my own experience, if the attachment makes it to the mailbox but the limit is insufficient to contain it, the attachment will arrive corrupted.

On 12/3/21 15:14, paulb wrote:

Hello,

Fair enough, sorry haha.

Its running on raspbian, build 939.

I've tried several attachments, images, a mp3, pdf files, text files. All of them are under the maximum message limit (I have set to 20 mb i believe).

The email shows up fine, it shows there's an attachment, and it has the file-size correct. When you go to view or download it, the file contains no data.

I'm assuming its not downloading the attachment with the message for some reason?

 

Thanks for your fast reply.

 

Fri Dec 03 2021 17:02:04 EST from IGnatius T Foobar Subject: Re: Mail attachments

Well, you could start by providing enough details for us to help you troubleshoot.
Citadel version, operating system and hardware architecture, what type and size attachments you are trying to deal with, whether you are trying to open them in WebCit or a client software, etc. Don't make us play 20 Questions.

 

 

Mail attachments wont receive correctly. I managed to send a text document attached, but ended up with text like the following; 

ensure that when the wor����2F��R��R�fR6��f�FV�6P��F�R&�6W72�B�W"��O�egrity.

 

There was no formatting in the original document.

I'm assuming this is why no other files are working correctly, the information is corrupted.

Citadel 939 with WebCit 939, server build 939

How does one set their user time zone? I've gone to my Preferences and settings page and am able to change my time format. But, nowhere on that page is an entry for setting for my time zone.

Reason I ask, I have just been admitted to a Citadel machine in Oregon (as an admin) and I live in New Jersey. In particular, getting a calendar entry correct seems difficult. Indeed, under Administration -> General site configuration items there is something called "Default timezone for unzoned calendar items". This would seem to indicate that Citadel is looking for someone's time zone when he makes a calendar entry.  Thus, my question.

Regards

 

Further info:

The system in question has the "Default timezone for unzoned calendar items" set to "America/Los Angeles". This appears to be set correctly for where the machine is located. Unfortunately, when I access the calendar, the dates/times appear to be in UTC. Something seems to be missing...

 

Why is citadel not packed for Debian 11?

 

Although for ease I would ask the same question some time ago.

Today I can say that Citadel presents several options that could be better than a debian package:

From https://www.citadel.org/download.html
A script for installation (EasyInstall) and a Docker version, and even the source code.

The latter needs an enthusiastic volunteer to create and maintain the package for Debian. (note the emphasis)


Personally, I am currently struggling trying to understand Docker (especially in allocating the space I need to migrate).
And of course, I have no doubt that once I master this it will be very easy (... ¿easy? ).

Why is citadel not packed for Debian 11?

 

Peter:

Found a work-around / fix for keys in the docker container. I have tested in both a RaspberryOS host, and a Debian 11 host, YMMV.

Note: The shared volume I had to change from /usr/local/citadel to /citadel-data to get it to work.

=====

sudo apt install docker.io -y
sudo usermod -aG docker pi
sudo mkdir /citadel-data
reboot
docker run -d --restart=unless-stopped --network host \
--volume=/citadel-data:/citadel-data \
--name=citadel citadeldotorg/citadel

docker stop citadel

sudo cd /citadel-data/keys
sudo rm -f citadel.*
sudo openssl genrsa -out citadel.key 2048
sudo openssl req -new -key citadel.key -out citadel.csr
     Answer the questions to the best of your ability
sudo openssl x509 -req -days 365 -in citadel.csr -signkey citadel.key -out citadel.cer
sudo chmod 777 citadel.*
docker start citadel
Connect to Citadel:
https://<ip_address>
username: admin
password: citadel

You get the warning about a self-signed certificate, and you can accept the exception
now, and all the ssl functionality now works in the other connections with the same limitation.

Feel free to use it, update docs, fix the issue for real.