@Elias96 bitte nicht das Architecture & Design Tag verwenden. Da bekommen einige Leute eine Email, die nichts mit unserem Projekt zu tun haben.

Richtig! Habe die Aufgabe mit der August Mail nicht lösen können.

Done.

That is fine with me. I don't expect anything more fancy in this case.

Actually a cancelled event has text-decoration:line-through on the title, but when the event's height takes only one time slot that title is not visible. I don't think we should display them "in white" as we do for pending/declined events, so I propose to just add opacity:0.6.

Duo has support for U2F, see https://guide.duo.com/u2f this would be an added bonus for incorporating Duo support in kolab_2fa. If this is out of the scope of kolab_2fa I would understand.

I'm sorry, but I'm not sure what feature it is, that is currently lacking, that a Duo backend would add.

I have a working plugin with Duo but I don't know enough to integrate it with kolab_2fa. The code is here: https://github.com/leonardomarino/duo_auth can someone point me in the right direction?

@vanmeeuwen, what's your take on this?

PS: I saw that you're the one managing the packages (kolab-plesk) for the Plesk extension, that's why I ended up here. However, if that's something Plesk has to deal with, please let me know.

I understand that and I don't expect you to support 3rd party repos. I asked if it would be possible to change the dependencies to support higher PHP versions on CentOS 7.3 instead of limiting to PHP 5.4 only.

Third party repositories like Remi's are not supported.

Actually, the sender is also hard coded in /usr/share/roundcubemail/plugins/kolab_delegation/kolab_delegation_engine.php :

Upstream ticket https://github.com/roundcube/roundcubemail/issues/4971 that shows the feature needs a proper design.

$headers['X-Sender'] = $from;
is actually hardcoded in
/usr/share/roundcubemail/program/steps/mail/sendmail.inc

sad to repeat: no mapi => no kolab (no, active sync is unable to do the job)

Question: I am looking for a full featured replacement for Exchange. I have been following this task a bit and am wondering what the actual status is as the last update was in October. Maybe I should ask, what kind of money does it take to get it done!

This is already implemented. Enable zipdownload plugin and make sure php-zip is installed.

@mollekopf I'd be intrigued to hear your thoughts as to how Kube (using open protocols) will handle the somewhat proprietary elements that Kolab Server offers, if at all they will be included in Kube.

I apologize for merging this task in to a later task, but that's where another number of subscribers already were via T224 and other such ongoing conversations.

got new Version here

We sifted through a lot of network dumps to verify the "wrong behaviour". The loadbalancer and all firewalls are sending the appropriate RST commands when a timeout is reached.

This issue is not about instability but inreliability of the base mechanism.

Having read through your response and analyzed the issue further, we still come back to the same conclusion. The instability that you refer to really seems to be caused by the way that your environment (assuming the load-balancer between your server and the client) is breaking connections in a non-standard way - mainly without sending a RST or FIN off to the client. The only way for the software to know, if a connection is still alive or not, is to ask the OS TCP stack, which in this case would not help, as the OS would still think that the connection is live. The failing connection would then come down to TCP/IP ttl or time outs.

What do you meen by "exact commands"?
One of those?

• "kolabd" is started during system boot
• "kolab sync" some times "kolab sync -d 9" some times "kolab sync -d 9 -l debug"
• "kolab sync --resync" some times "kolab sync --resync -d 9" some times "kolab sync --resync -d 9 -l debug"

would you like to change the status of this to some other Status than open? As far as I see now a kolab package for 2.5.9 exists right now.

What are the exact commands that you run?

Thank you for the hint with the "Empty" action. I did not know about that!

I agree some solution for cleaning old events could be useful. It could be also a command line utility for admins as they would likely want to keep the database size as small as possible.

The mechanism of "kolab sync" did not change an remains inreliable even with T1414 and the related commit D208.
Maybe the OPT_TIMEOUT on immediate LDAP connect mentioned there will go away with the new (not yet provided) version of pykolab but that will not make the process itself enterprise like reliable

OTRS: 1100113

This is already available at beta.kolabnow.com. Continued progress on this belongs in the hands of the Kolab Now ops team, and improvements in guam itself on the guam board.

1. print each task list seperately

You mean print all but grouped by folder, or print only tasks from one list (e.g. using fish-eye selection)?

3. Indentation

How many levels do you use? I feel some users might not like it. Either we display all indentation levels or none.

4. On-screen order

Works for me.

5. Page size

What exactly do you mean? I suppose it should be cutted, but maybe not inside a task record.

Thanks Alek, that hint is useful.
I might try to create a new dialog using the ideas from the mail compose screen.

The field has autocompletion feature implemented. So, should give you search results while typing. I know some people prefer addressbook widget, that's why we have it in mail compose screen.

see a screenshot of the dialogs in Horde:

Can you please elaborated why REJECT does not make sense?
There is a use when reservation requests to meeting room should be allowed to particular users only. VIP car is allowed to certain users to be reserved is yet another case I can think of.
Please share all the logic behind resource reservation then.

As discussed with Jeroen REJECT does not make much sense for resources. So, I don't see anything in the code that would need to be fixed now. Consider updating documentation to be more precise.

Again, the resources module is a different module from the invitation policy. I read this ticket as concerning the invitation policy. I'm not sure how the resources module got in to the mix.

As I understand setting kolabinvitationpolisy: ALL_REJECT for resources does not work as for users, i.e. does not respond with Declined status.

The resources module is a different one from the invitation policy module. This ticket concerns the invitation policy module.

In addition it is not clear what ALL_MANUAL policy means for resources. There is nobody behind the resource, so nobody can manually react to the reservation request. Even more, resource is calendar, so it has no mail type folder to deliver request.

at least, intense tests where at pykolab 0.7.27 we are currently testing pykolab 0.7.28 but discover other porblems "TIMEOUT" as reported of someone else in T1414 first. We are analysing this and tend to add our findings and logs to T1414 before we preceede testing reliability of 0.7.28 in conjunction with T1307 (this).

Which version of pykolab is this relating to?

Kolab-way of storing resource properties is to use kolabDescAttribute in LDAP. This field is supposed to contain JSON object with resource properties. We could add there e.g. "physical_location: true" there and use it in Calendar. The calendar plugin already supports that.

There are other plugins too and there's an upstream ticket for this feature: https://github.com/roundcube/roundcubemail/issues/4971.

Customer is using a LDAP attribute for ressources, "LhmKolabResourceType = Raum". Value "Raum" is used for rooms.
If multiple ressources are selected, you have to filter for this attribute and display only them on the location field.
They don´t want to see other ressources there, for example beamers ...