Hi.

It's been a while so sorry if i missed something.

I'm using Citadel on a Raspi 3B, been running for years.
I create a lot of users, so that it's easy to kill one should spam flood that user (which hasn't happened yet).
But i've also noted that those users can log in to get mail, but weren't able to send mail through a client.
They were able to send messages through webmail, but not by logging in with their mail program (such as Thunderbird), the passwords working in webmail will be denied.
I've been trying to find out why this happened, and found an answer somewhere else stating that passwords longer than 19 characters will not work.
So i've changed passwords, they're now up to 9 characters long (some of the not working ones were 12 characters long, most were 16).
Now they all work.
Is this a known issue, and is this a Citadel problem, something with SMTP protocols or could it be some OS problem with the PC running the client ?
I've been testing on a Win7 system if that is of any help.
I'll be testing on a Win11 system later on this week.

Thanks in advance for any of your insights.

so with the recent DB crash/restore/rebuilds, should i expect all my mail to be gone? Both incoming and outgoing?   Not a big deal, didnt need them. Just that i noticed it today so i thought id mention it. 

it was on here at uncensored.. not a local copy. sorry i wasn't more clear.  But again, not a big deal to me personally, i just thought id mention it, just in case.

Fri Sep 15 2023 13:16:19 EDT from IGnatius T Foobar

so with the recent DB crash/restore/rebuilds, should i expect all my
mail to be gone? Both incoming and outgoing?   Not a big deal,

If you restored from a backup, everything should still be intact.

If you ran database_cleanup.sh , it depends on how bad your corruption was.
I've seen it restore everything perfectly, and I've seen it not recover perfectly.

Once again however, you should definitely be running Citadel Server version 991 or later. We made the database layer absolutely bulletproof by adding mmap (disk-backed) dbenv. I haven't been able to make it fail even after deliberately and repeatedly crashing the server under high write load.

For me, not a problem at all. Just didnt want to leave it unreported :) 

Fri Sep 15 2023 17:52:45 EDT from IGnatius T Foobar

Oooooh, yes that. :(

As you know, here on Uncensored we run bleeding-edge Citadel software because we are the last stage of testing before new versions go out to the world.
And yes, the private rooms (including mailboxes) of some users were a casualty.
Sorry for the inconvenience.

Trying to install citadel using Easy Install. Libcitadel fails to install, it's missing the configure script. Was automake/autoconf not run ?

2023-09-16 21:16:56 (291 KB/s) - 'libcitadel-easyinstall.tar.gz' saved [248327/248327]

 Installing libcitadel...
./citadel.install: line 454: ./configure: No such file or directory
 Citadel Easy Install is aborting.
 The last few lines above this message may indicate what went wrong.
 Linux Debian bookworm/sid( 4.19.84-microsoft-standard x86_64)

Cheers,
Henri

Fri Sep 15 2023 13:09:48 EDT from IGnatius T Foobar Subject: Re: SMTP password lenth limit ?

So i've changed passwords, they're now up to 9 characters long (some
of the not working ones were 12 characters long, most were 16).
Now they all work.

Not sure about that, but Citadel Server permits passwords up to 31 characters long.

Do the usernames have spaces or other non-alnum characters in them? Unless you have a very old Citadel you should be able to remove all of the spaces and other characters from the login name and it will still work. That often helps when using third party clients.

No, usernames do not have spaces or unusual characters in them.
And using webmail, there are no problems, so i think it is unlikely that there is a problem with Citadel itself.
I did test with a windows 11 laptop, and had the same problem.
I'll create new users and their names will be test10, test11, test12, test13 and test14, with passwords containing only numbers to see what will happen.
They will be removed after testing.

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