Kolab Development Repository

[Carpenter, Troy]

Well, I just did a "yum update" on that system and it updated tons of 
Roundcube packages along with some other Kolab ones.  I let cyrus-imapd 
upgrade to see what would happen this time and it seems to be working 
now.  I am able to see all the folders in Roundcube, as well as calendar 
and contacts, as expected.


On 2015-03-27 1:27 pm, Franz Skale wrote:
> Hi,
> I think 2.5git was default in 3.3 too.
> Since i upgrade several git release to get rid of the ptclient segfault
> issue, i, of cource, had to rebuild the sqatter index by issuing the
> command "/usr/lib/cyrus-imapd/squatter -s -i" as user cyrus.
> Had no problem with folders after that.
> But since the update, i wrote but no one answered yet, i cannot deliver
> mails to shared folders.
> This particular issue is connected to imap lmtpd not using the right
> cannonification when delivering to "shared+%s".
> For some reason, cyrus tries netnews naming but not the kolab default,
> which folder names consist of "/" naming.
> 
> Rgds.
> 
> Franz
> 
> 
> Am 26.03.15 um 21:26 schrieb Carpenter, Troy:
>> Since I'm on a roll in sending emails to the list today, I thought I'd
>> continue.
>> 
>> On my test system, I recently upgraded up to 3.4 in Centos 6, then
>> activated the development repositories right afterward.  The only
>> packages that updated were a number of Roundcube packages, and
>> cyrus-imapd from 2.4 to 2.5, which is what I kind of expected right
>> after 3.4 was released...that the development packages haven't moved
>> much beyond 3.4 yet.  Apart from switching to nightly builds, is using
>> the development repository the best way to stay closer to the edge
>> (with all the caveats that go with using development packages, of
>> course)?
>> 
>> I noticed that with cyrus-imap at 2.5, I didn't see all my folders in
>> Roundcube, but only saw the Inbox.  When I downgraded back to 2.4
>> (from the 3.4 repository), then all the folders reappeared.  Is there
>> a thread about that somewhere else?  Is there a config change I need
>> to make in order to upgrade, or is it a bug that hasn't been fixed 
>> yet?
>> 
>> Thanks.
>> 

-- 
Troy Carpenter
troy at carpenter dot cx