headers
Richard Bos | 1 Feb 2008 10:30
X-Face
Picon
Gravatar

Re: Kolab Server 2 and mailman

Op Thursday 31 January 2008 16:51:07 schreef Lorenzo Ortega:
>     I've installed kolab2.2 on a debian4. All runs perfectly with the
> domain.net. The problem starts when I try to integrate mailman 2.1.9
> with kolab (using
> http://wiki.kolab.org/index.php/Kolab2_Integration_with_mailman), with
> the domain lists.domain.net.
>     When i send a mail to a created list, for example,
> people <at> lists.domain.net,  Postfix not "re-send" the mail to the list
> componentes.

In the wiki list is used instead of lists, like you're doing.  Is this perhaps 
the discrepancy?

--

-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.
Permalink | Reply | 0 comments |
headers
Adam Katz | 2 Feb 2008 00:48

how do groups work?

Using kolab-webadmin, I can set permissions for a Shared Folder by
"UID/email/GID."  I'd like to set a folder to a group of users (GID),
but I can't seem to figure out what that means.  It's not a
distribution list ... how do I create a group of users for Kolab?

I'm not afraid of raw LDAP commands (though I'm certainly
unexperienced), but it would be nice if the webadmin panel did this.

(I'm using Debian Etch packages for kolab-webadmin 0.4.0-20060810-4
with kolabd 1.9.4-20060707.dfsg-2)
Permalink | Reply | 2 comments |
headers
Rene Ouderling | 3 Feb 2008 16:07
Picon
Favicon

Completely stuck with free/busy issue

Hi listmembers,

Could anyone please give me a push in the right direction. I have been busy 
for 5 days with googling, searching the archives, wiki documentation, tolltec 
and even konsec documentation but can't find the solution.
I am running a kolab 2.1 server on FC6 installed according the preferred 
method with openpkg. There are three clients. One Fedora8 with Kontact and 
two MS XP clients with Outlook2007 SP1 and licensed Toltec connectors (I 
bought five licenses). On the Fedora client everything runs fine, but on the 
MS clients everything works except the  free/busy information. In the apache 
log i see for the  XP clients the GET info and the HTTP code on the end of 
the line gives a 401 and that is an authorisation failure. It reads like 
this; 
"GET /freebusy/testuser <at> linxs.nl.ifb HTTP/1.1" 401 480 when i put the url; 
https://myserver <at> linxs.nl/freebusy/testuser <at> linxs.nl.ifb in a browser al the 
info is provided without a problem. 
Also the server certificate is  imported on the windows by copying it from the 
kolab server to a network drive and then installed it on the windows clients 
by double clicking.
--------
Rene Ouderling 
E-mail: m.ouderling <at> linxs.nl 
Web:    www.linxs.nl 
****************************************************************************************  
LinXS is ingeschreven in het HR onder nummer: 18061424 en gevestigd te Tilburg
Permalink | Reply | 0 comments |
headers
Alex Chejlyk | 3 Feb 2008 20:34

Kolab 2.2Beta3 Postfix not creating db's

I've attempted installing Kolab 2.2 Beta3 on a Debian 4.0 machine.
Everything seems to build properly, the kolab-install.log shows no 
errors or problems. I've downloaded the packages twice, and both times 
the same thing happens.

Users cannot send or receive mail.

On the first installation I created all the db files by running 
newaliases and postmap name. This allowed mail to leave the clients 
outbox, but it would never get delivered.

I now have a fresh install without any manual changes.

Below is the output of tail postfix.log

