Is there a way to remove the message number via command line client?

That might actually be a better option.  Once logged in to the command line client, type ".Goto __CtdlSMTPSpoolout__"

Then hit "F" to read-Forward

You'll see two types of messages there.  Half ought to be "delivery instructions" and the other half should be the messages themselves.  If you find one without the other it is a stray message and you can hit "D" to delete it.

BTW, is there a documentation on error and return codes somewhere? I noticed that 'systemctl stop citadel' does not exit clean but with retun code 15. Not sure what this means.

That's a different story.  But there's a way to find out.  Stop the Citadel server with systemctl, then start it in the foreground with:

cd /usr/local/citadel

./citserver -x9

Run it for a little while, then stop it with ctrl-c or by shutting it down from the user interface.  Then post the last screenful of log messages here, so we can see why you got that exit code.

After the upgrade I am playing around with the server a bit to harden and improve reputation. I noticed that TLS does not seem to be advertized. Tested with the local server:

The server has certificates installed and uses those when connecting via IMAP. There are also a lot of TLS messages in syslog. But in the response above I miss repsonse line 250-STARTTLS indicating TLS support for the MTA. STARTTLS command is accepted (220) though so in theory would work but as it's not advertized might not be used when remote server is waiting for that capability response.

Am I missing something?

You're not missing anything; that is the normal behavior.

The reason we do not advertise STARTTLS is because too many sites start up with a self-signed certificate, and we've found that those sites will not receive mail from many popular sources if STARTTLS is advertised but the certificate is invalid from the sender's perspective.

If this is something you need, we could add an undocumented server configuration item to switch it on manually.  Would that help?

Hello! I provide Citadel hosting starting at $7 and would like to know if I can get it listed it here. My website is at https://citadelhosting.retro-os.live/. If any questions I'm listening at fstltna@yahoo.com :)

cd /usr/local/citadel

./citserver -x9

Run it for a little while, then stop it with ctrl-c or by shutting it down from the user interface.  Then post the last screenful of log messages here, so we can see why you got that exit code.

citserver[251519]: Additional memory allocated since startup: 0 bytes
citserver[251519]: listdeliver: delivery interval not yet reached; last run was 2m2s ago
citserver[251519]: smtpclient: start full queue run , last_queue_job_processed=0 , last_queue_job_submitted=0
citserver[251519]: smtpclient: 0 messages to be processed
citserver[251519]: smtpclient: end full queue run , last_queue_job_processed=0 , last_queue_job_submitted=0
citserver[251519]: rssclient: polling interval not yet reached; last run was 2m2s ago
citserver[251519]: bdb: -- checkpoint --
citserver[251519]: Additional memory allocated since startup: 0 bytes
^Ccitserver[251519]: sysdep: caught signal 2
citserver[251519]: citserver: closing databases
citserver[251519]: bdb: performing final checkpoint
citserver[251519]: bdb: flushing the database logs
citserver[251519]: bdb: closing databases
citserver[251519]: bdb: closing database 00
citserver[251519]: bdb: closing database 01
citserver[251519]: bdb: closing database 02
citserver[251519]: bdb: closing database 03
citserver[251519]: bdb: closing database 04
citserver[251519]: bdb: closing database 05
citserver[251519]: bdb: closing database 06
citserver[251519]: bdb: closing database 07
citserver[251519]: bdb: closing database 08
citserver[251519]: bdb: closing database 09
citserver[251519]: bdb: closing database 0a
citserver[251519]: bdb: closing database 0b
citserver[251519]: bdb: closing database 0c
citserver[251519]: bdb: closing database 0d
citserver[251519]: bdb: closing environment
citserver[251519]: bdb: shutdown completed
citserver[251519]: citserver: Exiting with status 2
citserver[251519]: main: removing lockfile

Looks like this is creatign a different result than when run under systemd.

That might actually be a better option.  Once logged in to the command line client, type ".Goto __CtdlSMTPSpoolout__"

Then hit "F" to read-Forward

Indeed I found there two message that were more than a year old and deleted them. This greatly reduced the amount of noise in the log. But I still have msgbase errors for two messages. One comes up around every half an hour, the other has longer cycles.

Jan 18 20:38:41 [host] citserver[251656]: citserver[251656]: msgbase: message #93647 was not found
Jan 18 20:38:41 [host] citserver[251656]: msgbase: message #93647 was not found
Jan 18 20:38:41 [host] citserver[251656]: citserver[251656]: msgbase: message #93647 was not found
Jan 18 20:38:41 [host] citserver[251656]: citserver[251656]: msgbase: message #93647 was not found
Jan 18 20:38:41 [host] citserver[251656]: citserver[251656]: msgbase: error; invalid preloaded message for output
Jan 18 20:38:41 [host] citserver[251656]: msgbase: message #93647 was not found
Jan 18 20:38:41 [host] citserver[251656]: msgbase: message #93647 was not found
Jan 18 20:38:41 [host] citserver[251656]: msgbase: error; invalid preloaded message for output

Is there a way from the command line to identify a specific message number?

KR,

P.

If this is something you need, we could add an undocumented server configuration item to switch it on manually.  Would that help?

That would be great. I mainly use Citadel as mail and collaboration platform and this would be greatly improve reputation interacting with other public MTAs. Not mega urgent though probably something for a next release.

Many thanks for considering!

P.

Hi There!

