kolab.user | 6 May 02:08 2016

OSX iCal connection

Several months ago there was a thread
http://lists.kolab.org/pipermail/users/2015-October/020161.html with the same subject. Back in
4.3 time I had all working but neglected to write down required workarounds. Now, fresh in pristine
Kolab_16, after following secure HOWTO and mulity domains HOWTO, iOS devices have no problems
whatsoever however latest OSX is not working.

Instructions offered in https://kolabnow.com/clients/osx don't help.

If I use account type Automatic then in log file:

"PROPFIND /.well-known/carddav HTTP/1.1" 405 245
"PROPFIND / HTTP/1.1" 405 226
"PROPFIND /principals/ HTTP/1.1" 405 237

and "Unable to verify account name or password" error

If I use account type Manual and specify server address as mail.example.com/iRony the configuration
dialog completes, in log file I see 

"PROPFIND /iRony HTTP/1.1" 301 238
"PROPFIND /iRony/ HTTP/1.1" 401 291
user <at> example.com "PROPFIND /iRony/ HTTP/1.1" 207 637
user <at> example.com "OPTIONS /iRony/principals/kolab.user%40example.com/ HTTP/1.1" 200 -
user <at> example.com "PROPFIND /iRony/principals/kolab.user%40example.com/ HTTP/1.1" 207 1319
user <at> example.com "PROPFIND /iRony/addressbooks/kolab.user%40example.com/ HTTP/1.1" 207 3676
user <at> example.com "PROPFIND /.well-known/carddav HTTP/1.1" 405 245
user <at> example.com "PROPFIND / HTTP/1.1" 405 226
user <at> example.com "PROPFIND /principals/ HTTP/1.1" 405 237
user <at> example.com "PROPFIND /.well-known/carddav HTTP/1.1" 405 245

(Continue reading)

Gregor Adamczyk | 5 May 06:34 2016
Picon

guam crashes

Dear list members,

guam crashes often that seems be a fact.

Imap stops working and nobody can receive mails until a restart.

So my temporary solution is to modify:

vi /usr/lib/systemd/system/guam.service

and add:

[Service]
WatchdogSec=30min
Restart=always

Do somebody have a better ideal to deal with the GUAM instability?


-- Mit freundlichen Grüßen/With best regards Gregor Adamczyk
_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Stefan Froehlich | 4 May 14:37 2016
Picon

Timezone issue again

Kolab 3.4 on Debian 8:

I'm trying to enable auto accept to calendar events. When it is set to 
ACT_MANUAL the following happens:

Sending an invitation from a different calendar (office365) it appears 
in inbox. Opening in Roundcube and accepting produces correct values.

When it is set to ACT_ACCEPT, it is accepted but the time entry is 
totally wrong. I see following error in /var/log/apache2/error.log:

Critical: /usr/src/packages/BUILD/src/xcalconversions.h 1944: Failed to 
parse calendar!

Error: 0:  Not a valid olson timezone: E. Australia Standard Time

Error: /usr/src/packages/BUILD/src/objectvalidation.cpp 92: 
event.start() is not valid

MfG Stefan Fröhlich

42 ;-)
_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Gustav Spellauge | 3 May 13:44 2016

kolab and syncml

hello,

still evaluating kolab and a new question turned up:

does kolab-16(+) support a syncml interface? this would enable our 
mobile users to use their well known client.

tia, gustav
g.spellauge | 1 May 14:10 2016

Re: Wallace

to those, who might be interested

in /usr/lib/python2.7/site-packages/pykolab/xml/event.py

replacing (line 352-354) reading

         for attr in list(set(ical_event.singletons)):
             if ical_event.has_key(attr):
                 self.set_from_ical(attr.lower(), ical_event[attr])

by

         for attr in list(set(ical_event.singletons)):
             if ical_event.has_key(attr):
                 if isinstance(ical_event[attr], list):
                     ical_event[attr] = ical_event[attr][0];
                 self.set_from_ical(attr.lower(), ical_event[attr])

will fix this issue.

On 04/29/2016 02:30 PM, Timotheus Pokorra wrote:
> Hello,
>
> according to https://git.kolab.org/T1213, this has been fixed already,
> but has not arrived in Kolab Winterfell yet.
>
> Timotheus
>
> On 29 April 2016 at 14:14, Gustav Spellauge
> <Gustav.Spellauge <at> softing.com> wrote:
>> this is exactly what i am observing and i wonder if there is really no
>> solution.
>>
>>
>> On 11/13/2015 02:27 PM, Kuusela, Klaus wrote:
>>>
>>> Hello!
>>>
>>> I'm asking how to fix this wallace problem with resources. It seems that
>>> resource reservation doesn't work and wallace will redirect mail to
>>> postfix (and there's no rules for process this...and I will get of
>>> course undelivery report).
>>>
>>> It complains about 'year' attribute... where to fix this?
>>>
> _______________________________________________
> users mailing list
> users <at> lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users
Gregor Adamczyk | 28 Apr 15:44 2016
Picon