Feb 03 14:48:20 mail <info> postfix/postfix-script[23969]: starting the 
Postfix mail system
Feb 03 14:48:20 mail <info> postfix/master[23970]: daemon started -- 
version 2.4.6, configuration /kolab/etc/postfix
mail:~/klb2.2b3/ix86-debian4.0# tail /kolab/var/postfix/log/postfix.log
Feb 03 14:50:50 mail <info> postfix/master[23970]: reload configuration 
/kolab/etc/postfix
Feb 03 14:51:34 mail <critical> postfix/smtpd[24570]: fatal: open 
database /kolab/etc/postfix/aliases.db: No such file or directory
Feb 03 14:51:35 mail <warning> postfix/master[23970]: warning: process 
/kolab/libexec/postfix/smtpd pid 24570 exit status 1
Feb 03 14:51:35 mail <warning> postfix/master[23970]: warning: 
/kolab/libexec/postfix/smtpd: bad command startup -- throttling
Feb 03 14:52:35 mail <critical> postfix/smtpd[24575]: fatal: open 
database /kolab/etc/postfix/aliases.db: No such file or directory
(Continue reading)

Permalink | Reply | 0 comments |
headers
Volker Stoppe | 4 Feb 2008 12:19
Picon

Sending mails to distribution lists from external domains

Hallo together,

as far as I have read in the "Documentation for Administrators" it should  
be possible to send from an external domain a mail to a distribution list  
(Verteilerliste) in Kolab, as long as it is not hidden. Unfortunately it  
doesn´t work for me. Am I wrong with my assumption, or do I have to  
reconfigure something?
I wanted to see only logging of the kolab services to analyse this thing.  
With OpenSuSE and kolab from rpm-packages it seems to log to  
/var/log/messeges. How can I redirect it to a sperate file? I coulnd´t  
find anything in the wiki about configuring the loggin.

Greetinx

Volker

_______________________________________________
Kolab-users mailing list
Kolab-users <at> kolab.org
https://kolab.org/mailman/listinfo/kolab-users
Permalink | Reply | 6 comments |
headers
Rene Ouderling | 4 Feb 2008 14:34
Picon
Favicon

Re: Completely stuck with free/busy issue

Problem solved.

In the server back-end option services I enabled the unauthorised downloads of 
free/busy information and then it worked.

Regards 
--------
M.N.E. Ouderling 
E-mail: m.ouderling <at> linxs.nl 
Web:    www.linxs.nl 
****************************************************************************************  
LinXS is ingeschreven in het HR onder nummer: 18061424 en gevestigd te 
TilburgOp Sunday 03 February 2008 16:07:22 schreef Rene Ouderling:
> Hi listmembers,
>
> Could anyone please give me a push in the right direction. I have been busy
> for 5 days with googling, searching the archives, wiki documentation,
> tolltec and even konsec documentation but can't find the solution.
> I am running a kolab 2.1 server on FC6 installed according the preferred
> method with openpkg. There are three clients. One Fedora8 with Kontact and
> two MS XP clients with Outlook2007 SP1 and licensed Toltec connectors (I
> bought five licenses). On the Fedora client everything runs fine, but on
> the MS clients everything works except the  free/busy information. In the
> apache log i see for the  XP clients the GET info and the HTTP code on the
> end of the line gives a 401 and that is an authorisation failure. It reads
> like this;
> "GET /freebusy/testuser <at> linxs.nl.ifb HTTP/1.1" 401 480 when i put the url;
> https://myserver <at> linxs.nl/freebusy/testuser <at> linxs.nl.ifb in a browser al
> the info is provided without a problem.
> Also the server certificate is  imported on the windows by copying it from
(Continue reading)

Permalink | Reply | 0 comments |
headers
Vladislav Tchernev | 4 Feb 2008 23:35
Picon

URGENT: DBERROR: critical database situation

Hello,
I need an urgent assistance. What happend is that on a kolab server I
accidentally I overwrote /kolab/sbin/sendmail binary. I have recovered
it from a backup few minutes later but the imap on the server got
somehow corrupted. Right now the incoming mail is not being deliver
and I am getting this errors in my imapd.log log file:

Feb 04 17:25:40 mail02.broadsign.com <warning> imaps[15676]: DBERROR
PANIC: fatal region error detected; run recovery: PANIC: fatal region
error detected; run recovery
Feb 04 17:25:40 mail02.broadsign.com <critical> imaps[15676]: DBERROR:
critical database situation

I have stopped sendmail on the box since the mail is getting bounced
back and I have to fix the issue as soon as possible.

Any help will be highly appreciated
Thanks in advance

