Rerun the setup, or just run easy install again - which is an "in place upgrade" - it'll come to a point where it will verify the username and password for the Admin account - you can change it there. I think that will solve your issue. 

Thu Apr 01 2021 10:08:33 EDT from spot Subject: maximum password length exceeded on setup

How to reset the password on the admin account with a ssh connect to the server.

 

I've googled and you have no idea how many things out there are called "citadel". Steam apparently have a game and it swamps the search hits for overriding passwords, even if you put a -steam qualifier.

 

I did find a very belated note out there that the maximum character length is 32 characters, which may or may not be outdated information. The shortest maximum I've ever seen was 9 characters on ICQ after the protocol became popular in Russia, presumably someone running the network was trying hard not to get arrested.

 

Anyway, I fell head-first into the trap and I don't know how to climb out. I could re-run the easy install but I thought I'd ask and then go for a walk.

Hello developers,

I think the smart host feature is not working for sure.

I used a network sniffer to analyse the network traffic of my old and my new citadel server (the new one runs by the way at the time of writing the most recent software).

What was the result? The old citadel server connected to the smart host as it should and delivered the mail without any error. But the new server did nothing. Beeing configured with the same smart host connection parameters it did not even try to connect to the smart host. Please fix this issue!

Developers, when you release new software, I strongly encourage you to provide detailed release notes, too. Notes that tell us what made it into the new software. Feautures and bug fixes. I don't want to test all issues after each software release just to see if it is fixed or not. Thank you.

Happy Easter!

Markus

Sun Feb 14 2021 18:09:46 EST from markus Subject: Re: How to address smart hosts in citadel?

Hello folks,

I did some investigation concerning my smart host problem.

What I have found so far: When I send mails with my mail user agent that connects to my citadel server and this citadel server is configured to use a smart host for outgojng mails then citadel porbably does not try to connect to the smart host. It is an assumption, but underpinned by the fact that I cannot find any entries in

/var/log/syslog

/var/log/mail.log

/var/log/mail.info

and my mail service provider that provides the smart host cannot find any smart host's log entries that would show that citadel tries to connect to it.

Dear memeber of the development team: Doesn't citadel log connections to smart hosts or is it possible that the smart host feature is actually not working?

Thanks,

Markus

 

Tue Feb 02 2021 17:04:07 EST from markus Subject: Re: How to address smart hosts in citadel?

Thanks for the responses of you both.

I think I have to explain what I did:

My old citadel system was running for years successfully using a smart host to deliver emails. The smart host was configured according to the following pattern:

   username:password@host:port

On my new citadel system I wanted to use the very same smart host. That's why I had configured the smart host the very same way. But while the old citadel system delivers mails via smart host, the new citadel system does not.

That's my problem. And that's why I was asking for the precise addressing in order to exclude any changes that could have been taking place on the road from the old to the most recent citadel system. And when I understand you right, warbaby, nothing has changed.

What I kno is that I can reach the smart host from both machines, from the older and the newer one. What I haven't done so far is asking the system administration people of the smart host if their log files can tell a story.

digbick, does your citadel system successfully deliver mails via smart host? If so, do you run the most recent webcit/citadel that is availabel via Easy Install?

warbay, when I try to find the reason for my smart host problem can I exclude any envolvement of citadel/webcit?

Thank you both a lot,

Markus

 

 

Mon Feb 01 2021 20:02:21 EST from warbaby Subject: Re: How to address smart hosts in citadel?

 

smart-host: Normally, Citadel sends outbound Internet e-mail directly to its destination. This may not be appropriate for some sites; you may require (due to local convention, security policy, or whatever) that all outbound mail be sent to an SMTP relay or forwarder. To configure this functionality, simply enter the domain name or IP address of your relay as a 'smart-host' entry.

If your relay server is running on a port other than the standard SMTP port 25, you can also specify the port number using "host:port" syntax; i.e. relay99.myisp.com:2525

Furthermore, if your relay server requires authentication, you can specify it using username:password@host or username:password@host:port syntax; for example, jsmith:pass123@relay99.myisp.com:25

A fallback host is a smart-host that is only used if mail cannot be delivered directly to its destination. This is useful if you prefer direct delivery but do not want your server queue filling up with deferred deliveries.

https://www.citadel.org/system_administration_manual.html

Mon Feb 01 2021 04:49:58 PM EST from digbick Subject: Re: How to address smart hosts in citadel?

 

