Hey, has anyone here integrated Citadel with AD?

Hello,

Very new to this room.

From a client machine I am trying to: echo "Subject: Client machine citmail" | /usr/local/citadel/citmail red@webmailserver.dom.com

An getting this: citmail: can't connect: Connection refused

The webmailserver sever is ONLY listening on 587.

The command works fine from the webmailserver sever itself (localhost).

In the client machine I did install another citadel full but stop the 3 services (citadel, http/https web)... on/off does not make any change)

Telnet from client to server on port 587 is OK

netstat -ltnp | grep cit

tcp        0      0 0.0.0.0:504             0.0.0.0:*               LISTEN      129029/citserver

tcp        0      0 0.0.0.0:587             0.0.0.0:*               LISTEN      129029/citserver

tcp6       0      0 :::444                  :::*                    LISTEN      119743/webcit

I thought it was a certificate/key issue and copy from the server to the client (citadel.key and citadel.cer).

Question:

1) I can't find a conf file that I can check for citmail is this normal?

2) I can find in the server any logs that could tell me why it's rejecting

3) from the CLient adding the "-d" to citmail does not display more info

Any tips ?

Trying to get Citadel going on the cheapest AWS server I can, and on ARM, if possible. Tried AmazonLinux both x64 and ARM versions and get the error "==: unary operator expected" when attempting to run the quickstart curl https://easyinstall.citadel.org/install | bash

Is there an ARM distro that Citadel works on?

My intent in using citmail is to minimize the number of different software needed.

If I am using citadel, why not use citmail on my linux client?

Well I did try another SW and it's failing, that one also as bad logs, not sure of the reason of failure.

User/password authen is my guess but don't know how to fix in that SW.

My echo test with citmail is also to ensure that the basic is all good.

Thank you for the SW suggestion I will try.

Only just started using Citadel. It was working perfectly fine until I recently rebooted the instance it was running on. 

Now it starts, runs for 10 seconds, and then systemctl status returns this:

citadel.service - Citadel Server

   Loaded: loaded (/etc/systemd/system/citadel.service; enabled; vendor preset: disabled)

   Active: failed (Result: signal) since Thu 2023-09-21 13:46:34 EDT; 5s ago

  Process: 25129 ExecStart=/usr/local/citadel/citserver (code=killed, signal=SEGV)

 Main PID: 25129 (code=killed, signal=SEGV)

systemd[1]: citadel.service: Main process exited, code=killed, status=11/SEGV

systemd[1]: citadel.service: Failed with result 'signal'.

systemd[1]: citadel.service: Service RestartSec=100ms expired, scheduling restart.

systemd[1]: citadel.service: Scheduled restart job, restart counter is at 5.

systemd[1]: Stopped Citadel Server.

systemd[1]: citadel.service: Start request repeated too quickly.

systemd[1]: citadel.service: Failed with result 'signal'.

systemd[1]: Failed to start Citadel Server.

journalctl -xe returned this:

citserver[25125]: extensions: TCP port *:465: (SMTPs-MTA) registered.

citserver[25125]: extensions: TCP port *:587: (SMTP-MSA) registered.

citserver[25125]: extensions: unix domain socket 'lmtp.socket': registered.

citserver[25125]: extensions: unix domain socket 'lmtp-unfiltered.socket': registered.

citserver[25125]: citserver[25125]: Existing database version on disk is 992

citserver[25125]: Existing database version on disk is 992

citserver[25125]: citserver[25125]: extensions: service DICT_TCP has been manually disabled, skipping

citserver[25125]: extensions: service DICT_TCP has been manually disabled, skipping

citserver[25125]: citserver[25125]: extensions: TCP port *:5222: (XMPP) registered.

citserver[25125]: extensions: TCP port *:5222: (XMPP) registered.

citserver[25125]: citserver[25125]: main: changing uid to 1003

citserver[25125]: main: changing uid to 1003

kernel: citserver[25126]: segfault at 10 ip 00007f88216d8d40 sp 00007f8819b1bb98 error 4 in libcitadel.so.4.0.992[7f88216be000+21000]

