Earlier (with Outlook 2010 32bit and Gpg4win 3.1.x < 3.1.2) using the option "Neue Nachrichten per Voreinstellung signieren" (Sign new mails by preference) would sign mails when answering / forwarding.
Now (with Outlook 2013 64bit and Gpg4win 3.1.2) signing is preselected only with new mails, but not when answering / forwarding.
| rO GpgOL | |||
| rO630844dc453a Handle always sign/encrypt for inline reply/fw | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | aheinecke | T4037 Autosigning mails doesn't work when answering / forwarding | ||
| Resolved | aheinecke | T4029 Gpg4win 3.1.3 |
I can't confirm the regression yet. For me (albeit with Outlook 2016) preselecting sign / encrypt based on the options works for reply and forward. But only as long as the Mail is opened in a dedicated window.
Automatically signing the reply or forward using the inline editor (the one inside the messagelist) does not work, but this also does not work for me with Gpg4win-3.1.1.
Is it possible that you might remember the behavior from 3.1.1 with mails opened in a new window and are now surprised that it does not work with 3.1.2 but looking at the inline editor?
Using the inline editor is a "missing feature" in that it has AFAIK never worked. Very easy to fix though. I'll do it now.
Yes, definitely the real reason is in the inline editor.
In O2010: Both clicking "answer" in an open mail window as in the ribbon
above the inline display opens a dedicated mail window. There is no
inline editor, so I never had that problem.
In O2013: Both clicking "answer" in the ribbon as in the inline display
opens the inline editor, with the problem. Only explicitely opening the
mail in a dedicated window by double-clicking and clicking "answer"
there will put my answering mail in this extra window and preselect "Sign".
Am 20.06.2018 um 14:23 schrieb aheinecke (Andre Heinecke):
aheinecke triaged this task as "Normal" priority.
aheinecke claimed this task.
aheinecke added a comment.I can't confirm the regression yet. For me (albeit with Outlook 2016)
preselecting sign / encrypt based on the options works for reply and
forward. But only as long as the Mail is opened in a dedicated window.Automatically signing the reply or forward using the inline editor
(the one inside the messagelist) does not work, but this also does not
work for me with Gpg4win-3.1.1.Is it possible that you might remember the behavior from 3.1.1 with
mails opened in a new window and are now surprised that it does not
work with 3.1.2 but looking at the inline editor?Using the inline editor is a "missing feature" in that it has AFAIK
never worked. Very easy to fix though. I'll do it now.*TASK DETAIL*
https://dev.gnupg.org/T4037*EMAIL PREFERENCES*
https://dev.gnupg.org/settings/panel/emailpreferences/*To: *aheinecke
*Cc: *aheinecke, JJworx, Rafixmod, ccharabaruk, Mak, gp_ast
This is an automated email from the GnuPG development hub. If you have
registered in the past at https://bugs.gnupg.org/ your account was
migrated automatically. You can visit https://dev.gnupg.org/ to set a
new password and update your email preferences.
Nice, then my commit should fix the issue here.
If you want, 2.2.1-beta7 has the fix:
http://files.gpg4win.org/Beta/gpgol/
Yes, that did the trick for me!
Am 20.06.2018 um 15:14 schrieb aheinecke (Andre Heinecke):
aheinecke changed the task status from "Open" to "Testing".
aheinecke added a comment.Nice, then my commit should fix the issue here.
If you want, 2.2.1-beta7 has the fix:
http://files.gpg4win.org/Beta/gpgol/*TASK DETAIL*
https://dev.gnupg.org/T4037*EMAIL PREFERENCES*
https://dev.gnupg.org/settings/panel/emailpreferences/*To: *aheinecke
*Cc: *aheinecke, JJworx, Rafixmod, ccharabaruk, Mak, gp_ast
This is an automated email from the GnuPG development hub. If you have
registered in the past at https://bugs.gnupg.org/ your account was
migrated automatically. You can visit https://dev.gnupg.org/ to set a
new password and update your email preferences.
Beware: Beta-7 was bad timing, yesterday I was in the middle of implementing T3999 and broke the internal keycache. If you use "Empfängerschlüssel automatisch auflösen" please switch back to a different GpgOL Version. I might upload a new Beta soon but for now I've removed Beta-7. Automatic resolution will not work with that version and can lead to crashes.
ok
Am 21.06.2018 um 10:31 schrieb aheinecke (Andre Heinecke):
aheinecke added a comment.
Beware: Beta-7 was bad timing, yesterday I was in the middle of
implementing T3999 https://dev.gnupg.org/T3999 and broke the
internal keycache. If you use "Empfängerschlüssel automatisch
auflösen" please switch back to a different GpgOL Version. I might
upload a new Beta soon but for now I've removed Beta-7. Automatic
resolution will not work with that version and can lead to crashes.*TASK DETAIL*
https://dev.gnupg.org/T4037*EMAIL PREFERENCES*
https://dev.gnupg.org/settings/panel/emailpreferences/*To: *aheinecke
*Cc: *aheinecke, JJworx, Rafixmod, ccharabaruk, Mak, gp_ast
This is an automated email from the GnuPG development hub. If you have
registered in the past at https://bugs.gnupg.org/ your account was
migrated automatically. You can visit https://dev.gnupg.org/ to set a
new password and update your email preferences.