Hello,
if I restart from webinterface citadel crashes and web isn't reachable
after server reboot citadel is up and running again and webinterface is reachable
seems that citadel shutdown instead of restarting
if I enter "sudo service citadel start" in console I can access webinterface again
Subject: Re: Sending mail to restictive sites like gmail (DKIM?)
I have issues where sending mail to @gmail addresses never gets
delivered but doesn't bounce. I think I need to set up the DNS to
allow this but I don't know how to set it up. Any tips?
Check your logs to see if gmail actually accepted the mail. If it did, the recipient probably has the messages in their spam folder. Google are absolute nazis when it comes to filtering.
Citadel doesn't currently support DKIM but you should definitely do all of the other things:
1. Make sure your forward and reverse DNS agree with each other
2. Set up an SPF record to tell the world where legitimate mail from your domain originates
3. Set up a DMARC record to tell the world that your SPF record is really true
seems that citadel shutdown instead of restarting
if I enter "sudo service citadel start" in console I can access webinterface again
Hi,
In my set-up, I have always used a different outgoing host for my mail clients. Now, I would like to start using Citadel also for outgoing mail.
I understand, That I need to create a smart host; this smart host will be the same as my previous outgoing host for SMTP.
The outgoing hosts requires login/password, and also requires that all mail has this login in the From:-header.
So, for example, for outgoing host smtp.abc.com, I need to log-in with Abcname@abc.com, and all mail needs to come from Abcname@abc.com. For outgoing host smtp.def.com, I need to log-in with defname@def.com, and all mail needs to come from defname@def.com.
Anyone knows how to configure that?
Subject: Re: rewrite From: to accomodate outgoing hosts
You can configure your smart host as smtp://username:password@smarthostname.com
There are two problems with simply defining a smarthost:
1) The username also contains an @ sign.
2) The From: -field always must match the username that is used to login.
2) I can do manually by putting in the right from-name, but I would like to have it being rewritten automatically, depending on the smarthost that is used.
1) seems to be more of a problem. I tried simply putting the username with the @, escaping the @ with a \ and quoting, but none of it seems to work.
Subject: Just Started Getting BDB 2055 Locks error and error 12 of bdb fetch
I have 13GB attached to system and the server is core dumping with 8500+ log filees. Started this morning
on 996
Subject: Re: Just Started Getting BDB 2055 Locks error and error 12 of bdb fetch
Getting this is messages:
Mar 11 11:59:19 setamco-cosmsrv systemd-coredump[7521]: Process 7514 (citserver) of user 1001 dumped core.#012#012Stack trace of thread 7514:#012#0 0x0000000000449f5d imap_cleanup_function (citserver + 0x49f5d)#012#1 0x00000000004247f2 PerformSessionHooks (citserver + 0x247f2)#012#2 0x000000000040cbb0 RemoveContext (citserver + 0xcbb0)#012#3 0x000000000040d547 context_cleanup (citserver + 0xd547)#012#4 0x000000000040a592 master_cleanup (citserver + 0xa592)#012#5 0x000000000042574d signal_cleanup (citserver + 0x2574d)#012#6 0x00007f5ddec54db0 __restore_rt (libc.so.6 + 0x54db0)#012#7 0x00007f5dded159e5 clock_nanosleep@GLIBC_2.2.5 (libc.so.6 + 0x1159e5)#012#8 0x00007f5dded1a597 __nanosleep (libc.so.6 + 0x11a597)#012#9 0x00007f5dded457a9 usleep (libc.so.6 + 0x1457a9)#012#10 0x00000000004274df go_threading (citserver + 0x274df)#012#11 0x000000000042526b main (citserver + 0x2526b)#012#12 0x00007f5ddec3feb0 __libc_start_call_main (libc.so.6 + 0x3feb0)#012#13 0x00007f5ddec3ff60 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x3ff60)#012#14 0x0000000000409f15 _start (citserver + 0x9f15)#012#012Stack trace of thread 7515:#012#0 0x0000000000499aed __memp_fput_ctdl (citserver + 0x99aed)#012#1 0x00000000005153e9 __db_free_ctdl (citserver + 0x1153e9)#012#2 0x0000000000516e87 __db_doff_ctdl (citserver + 0x116e87)#012#3 0x00000000005349f2 __bam_ditem_ctdl (citserver + 0x1349f2)#012#4 0x0000000000537838 __bam_iitem_ctdl (citserver + 0x137838)#012#5 0x0000000000531c89 __bamc_put (citserver + 0x131c89)#012#6 0x000000000050124a __dbc_iput_ctdl (citserver + 0x10124a)#012#7 0x0000000000503af5 __dbc_put_ctdl (citserver + 0x103af5)#012#8 0x00000000004fb57a __db_put_ctdl (citserver + 0xfb57a)#012#9 0x0000000000510090 __db_put_pp_ctdl (citserver + 0x110090)#012#10 0x00000000004671f8 bdb_store (citserver + 0x671f8)#012#11 0x000000000043d8ba ft_index_message (citserver + 0x3d8ba)#012#12 0x000000000043dbda do_fulltext_indexing (citserver + 0x3dbda)#012#13 0x00000000004247f2 PerformSessionHooks (citserver + 0x247f2)#012#14 0x0000000000410808 do_housekeeping (citserver + 0x10808)#012#15 0x0000000000427281 worker_thread (citserver + 0x27281)#012#16 0x00007f5ddeca1912 start_thread (libc.so.6 + 0xa1912)#012#17 0x00007f5ddec3f450 __clone3 (libc.so.6 + 0x3f450)#012#012Stack trace of thread 7516:#012#0 0x00007f5dded159e5 clock_nanosleep@GLIBC_2.2.5 (libc.so.6 + 0x1159e5)#012#1 0x00007f5dded1a597 __nanosleep (libc.so.6 + 0x11a597)#012#2 0x00007f5dded1a4ce sleep (libc.so.6 + 0x11a4ce)#012#3 0x0000000000431358 bind_to_key_and_certificate (citserver + 0x31358)#012#4 0x0000000000431425 update_key_and_cert_if_needed (citserver + 0x31425)#012#5 0x0000000000431e02 CtdlStartTLS (citserver + 0x31e02)#012#6 0x0000000000424a4c CtdlModuleStartCryptoMsgs (citserver + 0x24a4c)#012#7 0x000000000044a271 imaps_greeting (citserver + 0x4a271)#012#8 0x00000000004271b9 worker_thread (citserver + 0x271b9)#012#9 0x00007f5ddeca1912 start_thread (libc.so.6 + 0xa1912)#012#10 0x00007f5ddec3f450 __clone3 (libc.so.6 + 0x3f450)#012#012Stack trace of thread 7517:#012#0 0x00007f5dded44ffd __select (libc.so.6 + 0x144ffd)#012#1 0x0000000000426d92 worker_thread (citserver + 0x26d92)#012#2 0x00007f5ddeca1912 start_thread (libc.so.6 + 0xa1912)#012#3 0x00007f5ddec3f450 __clone3 (libc.so.6 + 0x3f450)#012ELF object binary architecture: AMD x86-64
Mar 11 11:59:19 setamco-cosmsrv systemd[1]: citadel.service: Main process exited, code=dumped, status=11/SEGV
Mar 11 11:59:19 setamco-cosmsrv systemd[1]: citadel.service: Failed with result 'core-dump'.
Mar 11 11:59:40 setamco-cosmsrv webcit[941]: Can't connect [/usr/local/citadel/citadel.socket]
Mon Mar 11 2024 11:58:22 EDT from stormytramp Subject: Just Started Getting BDB 2055 Locks error and error 12 of bdb fetchI have 13GB attached to system and the server is core dumping with 8500+ log filees. Started this morning
on 996
Subject: Just Started Getting BDB 2055 Locks error and error 12 of bdb fetch
I have 13GB attached to system and the server is core dumping with 8500+ log filees. Started this morning
on 996
Subject: Re: Just Started Getting BDB 2055 Locks error and error 12 of bdb fetch
Subject: Citadel 996 Easy Install on Debian System aborts
Hi,
I am running Citadel 996 on an Odroid C2. While upgrading Citadel to a newer version with Easy Install, the installation aborts during the "Installing Citadel" process. Could you point me in a direction that helps me to solve the issue?
Tx,
Mike
Installing Citadel...
Running the configure script to create config.mk
Testing for OpenSSL...
Testing for iconv...
iconv.h is present and requires no additional libraries
Testing for lresolv...
Testing for lintl...
Testing for lcrypt...
# config.mk is generated by configure
CTDLDIR := /usr/local/citadel
CC := gcc
CFLAGS := -I/usr/local/ctdlsupport/include -g -DHAVE_OPENSSL -DBUILD_ID=\"24074\" -DCTDLDIR=\"/usr/local/citadel\" -I/usr/local/ctdlsupport/include -g
LDFLAGS := -L/usr/local/ctdlsupport/lib -Wl,--rpath -Wl,/usr/local/ctdlsupport/lib -lssl -lcrypto -lz
LRESOLV := -lresolv
LINTL :=
BACKEND_LDFLAGS := -ldb
CHKPW := chkpw chkpwd
server/backends/berkeley_db/berkeley_db.c
server/backends/common/database.c
gcc -I/usr/local/ctdlsupport/include -g -DHAVE_OPENSSL -DBUILD_ID=\"24074\" -DCTDLDIR=\"/usr/local/citadel\" -I/usr/local/ctdlsupport/include -g -L/usr/local/ctdlsupport/lib -Wl,--rpath -Wl,/usr/local/ctdlsupport/lib -lssl -lcrypto -lz utils/ctdldump.c server/backends/berkeley_db/berkeley_db.o server/backends/common/database.o -lcitadel -lz -ldb -lpthread -o ctdldump
/usr/bin/ld: /usr/local/ctdlsupport/lib/libdb.a(os_yield.o): in function `__os_yield_ctdl':
os_yield.c:(.text+0xc4): undefined reference to `pthread_yield'
collect2: error: ld returned 1 exit status
gmake: *** [Makefile:60: ctdldump] Error 1
Subject: Re: Citadel 996 Easy Install on Debian System aborts
I am running Citadel 996 on an Odroid C2. While upgrading Citadel
to a newer version with Easy Install, the installation aborts during
the "Installing Citadel" process. Could you point me in a direction
that helps me to solve the issue?
What operating system are you running on your Odroid? Is it Ubuntu, Fedora, Arch, Armbian ... and what version?
Subject: Re: Citadel 996 Easy Install on Debian System aborts
I am on Debian Bookworm (dietpi)
I am running Citadel on a Raspi. I would like to keep the installation on its SD card but would like all the data (mail contents, ...) to be stored on an external USB SSD. Can I change the file structure in an installed system or only at compile time?
Subject: Just Started Getting BDB 2055 Locks error and error 12 of bdb fetch
I have 13GB attached to system and the server is core dumping with 8500+ log filees. Started this morning
on 996
Subject: Re: Just Started Getting BDB 2055 Locks error and error 12 of bdb fetch
LG answered your question a few posts above.
Mon Mar 18 2024 09:54:27 EDT from stormytramp Subject: Just Started Getting BDB 2055 Locks error and error 12 of bdb fetchI have 13GB attached to system and the server is core dumping with 8500+ log filees. Started this morning
on 996
Subject: Re: Citadel 996 Easy Install on Debian System aborts
I am on Debian Bookworm (dietpi)
Unfortunately I don't have a "dietpi" system to test on. I did try it on regular Debian, the latest version (bookworm) on an ARM system and it completed the build without that error.
You might try running the Docker version instead of building the Easy Install.
I am running Citadel on a Raspi. I would like to keep the
installation on its SD card but would like all the data (mail
contents, ...) to be stored on an external USB SSD. Can I change the
file structure in an installed system or only at compile time?
Sure, that's pretty easy. The database is in /usr/local/citadel/data and you can just make that a symbolic link to a location on your SSD. Or if that's the only thing on your SSD then you can simply mount it there.