Citadel Support

Thanks for the reply.  Unfortunately, I'm still stumped.

I edit the first page in a wiki room - nominate a link name and post - but then am unable to create the page i want to link to.  Obviously something I don't understand - shall let it sit and think about it for a while.

Rgds

Just noticed that the wheezy repository for Citadel downloads needs configuration to allow use with apt-get etc.  (compare with the squeeze directory).  It is lacking "main" and the "binary-i386" subdirectories.

hth

fixed, thanks for reporting.

Victory is mine.  Largely fixed by the upgrade to 8.11.

When you create a Wiki room, it starts by saying there is no home page and would you like to create one. 

• You create the page.
• Highlight what you want to link.  
• Enter the desire page name in the URL link.
• Select "show in same window" for the target.
• Post message.

When you click the link, it will say there is no page of that name and would you like to create one.

Violas!!  We have a string section.

Rgds

Next mission ...

Working out how to express the date in normal mode.

ie  dd/mm/yy

:)

Tue May 15 2012 14:24:00 EDT from chuckf @ Uncensored Subject: Problem/possible bug? - Latest Citadel on Ubuntu 10.10 64-bit

I have a customer running citadel as their MTA.  They communicate on a regular basis with FedEx.  After applying the recent release via 'apt-get dist-upgrade' they have been having trouble getting email to fedex.

FedEx has 3 MX servers listed and the first, by design, always fails with 'Connection Refused'.  Each of the MX entries is mapped to multiple IP addresses rather than them having each and every IP listed as a separate MX.

For some reason the latest citadel will not go to the next MX in the list.  My workaround was to hardcode a fake entry into the local bind server to remap the first MX addresses to the secondary MX addresses.  I'm not really sure why this broke if it is because fedex.com's DNS is misconfigured (my guess) or if something is failing.  It seems as though once the 'Connection Refused' happens, citadel throws the message away without any error bounces and never tries the next MX.

 

Can anyone please advise?

 

Best,

Chuck

fixed; please upgrade. Thanks for reporting.

Wed May 23 2012 08:07:13 EDT from dothebart @ Uncensored Subject: Re: Problem/possible bug? - Latest Citadel on Ubuntu 10.10 64-bit

 

Tue May 15 2012 14:24:00 EDT from chuckf @ Uncensored Subject: Problem/possible bug? - Latest Citadel on Ubuntu 10.10 64-bit

I have a customer running citadel as their MTA.  They communicate on a regular basis with FedEx.  After applying the recent release via 'apt-get dist-upgrade' they have been having trouble getting email to fedex.

FedEx has 3 MX servers listed and the first, by design, always fails with 'Connection Refused'.  Each of the MX entries is mapped to multiple IP addresses rather than them having each and every IP listed as a separate MX.

For some reason the latest citadel will not go to the next MX in the list.  My workaround was to hardcode a fake entry into the local bind server to remap the first MX addresses to the secondary MX addresses.  I'm not really sure why this broke if it is because fedex.com's DNS is misconfigured (my guess) or if something is failing.  It seems as though once the 'Connection Refused' happens, citadel throws the message away without any error bounces and never tries the next MX.

 

Can anyone please advise?

 

Best,

Chuck

fixed; please upgrade. Thanks for reporting.

Thanks for such a quick response.

Best,

Chuck

Hi, I´d like to know if someone has translated webcit and citadel into spanish?

Thanks.

Thu May 24 2012 11:09:58 EDT from mac @ Uncensored Subject: Spanish translation

Hi, I´d like to know if someone has translated webcit and citadel into spanish?

Thanks.

 

the current state of the spanish translation:

https://translations.launchpad.net/citadel/trunk/+lang/es

75%

be welcome to revalidate the first 75% and add the missing 25 % ;-)

Wed Feb 22 2012 17:14:10 EST from "K. Grishnak" <henne.gwath@gmx.de> to
room_Citadel_Support@uncensored.citadel.org:
Hi,

Is there a way to block brute-force attacks on a citadel-server? I think
it does not log the ip-addresses of hosts who try to connect, so it
seems difficult with iptables/fail2ban. Acually I run citadel version
8.04, maybe this feature yet was realized in the newest version.
Someone does know?

Kind regards,
Henning

since 8.10:

        CON_syslog(LOG_WARNING, "Bad password specified for <%s> Service <%s> Port <%ld> Remote <%s / %s>\n",
               CCC->curr_user,
               CCC->ServiceName,
               CCC->tcp_port,
               CCC->cs_host,
               CCC->cs_addr);


//citserver[5610]: Bad password specified for <willi> Service <citadel-TCP> Remote <PotzBlitz / >
in case of smtp the address should be there.

smtp:

    syslog((LOG_MAIL | LOG_INFO),
        "%ld: from=<%s>, nrcpts=%d, relay=%s [%s], stat=%s",
        msgnum,
        sSMTP->from,
        sSMTP->number_of_recipients,
        CC->cs_host,
        CC->cs_addr,
        result
    );
where result can be

        if (msgnum > 0L) {
            sprintf(result, "250 Message accepted.\r\n");
        }
        else {
            sprintf(result, "550 Internal delivery error\r\n");
        }

    if (scan_errors > 0) {    /* We don't want this message! */

        if (msg->cm_fields['0'] == NULL) {
            msg->cm_fields['0'] = strdup("Message rejected by filter");
        }

        sprintf(result, "550 %s\r\n", msg->cm_fields['0']);

here could alternatively to 'Message rejected by filter' be the error message of the spam facility.

    }

so
stat=550

should be your trigger here.

since 8.10:

CON_syslog(LOG_WARNING, "Bad password specified for <%s> Service <%s>
Port <%ld> Remote <%s / %s>\n",
CCC->curr_user,
CCC->ServiceName,
CCC->tcp_port,
CCC->cs_host,
CCC->cs_addr);


//citserver[5610]: Bad password specified for <willi> Service <citadel-TCP>
Remote <PotzBlitz / >
in case of smtp the address should be there.

when you have some working rules, would you like to write a littel howto citadel <-> fail2ban?

when you have some working rules, would you like to write a littel howto citadel
<-> fail2ban?

I guess webcit didn't fill in the ip here already...

citadel-tcp is port 504.

Hey guys,

Any idea why my freshly-installed-from-debs Citadel server would work fine under firefox but "Not found" is displayed under Chrome?

Thanks

are you installing with an apache/nginx proxy?

Hello everybody

i have a few issues when i try to make an apt-get upgrade

insserv: Starting webcit depends on nxsensor and therefore on system facility `$all' which can not be true!

insserv: Starting citadel depends on nxsensor and therefore on system facility `$all' which can not be true!

insserv: Starting webcit depends on nxsensor and therefore on system facility `$all' which can not be true!
insserv: Starting citadel depends on nxsensor and therefore on system facility `$all' which can not be true!

i also noticed that webcit doesn't start automacly after a server reboot, i have to make an

/etc/init.d/webcit start

i used the easyinstall , and i allready tried to reinstall

thank you for you help :-)