Please wait...
0 files
kernel: citserver[66147]: segfault at 7c006ec0 ip 000000000047bfdc sp
00007fda80e0f210 error 4 in citserver[400000+a0000]
If possible, can you run citserver in the debugger (gdb) and supply a backtrace?
Subject: Re: How relaying (or denying it) works
I noted is that when sending an Internet message from IMAP (and I
believe it's not this way in Webcit,) the return address always shows
as user@<serverFQDN>. Not sure why that is. I have no more
Each user can set a default email address in WebCit. This is the one that will be used when you send mail through an SMTP/IMAP client.
Subject: Re: Housekeeping failing - log files filling disk
Citadel is creating 10M log files every minute or so which is causing
the disk to fill.
Well that's not good ... something is writing to disk -- what could it be?
Do you perhaps have messages entering and exiting your system in an endless loop? You might be able to run one of those log files through "strings" or "hexdump -C" so you can see what's in them.
However, I need to access the system in a method similar to this site
- at citadel.mydomain.ca. How do i configure apache2 to work with the
service? When i tried following the guide, it gives an error for
proxy command in the sites.conf.
Hmm. It's hard to say without seeing your configuration and/or the exact error message.
Do keep in mind though -- from Apache's point of view, there's nothing special in particular about Citadel -- the WebCit interface is "just another" web site. So this is really an Apache issue. We'll try to help you with it, but we're not the Apache experts.
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!!!
Unfortunately I can't find it ... do you have a copy to read or download somewhere?
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.
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.
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!
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.
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.
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.
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
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
Subject: Re: Mail attachments
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.
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.
Subject: Re: Interesting issue with docker version
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.