Vlad
Permalink | Reply | 0 comments |
headers
Vladislav Tchernev | 4 Feb 2008 23:54
Picon

DBERROR: critical database situation

Hello,
I need an urgent assistance. What happend is that on a kolab server I
accidentally I overwrote /kolab/sbin/sendmail binary. I have recovered it
from a backup few minutes later but the imap on the server got somehow
corrupted. Right now the incoming mail is not being deliver and I am getting
this errors in my imapd.log log file:

Feb 04 17:25:40 mail02.broadsign.com <warning> imaps[15676]: DBERROR PANIC:
fatal region error detected; run recovery: PANIC: fatal region error
detected; run recovery
Feb 04 17:25:40 mail02.broadsign.com <critical> imaps[15676]: DBERROR:
critical database situation

I have stopped sendmail on the box since the mail is getting bounced back and
I have to fix the issue as soon as possible.

Any help will be highly appreciated
Thanks in advance

Vlad
Permalink | Reply | 4 comments |
headers
Vladislav Tchernev | 5 Feb 2008 01:25
Picon

Re: DBERROR: critical database situation

Hi,
I have just fixed the problem. What was happening was that somehow I
ended up with a bunch of corrupted imap db-s, not even sure which
ones. I was trying to recover mailboxes.db and annotations.db from my
hourly backup but it wasn't helping. What I did in the end and which
fixed my setup was deleting annotations.db, db/, db.backup1,
db.backup2, deliver.db and tls_sessions.db, restore mailboxes.db from
backup and run /kolab/bin/ctl_cyrusdb -r.

Regards
Vlad

On Feb 4, 2008 5:54 PM, Vladislav Tchernev <vtchernev <at> gmail.com> wrote:
> Hello,
> I need an urgent assistance. What happend is that on a kolab server I
> accidentally I overwrote /kolab/sbin/sendmail binary. I have recovered it
> from a backup few minutes later but the imap on the server got somehow
> corrupted. Right now the incoming mail is not being deliver and I am getting
> this errors in my imapd.log log file:
>
> Feb 04 17:25:40 mail02.broadsign.com <warning> imaps[15676]: DBERROR PANIC:
> fatal region error detected; run recovery: PANIC: fatal region error
> detected; run recovery
> Feb 04 17:25:40 mail02.broadsign.com <critical> imaps[15676]: DBERROR:
> critical database situation
>
> I have stopped sendmail on the box since the mail is getting bounced back and
> I have to fix the issue as soon as possible.
>
>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Gunnar Wrobel | 5 Feb 2008 10:34
Picon
Gravatar

Re: DBERROR: critical database situation

"Vladislav Tchernev" <vtchernev <at> gmail.com> writes:

> Hi,
> I have just fixed the problem. What was happening was that somehow I
> ended up with a bunch of corrupted imap db-s, not even sure which
> ones. I was trying to recover mailboxes.db and annotations.db from my
> hourly backup but it wasn't helping. What I did in the end and which
> fixed my setup was deleting annotations.db, db/, db.backup1,

The problem with deleting your annotations.db is that you loose all
groupware folder information thus killing the groupware functionality
of the server. Depending on the client you are using this may or may
not create problems. Hopefully your users don't use the functionality
not too much.

> db.backup2, deliver.db and tls_sessions.db, restore mailboxes.db from
> backup and run /kolab/bin/ctl_cyrusdb -r.
>
> Regards
> Vlad
>
> On Feb 4, 2008 5:54 PM, Vladislav Tchernev <vtchernev <at> gmail.com> wrote:
>> Hello,
>> I need an urgent assistance. What happend is that on a kolab server I
>> accidentally I overwrote /kolab/sbin/sendmail binary. I have recovered it
>> from a backup few minutes later but the imap on the server got somehow
>> corrupted. Right now the incoming mail is not being deliver and I am getting
>> this errors in my imapd.log log file:
>>
>> Feb 04 17:25:40 mail02.broadsign.com <warning> imaps[15676]: DBERROR PANIC:
(Continue reading)

Permalink | Reply | 0 comments |

Gmane