Okay, it's correct that better documented or cleaner would have helped in this
situation. This bug is marked as wontfix, it seems, that you can't do anything
against this situation. If there was any discussion on the mailinglist about
this issue. Sorry, I haven't read it: The situation as I understand it:
Enigmail can't control the behaviour of GnuPG. If GnuPG takes long for certain
actions, Thunderbird could think, that Enigmail is not running correctly and
suggest continuing or stopping Enigmail. If we enumerate all cases, where GnuPG
takes long for certain actions, these actions can probably forced before doing
any critical actions. This could decrease the probability, that this window
alert pop up in the wrong time. If all cases can be enumerated and can be
forced, it should be checked, if it's possible to deactivate the send-button on
Thunderbird. If it's possible, the send-button is deactivated, before Enigmail
is forcing GnuPG's risky actions to get in a fail-safe condition, if the user
stops Enigmail. Is that possible?
Yes, that would be possible, but it could lead to situations where you would
simply not be able to send a message at all.
Once you stop the script, it's stopped, and you will not be able to
reactivate the send button. We would have to provide an extra function for
this.
I will look into it.
Patrick
--
Sent from my tablet
_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
