Please wait...
0 files
I'd like to know if the developers are working on (or is it planned) adding
posting and feed control features to the Citadel's NNTP service.
Unfortunately that is not on the short-term roadmap. The existing read-only NNTP support was built as part of a collaboration that ended before posting and feed control were implemented.
The best we can say right now is "someday".
I am running on a Pi one! all good. How do I implement a mobile
template?
I would advise waiting for WebCit-NG, which is in development and will be "responsive" by default.
I am presently running citadel on Centos 7, I am using a CA Provided SSL. I have been trying configure the server using the most secure methods possible.
Presently every online TLS/SSL test I run against the server is telling me that SSLv3 is running yet I have not been able to find any way to disable it. I have found plenty of resources to disable it in Apache, but I am only running Citadel and Apache is not installed. Any assistance would be appreciated.
The domain I am running it on is https://takethepics.org
Thanks
Chris
I'd like to know if the developers are working on (or is it planned) adding
posting and feed control features to the Citadel's NNTP service.
Unfortunately that is not on the short-term roadmap. The existing read-only NNTP support was built as part of a collaboration that ended before posting and feed control were implemented.
The best we can say right now is "someday".
What a pity. If I had had enough programming knowledge I would try it. NNTP is a fascinating protocol.
Thank you for your answer.
I am presently running citadel on Centos 7, I am using a CA Provided SSL. I have been trying configure the server using the most secure methods possible.
Presently every online TLS/SSL test I run against the server is telling me that SSLv3 is running yet I have not been able to find any way to disable it. I have found plenty of resources to disable it in Apache, but I am only running Citadel and Apache is not installed. Any assistance would be appreciated.
The domain I am running it on is https://takethepics.org
Thanks
Chris
Hi, I have installed citadel on my raspberry (debian 10) and also on a vps (debian 9) and there is the same problem ...sender : user@mydomain.comrecipient : user@gmail.comthe message downloaded with thunderbird (and also with the webmail) looks like this :
sender : user@mydomain.comrecipient : user@mydomain.com, user@gmail.comwhy does citadel add sender address to recipient ?
Hi, I have installed citadel on my raspberry (debian 10) and also on a vps (debian 9) and there is the same problem ...
sender: user@mydomain.com
recipient: user@gmail.com
the message downloaded with thunderbird and also with the webmail looks like this:
sender: user@mydomain.com
recipient: user@mydomain.com, user@gmail.com
why does citadel add sender address to recipient address ?
Subject: Re: Sender address added to recipient address
The Dev team is aware of this issue. Is it causing other issues for you?
Previous testing has shown that it only happens when using an external client. Have you been able to recreate the issue just from the Webclient, or does the issue appear in the webclient only after an external client (TB) has touched the mail?
Hi, I have installed citadel on my raspberry (debian 10) and also on a vps (debian 9) and there is the same problem ...
sender: user@mydomain.com
recipient: user@gmail.com
the message downloaded with thunderbird and also with the webmail looks like this:
sender: user@mydomain.com
recipient: user@mydomain.com, user@gmail.com
why does citadel add sender address to recipient address ?
Subject: Re: Sender address added to recipient address
Fri Feb 12 2021 17:13:40 ESTfrom ParanoidDelusions Subject: Re: Sender address added to recipient addressThe Dev team is aware of this issue. Is it causing other issues for you?
Previous testing has shown that it only happens when using an external client. Have you been able to recreate the issue just from the Webclient, or does the issue appear in the webclient only after an external client (TB) has touched the mail?
Subject: Error 550 Messages should have one or no To headers, not 2
Newbie to Linux here so go easy. Also, since I can only say this once, it's my first public forum post in >20 years.
I have Apache2 and Citadel/Webcit-https installed and working on a virtual host with Ubuntu 20.04.
The email problem is there are always two "To: ..." sections included in the email header, which results in email getting kicked back by some servers with:
Delivery Status Notification (Failure)
... (550 Messages should have one or no To headers, not 2. )
This happens with entirely webcit internal email (i.e., no external email client touching the message). And identically, when replying to a message from an internal user or from an external email address message.
An example Header looks like:
Return-Path: admin@domain.net
Date: Sat, 13 Feb 2021 13:19:18 -0700
To: admin@domain.net
To: mgolden@domain.net
Subject: Test admin-->mgolden
Message-ID: <60283446-00000060@hostname.domain.net>
From: "admin" <admin@domain.net>
MIME-Version: 1.0
X-Mailer: WebCit 927
Content-type: multipart/alternative; boundary="Citadel--Multipart--hostname.domain.net--1721--0002"
The first "To:..." is always the email address of the logged-in citadel user, whether it's a new message or a reply. The second "To:..." is always the intended recipient of the email..
Am really hoping to make Citadel work for us but this creates a no-go situation b/c I seemingly can't fix it or find a workaround.
Any suggestions? Thanks.
-Mike
Subject: Re: Error 550 Messages should have one or no To headers, not 2
Hello Mike, welcome to your first post in 20 years. Please use the Citadel Support room for any questions.
Subject: Re: Sender address added to recipient address (Error 550)
Newbie to Linux here so go easy. Also, since I can only say this once, it's my first public forum post in >20 years.
I have Apache2 and Citadel/Webcit-https installed and working on a virtual host with Ubuntu 20.04.
The email problem is there are always two "To: ..." sections included in the email header, which results in email getting kicked back by some servers with:
Delivery Status Notification (Failure)
... (550 Messages should have one or no To headers, not 2. )
This happens with entirely webcit internal email (i.e., no external email client touching the message). And identically, when replying to a message from an internal user or from an external email address message.
An example Header looks like:
Return-Path: admin@domain.net
Date: Sat, 13 Feb 2021 13:19:18 -0700
To: admin@domain.net
To: mgolden@domain.net
Subject: Test admin-->mgolden
Message-ID: <60283446-00000060@hostname.domain.net>
From: "admin" <admin@domain.net>
MIME-Version: 1.0
X-Mailer: WebCit 927
Content-type: multipart/alternative; boundary="Citadel--Multipart--hostname.domain.net--1721--0002"
The first "To:..." is always the email address of the logged-in citadel user, whether it's a new message or a reply. The second "To:..." is always the intended recipient of the email..
Am really hoping to make Citadel work for us but this creates a no-go situation b/c I seemingly can't fix it or find a workaround.
Any suggestions? Thanks.
-Mike
P.S. Sorry for the accidental post to 'Main Floor'. Turns out it wasn't entirely my fault. At that moment I was using Brave (whereas here I'm using FireFox) and this site doesn't/didn't work right with Brave apparently...
Oops. The post also ended-up in LXer. The problem was this site seemingly doesn't work right using Brave. It's working differently/better with Firefox.
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?