Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    PUBLIC_KEYS    |    Public-Key Discussion Echo    |    845 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 366 of 845    |
|    Wilfred van Velzen to August Abolins    |
|    Re: testing signed message    |
|    04 Jan 20 23:49:52    |
      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 5e1116a7       REPLY: 2:221/360.0 5e110252       Hi August,              On 2020-01-04 23:23:32, you wrote to All:               AA> -----BEGIN PGP SIGNED MESSAGE-----        AA> Hash: SHA256               AA> I don't think the previous message got signed.               AA> Enigmail for TB 60.9 and TB 24 are quite different!               AA> This one will be signed when I send the message.               AA> ../|ug               AA> Time transpires.. [ ... ] ..I'm back.               AA> The signing process seemed to go ok, but the actual send failed.               AA> Enigmail for TB 60.9 seems to want to send a signed message multi-part        AA> whatever - which is rejected.               AA> Whoa! ... I found a setting for "Protocol: Inline PGP" version .vs.        AA> the default "Protocol: MIME/PGP".               AA> Hopefully this one will get sent with inline signature.              Yep:              gpg: Signature made za 04 jan 2020 22:23:26 CET using RSA key ID 5789589B       gpg: Good signature from "August Abolins |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca