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.

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.

I just installed Citadel yesterday and am having lotsa fun with it.  I have a few users set up using IMAP all on one user agent.  At the same time, I am using a different mail server which has it's own IMAP-linked user agent.  What I encounter is ... if I send a message from Citadel (via IMAP) to an external address, it works great.  But if I go the other way, as in mailing the Citadel server user from the external account, it is rejected with 511 relaying not allowed.  I read somewhere that all messages must originate or terminate at Citadel, which avoids the hassle of operating a relay accidentally and having your provider shut off port 25.  I just don't understand why a message originating outside of Citadel, but terminating inside (via IMAP) is not allowed, but going the other direction is.

Thanks.

-Steve

Tue Nov 23 2021 11:20:31 EST from sirdotcom Subject: How relaying (or denying it) works

I just installed Citadel yesterday and am having lotsa fun with it.  I have a few users set up using IMAP all on one user agent.  At the same time, I am using a different mail server which has it's own IMAP-linked user agent.  What I encounter is ... if I send a message from Citadel (via IMAP) to an external address, it works great.  But if I go the other way, as in mailing the Citadel server user from the external account, it is rejected with 511 relaying not allowed.  I read somewhere that all messages must originate or terminate at Citadel, which avoids the hassle of operating a relay accidentally and having your provider shut off port 25.  I just don't understand why a message originating outside of Citadel, but terminating inside (via IMAP) is not allowed, but going the other direction is.

Thanks.

-Steve

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.)

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.)

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.  :)

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!

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.

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'.

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

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!

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?

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.

 

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!