Fup Duck
Fup Duck
Ok, I'll try.
I have some working code now, but there is one big difference in behaviour of which I'm not sure if you're OK with: As an interceptor, mail-gpg must work on...
Alright, so I'll clean up the interceptor-code. Regarding the other topics: * Since [2012-01-24](https://github.com/mikel/mail/commit/74568ad9098b6c1007cb3623173c92a538851ca5), `deliver!` calls interceptors (released in mail v2.4.2) * I would opt to register the Interceptor on...
@ge-fa I think the ball is on my side. It's only that my pressing problem with this has vanished and I can't find the time to do this nonetheless. It's...
One option could be to store the verification-result with every header and mime-part, I think. E.g. by monkey-patching the corresponding classes and adding methods like `was_signed?`, `was_encrypted?`, `signature`, etc.
In the line you reference, `k` is the fingerprint(s) from the imported key-material you provided. If that lookup results in an empty set, [GpgmeHelper#17](https://github.com/jkraemer/mail-gpg/blob/cbe381f9d982ce92bee960a5b4dc423be2addcee/lib/mail/gpg/gpgme_helper.rb#L17) raises an exception. To me that...
As far as I understand, the code of GpgmeHelper doesn't work as you described, because ```ruby [] || 'something' => [] ``` But the code actually does behave similar to...
This appears to have stalled? Isn't there anyone interested in the new features and fluent enough in C to implement them?
Hey @dansketcher, thank you for your reply! I'm mostly interested in the functions to create and manipulate keys. * `gpgme_op_createkey` * `gpgme_op_createsubkey` * `gpgme_op_adduid` * `gpgme_op_set_uid_flag` * `gpgme_op_keysign` Right now...