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 5e0f577c
REPLY: 2:221/360.0 5e0f4aac
Hi August,

On 2020-01-03 16:07:45, you wrote to me:

 >> So where can we get your key?

 AA> I just got started with this. I am not completely familiar how to use
 AA> OpenPGP/Enigmail.

 AA> The following should be the right key for ID 5789589B

 AA> - -----BEGIN PGP PUBLIC KEY BLOCK-----

I can now verify your message had a correct signature made with this key:

wilfred@wilnux5:~/tmp> gpg --import aug.key
gpg: key 5789589B: public key "August Abolins "
imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
wilfred@wilnux5:~/tmp> gpg --verify aug.msg
gpg: Signature made vr 03 jan 2020 15:07:38 CET using RSA key ID 5789589B
gpg: Good signature from "August Abolins "
[unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: D0EB 2A29 5204 F316 7EB2  503C EF0E 8965 5789 589B

The trust thing is sort of an issue. I can't just sign your key (technically I
could of course), because I can't verify it's really you. Anyone could login
to Tommy's nntp server as 'August Abolins'. and "fake" email addresses are
also easy to create/get. And since you are not a node we can't even exchange
some crash netmails...


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