same issue

Fri Mar 26 2021 18:07:36 EDT from gronkdalonka Subject: 500 No such user on AUTH LOGIN

I noticed with the latest easy-install version of citadel sending mails via some clients (Fairemail) is not possible because smtp's AUTH LOGIN throws a "500 No such user" error when submitting an existing user name.
AUTH PLAIN is working fine.

So i guess smtp LOGIN is broken.

Can this be fixed or LOGIN removed from available AUTH methods?
Or is just something wrong with my setup?

 

We got the same issue:

auth login + crlf

encodedUsername

500 no such user

But login this way will be ok:

auth login + encodedUsername

encodedPwd

BTW, "AUTH LOGIN" works fine on version 917, so this may be a specific issue of version 931. 

Thu Aug 26 2021 00:47:18 EDT from IGnatius T Foobar Subject: Re: 500 No such user on AUTH LOGIN

Have you done an update from Easy Install any time since June 5? That is the date the issue was fixed.

If your update is newer than that, we will reopen this issue; otherwise please upgrade.

We installed CITADEL of Easy Install in mid-Aug with "curl https://easyinstall.citadel.org/install | bash", and we will reinstall in a few days, just in case.

Hello, im Stuck configuring the Smarthost the right way.

I have a

username: user@example.com

passwort: passwrd

a smtp server: example.smtp.com

a port: 25 or 587

I found this on the website:

