Skip to content

fix(imp): move pgp-compose-attach-pubkey into compose-options-encrypt… #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ralflang merged 1 commit into from
Aug 5, 2026
Merged

fix(imp): move pgp-compose-attach-pubkey into compose-options-encrypt… #104

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 4 additions & 7 deletions locale/en/help.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,13 +150,6 @@
</tip>
</entry>

<entry id="pgp-compose-attach-pubkey">
<title>PGP: Preferences: Attach Public Key</title>
<para>
If selected then a copy of your PGP public key, if it exists, will be attached to the outgoing message. You can set the default behavior via the PGP Preferences screen.
</para>
</entry>

<entry id="pgp-option-reply-pubkey">
<title>PGP: Preferences: Validate PGP Public Keys When Replying</title>
<para>
Expand Down Expand Up @@ -190,6 +183,10 @@
<para>
This option will first digitally sign your message and then will encrypt the resulting output with a passphrase. See the &quot;PGP Encrypt Message with passphrase&quot; and &quot;PGP Sign Message&quot; entries for further information.
</para>
<heading>Attach Public Key</heading>
<para>
If selected then a copy of your PGP public key, if it exists, will be attached to the outgoing message. You can set the default behavior via the PGP Preferences screen.
</para>
<heading>S/MIME Encrypt Message</heading>
<para>
This option will encrypt the current message, using S/MIME and the recipient's certificate, and then send it. You MUST have the certificate of the recipient stored in your addressbook or else this option will fail. If you have the certificate for the recipient in your addressbook and are still receiving errors, verify that the e-mail address in the recipient field matches the e-mail address where the certificate is stored. The encrypted data will be attached to the outgoing message.
Expand Down
Loading