Language:
switch to room list switch to menu My folders
Go to page: First ... 5 6 7 8 [9] 10 11 12 13 ... Last
[#] Wed Sep 12 2018 10:46:58 EDT from ano @ Uncensored

Subject: Re: XMPP server

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

I think, the problem is in the second <?xml ... ?> from client. It is inside of first stream from expat's point of view. Expat error message is "XML or text declaration not at start of entity". By RFC, first <stream> assumed to be closed after TLS negotiation even if server not received </stream> (which is optional).

So citserver must reset XML parser immediately after <proceed ...> OR when it receive new <?xml ... ?>. Where is a right place for XML_ParserFree+XML_ParserCreate[NS] for this case? In the xmpp_command_loop()?



[#] Wed Sep 12 2018 15:14:23 EDT from beachwalk @ Uncensored

Subject: Citadel installation problem on FreeBSD

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

 

After read the 'Installing Citadel on FreeBSD' page and installed every files as what the page said, I started easyinstall to compile & install, but it stopped - see the message below:

<pre>

zlib compression:                 yes
Character set conversion support: yes

LTCompile: /bin/sh ./libtool --silent --mode=compile gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -D HAVE_MMAP -o buildinfo -c

CC: lib/libcitadel.c
In file included from lib/libcitadel.c:30:0:
lib/libcitadel.h:264:2: error: unknown type name 'loff_t'
  loff_t TotalSentAlready;
  ^~~~~~
lib/libcitadel.h:265:2: error: unknown type name 'loff_t'
  loff_t TotalReadAlready;
  ^~~~~~
gmake: *** [Makefile:169: lib/libcitadel.lo] Error 1
 Citadel Easy Install is aborting.
 The last few lines above this message may indicate what went wrong.
</pre>

 

My server currently running FreeBSD version: 10.4-RELEASE

Anyone here have running Citadel on FreeBSD?

 

 



[#] Fri Sep 14 2018 00:02:44 EDT from Clay @ Uncensored

Subject: This program was unable to connect or stay connected to the Citadel se

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

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

After hours of Googling, and reading the articles on the main Citadel site, I seem to be running into a brick wall. I am managing an email server for my wife's photography business. Everything had been working fine, until I attempted to log into the web interface, and I was met with that error. 

From what I have been able to gather, this points to the inability of WebCit to communicate with CitServer.

I can access and log into Citadel from SSH, and my wife appears to be able to access her email from her phone and Microsoft Outlook, so everything there appears to be running as expected.

Today, I stopped all the running services, and attempted to manually start CitServer. Immediately I noticed a message that read: "citserver[18676]: configuration setting c_port_number is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 504"

I don't recall doing anything that would change this setting, and for the life of me, I can't seem to find an answer to where I can easily check this configuration. I did run netstat -plnt and nothing is listening on Port 504

ubuntu@ip-172-31-44-206:/var/lib/citadel/data$ sudo netstat -plnt

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name

tcp        0      0 0.0.0.0:993             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:995             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      1060/mysqld

tcp        0      0 0.0.0.0:587             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:110             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:143             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:465             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:563             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1024/sshd

tcp        0      0 0.0.0.0:119             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      18751/citserver

tcp6       0      0 :::80                   :::*                    LISTEN      1662/apache2

tcp6       0      0 :::22                   :::*                    LISTEN      1024/sshd

 
 
 
Any information on how to correct this, would be greatly appreciated.
 
Thank You.


[#] Fri Sep 14 2018 08:35:24 EDT from Clay @ Uncensored

Subject: Re: This program was unable to connect or stay connected to the Citadel se

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

Looks like I was finally able to find my own solution. While using the search feature, here in the support forum, I found someone mention the command: /usr/lib/citadel-server/setup

I ran that setup, which brought me to a prompt to set the TCP port for Citadel. For some reason it was set to 0. I changed it to 504, and started webcit back up, and everything appears to be running as expected. The web interface is once again working.

Fri Sep 14 2018 00:02:44 EDT from Clay @ Uncensored Subject: This program was unable to connect or stay connected to the Citadel se

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

After hours of Googling, and reading the articles on the main Citadel site, I seem to be running into a brick wall. I am managing an email server for my wife's photography business. Everything had been working fine, until I attempted to log into the web interface, and I was met with that error. 

From what I have been able to gather, this points to the inability of WebCit to communicate with CitServer.

I can access and log into Citadel from SSH, and my wife appears to be able to access her email from her phone and Microsoft Outlook, so everything there appears to be running as expected.

Today, I stopped all the running services, and attempted to manually start CitServer. Immediately I noticed a message that read: "citserver[18676]: configuration setting c_port_number is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 504"

I don't recall doing anything that would change this setting, and for the life of me, I can't seem to find an answer to where I can easily check this configuration. I did run netstat -plnt and nothing is listening on Port 504

ubuntu@ip-172-31-44-206:/var/lib/citadel/data$ sudo netstat -plnt

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name

tcp        0      0 0.0.0.0:993             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:995             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      1060/mysqld

tcp        0      0 0.0.0.0:587             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:110             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:143             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:465             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:563             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1024/sshd

tcp        0      0 0.0.0.0:119             0.0.0.0:*               LISTEN      18751/citserver

tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      18751/citserver

tcp6       0      0 :::80                   :::*                    LISTEN      1662/apache2

tcp6       0      0 :::22                   :::*                    LISTEN      1024/sshd

 
 
 
Any information on how to correct this, would be greatly appreciated.
 
Thank You.


 



[#] Mon Sep 17 2018 17:19:52 EDT from userT @ Uncensored

Subject: Connectors to email clients

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

Are there plans to support again connectors allowing Citadel to be used with email clients such as Outlook and Thunderbird?

Or are those more of third-party projects?



[#] Mon Sep 17 2018 17:27:05 EDT from userT @ Uncensored

Subject: Re: XMPP server

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

 

Tue Sep 11 2018 22:42:41 EDT from IGnatius T Foobar @ Uncensored Subject: Re: XMPP server
Actually it would be a mapping of IRC protocol to the existing Citadel internals.
Just like XMPP users can exchange messages with Citadel native clients, IRC would be added to that mix too.

I'm getting interested in trying this out, that is of course, if contributions or even contribution attempts are accepted by the project...
I'm taking that IRC would be preferred over XMPP after all.

Already began to read RFCs regarding IRC protocol, and took a look at the current XMPP server module, just for a start...
Uff... really lots of information!

If it was not bothering, may I ask for a bit of advise as for where to begin and how to warm up?

Thanks



[#] Tue Sep 18 2018 09:28:51 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: XMPP server

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

I'm getting interested in trying this out, that is of course, if
contributions or even contribution attempts are accepted by the
project...
I'm taking that IRC would be preferred over XMPP after all.

Of course. The project is open to participation by anyone who's interested.
I'll add you to the Citadel Development room for further discussion.

And as you might expect, we're a meritocracy; if anyone feels offended by a lack of social justice in the project, shut the fuck up and go make me a sandwich.

[#] Tue Sep 18 2018 15:05:15 EDT from "tony" <tony@instaview.com> to Citadel Support <room_Citadel_Support@citadel.org>

Subject: Re: [Citadel Support]

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

now that is a CoC i can get behind.


On 09/18/2018 09:29 AM, Citadel Support wrote:
------------------------------------------------------------------------------
From: IGnatius T Foobar <ajc@citadel.org>
Subject: Re: XMPP server

I'm getting interested in trying this out, that is of course, if
contributions or even contribution attempts are accepted by the
project...
I'm taking that IRC would be preferred over XMPP after all.

Of course. The project is open to participation by anyone who's interested.
I'll add you to the Citadel Development room for further discussion.

And as you might expect, we're a meritocracy; if anyone feels offended by
a lack of social justice in the project, shut the fuck up and go make me a
sandwich.
------------------------------------------------------------------------------
You are subscribed to the 'Citadel Support' list.
To post to the list: room_citadel_support@citadel.org

[#] Tue Sep 18 2018 18:52:13 EDT from userT @ Uncensored

Subject: Re: XMPP server

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

@ano:
If I may ask, what XMPP client(s) were you trying?

I just did a quick test with latest Citadel and latest Pidgin client in order to try recreating this issue:
http://uncensored.citadel.org/readfwd?go=Citadel%20Support?start_reading_at=4338089#4338089
and succeeded.

For some reason I'm feeling your issue is related...

Anyway, I'll try reading again the XMPP RFCs, just in case...



[#] Wed Sep 19 2018 10:32:46 EDT from winzlo @ Uncensored

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

Unless I missed something, Citadel already supports POP3/IMAP and CalDAV for use with any e-mail client such as Outlook. If you are looking for something as plug-and-play as choosing "Exchange Server", I'm afraid you're in the wrong camp for that one. :)

[#] Wed Sep 19 2018 13:14:09 EDT from userT @ Uncensored

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

Yes, I'm realizing that was perhaps a dumb question...
Although I meant the lightning and synckolab connectors for Thunderbird for calendar and address book usage, connectors that are already long abandoned...



[#] Thu Sep 20 2018 16:02:58 EDT from scott @ Uncensored

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

Quick inquiry:

 

Can a catchall account (*@domain.tld) be setup as an alias for a user account to receive all mail not for a specific user in the domain?

 

As it appears to function, all mail addresses to an invalid user is rejected automatically, but I would like to capture them into a catchall account.



[#] Mon Sep 24 2018 22:07:02 EDT from IGnatius T Foobar @ Uncensored

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

Although I meant the lightning and synckolab connectors for
Thunderbird for calendar and address book usage, connectors that are
already long abandoned...

It's pretty clear that we can't count on anything Kolab-related anymore.
There was a lot of (ahem) collaboration between projects at one time, but that eventually went off the rails.

WebCit currently only supports DAV load/save of your entire calendar, which works but is a bit clumsy. Fear not, however: webcit-ng will support CalDAV.
Even in its current state I already have it working with Thunderbird+Lightning (very very frightening). CardDAV is on the roadmap too. Since webcit-ng is fundamentally a REST/DAV platform, implementation of CalDAV and CardDAV features is a lot easier than retro-hacking it into classic WebCit would have been.

[#] Mon Sep 24 2018 22:07:53 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: XMPP server

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

If I may ask, what XMPP client(s) were you trying?

Good question. While developing the server I mostly tested with Pidgin, so if ano is testing with something else that will be an interesting thing to find out.

[#] Mon Sep 24 2018 22:08:31 EDT from IGnatius T Foobar @ Uncensored

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

Can a catchall account (*@domain.tld) be setup as an alias for a user
account to receive all mail not for a specific user in the domain?

Citadel does not support catchall accounts.

[#] Tue Sep 25 2018 10:52:02 EDT from userT @ Uncensored

Subject: Re: XMPP server

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

 

Mon Sep 24 2018 22:07:53 EDT from IGnatius T Foobar @ Uncensored Subject: Re: XMPP server
If I may ask, what XMPP client(s) were you trying?

Good question. While developing the server I mostly tested with Pidgin, so if ano is testing with something else that will be an interesting thing to find out.

I left some notes in the Development room regarding Pidgin and the XMPP server; I'm still trying to analyze whenever I can.
Don't know if you have had chance to check them as well...



[#] Tue Sep 25 2018 11:30:44 EDT from userT @ Uncensored

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

 

Mon Sep 24 2018 22:07:02 EDT from IGnatius T Foobar @ Uncensored
Although I meant the lightning and synckolab connectors for
Thunderbird for calendar and address book usage, connectors that are
already long abandoned...

It's pretty clear that we can't count on anything Kolab-related anymore.
There was a lot of (ahem) collaboration between projects at one time, but that eventually went off the rails.

WebCit currently only supports DAV load/save of your entire calendar, which works but is a bit clumsy. Fear not, however: webcit-ng will support CalDAV.
Even in its current state I already have it working with Thunderbird+Lightning (very very frightening). CardDAV is on the roadmap too. Since webcit-ng is fundamentally a REST/DAV platform, implementation of CalDAV and CardDAV features is a lot easier than retro-hacking it into classic WebCit would have been.

So synckolab is dead for good...

So if I understand correctly, Webcit-ng is working with CalDAV on Thunderbird in some "beta" tests with the Lightning addon -even if *very* outdated already-.
But, wouldn't CardDav need an addon or the like as well to work with the address books?
And, if I may ask, why is it being currently very "frightening"?

Do you think there could be plans to support MS Outlook client as well?
Though actually the very few times I use a client is Thunderbird as well, but just in case...

And, well, if I'm deviating too much, think we could move further discussion to the Lobby or Development rooms as well?
Just like the chat module, I'm interested in this new Webcit as well

Thanks



[#] Tue Sep 25 2018 11:32:16 EDT from userT @ Uncensored

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

Ouch, and sorry for the many questions, I think I got slightly excited...



[#] Tue Sep 25 2018 11:33:36 EDT from userT @ Uncensored

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

NO!! I meant News room above, not Lobby!

Heck, I need to relax and rest for a while...



[#] Tue Sep 25 2018 11:36:02 EDT from winzlo @ Uncensored

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

The only way I can see to accomplish the catch-all is to use a hosting service such as GoDaddy to host your e-mail domain traffic, and set up aliases to direct your custom mail in those domains to the FQDN of your Citadel user's e-mail address, using the Catch-all option from within GoDaddy's control panel.
It's not free, so that's one negative behind that.
Having Citadel's SMTP rejection functions first check for a catch-all setting and alternate account would seem possible on its face, but under the hood, I imagine a ton of issues, especially around the message headers that [could] need to be revised [significantly] in order to allow for replies to go back out from said catch-all user.

FWIW, the suggestion I made above is how I handle my e-mail traffic, and it has been working well.

Go to page: First ... 5 6 7 8 [9] 10 11 12 13 ... Last