Language:
switch to room list switch to menu My folders
Go to page: First ... 24 25 26 27 [28] 29 30 31 32 ... Last
[#] Sun Feb 07 2021 14:49:56 EST from chrlorsw

Subject: Disabling SSLv3 - Centos 7

[Reply] [ReplyQuoted] [Headers] [Print]

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



[#] Fri Feb 12 2021 03:48:55 EST from baxeisindi

Subject: Sender address added to recipient address

[Reply] [ReplyQuoted] [Headers] [Print]

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 ?



[#] Fri Feb 12 2021 05:39:27 EST from baxeisindi

Subject: Sender address added to recipient address

[Reply] [ReplyQuoted] [Headers] [Print]

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 ?

[#] Fri Feb 12 2021 05:43:39 EST from baxeisindi

Subject: Sender address added to recipient address

[Reply] [ReplyQuoted] [Headers] [Print]

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 ?

 

 



[#] Fri Feb 12 2021 17:13:40 EST from ParanoidDelusions

Subject: Re: Sender address added to recipient address

[Reply] [ReplyQuoted] [Headers] [Print]

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? 

 

Fri Feb 12 2021 05:43:39 EST from baxeisindi Subject: Sender address added to recipient address

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 ?

 

 



 



[#] Sat Feb 13 2021 03:27:58 EST from baxeisindi

Subject: Re: Sender address added to recipient address

[Reply] [ReplyQuoted] [Headers] [Print]

 

Fri Feb 12 2021 17:13:40 ESTfrom ParanoidDelusions 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? 

Thank you for your reply, no other issue for me.

Yes, I was able to recreate the problem just from the web client, gmail and yahoo, 
instead there are no problems with roundcube webmail .


 

 



[#] Sat Feb 13 2021 16:37:46 EST from MikeGolden

Subject: Error 550 Messages should have one or no To headers, not 2

[Reply] [ReplyQuoted] [Headers] [Print]

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



[#] Sat Feb 13 2021 18:39:50 EST from zooer

Subject: Re: Error 550 Messages should have one or no To headers, not 2

[Reply] [ReplyQuoted] [Headers] [Print]

Hello Mike, welcome to your first post in 20 years.  Please use the Citadel Support room for any questions.



[#] Sat Feb 13 2021 19:20:47 EST from MikeGolden

Subject: Re: Sender address added to recipient address (Error 550)

[Reply] [ReplyQuoted] [Headers] [Print]

 

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...

 

 

 

 



[#] Sat Feb 13 2021 19:35:48 EST from MikeGolden

[Reply] [ReplyQuoted] [Headers] [Print]

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.



[#] Sun Feb 14 2021 18:09:46 EST from markus

Subject: Re: How to address smart hosts in citadel?

[Reply] [ReplyQuoted] [Headers] [Print]

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...

 



 



 



 



[#] Sun Feb 14 2021 18:33:09 EST from markus

Subject: What about deviding citadel/webcit into branches?

[Reply] [ReplyQuoted] [Headers] [Print]

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



[#] Fri Feb 19 2021 14:46:17 EST from platonov

Subject: Webcit left button pannel not displayed

[Reply] [ReplyQuoted] [Headers] [Print]

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?

 



[#] Sun Feb 21 2021 08:42:17 EST from Gaston

Subject: How to uninstall Citadel

[Reply] [ReplyQuoted] [Headers] [Print]

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?



[#] Sun Feb 21 2021 09:18:02 EST from Gaston

Subject: Re: How to uninstall Citadel

[Reply] [ReplyQuoted] [Headers] [Print]

When I rerun setup. I get extension errors. Unable to start TCP on all ports. Please advise?



[#] Sun Feb 21 2021 09:40:22 EST from Gaston

Subject: Webcit

[Reply] [ReplyQuoted] [Headers] [Print]

How do I access WebCit?



[#] Sun Feb 21 2021 10:18:13 EST from Gaston

Subject: Errors when running setup

[Reply] [ReplyQuoted] [Headers] [Print]

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



[#] Sun Feb 21 2021 15:28:04 EST from IGnatius T Foobar

Subject: Re: Sender address added to recipient address

[Reply] [ReplyQuoted] [Headers] [Print]

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.

[#] Sun Feb 21 2021 15:28:53 EST from IGnatius T Foobar

Subject: Re: Error 550 Messages should have one or no To headers, not 2

[Reply] [ReplyQuoted] [Headers] [Print]

  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.

[#] Mon Feb 22 2021 18:46:21 EST from tsalmon

Subject: Problems with initial setup

[Reply] [ReplyQuoted] [Headers] [Print]

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?

 



Go to page: First ... 24 25 26 27 [28] 29 30 31 32 ... Last