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
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
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
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...
Subject: What about deviding citadel/webcit into branches?
Dear developers,
What would you think about introducing braches like for example 'unstable', 'testing' and 'stable' for citadel/webcit development? Developers could change code in 'unstable' branch, people would test the behaviour of citadel in 'testing' branch and people can use 'stable' branch for production.
Regards,
Markus
Whenever I start the web browser after box reboot and webcit shows "Not Logged in", the left (vertical) button panel of webcit is not being displayed, but is simply blank.
So, the Log in button is not there and you have to change the address in the browser removing the previous command so you can redisplay the page and login panel shows up again.
Does anybody know what's to do to fix it?
I installed Citadel and everything seemed to work till I sent 2 messages with no content in body of email and caused server to crash. Now I can no longer access the server. How would I go about uninstalling then reinstalling Citadel?
When I rerun setup. I get extension errors. Unable to start TCP on all ports. Please advise?
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 0.0.0.0:504: (citadel-TCP) ;extensions: TCP port 0.0.0.0:143: (IMAP) ;extensions: TCP port 0.0.0.0:993: (IMAPS) ;extensions: TCP port 0.0.0.0:119: (NNTP) ;extensions: TCP port 0.0.0.0:563:
(NNTPS) ;extensions: TCP port 0.0.0.0:110: (POP3) ;extensions: TCP port 0.0.0.0:995: (POP3S) ;extensions: TCP port 0.0.0.0:25: (SMTP-MTA) ;extensions: TCP port 0.0.0.0:465: (SMTPs-MTA) ;extensions: TCP port 0.0.0.0: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:
http://www.citadel.org/doku.php?id=faq:mastering_your_os:net#netstat
Subject: Re: Sender address added to recipient address
recipient: user@mydomain.com, user@gmail.com
why does citadel add sender address to recipient address ?
This is a new bug that has been discovered and fixed. Please download Citadel Server again (using Easy Install again if that's how you originally installed it) and you will receive the fix.
Subject: Re: Error 550 Messages should have one or no To headers, not 2
To: admin@domain.net
To: mgolden@domain.net
This is a new bug that has been discovered and fixed.
Please update your Citadel Server again (for example, using the Easy Install script) and you will receive the fix.
I am generally new to setting up servers. I have read a few outdated guides on how to setup a Citadel Server.
I have weird problem. I Citadel installed on an Ubuntu 20 OS and it seems that my SMTP ports are closed.
My ip tables are blank and my UFW is disabled so all of my traffic should be allowed, but any inbound traffic to smtp ports is automatically dropped.
I am able to send emails to other organizations, but unable to receive them.
My DNS records and MX records are pointing correctly to my citadel server, this was confirmed when I restarted my Citadel server and was able for a brief time receive emails that I had previously sent.
I also did a local nmap scan on my Public Facing IP. It showed my ports being closed.
Is there anything that I could have misconfigured on initial Citadel setup?
Can anyone help me with this? Happens every time I restart Citadel server in Webcit!
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 0.0.0.0:504: (citadel-TCP) ;extensions: TCP port 0.0.0.0:143: (IMAP) ;extensions: TCP port 0.0.0.0:993: (IMAPS) ;extensions: TCP port 0.0.0.0:119: (NNTP) ;extensions: TCP port 0.0.0.0:563:
(NNTPS) ;extensions: TCP port 0.0.0.0:110: (POP3) ;extensions: TCP port 0.0.0.0:995: (POP3S) ;extensions: TCP port 0.0.0.0:25: (SMTP-MTA) ;extensions: TCP port 0.0.0.0:465: (SMTPs-MTA) ;extensions: TCP port 0.0.0.0: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:
http://www.citadel.org/doku.php?id=faq:mastering_your_os:net#netstat
My citadel server, which is being used only for email, has degraded to the point that it no longer runs. I can't log into the web interface. My devices can't fetch mail. It is running on an ubuntu server and was configured after easy install.
After it stopped working, I attempted to do an easy install from an updated package. When I ssh into the box I get the following messages:
citserver[3250]: db: cdb_fetch(9): BDB0075 DB_PAGE_NOTFOUND: Requested page not found
I was seeing these messages even before attempting to patch with the latest. Not sure what to do from here.
Hi,
I‘m by no means an expert, but every problem I’ve had so far with Citadel has been a database one.
If it’s not happy with the data, the server won’t start. Do you have any backups of the data directory?
I've been running Citadel for 5 years, at least, and I'm finding now that the only way to keep it going is to restore the server from backup. Cleaning the database, reinstalling, and all the other scripts just send me in circles. Once in a while I get lucky after deleting locks and sockets then using the scripts, it will function again, but for the time invested restoring from a working copy always works. On my email client, I keep local copies of important emails.
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 0.0.0.0:504: (citadel-TCP) ;extensions: TCP port 0.0.0.0:143: (IMAP) ;extensions: TCP port 0.0.0.0:993: (IMAPS) ;extensions: TCP port 0.0.0.0:119: (NNTP) ;extensions: TCP port 0.0.0.0:563:
(NNTPS) ;extensions: TCP port 0.0.0.0:110: (POP3) ;extensions: TCP port 0.0.0.0:995: (POP3S) ;extensions: TCP port 0.0.0.0:25: (SMTP-MTA) ;extensions: TCP port 0.0.0.0:465: (SMTPs-MTA) ;extensions: TCP port 0.0.0.0: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:
http://www.citadel.org/doku.php?id=faq:mastering_your_os:net#netstatCan anyone help me with this? Happens every time I restart Citadel server in Webcit!
Not so much a question just an fyi, been seeing that a LOT today on the forums.
Like every other refresh.
I got a security error one today, too.
Not so much a question just an fyi, been seeing that a LOT today on the forums.
Like every other refresh.
Did you fix some of my other points that I have mentioned in
#] Thu Jan 28 2021 18:34:21 EST from markus
too? Or in other words: Where can I read about what was fixed or changed in the actual software?
Thanks
Markus
Sun Feb 21 2021 15:28:04 EST from IGnatius T Foobar Subject: Re: Sender address added to recipient addressrecipient: user@mydomain.com, user@gmail.com
why does citadel add sender address to recipient address ?
This is a new bug that has been discovered and fixed. Please download Citadel Server again (using Easy Install again if that's how you originally installed it) and you will receive the fix.
Just installed Citadel on Ubuntu 20.04 from the repo. No configs have been changed, but, when accessing the web interface, I receive a 503 error that redirects me to a non-existent page in the Citadel docs.
This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.
Read More...
Advice is welcome.
Thank you,
Larry