Marek Marczykowski-Górecki

I see. Anyway IMO it would be good to pursue compliance to the specification. Or at least try to be compatible with other MUAs doing so.

One example of a MUA like this is mutt.

Don't require non-standard protected-header="v1" attribute

This indeed works, thanks! It would be helpful to add this info near custom gpg path setting, specifically that: - the setting is ignored by pEp - pEp needs to be disabled before account setup to use custom gpg path

custom gpg path ignored in some cases