Tue Jan 19 2021 17:47:56 EST from markus Subject: How to address smart hosts in citadel?

Hello all again,

could anybody tell me how smart host should be addressed in citadel (please be as precise as possible)?

Thanks in advance

Markus

 

 

From the Administration Menu, open:

Domain names and Internet mail configuration

Then fill the box at Smart hosts with the FQDN or IP address of your smarthost. That easy. The hard part is setting up a smarthost...

 

 

 

 

did this ever get resolved?  I found a recommendation to disable the db services in the nsswitch.conf file as a possible source of problems.   I believe you merely delete the instance of 'db' in the config file (create a backup beforehand).  Linux Mint does set the config file to use db services.  something in binding the ports at bootup.

https://www.citadel.org/citserver_crashes_when_running_on_debian_linux_when_sending_out_internet_email._fix.html

Edit /etc/nsswitch.conf and turn off the 'db' services if you're not using them.

Mon Mar 08 2021 05:52:40 EST from infomatics Subject: closed ports

Running citadel on debian 9 with no other apps.

firewall is disabled and all iptable entries removed with default allow on all

citadel setup with standard ports and webcit running with 8080 and 8443

8080 and 8443 work and are open ie can configure and add users

ports 25,123,465,587,993 are all closed when testing with  tcptraceroute

can someone please offer some guidance

rgds Ian

"Running Citadel Instance Costs and Stats"

    Apparently I can create a room, but not delete it is under 'Computer Level'.  I created 'Costs of Running Citadel" room under computer level.

   Not sure if it was appropriate to do either.  Trying this out for a particular 'community' in mind.

 BTW - a lot of comments appear to be only this year and last, how long has this site been running.  Do you purge old messages?

  Thanks,

viper

I have a working setup with SpamAssassin marking incoming Mail.

Now I want Citadel to move all marked EMails to a Spam-Folder before delivering them to the clients. As I understand it the way to do that is using the server-side mail filters. I just can't seem to get the filter to work.
I expected the filter to be like:
If |X-Spam-Status| |contains| |True| |Move message to| |Spam| and then |continue processing|

I derived the filter from the EMail headers generated by SpamAssassin (The required value is -10.0 to force the EMail as Spam)

X-Spam-Level: 
X-Spam-Status: True, score=0.8 required=-10.0

However, no EMail matches the filter. If I invert the condition (from |contains| to |does not contain|), all EMails get sent to the Spam folder, so the problem is not with in the moving messages part.

Any Ideas?

Mon Apr 05 2021 12:21:21 EDT from IGnatius T Foobar Subject: Re: Please delete this room.

Subject: Please delete this room.
"Running Citadel Instance Costs and Stats"

At your request I have deleted the room. Thank you.

Thanks.

Mon Apr 05 2021 22:24:26 EDT from viper Subject: Re: Please delete this room.

 

Mon Apr 05 2021 12:21:21 EDT from IGnatius T Foobar Subject: Re: Please delete this room.

Subject: Please delete this room.
"Running Citadel Instance Costs and Stats"

At your request I have deleted the room. Thank you.

Thanks.

 

I know that you know that I know that you know that I know that...

Is this an example of that?

I would like to use OpenLDAP for user auth on my citadel install because 2 other apps on the same server can support OpenLDAP for single sign on and I want it to be homogenous, I dont want users to have to create "accounts" and be bothered with the bullshit of validation just to chat and yammer on a service that I provide for free. 

If anyone has sucessfully integrated a citadel with a phpBB via OpenLDAP, please talk to me. (I realize that integrating phpbb and citadel is frankenstein in nature, run with me here...)

https://www.smashbot.com has 3 different applications within the same "concept". 

phpBB, My Internet Chat Room, and Citadel. 

please feel free to dig around. Try to break stuff, I need beta testers. 

Hello,

I have a citadel server running in my network via a Raspberry Pi.

Since about one year, the server is not running anymore.

I get the following message when I try to access it:

"This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator"

When I type "systemctl status citadel", I get the following message:

● citadel.service - LSB: Start daemon at boot time

   Loaded: loaded (/etc/init.d/citadel; generated; vendor preset: enabled)

   Active: active (exited) since Sun 2020-01-19 17:08:09 CET; 1 years 2 months ago

     Docs: man:systemd-sysv-generator(8)

  Process: 205 ExecStart=/etc/init.d/citadel start (code=exited, status=0/SUCCESS)

   CGroup: /system.slice/citadel.service

 

