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 5e19a46f   
   REPLY: 2:221/360.0 5e1911b8   
   Hi August,   
      
   On 2020-01-11 02:07:22, you wrote to me:   
      
    AA>>> According to the dates (and time), we have exactly the same   
    AA>>> version of your keys. So, if Tommi (or me) signed your key,   
    AA>>> and I refreshed your keys on my systems, then the   
    AA>>> error "BAD signature" message to me would go away?   
      
    WvV>> No. 'BAD signature' really means a bad signature!   
      
    AA> What made it report BAD for me?  It was exactly the same pub key pair   
    AA> between us.  The exact time and date proved that.   
      
   So if the keys weren't the problem. Something must have changed in the plain   
   text that was signed, before it reached you, that made it fail the verify...   
      
   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