kernel: Code: 08 83 ef 01 eb a5 0f 1f 40 00 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 63 f6 48 0f af 77 08 48 8b 07 48 01 f0 c3 90 <8b> 47 10 c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 48 89 f1 48 8b 57

systemd[1]: citadel.service: Main process exited, code=killed, status=11/SEGV

systemd[1]: citadel.service: Failed with result 'signal'.

I'm new to Citadel, know some Linux and basic coding, but otherswise am stumped here. Not sure what to do, because I'm not entirely sure what's going on. It mentions a "segfault," which sounds like some sort of illegal memory issue. Maybe it's a permissions based issue, but I haven't knowingly changed any on that box. Just rebooted, and that was it.

Any guidance would be greatly appreciated as I'm stuck.

Cheers,

JP

I get a similar error on Ubuntu:

  This is a NEW Citadel installation. 

 Installation will now begin. 

find: '/usr/local/ctdlsupport': No such file or directory

find: '/usr/local/ctdlsupport': No such file or directory

find: '/usr/local/ctdlsupport': No such file or directory

find: '/usr/local/ctdlsupport': No such file or directory

 Do you want Easy Install to attempt to install your OS dependencies? Y

sh: 319: [: Debian: unexpected operator

sh: 332: [: Debian: unexpected operator

 

Docker supports ARM.

( cant believe im suggesting docker.. )

i guess i should have added, that 'real' ARM hardware does work.  One of mine is being used to test builds with..

Not knowing AWS, but i wonder if their stuff is 'different' than the rest somehow. 

Fri Sep 22 2023 16:19:58 EDT from Nurb432 Subject: Re: installing on AmazonLinux (or any ARM, really)

Docker supports ARM.

 

( cant believe im suggesting docker.. )

Dear All,

couple of days back server stopped sending mails. Notices because of an error message coming back with SMTP code 412. Receiving is fine, no issues.

In the logs I keep seeing this message:

Sep 23 12:56:17 citserver[5959]: citserver[5959]: msgbase: message #97535 was not found
Sep 23 12:56:17 citserver[5959]: citserver[5959]: smtpclient: 97535 does not exist
Sep 23 12:56:17 citserver[5959]: msgbase: message #97535 was not found
Sep 23 12:56:17 citserver[5959]: smtpclient: 97535 does not exist

Thought maybe database had issues so restored a backup from before last time message was sent successfully. But this did not change anything. No mail goes out and the error also reappears. I therefore guess it is unrelated.

When I login as admin in Webcit and go to outbound SMTP queue it is showing:

As there are mails pending that have not been delivered, I would have expected to see them here.

Any ideas would be much welcome.

Thanks,

P.

Tried re-running the Easy Install, but that crapped out too after it started up.

I guess I can try just blowing it all away and start from scratch, but I'd rather not.

Definitely bombs out at the segfault mentioned above. 

Yep. Doing that right now. Thank you.

I got through the Easy Install after deleting those folders and cleaning everything up, seemed to install just fine, but...

Then it crashed as I was re-creating an email account through the web interface. I saved the changes, and then it lost connection.

Checked systemctl status citadel on the server, and it looks like the same exact segfault issue again.

It's strange because it was working perfectly fine for over a week, and I was starting to create a few accounts, and then this happened. Actually, now that I'm thinking about it, I think this started when I changed something from the web interface the first time.

FWIW I'm running: Red Hat Enterprise Linux release 8.8 (Ootpa).

It's frustrating because I was really starting to dig Citadel, and then this. 

Everything else on that server is running fine. Didn't do a yum update until AFTER the first time this happened. 

Weird.

Thanks for looking into it, thought. Much appreciated.

Cheers,

-JP

Sir,

Here's what I've been able to figure out, so far, not that I entirely understand it:

When I write data to the server using the web app via HTTP (8080), it's fine, but...

If I do the same thing via HTTPS (8443) it crashes and the server poops the bed with the same segfault error until I blow it all away and start over.

Something happens when I write to the server from 8443. It's the only variable I changed that lead it to crash. And it was working for a while just using 8080, so...

Will do it again to confirm.

I hope this helps. 

Cheers,

-JP