summaryrefslogtreecommitdiffstats
path: root/framework/src/domain/mime/mimetreeparser
Commit message (Collapse)AuthorAge
* More metadata testingChristian Mollekopf2018-07-03
|
* Removed unusedChristian Mollekopf2018-07-03
|
* Fixed and tested isGoodSignatureChristian Mollekopf2018-07-03
|
* The tests passChristian Mollekopf2018-06-29
|
* Partial fix for multipart/mixed in alternative partChristian Mollekopf2018-06-29
| | | | We only render the first part right now, which is not correct.
* Fixed apple html messages with attachments.Christian Mollekopf2018-06-29
|
* Windows is why we can't have nice things..Christian Mollekopf2018-05-08
|
* Use a Gpgpme::Gpgpme style exported targetChristian Mollekopf2018-05-08
|
* Make use of interface include directories and link libraries.Christian Mollekopf2018-05-08
| | | | | | | | Instead of manually specifying the libraries to link against and the include directories to include we'd much rather have a single target to link against. find_package already defines the Gpgme target for some reason, which seems like a waste, but with the lowercase gpgme target we can work around that problem.
* A slightly simpler FindGpgme.cmakeChristian Mollekopf2018-05-07
|
* CleanupChristian Mollekopf2018-05-07
|
* Extract attachments from multipart/relatedChristian Mollekopf2018-05-07
| | | | | So we can offer them for download even if displayed inline. This is necessary for some attachments to show up from apple mail.
* Insert spacesChristian Mollekopf2018-05-07
|
* Separate multipart/related formatterChristian Mollekopf2018-05-07
|
* Made structure available in debug viewChristian Mollekopf2018-05-07
|
* Port to gpgme only.Christian Mollekopf2018-05-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | QGpgme and Gpgmepp are not readily available, the cmake files buggy, the buildsystem horrendous and generally just difficult to build on windows. Given that all they are is a wrapper around gpgme, we're better of without all the indirections. What we loose is: * QGpgme moved the work to separate threads (but we then blocked anyways), something that we can just do in our own code should we want to. * QGpgme has a function to prettify dn's that was used to show the signer. Also something we could bring back should we need to (don't know where it is useful atm.) Ported messagepart to gpgme Almost there Moved the crypto bits to a separate file All gpg code is in one place. All tests passing Use error codes Cleanup
* Windows compatChristian Mollekopf2018-05-02
|
* No need to install a shared library if we only use it internally.Christian Mollekopf2018-05-02
| | | | | And that keeps us from having to export stuff from the library for windows to work.
* windows compatChristian Mollekopf2018-05-02
|
* No need to find those again.Christian Mollekopf2018-05-02
|
* That's not how you write gpgmeppChristian Mollekopf2018-04-27
|
* Link explicitly against gpgmeppChristian Mollekopf2018-04-27
|
* Remove showOnlyOneMimepart from the public interface.Christian Mollekopf2018-04-26
| | | | That makes it much more obvious where we actually rely on it.
* 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
|
* 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.
* CleanupChristian Mollekopf2018-03-23
|
* 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
|
* 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
|
* 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
|
* Removed unused argumentChristian Mollekopf2018-02-20
|
* Fixed inline signedChristian Mollekopf2018-02-14
|
* Remvoed unused codeChristian Mollekopf2018-01-25
|
* Removed unused codeChristian Mollekopf2018-01-25
|
* Stop using useless abstractions (that are not even threadsafe)Christian Mollekopf2017-12-11
|
* Removed unreachable codepathsChristian Mollekopf2017-12-10
|
* CleanupChristian Mollekopf2017-12-07
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-23 04:05:02 +0000