I was just recommended citadel as a mail server.

I have ubuntu-22.04 and I follow the instructions to configure/compile and setup citadel.

After providing all input the setup program says it is restarting services, but the setup program never completes.

If I manually start citadel, I can connect on mail port and talk to the service.

If I run setup again, it takes me through the few questions about admin and passwords and then it tries to restart but never finishes.

Any help is appreciated.

PS: I would expect the configuration files to be under /usr/local/citadel or /etc/citadel, but I cannot find any...

Found out I need to enable the web interface :-)

Debian repositories is at 916..  Ouch.

Hi Guys,

I am new at this forum.

I have just installed a brand new Citadel server, and it is running like a charm.

OS is Ubuntu 22.04.

I would appreciate if someone would tell me how the web server of Webcit can be configured to redirect all the http requests to https requests automatically.

I am running Webcit without any proxy in between. No Apache or Nginx installed, just bared Citadel.

Carlos

Hi Guys,

I am new at this forum.

I have just installed a brand new Citadel server, and it is running
like a charm.

OS is Ubuntu 22.04.

I would appreciate if someone would tell me how the web server of
Webcit can be configured to redirect all the http requests to https
requests automatically.

I am running Webcit without any proxy in between. No Apache or Nginx
installed, just bared Citadel.

Carlos

For what its worth, that is how i run everything at home that has an incoming connection so i can get SSL.  Works well, not a lot of setup overhead. Pretty bullet proof.

Only difference is i use full VMs.  

Sat Jan 27 2024 13:56:06 EST from s3cr3to Subject: Re: How to redirect http to https for Webcit

My personal solution:

A LXC on Proxmox running  "Nginx Proxy Manager" (NPM)

Sat Jan 27 2024 17:13:05 EST from IGnatius T Foobar Subject: Re: How to redirect http to https for Webcit

Right ... unfortunately WebCit does not have HTTP-to-HTTPS redirection built in. If that is something you need you will have to generate the redirect from another web service.

Thank you for your answer.

Yes, this is what I am looking for. May be it would be worth to add this feature in the future to the webserver imbedded into Webcit.

It seems that the only solution of this kind now would be to proxy via Nginx. (I don't have experience with Docker) 

But I prefer to have as little middlemen as possible. :-)

Mon Jan 29 2024 19:12:44 EST from IGnatius T Foobar Subject: Re: TLS configuration

On it! Server option completed already (it was just a couple extra
lines of code) so we just need to go through the user interfaces adding

that switch in. Look for it in the next release.

Look for Citadel 997 arriving tomorrow (January 30) with your requested feature available. The SMTP server will have a configurable option to offer STARTTLS.

If I haven't mentioned it yet, the reason we don't offer STARTTLS by default on port 25 is because offering TLS with an invalid certificate will cause a lot of senders to refuse to talk to your server. So definitely only enable this option if you have a valid and trusted certificate.

This is good news!

I have a trusted certificate and would keep it only that way. 

Would you tell me where to find the setting of this feature?

Mon Jan 29 2024 19:12:44 EST from IGnatius T Foobar Subject: Re: TLS configuration

On it! Server option completed already (it was just a couple extra
lines of code) so we just need to go through the user interfaces adding

that switch in. Look for it in the next release.

Look for Citadel 997 arriving tomorrow (January 30) with your requested feature available. The SMTP server will have a configurable option to offer STARTTLS.

If I haven't mentioned it yet, the reason we don't offer STARTTLS by default on port 25 is because offering TLS with an invalid certificate will cause a lot of senders to refuse to talk to your server. So definitely only enable this option if you have a valid and trusted certificate.

This is good news!

I have a trusted certificate and would keep it only that way. 

Would you tell me where to find the setting of this feature?

Dear developers, dear community,

I usually install citadel by build script file "install.sh" to a non-standard location. The 'install.sh" defines at the beginning three basic path variables, namely SUPPORT, CITADEL and WEBCIT that hold the basic pathes to ctdlsupport, citadel and webcit, respectively. So in order to install to a non-standard location ideally I only have to change the values of the three path variables. But unfortunately "install.sh" uses some pathes that don't rely on those path variables like those listed below:

PERMSTESTDIR=/usr/local/ctdltest.$$

mkdir /usr/local/ctdlsupport 2>/dev/null
mkdir /usr/local/citadel 2>/dev/null
mkdir /usr/local/webcit 2>/dev/null
find /usr/local/ctdlsupport | grep -i ical | xargs rm -v 2>/dev/null
find /usr/local/ctdlsupport | grep -i expat | xargs rm -v 2>/dev/null
find /usr/local/ctdlsupport | grep -i curl | xargs rm -v 2>/dev/null
find /usr/local/ctdlsupport | grep -i sieve | xargs rm -v 2>/dev/null

/usr/local/citadel/setup </dev/tty >/dev/tty 2>/dev/tty || die

ExecStart=/usr/local/webcit/webcit -pWEBCIT_PORT uds /usr/local/citadel

ExecStart=/usr/local/webcit/webcit -s -pWEBCITS_PORT uds /usr/local/citadel

And thats the reason why the installtion proces allways stopes unsuccessfully.

Could you please make all does pathes rely on the basic path variables mentioned above? So whenever my installation pathes differ from the standard pathes the build script runs smoothly and installs all software successfully.

Thanks and good night

Sukram