Failed to retrieve user's DN: [0] Success

I have not been able to figure out this error.  I am using the latest  
kolab server and the latest cvs version (just updated).  But I still  
get the error "Failed to retrieve user's DN: [0] Success" when using  
kronolith. That same error also shows up in place of the left menu  
which doesn't show up at all (except for white space where it is  
suppose to be and that error).  I have not been able to find any  
documentation anywhere on what could be causing this problem.  It  
seems that none of the other kolab users have the issue since I can't  
find any help on it.  Does anyone have any ideas?  I'm at my wits end!

Thanks!
Alan

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Failed to retrieve user's DN: [0] Success

I have not been able to figure out this error.  I am using the latest  
kolab server and the latest cvs version (just updated).  But I still  
get the error "Failed to retrieve user's DN: [0] Success" when using  
kronolith. That same error also shows up in place of the left menu  
which doesn't show up at all (except for white space where it is  
suppose to be and that error).  I have not been able to find any  
documentation anywhere on what could be causing this problem.  It  
seems that none of the other kolab users have the issue since I can't  
find any help on it.  Does anyone have any ideas?  I'm at my wits end!

Thanks!
Alan

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: amavis logs

* Andrew J. Kopciuch <akopciuch <at> bddf.ca> [20060422 09:50]:
> It appears that when virus / spam scanning is enabled, the amavis logs are not 
> being rotated.

This is a known problem and already corrected in CVS, so it will be
fixed in the next release.

In the meantime you can change in
/kolab/etc/kolab/templates/amavisd.conf.template
the line
 $LOGFILE = "$MYHOME/amavis.log";
to
 $LOGFILE = "$MYHOME/amavisd.log";

and run kolabconf.

Thomas

--

-- 
Email: thomas <at> intevation.de
http://intevation.de/~thomas/

Re: Vacation AND mail forwarding together and not XOR

* Jakob Boos <jakob.boos <at> freenet.de> [20060420 20:00]:
> I'm wondering why it isn't possible to set a vacation message and to forward
> incoming mail to a defined mail address. All of my users are working with
> Outlook or Squirrelmail. Nobody works with KDE/Kontact. During vacation, the
> policy is, that a vacation message is set and that incoming mail is
> forwarded to another person. Kolab's policy is not to allow both vacation
> and mail forwarding.
> 
> To solve this problem, I installed the avelsieve plugin for Squirrelmail.
> But that's not a good solution, because I'd like to have all admin functions
> in one interface, hopefully the Kolab admin interface.
> 
> Could anyone explain to me why the Kolab admin interface lacks this
> functionality.

Because the current implementation is simple, but stupid.

You're right, this should work. I think there's already an open
issue for this, but nobody found time to implement it.

Thomas

--

-- 
Email: thomas <at> intevation.de
http://intevation.de/~thomas/

Re: more on logs

* Andrew J. Kopciuch <akopciuch <at> bddf.ca> [20060423 09:40]:
> I seem to have another found another problem with the log rotations :
> 
> The imap cyr_db.log file is not being rotated.  I noticed 
> in /kolab/etc/rc.d/rc.imapd that there was a missing configuration :
> 
> imapd_cyr_db_complevel="9"

Yes, can you file a bug for this?

> I also noticed there was no configuration for the sieve.log.

Maybe true, too.

> The pop3d.log, and misc.log file were not being rotated either.  The order in 
> the rc file seems to be
> 
> pop3d
> cyr_db
> misc
> 
> Are the log rotations stopping at a problem with the pop3d log? And then not 
> continuing on?  The configurations for pop3d seem alright.  

pop3d.log is rotated correctly here, though not very often, since we
don't use it that often.

For misc.log I only have one rotation and no rotation for sieve.log,
but this is probably because they don't grow fast enough.

Kolab at LinuxTag

Hi all,

As last year, Kolab will be present at the LinuxTag.  This year it's held in 
Wiesbaden, Germany from May 3rd (tomorrow) to the 6th.  The Kolab Konsortium 
will be presen at the Intevation booth (Hall 9, booth 930).

