Hi,
I've been searching through documentation trying to find how to use the Wiki - specifically how to add pages and internal links. Not finding anything, I KNOW I am missing something, so I throw myself on your mercy and ask:
- Is the wiki engine self contained, or do I need to install Dokuwiki?
- If it is self contained, how do you add pages and internal links?
- I'm using v 8.05 from the Debian Wheezy repository.
- When I denote a room as a wiki, I get the Rich Text editor which only allows external links.
Even showing me where to look would be helpful.
Rgds
Geoff.
Subject: Re: Wiki Documentation
It's as simple as it could possibly be, but we should make the instructions clearer.
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
Subject: Citadel Wheezy Repository - needs configuration
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
Subject: Re: Citadel Wheezy Repository - needs configuration
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
:)
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-bitI 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.
Subject: Re: Problem/possible bug? - Latest Citadel on Ubuntu 10.10 64-bit
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-bitI 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 translationHi, 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 % ;-)
Subject: block brute-force-attacks on citadel-server
Some time ago I asked if there were any way to block hosts which are
trying to connect too often in too short time to my server with wrong
creditentials. fail2ban offers a regex-based way to do this, but you
need to know the IP of the connecting host.
Citadel does not log those IPs I think. The only thing is, that it
throws out the IP on connecting like:
Client 0/4/8.05 () from x.x.x.x
Furthermore it shows messages, but without the host/IP as:
Valid User, bad password:
Bad password specified for <USER>
Invalid User:
error: 1 <Invalid recipient: USER>
Valid User:
<USER> logged in
Please add the hostname as something like "Bad password specified for
<USER> from x.x.x.x" to be able to use some kind of host-based banning
with iptables/fail2ban.
Henning
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
Subject: Re: block brute-force-attacks on citadel-server
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.
Subject: Re: block brute-force-attacks on citadel-server
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.
Subject: Re: [Citadel Support] Re: block brute-force-attacks on citadel-server
Am 25.05.2012 11:02, schrieb dothebart:
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.
Subject: Re: [Citadel Support] Re: block brute-force-attacks on citadel-server
when you have some working rules, would you like to write a littel howto citadel <-> fail2ban?
Subject: Re: [Citadel Support] Re: block brute-force-attacks on citadel-server
If you first explain me some more things I'll do it. If I try to login
with some existing username but wrong password I get
the new logline (citadel 8.11), but without content:
Context: Bad password specified for <USER> Service <citadel-UDS> Port
<0> Remote < / >
I think this is due to HTTPS/SSL. Can I get the IP anyway?
Henning
Am 25.05.2012 11:43, schrieb dothebart:
when you have some working rules, would you like to write a littel howto citadel
<-> fail2ban?
Subject: Re: [Citadel Support] Re: block brute-force-attacks on citadel-server
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