Language:
switch to room list switch to menu My folders
Go to page: First ... 70 71 72 73 [74] 75 76 77 78 ... Last
[#] Thu Dec 03 2015 02:41:38 EST from dothebart @ Uncensored

Subject: Re: What's the scoop on Citadel 9.01?

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

debian.citadel.org hardware was swappped last fall, and switched from linux vserver to lxc.

I didn't have the time yet to get the build system back online :-(

9.01 contains markdown support, and a large internal refactoring of citserver.



[#] Thu Dec 03 2015 09:08:43 EST from "John Goerzen" <jgoerzen@complete.org> to citadel_support@citadel.org

Subject: Re: [Citadel Support] Re: What's the scoop on Citadel 9.01?

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

Hi,

I have been looking at the sources and noticing that the debian/
directory in git differs, sometimes significantly, from the debian/ in
Debian testing. I'm building some homegrown jessie packages for amd64
with a few fixes I could send your way if that would be helpful. I
noticed that Debian's webcit package isn't including the Markdown editor
code -- need to fix that yet.

John

On 12/03/2015 01:41 AM, dothebart wrote:

debian.citadel.org hardware was swappped last fall, and switched from
linux vserver to lxc.

I didn't have the time yet to get the build system back online :-(

9.01 contains markdown support, and a large internal refactoring of
citserver.

[#] Thu Dec 03 2015 09:32:09 EST from schaap23 @ Uncensored

Subject: W Context: Bad password specified for <user> Service <SMTPs-MTA> Po

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

Hi,

 

A couple of users can not send any email anymore. Email clients used are outlook and thunderbird. Both clients ask the user to input their login credentials again. When I check the syslog on the server running citadel I see the following log fragment:

Dec  3 15:16:57 berichthier citserver[3123]: New client socket 60
Dec  3 15:16:57 berichthier citserver[3123]: Session (SMTPs-MTA) started from xxxxxxx.com (ip address).
Dec  3 15:16:57 berichthier citserver[3123]: SSL/TLS using DHE-RSA-AES128-SHA on TLSv1/SSLv3 (128 of 128 bits)
Dec  3 15:16:57 berichthier citserver[3123]: SMTP server: EHLO [ip address]
Dec  3 15:16:57 berichthier citserver[3123]: SMTP server: AUTH PLAIN AGFyaWVubmUANjY0MURXMTU=
Dec  3 15:16:57 berichthier citserver[3123]: W Context: Bad password specified for <user> Service <SMTPs-MTA> Port <465> Remote <berichthier.nl / 77.174.186.94>
Dec  3 15:16:57 berichthier citserver[3123]: SMTP server: AUTH LOGIN
Dec  3 15:16:57 berichthier citserver[3123]: SMTP server: YXJpZW5uZQ==

According to citadel the password is actually incorrect. This is very strange to me since receiving mail (via imap) goes fine. So if receiving mail via imap is fine, then why is the same password denied for sending email?

I've already tried to change the user's password but this doesn't help.

Can anyone help me further troubleshoot this strange phenomenon?

 

kind regards,

schaap23



[#] Thu Dec 03 2015 15:58:40 EST from John Goerzen @ Uncensored

Subject: Citadel Display Name Question

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

I'm not sure if Webcit is broken or if I am.

In Webcit, you can go to Advanced -> Update your contact information and set a "display name".  Then when you go to Mail -> Write Mail, at the From line, you get to choose a display name.

So I set up an account on my test bbs with username jgoerzen.  I added a display name "John".  If I send a message and select "John" instead of "jgoerzen", then the message goes through, but it can't be replied to, from either webcit or textclient.  Both try to reply to John, and then complain that it's not a valid user on the system.  Viewing the headers in Webcit, though, shows the From: line as

From: "John" <jgoerzen@[hostname here]>

Which is correct.

In the text client, I can't find a way to either set or use the display name.

Strangely, in Webcit, I can also click on a display name in a room and it will try to look up the bio by that name instad of the username.  But the Who list always uses usernames.  I'm rather confused about what's used where.

Thanks!



[#] Thu Dec 03 2015 17:02:48 EST from dothebart @ Uncensored

Subject: Re: Citadel Display Name Question

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

please try thunderbird and ctrl+u to view source to find the real sender



[#] Thu Dec 03 2015 17:17:24 EST from "John Goerzen" <jgoerzen@complete.org> to citadel_support@citadel.org

Subject: Re: [Citadel Support] Re: Citadel Display Name Question

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

Pretty much the same (I've just redacted the hostname)

Return-Path: jgoerzen@redacted
Date: Thu, 03 Dec 2015 14:51:53 -0600
To: admin@redacted
Subject: test with journaling
Message-ID: <5660AB69-000000ED@redacted>
From: "John" <jgoerzen@redacted>
MIME-Version: 1.0
X-Mailer: WebCit 9.01

[#] Thu Dec 03 2015 18:03:56 EST from "John Goerzen" <jgoerzen@complete.org> to citadel_support@citadel.org

Subject: Bugs with journaling

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

Hi folks,

I turned on journaling on the system and it caused a segfault on just
about every email.

gdb showed the error here, in journaling.c:

CM_SetField(journal_msg, eMsgSubject, jmsg->subj,
strlen(jmsg->subj));

I suspect that many messages don't have a subject and I bet that's the
problem (since I'm using external editor).

Thanks,

John

[#] Fri Dec 04 2015 18:01:02 EST from schaap23 @ Uncensored

Subject: Easyinstall fails on compiling text client

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

 

Easyinstall fails when compiling the text mode client. I'm using Ubuntu 15.10 64bit. I installed all the prerequisites mentioned at http://citadel.org/doku.php/installation:easyinstall:prereq-debian.html.

 

Last part of log file:

./src/include/citadel_ipc.h:479:13: warning: inline function 'CtdlIPC_lock' declared but never defined
 INLINE void CtdlIPC_lock(CtdlIPC *ipc);
             ^
src/citadel_ipc.o: In function `CtdlIPCQuit':
/tmp/citadel-build.9725/textclient/src/citadel_ipc.c:267: undefined reference to `CtdlIPC_lock'
/tmp/citadel-build.9725/textclient/src/citadel_ipc.c:281: undefined reference to `CtdlIPC_unlock'
src/citadel_ipc.o: In function `CtdlIPCLogout':
/tmp/citadel-build.9725/textclient/src/citadel_ipc.c:295: undefined reference to `CtdlIPC_lock'
/tmp/citadel-build.9725/textclient/src/citadel_ipc.c:299: undefined reference to `CtdlIPC_unlock'
src/citadel_ipc.o: In function `CtdlIPCPartialRead':
/tmp/citadel-build.9725/textclient/src/citadel_ipc.c:2365: undefined reference to `CtdlIPC_lock'
/tmp/citadel-build.9725/textclient/src/citadel_ipc.c:2383: undefined reference to `CtdlIPC_unlock'
src/citadel_ipc.o: In function `CtdlIPCHighSpeedReadDownload':
/tmp/citadel-build.9725/textclient/src/citadel_ipc.c:2467: undefined reference to `CtdlIPC_lock'
/tmp/citadel-build.9725/textclient/src/citadel_ipc.c:2494: undefined reference to `CtdlIPC_unlock'
src/citadel_ipc.o: In function `CtdlIPCGenericCommand':
/tmp/citadel-build.9725/textclient/src/citadel_ipc.c:2611: undefined reference to `CtdlIPC_lock'
/tmp/citadel-build.9725/textclient/src/citadel_ipc.c:2717: undefined reference to `CtdlIPC_unlock'
collect2: error: ld returned 1 exit status
Makefile:102: recipe for target 'citadel' failed
make: *** [citadel] Error 1
Operating system: Linux Debian jessie/sid ( 4.2.0-19-generic x86_64)

 

I've attached the complete log file of the installation. Can someone help me troubleshoot this issue?



citadel-install-log.txt (text/plain, 35315 bytes) [View| Download]
[#] Fri Dec 04 2015 18:35:29 EST from sureshot @ Uncensored

Subject: something i need to know

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

Hello

 

I just need to know if and how citadel can be used to connect to a vax system

 

sureshot

 



[#] Sat Dec 05 2015 08:19:04 EST from dothebart @ Uncensored

Subject: Re: something i need to know

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

 

Fri Dec 04 2015 18:35:29 EST from sureshot @ Uncensored Subject: something i need to know

Hello

I just need to know if and how citadel can be used to connect to a vax system

sureshot

well, depends on the vax ;-)

If it can to TCP, telnet or ssh to the citadel client shell, or getty with serial line.

*bsd portability isn't enshured, since nobody wants to maintain a port on a durable basis.



[#] Mon Dec 07 2015 14:13:34 EST from jgoerzen @ Uncensored

Subject: Several Citadel Bug Reports

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

Hello,

In experimenting with Citadel, I've encountered a few bugs.  These are all with 9.01:

  • Security: In a system configured to require permission to send Internet mail, a user that is not granted that permission can configure a Sieve filter to send out mail to the Internet, regardless of whether the admin has granted Internet permission.
  • Security: In the textclient, pushing O to open an attachment will invoke the opencmd even if allow_attachments=0 in citadel.rc
  • Security: Passwords are validated case-insensitive with built-in auth
  • Webcit: Saving the system configuration always resets the Citadel port (504) to 0, and the Citadel UID to 0.  On next restart, the Citadel server will be running as root and webcit will not be able to connect to it due to the port changing.  Textclient does not have this issue.
  • Setup: Does not honor CITADEL_UID, winds up running the server as root in more situations than should.
  • Citadel: Replying to an email from someone using their display name will not work (invalid recipient)
  • Wiki: Does not save history, even if the room is not set to expire.

Hope this helps,

John

 



[#] Tue Dec 08 2015 18:37:56 EST from Zycorax @ Uncensored

Subject: Help setting up SSL for webcit and on IMAP/SMTP

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

Hello all,

I'd like to have instructions on how to apply CA-signed certificates to both webcit and citadel's mail server. I currently have a working but unsecured setup. I am not particularly familiar with the software and may have overlooked one of the options. I have also attempted in getting both to work by placing the certificates under /etc/ssl/webcit and /etc/ssl/citadel but that alone doesn't seem enough.

 

Looking forward to a solution,

   Zycorax Tokoroa



[#] Tue Dec 08 2015 23:07:43 EST from "John Goerzen" <jgoerzen@complete.org> to citadel_support@citadel.org

Subject: Re: [Citadel Support] Help setting up SSL for webcit and on IMAP/SMTP

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

Hi,

The instructions under "godaddy certificates" (even if you don't use
GoDaddy) on this page may help:

http://www.citadel.org/doku.php/faq:systemadmin:how_to_install_a_certificate_signed_by_a_recognized_certificate_authority?s[]=godaddy#godaddycertificates

On 12/08/2015 04:37 PM, Zycorax wrote:

Hello all,

I'd like to have instructions on how to apply CA-signed certificates
to both webcit and citadel's mail server. I currently have a working
but unsecured setup. I am not particularly familiar with the software
and may have overlooked one of the options. I have also attempted in
getting both to work by placing the certificates under /etc/ssl/webcit
and /etc/ssl/citadel but that alone doesn't seem enough.



Looking forward to a solution,

Zycorax Tokoroa

[#] Wed Dec 09 2015 08:31:18 EST from Zycorax @ Uncensored

Subject: Re: [Citadel Support] Help setting up SSL for webcit and on IMAP/SMTP

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

As per the paths specified in my original question I do have already tried that method and am aware of the existence of that page, which unfortunately doesn't lead to the expected result.



[#] Thu Dec 10 2015 11:10:16 EST from bangfoo @ Uncensored

Subject: Good day. I have a question...

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

Hi all,

I have been tasked with setting up a mail server for a company that is severely firewalled/blue-coated.

They are only allowing access to a mirrored centos repo structure, which does not allow access to the repo that has Citadel packages.

Is there any way to get around this limitation?

Do you have a tar ball or zip file of all the necessary packages for Citadel that I could download and transfer to my centos host?

 

Thanks!!

Mark

 



[#] Fri Dec 11 2015 05:43:35 EST from dothebart @ Uncensored

Subject: Re: Good day. I have a question...

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

the centos rpms are availabe via suse OBS. You can download them via http and install them manually.

or you demand access to the obs repositories.



[#] Sat Dec 12 2015 11:55:20 EST from nnnn20430 @ Uncensored

Subject: https

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

to admins of uncensored.citadel.org

you have some weird expired cert on https://uncensored.citadel.org which expires on 04/11/1906 for some reason

why not get a trusted cert that doesn't give a warning to everyone that visits the page using https://letsencrypt.org/

it's free!, you just install their python program on the server and just run the command including all domains you want and get a cert, and to renew just run it again.

example: $ letsencrypt certonly -d citadel.org,uncensored.citadel.org

and make link in your server to use certs at /etc/letsencrypt/live/citadel.org



[#] Sat Dec 12 2015 14:50:01 EST from "Robert J. Clay" <rjclay@gmail.com> to citadel_support@citadel.org

Subject: Errors: "pthread_create() : Cannot allocate memory" ?

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

All,

  Anyone have a idea what might be causing periodic errors like following on a Debian v8 Linux Container system:

-----<cut>---------------------------------
Broadcast message from systemd-journald@mailus (Sat 2015-12-12 09:02:11 EST):

citserver[9951]: pthread_create() : Cannot allocate memory


Message from syslogd@mailus at Dec 12 09:02:11 ...
 citserver[9951]: pthread_create() : Cannot allocate memory
-----<cut>---------------------------------

  This is with Debian package version  08.24-1-b3 on an amd64 system (which was apparently rebuilt with  libical >= 1.0-1.2).




--
Robert J. Clay
rjclay@gmail.com


[#] Sun Dec 13 2015 16:32:41 EST from platonov @ Uncensored

Subject: Webcit SSL access with Apache HTTP server running

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

I just read a post about trusted cert that doesn't give a warning to everyone that visits the page using https://letsencrypt.org/ here.

The question I have is after I configured the letsencrypt for Apache server and I can access the site via https address, and, since I also want to use the https to webcit, then what do I do to make sure the https access to that domain is served by the webcit and not by Apache?

One alternative seems to be to change the webcit port for https access to something other than 443.

How do I do that?

Another one is to disable the Apache serving the https requests, so that when domain is accessed as secure site, it is automatically served by the webcit, and not apache. In that case, how do I configure the letsencrypt certificates that work for that domain to work with webcit instead?

Thanx in advance.



[#] Sun Dec 13 2015 16:50:15 EST from "nnnn20430" <nnnn20430@mindcraft.si.eu.org> to citadel_support@citadel.org

Subject: Re: [Citadel Support] Webcit SSL access with Apache HTTP server running

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

i my self use nginx and have a special subdomain for webcit to be
citadel.domain and then i simply reverse proxy that subdomain to local
webcit
you can run that webcit on plain http doesn't matter cause it's local, i
have it running with ssl on port 2443... but you can use any other port
and don't need ssl...

i don't use letsencrypts auto configuration option, just use the
certonly option it places all certs in standard location, the main
domain will be the first domain specified in the cli and certs will be
placed in /etc/letsencrypt/live/domain/

then just create link in your servers config to
/etc/letsencrypt/live/domain/ and use that

so just do $ letsencrypt certonly -d mydomain,citadel.mydomain
or something like that and configure your server to reverse proxy it to
webcit when $host is ^citadel.*

On 12/13/2015 10:32 PM, platonov wrote:

I just read a post about trusted cert that doesn't give a warning to
everyone that visits the page using https://letsencrypt.org/ here.

The question I have is after I configured the letsencrypt for Apache
server and I can access the site via https address, and, since I also
want to use the https to webcit, then what do I do to make sure the
https access to that domain is served by the webcit and not by Apache?

One alternative seems to be to change the webcit port for https access
to something other than 443.

How do I do that?

Another one is to disable the Apache serving the https requests, so
that when domain is accessed as secure site, it is automatically
served by the webcit, and not apache. In that case, how do I configure
the letsencrypt certificates that work for that domain to work with
webcit instead?

Thanx in advance.

Go to page: First ... 70 71 72 73 [74] 75 76 77 78 ... Last