1 |
\input texinfo |
\input texinfo |
2 |
|
|
3 |
@setfilename GPGOE.txt |
@setfilename GPGOE |
4 |
|
|
5 |
This file describes the GPGOE functions and the integration |
This file describes the GPGOE functions and the integration |
6 |
in the Outlook Express mailer. |
in the Outlook Express mailer. |
7 |
|
|
8 |
|
This file is free under the terms of the GNU General Public License v2. |
9 |
|
|
10 |
|
Copyright (C) 2006 Timo Schulz |
11 |
|
|
12 |
|
@settitle GPGOE - the GnuPG plug-in for Outlook Express |
13 |
|
|
14 |
@section Requirements for GPGOE |
@section Requirements for GPGOE |
15 |
|
|
16 |
First you need to have a working GnuPG installtion on the machine you |
First you need to have a working GnuPG installtion on the machine you |
69 |
was correct, the plugin will sign the message and store it in |
was correct, the plugin will sign the message and store it in |
70 |
the outbox. |
the outbox. |
71 |
|
|
72 |
|
@subsection Sign and Encrypt a message |
73 |
|
To sign and encrypt a message, you have to check both toolbar |
74 |
|
buttons ("Sign" and "Encrypt"). The procedure is the same as |
75 |
|
in encrypt-only when one or more email addresses couldn't be |
76 |
|
mapped. Then the default key is used to sign the plaintext |
77 |
|
before it is encrypted with the selected recipients. |
78 |
|
|
79 |
@subsection Decrypt and/or verify a message |
@subsection Decrypt and/or verify a message |
80 |
If you received an OpenPGP message, you can just double-click |
If you received an OpenPGP message, you can just double-click |
81 |
the message to open it. The plug-in will figure out if it is |
the message to open it. The plug-in will figure out if it is |
88 |
will figure out the message status and will take the needed steps. |
will figure out the message status and will take the needed steps. |
89 |
If the message is neither signed nor encrypted, no action is performed. |
If the message is neither signed nor encrypted, no action is performed. |
90 |
|
|
91 |
|
@subsection Reply to an encrypted message |
92 |
|
Newer versions of the plug-in provide a feature to decrypt the |
93 |
|
message before the text is used in the reply mail. As a result, |
94 |
|
the reply message will contain the plain text instead of the encrypted |
95 |
|
GPG armored message. |
96 |
|
This feature is automatically used whenever the user clicks on "Reply" |
97 |
|
or "Reply All" in the Outlook main window. But only in the case, the |
98 |
|
mail is actually encrypted. Optionally the plug-in will ask for a |
99 |
|
key passphrase. |
100 |
|
|
101 |
@section Additional information and limitations of the GPGOE plug-in |
@section Additional information and limitations of the GPGOE plug-in |
102 |
|
|
103 |
@itemize @bullet |
@itemize @bullet |
104 |
|
|
105 |
@item |
@item |
106 |
|
If you manually installed GPG and GPGoe, please make sure that |
107 |
|
you installed GPG at a standard place or create at least the gpgBinary |
108 |
|
registry entry. This is not needed if you use an automatic installer |
109 |
|
like GPG4WIN or GnuPT. |
110 |
|
|
111 |
|
@item |
112 |
Due to the fact the plug-in uses the clipboard for data transfer, |
Due to the fact the plug-in uses the clipboard for data transfer, |
113 |
the clipboard itself can be only of limited use to copy/paste messages |
the clipboard itself can be only of limited use to copy/paste messages |
114 |
into the mailer window or elsewhere. |
into the mailer window or elsewhere. Newer versions of the plug-in |
115 |
|
save the original clipboard text before encryption/signing and the |
116 |
|
ext is restored after the GPG operation ends. |
117 |
|
|
118 |
@item |
@item |
119 |
The current version of the plug-in will NOT encrypt any attachments |
The current version of the plug-in will NOT encrypt any attachments |
127 |
|
|
128 |
@item |
@item |
129 |
Even so the plug-in supports native line endings, which means you |
Even so the plug-in supports native line endings, which means you |
130 |
can properly exchange mails with Linux or MAC users, it is likely |
can properly exchange mails with Linux or Apple users, it is likely |
131 |
that there are problems with the charset. |
that there are problems with the charset. Newer versions of the |
132 |
|
plug-in try to handle UTF8 encoding correctly but even so it cannot |
133 |
|
be 100% assured that the receiver can handle the text in all cases. |
134 |
|
|
135 |
@item |
@item |
136 |
If you want to import keys or attach keys to a mail, you have to |
If you want to import keys or attach keys to a mail, you have to |
137 |
use an external key manager. WinPT is recommend in this case. It |
use an external key manager. WinPT is recommend in this case. It |
138 |
contains features to send public keys to mail recipients and also |
contains features to send public keys to mail recipients and also |
139 |
to export keys via the clipboard so you can easily paste the key |
to export keys via the clipboard so you can easily paste the key |
140 |
into the text body of the message. |
into the text body of the message. The current version of the |
141 |
|
plug-in automatically uses WinPT for key import if the program |
142 |
|
is available and running. |
143 |
|
|
144 |
@item |
@item |
145 |
Currently signing can be only done with the default signing key. |
Currently signing can be only done with the default signing key. |