TID: FMail-lnx64 2.1.0.18-B20170815
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 5e14f0bf
REPLY: 2:221/360.0 5e14df62
Hi August,

On 2020-01-07 21:43:31, you wrote to me:

 >> Decoding and verifying went well:
 >>
 >> wilfred@wilnux5:~> gpg tommi.msg
 >>
 >> You need a passphrase to unlock the secret key for
 >> user: "Wilfred van Velzen "
 >> 4096-bit RSA key, ID 2D3482F3, created 2017-10-25 (main key ID 4A97932B)

 AA> Ahh..  so you are saving the block (pulling it out of your echomail
 AA> reader) to file tommi.msg manually, and then running gpg in a separate
 AA> window/session.

Yes, I think it's easy enough...

 AA> The process is much smoother with TB and processed within the same
 AA> reading environment/application.   :)

 AA> I guess you could accomplish something similar using macros/scripts with
 AA> your GoldED?

I actually just discovered I already had such a macro in my golded.cfg, I just
had to assign a key to it, to actually be able to use it. ;)

The only drawback is, I can't see the output of the decoding/verifying proces,
so I don't know if the encrypted message was signed with a trusted key, or
even not signed at all. It's probably just a matter of adding a "press any key
to continu" option to the end of the decoding script, to make that possible.
That would also work on clearsigned messages.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 1/123 90/1 154/10 203/0 221/0 227/114 229/426 1014 240/5832
SEEN-BY: 249/206 317 400 280/464 5003 292/854 310/31 317/3 322/757
SEEN-BY: 342/200 396/45 423/120 712/848 770/1 2452/250
PATH: 280/464 229/426