This happens only if GPGME_DEBUG is set to 9 which was accidentally set in my environment. So I've lowered the priority.

It's not super good but now when S/MIME is disabled we also look into the body of S/MIME mails to check for the PGP Inline message marker.

Up to rEe0aecec6d040: Remove AC_CONFIG_COMMANDS for gpg-error-config., now it supports dependency of modules and multiple modules.
A single shell script can be same content (but only names differ).
It only supports features used by our *-config command, though. (Not support --static yet, for example)

I've tried again with different Versions to rerproduce this issue and I can't reproduce it.

I did not find any differences regarding junk mail. So I believe that this is fixed with T3459

This is done now. Didn't help with crashes but is a good thing anyway IMO.

This is done now.
I had a slight hope that this might help with random crashes as the COM is now under less load but it did not help.

This was fixed by adding a new reference mechanism with cebe6484acaa250858affa3d854ef2b25cecd59f (Where I acidentally mangled the commit message.

According to RFC 3628 there are two additional conditions to consider:

A timestamp or a time mark (which is an audit record kept in a secure
audit trail from a trusted third party) applied to a digital
signature value proves that the digital signature was created before
the date included in the time-stamp or time mark.

There is no way for us to fix. It is a shell issue.

We won't fix that. If you want to build for Apple iOS make sure to use

The “this” is used so that we don't have too many strings to translate.
I added a call to print_further_info which will in --verbose mode explain it.

@elonsatoshi: Were you able to check this with 2.2.9 which has a fix for the resolver?

We won't do that. Those with badly encoded user ids should create new keys or meanwhile have done so. The whole charset back and forth encoding adds a lot of complexity for some legacy applications. Frankly I would like to get rid of all code conversions and stick to utf-8.

In T3464 is is described how you can do it. Sure, in your case you want to have a home directory so that the agent and pinentry can work. --no-keyring makes sure that a decryption with a private key can't happen. How we have the cache for symmetric encrypted data which you can disable with --no-symkey-cache.

I'm sorry but the explanation you give does not address the original issue I described, and which dkg then clarified. The discussion about AE is tangentially related, but the issue I described relates to the gpg interface:

--verify-files is mostly useful for scripting and and not for manual checking. With scripting etc you always need to use --status-fd and with that you get:

To use encryption and for both purposes: encryption and authentication.

I was already implementing a --no-homedir when I figured that we have --no-keyring. Using that with any homedir fulfills the requested purpose.

Hooray!

We are actually in the final release preparation and just waiting for GnuPG 2.2.10. If everything goes well it will be released this week. If not, next week.

Sweet, thank you! Any estimate on when that might come out?

yes

excellent - will this be includedin gpg4win 3.1.3?

Thanks. I can work with that. It is indeed clearly visible what the "Sent on behalf of" address is. So it makes sense to check that, too.

Sent two messages to the test mailinglist. Please let me know if you need / want more.

Will be in 2.2.10

Thank you!

Will be in 2.2.10

Yes that would work for me and the pgp key is the right one. Thanks!

In gniibe/pkg-config-support branch of libgpg-error, I put my attempt to the improvement.
Now, gpg-error-config is a shell script which uses gpg-error.pc.
This way, we can avoid to introduce more of our local incompatible change against pkg-config, keeping pkg-config style easier.
Now, we have incompatible things: --mt and --host, I'd like to encourage to switch to new compatible use of --variable=mtlibs, --variable=mtcflags, and --variable=host.

Actually, I can add you to a test mailinglist and send you a signed message tomorrow, would that work?