See you there,

   Bernhard

_______________________________________________
Kolab-users mailing list
Kolab-users <at> kolab.org
https://kolab.org/mailman/listinfo/kolab-users

Re: more on logs

On Tuesday 02 May 2006 05:05, Thomas Arendsen Hein wrote:
> * Andrew J. Kopciuch <akopciuch <at> bddf.ca> [20060423 09:40]:
> > I seem to have another found another problem with the log rotations :
> >
> > The imap cyr_db.log file is not being rotated.  I noticed
> > in /kolab/etc/rc.d/rc.imapd that there was a missing configuration :
> >
> > imapd_cyr_db_complevel="9"
>
> Yes, can you file a bug for this?
>

Done.   Issue #1230.

> pop3d.log is rotated correctly here, though not very often, since we
> don't use it that often.
>

Ah ...  our clients typically do not either ... it was a quick glance note.  
Upon a closer look the logs are so small there is no need to rotate them.

Thanks for the advice,

Andy

Re: [Kolab-devel] amavis logs

On Tuesday 02 May 2006 04:58, Thomas Arendsen Hein wrote:
> * Andrew J. Kopciuch <akopciuch <at> bddf.ca> [20060422 09:50]:
> > It appears that when virus / spam scanning is enabled, the amavis logs
> > are not being rotated.
>
> This is a known problem and already corrected in CVS, so it will be
> fixed in the next release.
>

Awesome ... I couldn't find anything on the bug tracker about this.  So I 
figured I would ask first.

> In the meantime you can change in
> /kolab/etc/kolab/templates/amavisd.conf.template
> the line
>  $LOGFILE = "$MYHOME/amavis.log";
> to
>  $LOGFILE = "$MYHOME/amavisd.log";
>
> and run kolabconf.

So it should be amavisd.log, and not amavis.log.

I modified the rc.amavis, and the logs are being rotated now.  When I have 
time ... I'll modify them to go this route instead.

Thanks,

Andy

Re: Problem with Toltec and 2 Outlooks

Torsten Irländer schrieb:
> Am Mittwoch, 26. April 2006 15:33 schrieben Sie:
>   
>> Torsten Irländer schrieb:
>>     
>>> On Wednesday, 26. April 2006 13:20, Rene Marticke wrote:
>>>       
>>>> 2 Outlook 2003 with Toltec and same settings.
>>>> Now I fetch my mails with Outlook 1 and sync it with Toltec.
>>>> If I resync Outlook 2 sometimes a message is marked as not seen (but it
>>>> was seen with Outlook 1) ?!
>>>> Is this a know issue or can someone give me a hint how to fix this ?
>>>>         
>>> Hi,
>>> Yes there are some unresolved issues with "seen" flags an toltec. See
>>> https://intevation.de/roundup/kolab/issue939
>>>       
>> Do you know if there is a solution planed ?
>>     
>
> Hi, 
> As this is a known bug chances are good that this will be fixed, but I can  
> not say anything about when. Maybe you want to ask the creator of toltec 
> directly.
>
> Best, 
> Torsten 
>
>   
Hi,

Re: kolabd package available in Debian sid

Op maandag 10 april 2006 19:25, schreef Bernhard Reiter:
> > Some more: Horde should be really reliably integrated in kolab. No
> > frickling around to get it runnig! One click in a graphical install tool
> > and that's it!
>
> The estimation of many developers is that Horde is probably very hard to
> fix because of design problems. Fixing Horde or using different components
> will be a lot of work.

Bernhard,

is it possible for you to point out the problems that you see with respect to 
horde working together with kolab?  Looking at the bug reports in the horde 
bugdb (http://bugs.horde.org/ fill in 'kolab' in the summary field), there 
aren't too many issue's.  Especially not design issue's...

Or do you refer to
this:
http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde#Customisation_to_run_with_Kolab ??

--

-- 
Richard Bos
Without a home the journey is endless