> when mailing out to Thunderbird/Enigmail for example, 
> the signature cannot be verified.

Which other mailers were tested? Wondering if this is Evolution/Seahorse behaving weirdly or Enigmail.

I tried with evolution(-data-server) git master, basically 3.17.91 development release, and the DSA Elgamal PGP key generated by Seahorse works fine for signing in both evolution and Thunderbird 38.2.0 with Enigmail 1.8.2 extension.

For some odd reason the Enigmail doesn't offer me the Seahorse-generated DSA key to be selected, thus it cannot decrypt a message with its key, but the signature says it's a Good signature.

The messages had been received through IMAP in both application.

Either I'd close this in favour of the upcoming 3.18.0, or try with (at least) my versions of the Thunderbird.

The problem seems to be fixed upstream, but there is an interoperability-problem with seahorse and Enigmail regarding DSA encryption/decryption. 
If so this does not really have anything to do with Evolution, but it's either Enigmail's or seahorses's fault or both.

On my behalf I would prefer to leave the report open, because, it will take quite some time until Evolution 3.17.something or higher arrives in Debian-stable, except somebody ports the stretch-testing version of Evolution back to Jessie.

DSA, is an acronym for Digital-Signing-Algorithm, so the name says it already, it's for signing only, not for encrypting, you have to use ElGamal for that.

Thanks for the update. I noticed a little issue in seahorse, it didn't show me that DSA key, because I had another key for the same email address in gpg. When I deleted the older key the DSA key was shown. Maybe it's related, maybe not.

I can keep this opened in the Need-Info state, which means it'll be closed after ~3 months, though the reason to "keep this open due to Debian distribution" doesn't feel right, because this is Evolution upstream, while Debian is just one distribution providing the Evolution for its users. More appropriate place would be Debian's bugzilla, from my point of view.

Thanks a lot for your reply, I am always keen about having online-conversations, because so many people seem to be wanting to do this mostly read-only.

As mentioned before, DSA is for signing only.

Honestly I don't mind if the report about this issue stays open in Bugzilla or not. Because the first reply I received about this referred to some alpha development version, it would probably make sense to keep the needinfo status.

I have been referring to the Debian BTS, thats debbugs actually, not Bugzilla. The original report was posted there:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794231

> Package: debbugs                         
> State: not installed
> Version: 2.4.1.1
> Priority: optional
> Section: misc
> Maintainer: Debbugs developers <debian-debbugs@lists.debian.org>
> Architecture: all
> Uncompressed Size: 384 k
> Depends: perl5 | perl, exim | mail-transport-agent, libmailtools-perl, ed,
> libmime-perl, libio-stringy-perl Recommends: httpd, links | lynx
> Description: The bug tracking system based on the active Debian BTS
>  Debian has a bug tracking system which files details of bugs reported by users and
> developers. Each bug is given a number, and is kept on file until it is marked as
> having been dealt with. The system is mainly controlled by e-mail, but the bug reports
> can be viewed using the WWW. 
>  This version is fully functional, but it does not automatically configure.
> See /usr/share/doc/debbugs/README.Debian after installation. 
>  
>  Note: there might be various issues with this package, caveat emptor.
> 
> Tags: devel::bugtracker, suite::debian, works-with::bugs
> 


Cheers !

Okay, then I'm keeping this in the NeedInfo state.

Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!