Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 582  |
|  Sean Rima to August Abolins  |
|  bad crc?  |
|  23 Jun 20 00:11:30  |
 REPLY: 2:221/360.0 5eeadf4a MSGID: 2:263/1 5ef13ac0 CHRS: CP850 2 TZUTC: 0100 TID: hpt/lnx 1.9.0-cur 2020-04-15 Hello August! 18 Jun 20 06:28, you wrote to me: AA> Hello Sean! AA> ** On Thursday 18.06.20 - 03:43, Sean Rima wrote to August Abolins: AA> ^^^^^ AA> That's almost 4am your local time? SR>> when I did gpg --verify on the message I got : SR>> gpg: invalid radix64 character 3A skipped SR>> gpg: invalid radix64 character 2E skipped SR>> gpg: invalid radix64 character 2E skipped SR>> gpg: CRC error; 750A9B - 3982ED SR>> gpg: [don't know]: invalid packet (ctb=0a) SR>> gpg: not a detached signature SR>> gpg: no signature found SR>> gpg: the signature could not be verified. SR>> Please remember that the signature file (.sig or .asc) SR>> should be the first file given on the command line. AA> Yes.. I'm getting the same thing after the message is posted: AA> OpenPGP Security Info AA> gpg command line and output: AA> C:\Program Files\gnupg\bin\gpg.exe AA> gpg: NOTE: you should run 'diskperf -y' to enable the disk AA> statistics AA> gpg: invalid radix64 character 3A skipped AA> gpg: invalid radix64 character 2E skipped AA> gpg: invalid radix64 character 2E skipped AA> gpg: CRC error; 750A9B - 3982ED AA> gpg: [don't know]: invalid packet (ctb=0a) AA> I don't know why this is happening. :( TB is dropping support for GPG or something so maybe that is affect it Sean --- GoldED+/LNX 1.1.5-b20180707 * Origin: A Destination in the Sun (2:263/1) SEEN-BY: 1/123 90/1 120/340 601 123/131 226/30 227/114 702 229/101 SEEN-BY: 229/424 426 664 1014 240/5832 249/206 317 400 292/854 317/3 SEEN-BY: 322/757 342/200 PATH: 263/1 222/2 261/38 396/45 280/464 229/101 426 |
[ << oldest | < older | list | newer > | newest >> ]