Citadel Support

[#] Fri Dec 27 2024 21:22:42 UTC from Will.i.am

Subject: unstaking IOST in citadel wallet

Why cannot not use the password I originally used to get this far ??? help

Screenshot 2024-12-28 at 10.21.12 (image/png, 213851 bytes) [ View | Download ]

[#] Fri Dec 27 2024 22:38:34 UTC from IGnatius T Foobar

Subject: Re: unstaking IOST in citadel wallet

Why cannot not use the password I originally used to get this far ???
help

Because I took all of your money. I can put it to better use than you can.

[#] Fri Dec 27 2024 23:33:29 UTC from Kurisu

Subject: Re: unstaking IOST in citadel wallet

This amused me far more than it should have. :D

Fri Dec 27 2024 22:38:34 UTC from IGnatius T Foobar Subject: Re: unstaking IOST in citadel wallet

Why cannot not use the password I originally used to get this far ???
help

Because I took all of your money. I can put it to better use than you can.

Anyway, were I in need of support I guess i would take this time to ask for help, but that's if I had a major problem that I needed assistance with... which I don't, so, yeah.

[#] Sat Dec 28 2024 01:13:04 UTC from IGnatius T Foobar

Subject: Re: unstaking IOST in citadel wallet

Heh. You should have been here in 1996 when a clueless journalist who thought she had stumbled across a message board populated by cadets at The Citadel, and asked us what we thought about the academy going co-ed. We gave her all sorts of great gossip about secret ceremonies with ritual sacrifices, and other wonderful inside information.

[#] Sat Dec 28 2024 02:20:21 UTC from Kurisu

Subject: Re: unstaking IOST in citadel wallet

HAHA! Ah, yes, I truly wish I had been here for that one. Sadly before my time with a computer of my own to speak of, for sure. :)

Still a nice story to hear about, even nearly 30 years after the fact.

Sat Dec 28 2024 01:13:04 UTC from IGnatius T Foobar Subject: Re: unstaking IOST in citadel wallet

Heh. You should have been here in 1996 when a clueless journalist who thought she had stumbled across a message board populated by cadets at The Citadel, and asked us what we thought about the academy going co-ed. We gave her all sorts of great gossip about secret ceremonies with ritual sacrifices, and other wonderful inside information.

[#] Thu Jan 02 2025 00:00:45 UTC from darkoff

Subject: RSpamd Integration

Hi,

I would like to know if it is possible to use an antispam other than SpamAssassin, and in this case RSpamd? I am trying to integrate RSpamd directly on Citadel (in the manner of spamassassin) without success.

Thanks in advance for your answers! :)

[#] Thu Jan 02 2025 08:00:44 UTC from jiten

Subject: Email Setup

How Do I setup email that citadel will send and received email from upstream provider (gmail, zoho) and serve it as imap to local network. ??

[#] Fri Jan 03 2025 00:57:47 UTC from IGnatius T Foobar

Subject: Re: RSpamd Integration

I would like to know if it is possible to use an antispam other
than SpamAssassin, and in this case RSpamd? I am trying to
integrate RSpamd directly on Citadel (in the manner of
spamassassin) without success.

You can use any spam filter you want, but SpamAssassin is the only one that can be directly integrated into Citadel's MTA.

Any other filter must be set up in the conventional manner: you have some other MTA listening on port 25, emails are passed through the filter and then forwarded to Citadel's MDA. Most mailers support final delivery via LMTP over a local socket, and Citadel has that available on /usr/local/citadel/lmtp.socket

rspamd does appear to have a client protocol, so it's conceptually possible to write a Citadel module for it. But such a module does not currently exist.

[#] Fri Jan 03 2025 00:58:09 UTC from IGnatius T Foobar

Subject: Re: Email Setup

How Do I setup email that citadel will send and received email
from upstream provider (gmail, zoho) and serve it as imap to
local network. ??

smart-host rule for outbound, and remote retrieval rule for inbound.

[#] Fri Jan 03 2025 04:58:42 UTC from jiten

Subject: Re: Email Setup

thanks.

Any link to documentation for smart-host and remote retrieval Please.

[#] Sun Jan 12 2025 17:36:13 UTC from sankalpa

Subject: Citserver crash when using SSL

Hi Everyone,

Everytime I try to connect to citadel via IMAPS or POP3S I get a crash when using SSL

citadel-1 | citserver[8]: context: session (IMAP) started from 77-172-227-99.fixed.kpn.net (77.172.227.99) uid=-1

citadel-1 | citserver[8]: 1.385 STARTTLS

citadel-1 | citserver[8]: ---- Looking up [STARTTLS] -----

citadel-1 | citserver[8]: Found.

citadel-1 | citserver[8]: crypto: using certificate chain keys/citadel.cer

citadel-1 | citserver[8]: crypto: using private key keys/citadel.key

citadel-1 | citserver[8]: sysdep: new client socket 36

citadel-1 | citserver[8]: context: session (IMAP) started from 77-172-227-99.fixed.kpn.net (77.172.227.99) uid=-1

citadel-1 | citserver[8]: 1.38 STARTTLS

citadel-1 | citserver[8]: ---- Looking up [STARTTLS] -----

citadel-1 | citserver[8]: Found.

citadel-1 | ctdlvisor: pid=8 exited, status=139, exitcode=0

citadel-1 | ctdlvisor: citserver crashed on signal 11

citadel-1 | ctdlvisor: citserver running on pid=16

citadel-1 | ctdlvisor: executing citserver

The certificate I am using where generated with letsencrypt !

Any ideas ?

[#] Sun Jan 12 2025 17:46:13 UTC from sankalpa

Subject: SSL Session crash server

Hi Everyone,

I am using SSL certificates from letsencrypt and for some reason they crash citadel server when using IMAPS or POP3S

The logs even in highest verbosity are quite bare Any ideas ?

citadel-1 | webcit[9]: Loading with: -> LoadStartpage("dotskip?room=_BASEROOM_", 0)

citadel-1 | citserver[8]: [pierre(2)] CHEK

citadel-1 | citserver[8]: [pierre(2)] GOTO __CitadelSMTPspoolout__

citadel-1 | citserver[8]: room_ops: __CitadelSMTPspoolout__ : 1 seen of 2 total messages, oldest=13, newest=32

citadel-1 | citserver[8]: [pierre(2)] LFLR

citadel-1 | citserver[8]: [pierre(2)] NOOP

citadel-1 | citserver[8]: sysdep: new client socket 37

citadel-1 | citserver[8]: context: session (IMAP) started from 77-172-227-99.fixed.kpn.net (77.172.227.99) uid=-1

citadel-1 | citserver[8]: 1.385 STARTTLS

citadel-1 | citserver[8]: ---- Looking up [STARTTLS] -----

citadel-1 | citserver[8]: Found.

citadel-1 | citserver[8]: crypto: using certificate chain keys/citadel.cer

citadel-1 | citserver[8]: crypto: using private key keys/citadel.key

citadel-1 | citserver[8]: sysdep: new client socket 36

citadel-1 | citserver[8]: context: session (IMAP) started from 77-172-227-99.fixed.kpn.net (77.172.227.99) uid=-1

citadel-1 | citserver[8]: 1.38 STARTTLS

citadel-1 | citserver[8]: ---- Looking up [STARTTLS] -----

citadel-1 | citserver[8]: Found.

citadel-1 | ctdlvisor: pid=8 exited, status=139, exitcode=0

citadel-1 | ctdlvisor: citserver crashed on signal 11

citadel-1 | ctdlvisor: citserver running on pid=16

citadel-1 | ctdlvisor: executing citserver

[#] Sun Jan 12 2025 17:53:39 UTC from cjonline

Subject: citdel db issues (Log)

Hi, I woke this morning to find citserver had crashed on my linux box.. I restarted but still same issue..

I checked the partition and found 100% space was being used..

the /data folder had thousands of LOG files (berkely DB logs). The disk ran out of space (85GB)..

how do I recover from this to get the server back up and running.. I ran the command db_archive -d (to delete unused logs) but the command just sat doing nothing .. after 30mins the space was still using 100%...

please help

Craig.

[#] Sun Jan 12 2025 23:54:30 UTC from IGnatius T Foobar

Subject: Re: SSL Session crash server

The logs even in highest verbosity are quite bare Any ideas ?

Any chance you're able to produce a core dump?

[#] Sun Jan 12 2025 23:58:25 UTC from IGnatius T Foobar

Subject: Re: citdel db issues (Log)

the /data folder had thousands of LOG files (berkely DB logs). The
disk ran out of space (85GB)..

Citadel Server normally deletes unused database logs on its own, unless you've selected the system configuration option to stop it from doing that ("automatically delete unused database logs (yes/no)"

If the logs are accumulating that fast then your system might be the target of a spammer or something. If you ran a command like "strings" or "hexdump -C" on the logs you might see a clue as to what it's trying to write.

Also, to commit database logs you need a little bit of free disk space, so if you are truly at 100% you'll need to free a little bit of space up first.
Also, you probably already know this, but Citadel Server can't be running when you run any of the db_ commands.

[#] Mon Jan 13 2025 08:18:18 UTC from sankalpa

Subject: Re: SSL Session crash server

If you walk me through it I would be happy to. Currently using the docker version.

[#] Mon Jan 13 2025 10:55:26 UTC from cjonline

Subject: Re: citdel db issues (Log)

Hi,

I already had the "automatically deleted unused logs" setting enabled..

I managed to delete the logs with db_archive util, however, they start appearing again once I deleted them and continued until the disk ran out of space.

I also noticed in /var/log/messages that the Citserver is restarting every 1 minute. How can I find why this is happening?

*** Citadel server engine ***

Jan 13 10:43:03 victor citserver: Version 1007 (build 25012) ***

Jan 13 10:43:03 victor citserver:

Jan 13 10:43:03 victor citserver: This program is open source software. Use, duplication, or disclosure

Jan 13 10:43:03 victor citserver: is subject to the GNU General Public License version 3.

Jan 13 10:43:03 victor citserver:

Jan 13 10:43:03 victor citserver: libcitadel(unnumbered)

Jan 13 10:43:03 victor citserver: main: running in data directory /usr/local/citadel

Jan 13 10:44:18 victor citserver:

Jan 13 10:44:18 victor citserver: *** Citadel server engine ***

Jan 13 10:44:18 victor citserver: Version 1007 (build 25012) ***

Jan 13 10:44:18 victor citserver:

Jan 13 10:44:18 victor citserver: This program is open source software. Use, duplication, or disclosure

Jan 13 10:44:18 victor citserver: is subject to the GNU General Public License version 3.

Jan 13 10:44:18 victor citserver:

Jan 13 10:44:18 victor citserver: libcitadel(unnumbered)

Jan 13 10:44:18 victor citserver: main: running in data directory /usr/local/citadel

Jan 13 10:45:24 victor citserver:

Jan 13 10:45:24 victor citserver: *** Citadel server engine ***

Jan 13 10:45:24 victor citserver: Version 1007 (build 25012) ***

Jan 13 10:45:24 victor citserver:

Jan 13 10:45:24 victor citserver: This program is open source software. Use, duplication, or disclosure

Jan 13 10:45:24 victor citserver: is subject to the GNU General Public License version 3.

Jan 13 10:45:24 victor citserver:

Jan 13 10:45:24 victor citserver: libcitadel(unnumbered)

Jan 13 10:45:24 victor citserver: main: running in data directory /usr/local/citadel

Jan 13 10:46:34 victor citserver:

Sun Jan 12 2025 23:58:25 UTC from IGnatius T Foobar Subject: Re: citdel db issues (Log)

the /data folder had thousands of LOG files (berkely DB logs). The
disk ran out of space (85GB)..

Citadel Server normally deletes unused database logs on its own, unless you've selected the system configuration option to stop it from doing that ("automatically delete unused database logs (yes/no)"

If the logs are accumulating that fast then your system might be the target of a spammer or something. If you ran a command like "strings" or "hexdump -C" on the logs you might see a clue as to what it's trying to write.

Also, to commit database logs you need a little bit of free disk space, so if you are truly at 100% you'll need to free a little bit of space up first.
Also, you probably already know this, but Citadel Server can't be running when you run any of the db_ commands.

[#] Mon Jan 13 2025 14:31:16 UTC from sankalpa

Subject: Re: SSL Session crash server

Found this:

How do I make my system produce core dump files?

On Linux this can be achieved with the ulimit command which is documented in the bash man page.

  ulimit -c 999999

The core files are created in the working directory. Be careful, they can grow and eat up your disk space. Making the whole system create core files on crashes in a central folder can be achieved like this:

# local to citadel by editing /etc/init.d/citadel or /etc/init.d/webcit and add in the second line:
ulimit -c unlimited

# systemwide by doing:
echo 1 > /proc/sys/kernel/core_uses_pid
echo /tmp/core-%e-%p-%t > /proc/sys/kernel/core_pattern

But even with ulimit set on my docker container it does not seem to produce any core dump either in '/tmp' nor in '/usr/lib/systemd/systemd-coredump'

[#] Mon Jan 13 2025 14:34:17 UTC from sankalpa

Subject: Re: SSL Session crash server

Interesting thing to, dovecot crash also with those certificates ... I wonder what's happening with them, they are from letsencrypt

mailserver | 2025-01-13T15:33:58.960395+01:00 mail amavis[900]: No decoder for .zst

mailserver | 2025-01-13T15:34:02.631826+01:00 mail dovecot: imap-login: Fatal: master: service(imap-login): child 1001 killed with signal 11 (core dumped) [last ip=149.11.64.115]

mailserver | 2025-01-13T15:34:02.930774+01:00 mail dovecot: imap-login: Fatal: master: service(imap-login): child 1003 killed with signal 11 (core dumped) [last ip=149.11.64.115]

[#] Mon Jan 13 2025 17:25:19 UTC from cjonline

Subject: Re: citdel db issues (Log)

Hello,I'm getting further now with this issue, it seems that citserver is crashing around a minute after it starts and restarts/crashes repeats. That's why the log files are generating and not getting flushed.

I ran citserver from console

/citserver -x9

below is the output.. could this message in the outbound queue be causing the segmentation fault? if so, how do I delete it? or infact how do I view/delete the queue as it says there is over 17k messages (I assume spam) waiting to be delivered (relay?)

citserver[22927]: pop3client: scan started

citserver[22927]: pop3client: processing started

citserver[22927]: pop3client: ended

citserver[22927]: listdeliver: sweep started

citserver[22927]: listdeliver: ended

citserver[22927]: smtpclient: start full queue run , last_queue_job_processed=0 , last_queue_job_submitted=0

citserver[22927]: smtpclient: 17596 messages to be processed

citserver[22927]: msgbase: CtdlFetchMessage(112703, 1)

citserver[22927]: smtpclient: attempting delivery of message <112703> now

citserver[22927]: smtpclient: smtp_attempt_delivery(112702, dhruvkaushik@gmail.com)

citserver[22927]: msgbase: CtdlOutputMsg(msgnum=112702, mode=1, section=<>)

citserver[22927]: msgbase: CtdlFetchMessage(112702, 1)

citserver[22927]: msgbase: CtdlOutputPreLoadedMsg(TheMessage=not null, 1, 0, 0, 1

Segmentation fault

Mon Jan 13 2025 10:55:26 UTC from cjonline Subject: Re: citdel db issues (Log)

Hi,

I already had the "automatically deleted unused logs" setting enabled..

I managed to delete the logs with db_archive util, however, they start appearing again once I deleted them and continued until the disk ran out of space.

I also noticed in /var/log/messages that the Citserver is restarting every 1 minute. How can I find why this is happening?

*** Citadel server engine ***

Jan 13 10:43:03 victor citserver: Version 1007 (build 25012) ***

Jan 13 10:43:03 victor citserver: Copyright (C) 1987-2024 by the Citadel development team.

Jan 13 10:43:03 victor citserver:

Jan 13 10:43:03 victor citserver: This program is open source software. Use, duplication, or disclosure

Jan 13 10:43:03 victor citserver: is subject to the GNU General Public License version 3.

Jan 13 10:43:03 victor citserver:

Jan 13 10:43:03 victor citserver: libcitadel(unnumbered)

Jan 13 10:43:03 victor citserver: main: running in data directory /usr/local/citadel

Jan 13 10:44:18 victor citserver:

Jan 13 10:44:18 victor citserver:

Jan 13 10:44:18 victor citserver: *** Citadel server engine ***

Jan 13 10:44:18 victor citserver: Version 1007 (build 25012) ***

Jan 13 10:44:18 victor citserver: Copyright (C) 1987-2024 by the Citadel development team.

Jan 13 10:44:18 victor citserver:

Jan 13 10:44:18 victor citserver: This program is open source software. Use, duplication, or disclosure

Jan 13 10:44:18 victor citserver: is subject to the GNU General Public License version 3.

Jan 13 10:44:18 victor citserver:

Jan 13 10:44:18 victor citserver: libcitadel(unnumbered)

Jan 13 10:44:18 victor citserver: main: running in data directory /usr/local/citadel

Jan 13 10:45:24 victor citserver:

Jan 13 10:45:24 victor citserver:

Jan 13 10:45:24 victor citserver: *** Citadel server engine ***

Jan 13 10:45:24 victor citserver: Version 1007 (build 25012) ***

Jan 13 10:45:24 victor citserver: Copyright (C) 1987-2024 by the Citadel development team.

Jan 13 10:45:24 victor citserver:

Jan 13 10:45:24 victor citserver: This program is open source software. Use, duplication, or disclosure

Jan 13 10:45:24 victor citserver: is subject to the GNU General Public License version 3.

Jan 13 10:45:24 victor citserver:

Jan 13 10:45:24 victor citserver: libcitadel(unnumbered)

Jan 13 10:45:24 victor citserver: main: running in data directory /usr/local/citadel

Jan 13 10:46:34 victor citserver:

Jan 13 10:46:34 victor citserver:

Sun Jan 12 2025 23:58:25 UTC from IGnatius T Foobar Subject: Re: citdel db issues (Log)

the /data folder had thousands of LOG files (berkely DB logs). The
disk ran out of space (85GB)..

Citadel Server normally deletes unused database logs on its own, unless you've selected the system configuration option to stop it from doing that ("automatically delete unused database logs (yes/no)"

If the logs are accumulating that fast then your system might be the target of a spammer or something. If you ran a command like "strings" or "hexdump -C" on the logs you might see a clue as to what it's trying to write.

Also, to commit database logs you need a little bit of free disk space, so if you are truly at 100% you'll need to free a little bit of space up first.
Also, you probably already know this, but Citadel Server can't be running when you run any of the db_ commands.

Uncensored

New user? Register now

Please wait...

How do I make my system produce core dump files?