One address with more recipients

Dear list members,

can someone explain me how I can create on Kolab 16 an email address for more than one users.

The simplest way...

So if somebody sends an email to:
family <at> example.eu

the email should be reach every member:

g.name <at> example.eu
a.name <at> example.eu
e.name <at> example.eu
p.name <at> example.eu


I tested already the Kolab redistribution static group...
But without success..

Should be this also en possible and working solution:

Simply add family <at> example.eu as additional external address for every user?
Or cause this problems?

What is the official and best way?
-- -- Regards Gregor Adamczyk
_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Gustav Spellauge | 27 Apr 10:09 2016

resource object types

hello,

using ./kolab-webadmin -> settings resources, i created a new object 
type key = 'absence', name = 'Absence and modeled object classes and 
attributes according to the type 'car'. When i try to create a resource 
of this type, i am not able to give it a name because the input field 
labeled 'Name' is not editable.

has anybody got an idea what i could have missed?

tia
Gustav Spellauge | 26 Apr 09:11 2016

calendar does not work in kolab-16

hello,

i have trouble using my fresh installed kolab-16 instance.

environment: kolab-16 running on cenos-7

symptom: when i try to create a new meeting, only the tabs 'Summary', 
'Recurrence' and 'Resources' are displayed - in kolab-3.4 there are the 
additional tabs 'Participants' and 'Attachments'. moreover when i try to 
save a meeting, a warning box saying 'Failed to save changes.' is displayed.

searching the logs for warnings/errors, i only found

016-04-26 08:24:16,831 pykolab.conf WARNING Option ldap/auth_cache_uri 
does not exist in config file /etc/kolab/kolab.conf, pulling from defaults
2016-04-26 08:24:16,839 pykolab.conf WARNING Option does not exist in 
defaults.

in /var/logs/kolab/pykolab.log.

does anybody have a hint what might be wrong with my installation.

