summaryrefslogtreecommitdiffstats
path: root/framework/src/domain/mime
Commit message (Collapse)AuthorAge
* Removed empty formatterChristian Mollekopf2018-04-26
|
* Removed some more unnecessary includesChristian Mollekopf2018-04-26
|
* Another qgpgme dependency goneChristian Mollekopf2018-04-26
|
* Less gpgme in the interfacesChristian Mollekopf2018-04-26
|
* No more direct GpgMe usage in the interfaces.Christian Mollekopf2018-04-26
|
* Collect gpgme usagesChristian Mollekopf2018-04-26
|
* Starting to isolate our gpgme++ usage.Christian Mollekopf2018-04-25
| | | | So we can destroy it.
* Fixed the case where we have plaintext inside the encrypted part.Christian Mollekopf2018-04-25
| | | | This is triggered when we have encrypted+signed inline parts.
* CleanupChristian Mollekopf2018-04-25
|
* Deal with rfc822 header partsChristian Mollekopf2018-04-25
| | | | As inserted by autocrypt enabled clients.
* Match auto css propertiesChristian Mollekopf2018-04-05
|
* Make sure we don't end up with any CRLF'sChristian Mollekopf2018-03-23
|
* CleanupChristian Mollekopf2018-03-23
|
* Fixed buildChristian Mollekopf2018-03-09
|
* Automatic key import / export + Expected monadRémi Nicole2018-03-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: There are many things going on here (perhaps a bit much for a single patch): - When an attachment is of mime type "application/pgp-keys", a button is added to import the key to GPG - When sending a mail and crypto is enabled (encryption, signing or both), the public key of the first private key found is sent as an un-encrypted attachment (T6994) - The `mailcrypto.{h,cpp}` was, for the most part, rewritten - Introduction of the expected monad, inspired by what was proposed for C++ [here](https://isocpp.org/files/papers/n4015.pdf), but not at all a strict implementation of this specification. We may want to add some more features of this standard later. The rationale for some of the choices: - I found mailcrypto a bit hard to edit to add new features, and a great part was commented code to prepare for the support the SMIME crypto format, which would (in my current knowledge) not be used for sending emails. - One thing I found that may be missing in the code base was a standardized way of handling errors in C++ code. Since exceptions are disabled I think that the functional way is the way to go. After some research I found the Expected monad / tagged union / sum type, which seemed to suit the problem particularly well. In the long run, I hope we would move the entire code base to use `Expected` to indicate if a function might fail. Of course every choice made here is to be considered as a proposition for doing things / RFC, critics wholeheartedly accepted. Reviewers: cmollekopf Tags: #kube Maniphest Tasks: T6994, T8147, T6995 Differential Revision: https://phabricator.kde.org/D11158
* Support encrypted mails forwardingRémi Nicole2018-03-08
| | | | | | | | | | | | | | | | | | | | Summary: Some notes: - What we do is: if the mail is encrypted, decrypt it and copy its content into a new message (with plaintext, html and attachments, if any), and use this message as attachment for forwarding - The `isEncrypted` function from KMime doesn't seem to detect every kind of encrypted mails. AFAIK this structure is not detected: - `multipart/mixed` - `text/plain` - `application/pgp-encrypted` (attachement, named "ATT00001") - `application/octet-stream` (attachment named "encrypted.asc") Reviewers: cmollekopf Tags: PHID-PROJ-6npnfcmppynqynn7slmv Maniphest Tasks: T8112, T7024 Differential Revision: https://phabricator.kde.org/D10966
* Fixed build on macChristian Mollekopf2018-03-05
|
* Revert "Support encrypted mails forwarding"Christian Mollekopf2018-03-02
| | | | | | This reverts commit f28ec43dca5b2915deb69d54fb942ddf1303f48c. That was pushed by accident.
* Support encrypted mails forwardingChristian Mollekopf2018-03-02
| | | | | | | | | | | | | | | | | | | | Summary: Some notes: - What we do is: if the mail is encrypted, decrypt it and copy its content into a new message (with plaintext, html and attachments, if any), and use this message as attachment for forwarding - The `isEncrypted` function from KMime doesn't seem to detect every kind of encrypted mails. AFAIK this structure is not detected: - `multipart/mixed` - `text/plain` - `application/pgp-encrypted` (attachement, named "ATT00001") - `application/octet-stream` (attachment named "encrypted.asc") Reviewers: cmollekopf Tags: PHID-PROJ-6npnfcmppynqynn7slmv Maniphest Tasks: T8112, T7024 Differential Revision: https://phabricator.kde.org/D10966
* gpg error handling cleanupChristian Mollekopf2018-02-26
|
* Removed unused codeChristian Mollekopf2018-02-26
|
* CleanupChristian Mollekopf2018-02-26
|
* Using setContent instead of setBody will lead to a trailing newlineChristian Mollekopf2018-02-26
|
* T7024 fix: implement attachment-based forwardingRémi Nicole2018-02-21
| | | | | | | | | | | | | | | | Summary: Implement attachment-based forwarding. Some notes: - `loadAsDraft` was removed in favor of new enum `loadType` in QML, and callback based generic programming in C++ Reviewers: cmollekopf Tags: #kube Maniphest Tasks: T7024 Differential Revision: https://phabricator.kde.org/D10676
* This is really a boolean in disguiseChristian Mollekopf2018-02-20
|
* Avoid unnecessary member variablesChristian Mollekopf2018-02-20
|
* Fixed encrypted+signed messagesChristian Mollekopf2018-02-20
|
* Fixed warningChristian Mollekopf2018-02-20
|
* Add key id to encryption infoChristian Mollekopf2018-02-20
|
* Removed unused argumentChristian Mollekopf2018-02-20
|
* Fixed inline signedChristian Mollekopf2018-02-14
|
* Fixed warningsChristian Mollekopf2018-02-11
|
* Properly encode non-ascii content.Christian Mollekopf2018-01-31
|
* Remvoed unused codeChristian Mollekopf2018-01-25
|
* Removed unused codeChristian Mollekopf2018-01-25
|
* testdata readmeChristian Mollekopf2018-01-25
|
* Generate a message id for new messagesChristian Mollekopf2017-12-29
|
* Avoid duplicating the contentType header on replyChristian Mollekopf2017-12-22
|
* Html mails that don't adhere to the strict dtd are probably too complexChristian Mollekopf2017-12-13
|
* Avoid using the non-threadsafe QGpgMEChristian Mollekopf2017-12-12
|
* Stop using useless abstractions (that are not even threadsafe)Christian Mollekopf2017-12-11
|
* These heuristics would even match html content from kubeChristian Mollekopf2017-12-11
| | | | so not what want.
* Removed unreachable codepathsChristian Mollekopf2017-12-10
|
* Always guard async callbacksChristian Mollekopf2017-12-08
|
* CleanupChristian Mollekopf2017-12-07
|
* Removed inProgressChristian Mollekopf2017-12-07
|
* Simplified verifySignatureChristian Mollekopf2017-12-07
|
* Revamped security border coloring and popup messageChristian Mollekopf2017-12-07
|
* Simplified codeChristian Mollekopf2017-12-07
|
* Removed unnecessary indentation.Christian Mollekopf2017-12-06
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 14:04:07 +0000