[smtp[s]://][username:password@]host[:port]

smtp://user@example.com:passwrd@example.smtp.com:587 does not work.

What am I doing wrong?

Thanks for you help!

Tank you very much, that worked!

So, thank you to everyone that helped with my previous little misunderstanding about how things worked with the text editor incorporated into Citadel.

Now, I have a more.. serious issue. I was trying to change the login image, and it got corrupted on upload, which has now apparently borked the snot out of the login screen.

.....help?  I'm trying to figure where it's saved and/or at least looking where I can make revertible changes to make it not try to serve said file, but I'm...not having luck.

Thanks!

first of all Im newby to configuring servers.

i just installed citadel mail server on my VPS with easy install but now I realized that I can send emails from Citadal Meil Server but I cant recieve them. 

I didnt change anything on my VPS. I just installed ubuntu 20 on it and started installing Citadel.

Day 17, testing Uncensored.

"This is Major Tom to Ground Control
I'm stepping through the door
And I'm floating in a most peculiar way
And the stars look very different today"

Test Sept-19B from Firefox; the previous test from SMTP does not appear yet.

Fri Sep 17 2021 08:34:56 PM EDT from s3cr3to Subject: Test for Uncensored

Day 17, testing Uncensored.

"This is Major Tom to Ground Control
I'm stepping through the door
And I'm floating in a most peculiar way
And the stars look very different today"

Test Sept-19B from Firefox; the previous test from SMTP does not appear yet.

The message shows as "Error"

ERROR: �n�� �E�

Wed Dec 31 1969 07:00:00 PM EST from <>

 

How strange, the message was originally sent from "Development" and appeared here in "Support" and no subject.
(Ignore please)

Sun Sep 19 2021 03:45:53 PM EDT from s3cr3to

Test Sept-19B from Firefox; the previous test from SMTP does not appear yet.

The message shows as "Error"

ERROR: �n�� �E�

Wed Dec 31 1969 07:00:00 PM EST from <>

 

 

Hi,

I have been using Citadel in a private situation for more than 10 years, without problems.

But the NAS (LG) I was running it on needed replacement.

So now I have a new OpenMediaVault NAS, which is running without problems.

After I installed Citadel as a normal application, alongside OpenMediaVault (same as I did on my old NAS), things in OpenMediaVault broke seriously. I had to re-install it completely.

Then I learned I could run Citadel through docker/portainer in OpenMediaVault. That installation was a breeze, and didn't affect OpenMediaVault.

I copied mails from old NAS to new OMV Nas with a simple tool imapcopy. Was a bit problematic, some mails failed. But it succeeded seemingly well.

Since then, I have been using it for a couply of weeks. I noticed some problems. Connection seemed problematic, difficult to receive new mails. Retreiving mails from folders other than Inbox was problematic as well.

After investigating, I found out that the Citadel server and container is continuously crashing, and automatically restarting. This explains the problems described.

This happend on version 931.

I created a new container, which has version 938. After initial install, this container is stable, no crashes/restarts.

After I copy the data from first container (931) to the new container, the new container shows the same problems as the first. This happens when I copy all data, or only cdb.08 datafile.

Log file:

2021-09-19T21:00:26.960210325Z ctdlvisor: Welcome to the Citadel System running in a container.,
2021-09-19T21:00:26.960330444Z ctdlvisor: command line arguments: /usr/local/bin/ctdlvisor ,
2021-09-19T21:00:26.968395558Z ctdlvisor: /citadel-data/data is writable,
2021-09-19T21:00:26.960339997Z ctdlvisor: /citadel-data is writable,
2021-09-19T21:00:26.968477417Z ctdlvisor: /citadel-data/files is writable,
2021-09-19T21:00:26.968483671Z ctdlvisor: /citadel-data/keys is writable,
2021-09-19T21:00:26.968631336Z ctdlvisor: citserver running on pid=9,
2021-09-19T21:00:26.968640286Z ctdlvisor: executing citserver,
2021-09-19T21:00:26.968645473Z ctdlvisor: webcit (HTTP) running on pid=10,
2021-09-19T21:00:26.968650047Z ctdlvisor: webcit (HTTPS) running on pid=11,
2021-09-19T21:00:26.968654534Z ctdlvisor: executing webcit (https),
2021-09-19T21:00:26.968658960Z ctdlvisor: executing webcit (http),
2021-09-19T21:00:36.682189203Z ctdlvisor: pid=9 exited, status=26880, exitcode=105,
2021-09-19T21:00:41.696606302Z ctdlvisor: webcit (HTTPS) running on pid=11,
2021-09-19T21:00:36.682271066Z ctdlvisor: citserver exited intentionally - ending container session,
2021-09-19T21:00:37.682593778Z ctdlvisor: pid=10 exited, status=15, exitcode=0,
2021-09-19T21:00:38.682742827Z ctdlvisor: pid=11 exited, status=15, exitcode=0,
2021-09-19T21:00:40.683049304Z ctdlvisor: exit code 105,
2021-09-19T21:00:39.682808558Z ctdlvisor: pid=-1 exited, status=15, exitcode=0,
2021-09-19T21:00:41.693614399Z ctdlvisor: Welcome to the Citadel System running in a container.

There seems to be nothing I can do to futher investigate, due to the contineous and frequent crashes/restarts

I was thinking to copy mails from the first container to a new stable container, but that won't work either due to the crashes.

Only solution I can think of now is copy mails from old NAS to new container again. And then accepting I loose the new mails from the couple of weeks I have been using Citadel on the new NAS. Or try to copy these mails one by one through a mail client like Thunderbird.

Do you have any other suggestions?

Best regards,

Jan den Ouden

I was having VERY similar issues, continuously - and interestingly - I discovered that I was getting multiple PIDs for both the HTTP and HTTPS instances of Citadel. Citadel was crashing and restarting constantly, flooding my logs with error messages. 

Finally I went after it very hard - and unfortunately as usually happens - this was months ago and I don't remember exactly what the fix was. I think I documented most of what I was doing either here on Uncensored or on my own Citadel - but I didn't do it in this room for sure - because I've gotten some heat for blogging my personal troubleshooting randomly in this room. It creates a mess of the threaded view. 

It may not be related - it may just be a similar symptom. I'll see if I can find the messages. 

Sun Sep 19 2021 17:09:37 EDT from JanDenOuden Subject: Citadel contineously crashing and restarting

Hi,

I have been using Citadel in a private situation for more than 10 years, without problems.

But the NAS (LG) I was running it on needed replacement.

So now I have a new OpenMediaVault NAS, which is running without problems.

After I installed Citadel as a normal application, alongside OpenMediaVault (same as I did on my old NAS), things in OpenMediaVault broke seriously. I had to re-install it completely.

Then I learned I could run Citadel through docker/portainer in OpenMediaVault. That installation was a breeze, and didn't affect OpenMediaVault.

I copied mails from old NAS to new OMV Nas with a simple tool imapcopy. Was a bit problematic, some mails failed. But it succeeded seemingly well.

Since then, I have been using it for a couply of weeks. I noticed some problems. Connection seemed problematic, difficult to receive new mails. Retreiving mails from folders other than Inbox was problematic as well.

After investigating, I found out that the Citadel server and container is continuously crashing, and automatically restarting. This explains the problems described.

This happend on version 931.

I created a new container, which has version 938. After initial install, this container is stable, no crashes/restarts.

After I copy the data from first container (931) to the new container, the new container shows the same problems as the first. This happens when I copy all data, or only cdb.08 datafile.

Log file:

2021-09-19T21:00:26.960210325Z ctdlvisor: Welcome to the Citadel System running in a container.,
2021-09-19T21:00:26.960330444Z ctdlvisor: command line arguments: /usr/local/bin/ctdlvisor ,
2021-09-19T21:00:26.968395558Z ctdlvisor: /citadel-data/data is writable,
2021-09-19T21:00:26.960339997Z ctdlvisor: /citadel-data is writable,
2021-09-19T21:00:26.968477417Z ctdlvisor: /citadel-data/files is writable,
2021-09-19T21:00:26.968483671Z ctdlvisor: /citadel-data/keys is writable,
2021-09-19T21:00:26.968631336Z ctdlvisor: citserver running on pid=9,
2021-09-19T21:00:26.968640286Z ctdlvisor: executing citserver,
2021-09-19T21:00:26.968645473Z ctdlvisor: webcit (HTTP) running on pid=10,
2021-09-19T21:00:26.968650047Z ctdlvisor: webcit (HTTPS) running on pid=11,
2021-09-19T21:00:26.968654534Z ctdlvisor: executing webcit (https),
2021-09-19T21:00:26.968658960Z ctdlvisor: executing webcit (http),
2021-09-19T21:00:36.682189203Z ctdlvisor: pid=9 exited, status=26880, exitcode=105,
2021-09-19T21:00:41.696606302Z ctdlvisor: webcit (HTTPS) running on pid=11,
2021-09-19T21:00:36.682271066Z ctdlvisor: citserver exited intentionally - ending container session,
2021-09-19T21:00:37.682593778Z ctdlvisor: pid=10 exited, status=15, exitcode=0,
2021-09-19T21:00:38.682742827Z ctdlvisor: pid=11 exited, status=15, exitcode=0,
2021-09-19T21:00:40.683049304Z ctdlvisor: exit code 105,
2021-09-19T21:00:39.682808558Z ctdlvisor: pid=-1 exited, status=15, exitcode=0,
2021-09-19T21:00:41.693614399Z ctdlvisor: Welcome to the Citadel System running in a container.

There seems to be nothing I can do to futher investigate, due to the contineous and frequent crashes/restarts

I was thinking to copy mails from the first container to a new stable container, but that won't work either due to the crashes.

Only solution I can think of now is copy mails from old NAS to new container again. And then accepting I loose the new mails from the couple of weeks I have been using Citadel on the new NAS. Or try to copy these mails one by one through a mail client like Thunderbird.

Do you have any other suggestions?

Best regards,

Jan den Ouden

 

 

http://uncensored.citadel.org/readfwd?go=Techie%20Talk?start_reading_at=2099263559#2099263559


Is where I am talking about this issue. It'll give you a date - and it was related to redirects to blog rooms in my case - I also see this happening on Smashbot's Citadel. 

in Aide: you should have an error message, fairly frequently, something like: 

Citadel had trouble on starting up. We couldn't bind all ports you configured to be provided by Citadel Server.
This means, Citadel won't be the service provider for a specific service you configured it to.

If you don't want Citadel to provide these services, turn them off in WebCit via: "Admin->System Preferences->Network".

The failed ports and sockets are: extensions: TCP port *:504: (citadel-TCP) ;extensions: TCP port *:143: (IMAP) ;extensions: TCP port *:993: (IMAPS) ;extensions: TCP port *:119: (NNTP) ;extensions: TCP port *:563: (NNTPS) ;extensions: TCP port *:110:
(POP3) ;extensions: TCP port *:995: (POP3S) ;extensions: TCP port *:25: (SMTP-MTA) ;extensions: TCP port *:465: (SMTPs-MTA) ;extensions: TCP port *:587: (SMTP-MSA)

If you want Citadel to provide you with that functionality, check the output of "netstat -lnp" on Linux, or "netstat -na" on BSD and disable the program that binds these ports.


To make both ways actualy take place restart the citserver with "sendcommand down"

The errors returned by the system were:
failed; failed; failed; failed; failed; failed; failed; failed; failed; failed

You can recheck the above if you follow this faq item:


------------------

A PS -A may be insightful in showing that Citadel thinks it isn't running, is trying to launch a new instance, and can't bind the new instance because Citadel is already running and has those ports bound. 

And I think it is related to how Citadel launches. Are you running Debian or a Debian variant?