Language:
switch to room list switch to menu My folders
Go to page: First ... 15 16 17 18 [19] 20 21 22
[#] Tue Nov 30 2021 01:50:29 EST from lodger

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

Just dropping by to give big kudos to the Citadel dev team for releasing the Citadel docker image - waited so long for this one! Already got it up and running and it works like a charm!! Yay!!!



[#] Tue Nov 30 2021 10:50:38 EST from IGnatius T Foobar

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

Happy to hear that. It was a long effort but totally worth it.

[#] Wed Dec 01 2021 03:47:06 EST from y2ksw

Subject: Re: Citadel Walk-Through needed

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

Unfortunately I can't find it ... do you have a copy to read or download somewhere?

Mon Nov 22 2021 21:36:50 EST from ParanoidDelusions Subject: Re: Citadel Walk-Through needed

I had written up a pretty straight forward walkthrough a couple of years ago. I don't know where it is. I'll see if I can find it and publish it again. It might be here. 

 

 

Mon Nov 22 2021 04:06:12 EST from y2ksw Subject: Citadel Walk-Through needed

Hello, is there any very simple, basic, walk-through for bloody Citadel noobs?

I am coming from postfix and dovecot based systems and have a hard time to understand how to setup a working mail server.

By now, I got 2 mailboxes working, but I struggle to get SSL working with 2 different domains on the same server. For all additional features, for which I installed the software in the first place, I have any time available, but mailing is a feature I can't procrastinate.



 



 



[#] Fri Dec 03 2021 15:43:06 EST from paulb

Subject: Mail attachments

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

Hey guys,

Incoming and outgoing mail work perfectly, however attachments show up in the message but when you try to view them, or download them - it just says the file is corrupted.

 

How do I go about resolving this?

 

Thanks!



[#] Fri Dec 03 2021 17:02:04 EST from IGnatius T Foobar

Subject: Re: Mail attachments

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

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.

[#] Fri Dec 03 2021 17:14:27 EST from paulb

Subject: Re: Mail attachments

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

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.

 



[#] Sat Dec 04 2021 07:05:31 EST from StarbaseSSD

Subject: Interesting issue with docker version

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

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

If a message is created, it's timestamped as Jan 01 1970. The docker container is not picking up current time and date from the host machine, and doesn't seem to be able to fetch it by itself from another source. I looked through the documentation, (mostly very well documented, thanks) but I haven't been able to find an answer to this. (as an aside, I was, thanks to the documentation, able to set up gmail as my smtp smarthost forwarder, and a few other 'specialty' tweaks)...

 

Kevin -- KD9EFV



[#] Sat Dec 04 2021 09:52:49 EST from Nurb432

Subject: Re: Interesting issue with docker version

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

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



[#] Sat Dec 04 2021 15:06:19 EST from s3cr3to to room_Citadel_Support@uncensored.citadel.org

Subject: Re: Mail attachments

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

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.

 




[#] Sat Dec 04 2021 20:31:58 EST from StarbaseSSD

Subject: Re: Interesting issue with docker version

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

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



[#] Sun Dec 05 2021 12:32:28 EST from StarbaseSSD

Subject: Citadel Docker XMPP client

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

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



[#] Sun Dec 05 2021 19:14:05 EST from StarbaseSSD

Subject: Re: Citadel Docker XMPP client

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

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?



[#] Sun Dec 05 2021 19:16:03 EST from StarbaseSSD

Subject: Re: Citadel Docker XMPP client

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

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

 



[#] Sun Dec 05 2021 20:12:28 EST from fang-castro

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

anyone have Citadel 345a documentation?

[#] Mon Dec 06 2021 11:19:52 EST from IGnatius T Foobar

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

Is that really the version you're running? 345a (which at the time would have been written as 3.45a)? That version would be more than 25 years old and only capable of running a text-mode BBS. If that's really what you've got, I'd love to hear more about it!

[#] Mon Dec 06 2021 13:01:39 EST from Nurb432

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

Time traveler perhaps? :)



[#] Mon Dec 06 2021 21:01:53 EST from StarbaseSSD

Subject: Re: Citadel Docker XMPP client

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

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.

 



 



[#] Tue Dec 07 2021 09:09:55 EST from IGnatius T Foobar

Subject: Re: Citadel Docker XMPP client

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

It shouldn't be. citadel-data/keys/* should be linked by both Citadel Server and WebCit. You do have to restart the container after updating the certificate though.

[#] Thu Dec 09 2021 11:49:47 EST from StarbaseSSD

Subject: Re: Citadel Docker XMPP client

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

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.



[#] Thu Dec 09 2021 13:11:44 EST from StarbaseSSD

Subject: Re: Citadel Docker XMPP client

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

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.



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