thanks in advance, gustav
G+M Dorn (Gregor Adamczyk | 25 Apr 10:30 2016
Picon

Re: Re: [SOLVED] Re: Manticore unable to create session for edit ODF documents

Manticore / Roundcubemail problems with editing ODF documents

Hello everyone, today i was testing kolab manticore after already edited:
/etc/manticore/local.env.js

Because of some problems with manticore configuration :

See:
https://lists.kolab.org/pipermail/users/2016-March/020550.html

now the editor opens, and I can already write and edit Text...

Another new problem:
Can't save, download document or invite an user.
On the right bottom corner I always see Loading...

Any ideas or suggestions?

Regards
Greg
Axel | 23 Apr 00:32 2016
Picon

New user login problems

Hi,

i experience login problems with new created users.
There's a thread on the german list with no further help and I already 
tried to debug and solve this problem as described in the 
troubleshooting guide and Google with no luck. Perhaps can anyone point 
me to the right direction...

System:

Centos 7 with these packages
389-ds-base.x86_64  1.3.4.0-29.el7_2   <at> updates
cyrus-imapd.x86_64  2.5-108.3.el7.kolab_3.4   <at> Kolab_3.4_Updates
kolab.noarch  3.1.9-3.4.el7.kolab_3.4   <at> Kolab_3.4_Updates
roundcubemail.noarch  1.1.4-4.11.el7.kolab_3.4   <at> Kolab_3.4_Updates

Situation:
Create an user in Kolab Webadmin and it doesn't matter whether I chose 
"Kolab User" or "Mail enabled Kolab user".

Login to Roundcube not possible according to the logs

===
/var/log/roundcubemail/userlogins

[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> Failed login for 
name.surname <at> domain.tld from 10.100.10.2(X-Real-IP: 
1.2.3.4,X-Forwarded-For: 1.2.3.4) in session 9eis8qgu8eokcsiaf2cjjfvbd7 
(error: 0)

===
/var/log/roundcubemail/imap

[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] S: * OK 
[CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE STARTTLS LOGINDISABLED] 
kolab.domain.tld Cyrus IMAP git2.5+0-Kolab-2.5-108.3.el7.kolab_3.4 
server ready
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] C: A0001 STARTTLS
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] S: A0001 OK Begin 
TLS negotiation now
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] C: A0002 
CAPABILITY
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] S: * CAPABILITY 
IMAP4rev1 LITERAL+ ID ENABLE ACL RIGHTS=kxten QUOTA MAILBOX-REFERRALS 
NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY 
CATENATE CONDSTORE ESEARCH SORT SORT=MODSEQ SORT=DISPLAY SORT=UID 
THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE 
ANNOTATE-EXPERIMENT-1 METADATA LIST-EXTENDED LIST-STATUS LIST-MYRIGHTS 
WITHIN QRESYNC SCAN XLIST XMOVE MOVE SPECIAL-USE CREATE-SPECIAL-USE 
URLAUTH URLAUTH=BINARY X-NETSCAPE AUTH=PLAIN AUTH=LOGIN SASL-IR 
COMPRESS=DEFLATE X-QUOTA=STORAGE X-QUOTA=MESSAGE 
X-QUOTA=X-ANNOTATION-STORAGE X-QUOTA=X-NUM-FOLDERS IDLE
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] S: A0002 OK 
Completed
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] C: A0003 ID 
("name" "Roundcube" "version" "1.1.4" "php" "5.4.16" "os" "Linux" 
"command" "/roundcubemail/?_task=login")
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] S: * ID ("name" 
"Cyrus IMAPD" "version" "git2.5+0-Kolab-2.5-108.3.el7.kolab_3.4 " 
"vendor" "Project Cyrus" "support-url" "http://www.cyrusimap.org" "os" 
"Linux" "os-version" "3.10.0-327.13.1.el7.x86_64" "environment" "Built 
w/Cyrus SASL 2.1.26; Running w/Cyrus SASL 2.1.26; Built w/OpenSSL 
1.0.1e-fips 11 Feb 2013; Running w/OpenSSL 1.0.1e-fips 11 Feb 2013; 
Built w/zlib 1.2.7; Running w/zlib 1.2.7; CMU Sieve 2.4; TCP Wrappers; 
NET-SNMP; mmap = shared; lock = fcntl; nonblock = fcntl; idle = idled")
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] S: A0003 OK 
Completed
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] C: A0004 
AUTHENTICATE PLAIN ****** [45]
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] S: A0004 OK 
[CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE ACL RIGHTS=kxten QUOTA 
MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN 
MULTIAPPEND BINARY CATENATE CONDSTORE ESEARCH SORT SORT=MODSEQ 
SORT=DISPLAY SORT=UID THREAD=ORDEREDSUBJECT THREAD=REFERENCES 
ANNOTATEMORE ANNOTATE-EXPERIMENT-1 METADATA LIST-EXTENDED LIST-STATUS 
LIST-MYRIGHTS WITHIN QRESYNC SCAN XLIST XMOVE MOVE SPECIAL-USE 
CREATE-SPECIAL-USE URLAUTH URLAUTH=BINARY X-NETSCAPE LOGINDISABLED 
COMPRESS=DEFLATE X-QUOTA=STORAGE X-QUOTA=MESSAGE 
X-QUOTA=X-ANNOTATION-STORAGE X-QUOTA=X-NUM-FOLDERS IDLE] Success (tls 
protection) 
SESSIONID=<kolab.domain.tld-23872-1461362875-1-4100288112662633837>
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] C: A0005 
NAMESPACE
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] S: * NAMESPACE 
(("" "/")) (("Other Users/" "/")) (("Shared Folders/" "/"))
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] S: A0005 OK 
Completed
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] C: A0006 LOGOUT
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] S: * BYE LOGOUT 
received
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> [DEAB] S: A0006 OK 
Completed

===
/var/log/roundcubemail/ldap

