[Kde-pim] delete chiasmus support in kdepim

[Sandro Knauß]

Hey,

> If it is not too much hassle (and it should not be), I would like to
> generally like keep supporting this. This is a feature that can be an
> argument for Institutional users in Germany to use KMail / Kleopatra
> because it supports this. I'm not arguing that Chiasmus is a good thing but
> it is a requirement for some users which might be forced to Windows / more
> proprietary Software if there are no Free Tools supporting this.

Than please provide some testmails for kmail. I need something to test against 
otherwise I can't touch the whole Chiasmus handling in objecttreeparser and 
that would result in very ugly code and properly broken code. That's why I 
don't want to keep code, that is untestable for most people.

To be able to keep Chiasmus I need valid signed/encrypted mails with a woking 
Kleo::CryptoBackendFactory::instance()->protocol("Chiasmus") [see 
ObjectTreePaser::decryptChiasmus]. For tests it would be enough, that it is a 
fake chiasmus that behaves like the real one in terms of the jobs/porperties.

> At least in Kleopatra the support should be kept. It's not that much code
> and doesn't complicate the code much as the Architecture is built on
> "Multiple crypto backends" anyway.

Kleopatra is not in my focus (at the moment).

Regards,

sandro

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20151006/4b04f4cd/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/