Jan 19 17:08:21 raspberrypi citserver[247]: db: BDB1544 process-private: unable to find environment

Jan 19 17:08:21 raspberrypi citserver[247]: db: dbenv->open: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery

Jan 19 17:08:21 raspberrypi citserver[247]: db: attempting catastrophic recovery...

Jan 19 17:08:21 raspberrypi citserver[247]: db: BDB1544 process-private: unable to find environment

Jan 19 17:08:23 raspberrypi citserver[247]: db: BDB2578 DB_LOGC->get: log record LSN 317/5480299: checksum mismatch

Jan 19 17:08:23 raspberrypi citserver[247]: db: BDB2579 DB_LOGC->get: catastrophic recovery may be required

Jan 19 17:08:23 raspberrypi citserver[247]: db: PANIC: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery

Jan 19 17:08:23 raspberrypi citserver[247]: db: PANIC: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery

Jan 19 17:08:23 raspberrypi citserver[247]: db: BDB1544 process-private: unable to find environment

Jan 19 17:08:23 raspberrypi citserver[247]: db: dbenv->open: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery

So, this is more just a general observation. I've been posting messages, then moving on from a room, then I'll notice the post I thought I had committed did not save. 

Today I noticed that in the upper left hand corner of the screen, in blue - it was flashing "Refusing to post empty message".

This happened several times - but I'm remote and can't really dig into researching any logs. 

But my thought was - I often miss these little alerts because the white on blue alert up in the corner. It is easy to miss. 


If it were just centered on the screen - it would be more noticeable. 

Hello all,

Could not find search function in this forum, so apologies if this is a recurring question.

Installed Citadel on my PI4, and most of it is working, except i have problems connecting outlook.

I have setup citadel as my mailserver, and i can send and receive email to external accounts (work, gmail, etc). (Test via Webcit)

I'm using outlook 2016 and connect via POP3/SMTP.

Outlook collects mail via POP3 fine from the server, using account settings either on port 110 and 995 no problem.

But is keeps asking for my credentials when using SMTP - controlpanel/mailsettings - test account setting - tries to send a test mail.

Tried SMTP via port 25 no encryption, but also using port 465 - with SSL enabled - keeps popping credentials question and port 587 STARTTLS - credentials quesions

'Your email server rejected your login. Verify your user name and password"

email server rejects login using username/password. But they work fine for POP3 logon......

Using the same credentials, sending from my Galaxy S10 via wifi on internal network using builtin mailclient using port 465 and SSL is no problem.

So Citadel & Pi should be configured correctly...

I'm lost. Any suggestions ?

Tnx

Bart

Thu Apr 08 2021 10:59:31 EDT from IGnatius T Foobar Subject: Re: This program was unable to connect or stay connected

Is it possible to repair the database without doing a reinstall?

Yes, run database_cleanup.sh

Hey,

thanks for your answer.

In which path is this file located?

Best regards

I've set up a new Citadel server and I'm trying to troubleshoot why e-mails send from the Citadel server are not being received.

I've performed all the steps here:

https://www.citadel.org/outbound_mail.html

and everything looks good!  I can telnet to gmail's SMTP server

 

root@raspberrypi:/home/laban# telnet alt1.gmail-smtp-in.l.google.com 25

 

Trying 64.233.186.27...

Connected to alt1.gmail-smtp-in.l.google.com.

Escape character is '^]'.

220 mx.google.com ESMTP o15si3122892qtr.382 - gsmtp

 

Problem is that the email is never received.  I've tested sending to other domains and have the same issue.

I also looked at 

https://www.citadel.org/i_want_to_be_a_whitehead.htm

 

and the only issue I see is that a reverse DNS by my IP resolves to ISP not to my domainname.

69.206.142.nn

root@XXXX:/home/laban# host 69.206.142.10

10.142.206.69.in-addr.arpa domain name pointer cpe-69-206-142-nn.hvc.res.rr.com.

check your mailbox for the delivery failure notice.  the 3 digit code after the recipient address is the foreign mail server rejection id.  your recipient likely subscribes to spamhaus.  If you are sending from a server at a residential address, your service provider likely logged your ip as part of the residential block of addresses to spamhaus.  You're likely on the policy block list.  search your ip to verify.  spamhaus is part of the internet cartel to prevent private upstarts from sourcing email.  PBL list is different from SBL.

https://www.spamhaus.org/sbl/