This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

In a broader sense, many such form fields in the webclient require input confirmation by pressing Enter, including those that initially use a "display filter", like the one able to search listed calendars vs. searching the server-side for all possible options. The exception to the rule seems to be auto-complete.

eimap is going the way of the dodo, but I'll comply with your request for at least a license.

Folders should generally not have a trailing space, so this should be fixed at the input / form level.

It seems to me this doesn't have the highest of priorities.

I fail to understand how this is not the expected result. When an input field is selected (presumably the keyboard pops up?), then the cursor is supposed to stick to that input field despite any scrolling, no? The cursor only disappears when a click event happens outside the input field?

I've disabled registration.

In the web client, what does Settings > ActiveSync show, and/or what does it show for the "device" or "application" listed?

This fundamentally flawed version of a build system has needed to be patched again, but this crap should now be resolved.

We have no standard definition for "slow", and you're not telling us anything about the system symptoms. High CPU load? High I/O? Memory consumption? Entropy?

What modifications exist against pykolab?

Wallace on CentOS 7 for kolab 16 uses systemd, not sysvinit, so I don't understand what I'm being told here.

Sending invitations uses the same routines as composing a new email message and sending that. As far as we're aware, compose+send under GSSAPI works, bearing in mind Postfix will of course need to be configured for it.

Please update roundcubemail-plugins-kolab.

Your problems shouldn't have occurred if you choose "Internet configuration" for postfix.

This isn't a Kolab bug, nor a bug in the master branch of kolab-plugins that provides kolab_2fa, that closely follows the roundcube upstream master branch.

Destroyed.

Could it be the user has not yet logged in to webmail before attempting to use ActiveSync? Should be resolved in the latest round of updates.

Was, at any point, some calendar imported?

In T5148#72927, @machniak wrote:

This has been fixed in 5834133fadb9e. Not yet packaged.

Either remove the content from the files, or remove the module from the configured list of modules.

The aspell-fi and aspell-pl dependencies have been dropped from kolab-webclient.

It seems the signatures are valid:

This isn't going to be a discussion about whichever level people may think they require for checksummed payload obtained over a secure channel, but should instead revolve around how something like the OBS starts failing to sign packages/repositories, and seemingly for APT repositories only.

The better solution may be to try/except the import of pdb, preserving the existing functionality while avoiding this error.

I'm not understanding what the difference is between;

Compatibility with other clients basically requires (read: "has required"?) file names for attachments are ascii-encoded and do not contain spaces. I think there's even an RFC on client-compatible naming conventions for naming attachments, but I'm failing to recall the number (maybe 2138?).

There's very little chance of Kolab being built on our end, for these architectures.

Copenhagen is, in principle, available. The reason for this ticket to exist has largely been obsoleted. This ticket, and its sub-tickets, can therefore be closed.

Copenhagen is, in principle, available. The reason for the parent ticket to exist has largely been obsoleted. This sub-ticket, and its sub-tickets, can therefore be closed.

Copenhagen is, in principle, available. The reason for the parent ticket to exist has largely been obsoleted. This sub-ticket, and its sub-tickets, can therefore be closed.

Copenhagen is, in principle, available. The reason for the parent ticket to exist has largely been obsoleted. This sub-ticket, and its sub-tickets, can therefore be closed.

Copenhagen is, in principle, available. The reason for the parent ticket to exist has largely been obsoleted. This sub-ticket, and its sub-tickets, can therefore be closed.

Copenhagen is, in principle, available. The reason for the parent ticket to exist has largely been obsoleted. This sub-ticket, and its sub-tickets, can therefore be closed.

Copenhagen is, in principle, available. The reason for the parent ticket to exist has largely been obsoleted. This sub-ticket, and its sub-tickets, can therefore be closed.

Copenhagen is, in principle, available. The reason for the parent ticket to exist has largely been obsoleted. This sub-ticket, and its sub-tickets, can therefore be closed.

Copenhagen is, in principle, available. The reason for the parent ticket to exist has largely been obsoleted. This sub-ticket, and its sub-tickets, can therefore be closed.

As the 750+ packages are now rebuilding, I'm going to declare this issue as resolved. Please reopen / create a new ticket should some discrepancies persist.

Now that we have the GPG key thing in the OBS sorted, perhaps it is time to rebuild all of Kolab:16 indeed, and refresh what is referred to as community.asc.

So, that got poked in the face... Happy bug-hunting!

I don't remember where to do this in a way that fixes it permanently, so I've hot-fixed it.

@machniak; since we can reproduce this on webmail.kolabsys.com, I can verify there's no discernible error in the console.