[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> C: Connect 
[localhost:389]
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> S: OK
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> C: Bind [dn: 
uid=kolab-service,ou=Special Users,dc=domain,dc=tld]
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> S: OK
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> C: Search base dn: 
[ou=People,dc=domain,dc=tld] scope [sub] with filter 
[(&(objectClass=kolabInetOrgPerson)(|(uid=name)(mail=name <at> domain.tld)(alias=name <at> domain.tld)))]
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> Using function 
ldap_search on scope sub ($ns_function is ldap_search)
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> C: (Without VLV) Setting 
a filter of 
(&(objectClass=kolabInetOrgPerson)(|(uid=name)(mail=name <at> domain.tld)(alias=name <at> domain.tld)))
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> Executing search with 
return attributes: array (
   0 => 'displayname',
   1 => 'mail',
   2 => 'alias',
   3 => 'nsroledn',
   4 => 'uid',
)
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> S: 1 record(s) found
[23-Apr-2016 00:07:55,000000 +0200]: <9eis8qgu> C: Close

Although the user seems to get a correct LDAP entry and a mailbox:

===
* ~# ldapsearch -D "uid=kolab-service,ou=Special Users,dc=domain,dc=tld" 
-w password -b "ou=People,dc=domain,dc=tld" uid=name

# extended LDIF
#
# LDAPv3
# base <dc=domain,dc=tld> with scope subtree
# filter: uid=name
# requesting: ALL
#

# name, People, domain.tld
dn: uid=name,ou=People,dc=domain,dc=tld
alias: j.name <at> domain.tld
alias: name <at> domain.tld
givenName: Name
kolabInvitationPolicy: ACT_MANUAL
loginShell: /usr/bin/zsh
mailQuota: 4194304
preferredLanguage: en_US
sn: Surname
cn: Name Surname
displayName: Surname, Name
gidNumber: 1002
homeDirectory: /home/name
mail: name.surname <at> domain.tld
uid: name
uidNumber: 1002
objectClass: inetorgperson
objectClass: kolabinetorgperson
objectClass: mailrecipient
objectClass: organizationalperson
objectClass: person
objectClass: posixaccount
objectClass: top
mailHost: localhost

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1

===
* ~# kolab lm "user/name.surname <at> domain.tld"
user/name.surname <at> domain.tld

* ~# kolab list-mailbox-metadata user/name.surname <at> domain.tld
Folder user/jana.tasch <at> xlrs.intern
   /shared/vendor/cmu/cyrus-imapd/partition          default
   /shared/vendor/cmu/cyrus-imapd/lastupdate         22-Apr-2016 23:15:50 
+0200
   /shared/vendor/cmu/cyrus-imapd/duplicatedeliver   false
   /shared/vendor/cmu/cyrus-imapd/pop3newuidl        true
   /shared/vendor/cmu/cyrus-imapd/size               0
   /shared/vendor/cmu/cyrus-imapd/sharedseen         false
   /shared/vendor/cmu/cyrus-imapd/uniqueid           
12345678-acc7-4ec7-b564-12345678

===
* cyrus <at> localhost ~# cyradm -u cyrus-admin localhost

lm user/name.surname <at> domain.tld
user/name.surname <at> domain.tld (\HasChildren)

lam user/name.surname <at> domain.tld
name.surname <at> domain.tld lrswipkxtecdan

What's the next step? Where should I look next?

THX

* 
https://docs.kolab.org/administrator-guide/verifying-the-installation.html
Georg Greve | 22 Apr 16:48 2016

Possible service degradation or disruption on Kolab Now and Kolab.org

[ See also
https://kolab-service-status.ghost.io/2016/04/22/possible-service-degradation-or-disruption-on-kolab-now-and-kolab-org/ ]

Dear Kolab.org Community,

As most of you know, we are not only providing the majority of development, 
resource and support for Kolab, we also offer it as a “Software as a Service” 
(SaaS) offering as “Kolab Now.” The beauty of this set-up is that people do not 
have to run their own servers, they can get Kolab as a service.  Also, it 
allows our users and customers to take advantage of extremely beneficial Swiss 
privacy laws.

As a secure, fully-featured enterprise collaboration provider, and the only 
one that is fully Open Source, as well as fully independent from the United 
States of America, we have many people place their confidence into our software 
and services.

Unfortunately this also seems to have put us on the radar as a potential 
victim of extortion by the criminal groups that have been holding to ransom 
other communication providers, banks, supermarkets and anyone else with 
substantial online services. Tuesday this week we received our ransom note, 
demanding we pay or face a large scale DDoS attack on all our services.

So our technical team has been scrambling to ensure we are as prepared as we 
can be for such a case before the attack begins, and we have put in place as 
many measures as possible while protecting and preserving the integrity and 
security of our infrastructure, services and the data of our customers.

But such situation always require setting priorities. And in this case we must 
prioritize the service to users of Kolab Now above all else, including some of 
our own internal systems, and also the Kolab.org community resources. In other 
words, you may find kolab.org, and its corresponding services, including 
git.kolab.org, unavailable while the attack is ongoing.

We will of course restore these services as quickly as possible, and still 
hope that it was an idle threat.

But we wanted to give you a heads up notice and ask for your patience and 
understanding. 

We have set up https://kolab-service-status.ghost.io for communication and 
updates and put up the background there https://kolab-service-status.ghost.io/2016/04/22/do-it-right-or-dont-do-it-at-all-part-iii/
while our own web sites may be impacted and we also suggest to keep an eye on 
https://twitter.com/kolabsupport as well as https://twitter.com/kolabops for 
those who are not afraid of strong language and technical lingo.

Best regards,

Your Kolab Team

--

-- 
Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG            Kolab Enterprise
Zürich, Switzerland            Collaborate in Confidence

e: greve <at> kolabsystems.com
t: +41 78 904 43 33
w: http://kolabsystems.com

pgp: B358917A Georg C. F. Greve
_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users

Gmane