Language:
switch to room list switch to menu My folders
Go to page: 1 2 [3] 4 5 6 7 ... Last
[#] Wed Nov 24 2021 18:03:41 EST from paulb

Subject: Citadel with Apache2

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

Hello Everyone,

 

Ive gotten my citadel server up and running. Finally got the outbound and inbound email working too!

 

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.

 

I already have a site running that i would like it running along side.

 

Thank you!



[#] Thu Nov 25 2021 15:10:32 EST from sirdotco

Subject: Re: How relaying (or denying it) works

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

 

Wed Nov 24 2021 17:07:38 EST from sirdotco Subject: Re: How relaying (or denying it) works

 

Wed Nov 24 2021 13:41:29 EST from s3cr3to

Subject: Re: How relaying (or denying it) works
Hope this helps.

Check in
"Administration"
- "Global Configuration"
- - "Domain names and Internet mail configuration"
- - - "Local host aliases"
- - - (domains for which this host receives mail)


Add your domain like:
domainexample.com

Then in the
user mail address:
user1@host.domainexample.com

edit and change that address or add an alias like:

user1@domainexample.com


On 11/24/21 04:05, sirdotcom wrote:

I think I figured it out.  I was sending to the internet email/domain for the user on Citadel which didn't work.  But now I sent it directly to the server's FQDN and it went through perfectly.  I guess sending to the internet address of the user doesn't work?  So I just need to stick to the server name as @domain (which shows up as the return address in the user agent anyway.)



Thanks very much for your reply and info.  However, now I find myself confused as ever.  I had already entered all the domain names I wanted to use in the Admin section.  I then tried putting <user>@<Server FQDN> as the user's internet email address.  I then set an alias for what I want the domain to be when the send mail.  That worked, at least on Webcit.  Scratch that.  I was thinking it was sending the FQDN as return path but indeed both the From: and Return Path: fields are what I entered as the user's alias.  I.E., the correct domain for that user.  So I think everything is working on that end.  But the relaying thing persists.  I shoot an email from test system to Citadel, and it immediately sends back an undeliverable message due to relaying not allowed error.  But I can send emails from Webcit or my Citadel-linked user agent to the test system fine.  I'm confused why it will go one way but not the other (as I understand it.)

Thanks again your help is much appreciated.  :)



Thanks to the help of s3cr3to, I learned a huge amount about email in general today and Citadel's way of handling it.  One important thing 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 problems with 551 Relaying not allowed, no idea why except I rebooted it and erased/reconfigured my user agent.  Overall, the system is brilliant and I look forward to more exploration.




[#] Thu Nov 25 2021 23:54:07 EST from sciens

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

Attempted another rebuild and its definitely something causing the citadel server process to crash while synchronizing users from LDAP.

 

citserver[66142]: ldap: synchronizing Citadel user database from LDAP

citserver[66142]: ldap: synchronizing Citadel user database from LDAP

kernel: citserver[66147]: segfault at 7c006ec0 ip 000000000047bfdc sp 00007fda80e0f210 error 4 in citserver[400000+a0000]

kernel: Code: 48 8b 45 d8 ba 27 35 49 00 48 89 ce 48 89 c7 b8 00 00 00 00 e8 c5 aa f9 ff 48 98 48 89 45 f8 48 83 7d f8 00 74 61 48 8b 45 f8 <48> 8b 00 48 85 c0 74 41 48 83 7d e8 00 74 1c 8b 45 e4 48 63 d0 48

systemd[1]: citadel.service: Main process exited, code=killed, status=11/SEGV

systemd[1]: citadel.service: Failed with result 'signal'.

 



[#] Fri Nov 26 2021 03:28:53 EST from ColP

Subject: Housekeeping failing - log files filling disk

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

Hi,

I have a Citadel server on a Pi that’s been happily ticking over for months.

I noticed today that the disk space was being consumed rapidly.

/var/log/syslog is showing housekeeping messages non stop:

housekeeping: WARNING: housekeeping loop has not run for 11 minutes.  Is something stuck?

Citadel is creating 10M log files every minute or so which is causing the disk to fill.

I‘ve stopped the Citadel server and ran database-cleanup which cleaned out the log files and freed up space but the problem is still happening.

I have a few weeks worth of database/log backups so I can roll back to try that but was hoping to get to the root of the issue.

I also have an idle backup Raspberry Pi which shows the same behaviour with my latest Citadel backup loaded on it.

 

Appreciate any help, thanks, Col



[#] Fri Nov 26 2021 20:10:25 EST from paulb

Subject: Re: Citadel with Apache2

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

EDIT: I added the needed mods to apache2 for the proxy; theres no errors, however it still wont forward.

 

What am i missing?

Wed Nov 24 2021 18:03:41 EST from paulb Subject: Citadel with Apache2

Hello Everyone,

 

Ive gotten my citadel server up and running. Finally got the outbound and inbound email working too!

 

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.

 

I already have a site running that i would like it running along side.

 

Thank you!



 



[#] Mon Nov 29 2021 19:11:41 EST from IGnatius T Foobar

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

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?

[#] Mon Nov 29 2021 19:12:35 EST from IGnatius T Foobar

Subject: Re: How relaying (or denying it) works

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

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.

[#] Mon Nov 29 2021 19:15:28 EST from IGnatius T Foobar

Subject: Re: Housekeeping failing - log files filling disk

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

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.

[#] Mon Nov 29 2021 19:17:25 EST from IGnatius T Foobar

Subject: Re: Citadel with Apache2

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

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.

[#] 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



Go to page: 1 2 [3] 4 5 6 7 ... Last