Any error message that we send to the client that contains the expression strerror(errno) makes the server crash, but only when running in Podman. I don't know why. I removed that expression from OIMG and it now works, but I looked for other functions that use that expression, and they crash too.
So I guess we just can't use that function anymore. I'll remove it. Not a huge deal.
Greetings:
Used easy install method. Was able to get spamd/clamav to function.
However unable to modify/edit drafts (draft room) . No prompt for editing draft or to "send message" from draft room available.
Write mail with Tiny MCE is o.k. Is there some configuration that was missed?
Thanks
Give the new container image a try and see how we did now.
I wholeheartly agree on IBM. Otherwise, I didn't had the chance to test too thoroughly, but hey, so far it looks good now! At least calling the login screen and editing rooms now seems to work without crashing. Nice job, thanks again!
In case I'll stumble over other issues, be sure, I'll let you know
Hi there,
my protocol says this.
Jul 18 17:50:17 pbcontrol citserver[21027]: SIGSEGV received in thread 139790179628800 at address 0x270
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #0: /usr/local/citadel/citserver(+0x163dc) [0x55f5876173dc]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #1: /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730) [0x7f23931de730]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #2: /usr/local/citadel/citserver(+0x61dc0) [0x55f587662dc0]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #3: /usr/local/citadel/citserver(+0x62bd4) [0x55f587663bd4]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #4: /usr/local/citadel/citserver(+0x62e7c) [0x55f587663e7c]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #5: /usr/local/citadel/citserver(+0x63aec) [0x55f587664aec]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #6: /usr/local/citadel/citserver(+0x6e044) [0x55f58766f044]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #7: /usr/local/citadel/citserver(+0x1732d) [0x55f58761832d]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #8: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3) [0x7f23931d3fa3]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #9: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f2392f1406f]
do someone else have any error like this since update 1018 ?
Subject: Error between Docker and "normal" installation (1020)
If you create a room and set up a Mailing List. In a Docker Container, subscribers will not shown in overview.
In a normal installation it works fine.
Subsribers will get mails normaly, but will not show up in overview. (Docker Container / 1020)
Is it possible to set a quota for space used per user? Want to be sure one user doesn't chew up all the space...
Is it possible to set a quota for space used per user? Want to
be sure one user doesn't chew up all the space...
Unfortunately there are no per-user quotas available in Citadel Server.
What we do have is a system-wide safety check, if available disk space goes below 100 MB it will refuse to accept new messages, so the system doesn't get corrupted by a disk full condition.
There is a problem with BCC recieptiens.
They will all appear in Mail header as > Envelope-to:
Is there a option to hide recieptens in header ?
Dear All,
I want to shrink my databases. I tried with the shell script "database_cleanup.sh" and it gives a error even with citadel shutdown and with plenty of disk space (I renamed /tmp in the script).
How to set the "c_shrink_db_files" variable (before compilation)?
I want only an one time shrink.
Thank you,
Luís Gonçalves.
There is a problem with BCC recieptiens.
They will all appear in Mail header as > Envelope-to:
Is there a option to hide recieptens in header ?
Can you clarify please, is this on outbound or inbound email?
I want to shrink my databases. I tried with the shell script "database_cleanup.sh" and it gives a error even with citadel shutdown and with plenty of disk space (I renamed /tmp in the script).
How to set the "c_shrink_db_files" variable (before compilation)?
I want only an one time shrink.
c_shrink_db_files is not a compile-time option. We've worked hard to have as few of those as possible.
If you set the c_shrink_db_files configuration option, the database will be compacted at shutdown time.
If you're not satisfied with the results, I would suggest using ctdldump and ctdlload, not database_cleanup.sh. But really, Citadel is good with disk space -- it will reuse the "holes" in those files to write new data. At some point your disk utilization will stabilize if you have both new data coming in and old data being purged. If you have plenty of disk space and your system is running cleanly I would advise leaving it alone.
Dear Foobar,
I have not so much space.
Do not see this as I putting bad reputation on the software.
Could you please explain how to set "c_shrink_db_files"?
Thank you,
Luís Gonçalves.
I want to shrink my databases. I tried with the shell script "database_cleanup.sh" and it gives a error even with citadel shutdown and with plenty of disk space (I renamed /tmp in the script).
How to set the "c_shrink_db_files" variable (before compilation)?
I want only an one time shrink.
c_shrink_db_files is not a compile-time option. We've worked hard to have as few of those as possible.
If you set the c_shrink_db_files configuration option, the database will be compacted at shutdown time.
If you're not satisfied with the results, I would suggest using ctdldump and ctdlload, not database_cleanup.sh. But really, Citadel is good with disk space -- it will reuse the "holes" in those files to write new data. At some point your disk utilization will stabilize if you have both new data coming in and old data being purged. If you have plenty of disk space and your system is running cleanly I would advise leaving it alone.
There is a problem with BCC recieptiens.
They will all appear in Mail header as > Envelope-to:
Is there a option to hide recieptens in header ?
Can you clarify please, is this on outbound or inbound email?
Hi Ignatius,
this happens on Outbound Mails. It doesnt matter wich Client you use. All BCC mails will show up for everybody who receive the mail. Not in client, but if you look in header from the mail... all will show up @envelopeto
Greetings
Mike