They are used to partition the events into the right day of the week (like before)

Ported to gpgme

Output of the !analyze command from windbg

0:037> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

This has been integrated.

I collected the relevant patches (I hope): https://github.com/cmollekopf/lmdb/tree/0.9.22_sparsewin32

Register color in Kube.Colors
Follow attribute naming conventions

As long as we check gpgme error codes we should be fine:

Upon further inspection it seems like the "CBC/CFB Gadget Attack" can only be executed if an attacker intercepts a message, tampers it appropriately and then forwards it to the recipient.
In such a case the attacker can potentially retrieve the plaintext of that specific email. One potential risk could be that with enough content the private key could be guessed, which would of course be much more severe.
In any case, this is about targeted attacks only I think.

I don't have commit access (or so I believe), would you commit the changes? Thanks.

I thought about that as well but haven't come up with a good name so far. Kube Mail would be tempting right now of course, but limiting ourselves to mail is really not what we're aspiring to be, so not a great name in the long run I think. Kube is about communication, collaboration and organizing/structuring (traditionally called Personal Information Management and Groupware) and I have yet to find a catchy name for that. Ideas welcome =)

How about instead of a full rename a "tweak" of the current name? Maybe something along the lines of 'Kube Mail'? What do you think?

Yeah I've noticed that.

So the solution would be to ensure a .def file is generated (-Wl,--output-def,testdll.def)

https://github.com/Kitware/CMake/blob/master/Modules/Platform/GNUtoMS_lib.cmake

Fix nitpicks

See also https://bugreports.qt.io/browse/QTBUG-49224

Great work, I think we can merge this after the nitpicks are fixed.

• Add period filtering (with start and length properties)
• Rename EventTreeModel to PeriodDayEventModel (because it does the partitioning + filter according to a period)

• Fix copyright
• Switch to live query
• React to layoutChanged, rowsInserted / Moved / Removed, and modelReset signals from sink's model
• Remove debug manual synchronization of sink store
• Notify views with the modelReset signal
• Get data from the store instead of test data

• Update to the adding of the Event preprocessor in Sink (T8485)
• Set the resources correctly in the calendar view

In general we'll rather want a model that can display an unlimited number of days, not fixed 7.
The model should be configured with a date-filter, that we'd ideally forward to the sink query, but for now we'll just filter inside the model.
That date-filter will then define how many rows the model has.

Keyboard layout:

My current plan is:

• Implement all shortcuts in the View.qml file
• Add a ? shortcut that brings up a popup listing all available shortcuts
• connect the shortcut to actions either via Fabric or some other means.

Actions:

• Move to next/previous conversation
• Move to next/previous mail in conversation
• Scroll up/down in conversation view
• Move to next/previous folder
• "Action" on mail/conversation with Action:
  • Toggle as unread
  • Toggle important
  • Move to folder
  • Move to trash

We match on ": auto;" and hope that it is indeed a css property assignment.

It might be the margin-left = auto that is not supported: http://doc.qt.io/qt-5/richtext-html-subset.html#css-properties

Fixed using some platform specific code.

QT_MAC_DISABLE_FOREGROUND_APPLICATION_TRANSFORM is apparently the workaround to achieve this, but that of course does not work at all.

This has now been implemented and is available from develop. The mechanism consists of two parts:

We simplified this on purpose for UX reasons. Most people will be covered with what we currently have.
Our idea to support these fringe cases is to offer a "expert imap account" in the UI where people who know what they are doing can configure whatever their setup requires.

The extra cmake modules contain similar code to enable various sanitizers.