RESCANNED 3:770/1
MSGID: 2:221/360 56d07fb8
REPLY: 1:3634/12.73 56d0731c
PID: JamNNTPd/2 1.2 20160109
TID: GE/32 1.2
CHRS: IBMPC 2
TZUTC: 0200
mark lewis - Tommi Koivula wrote:

 ml> 26 Feb 16 15:54, you wrote to Paul Hayton:

 TK>> XPost: p, u, b
 TK>> XPost: l, i, c
 TK>> XPost: _, k, e
 TK>> XPost: y, s

 TK>> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
 TK>> --DdhfP4QXQJPOOw5HqjI9i71KnDrMw4ikQ
 TK>> Content-Type: multipart/mixed;
 TK>>  boundary="------------72DBAAE51EADB07D7C166154"

 ml> uuugh what a mess ;) :lol:

Yes ;) I believe that was caused by using PGP/MIME in enigmail. :)

 TK>> Cannot decrypt your message. :(

 ml> yes, that's what he and i have been talking about... he tried to encrypt
 ml> it with his private key so that anyone with his public key could decrypt
 ml> it... i forget exactly how we did that with the original pgp and
 ml> everything i find now doesn't say how to do that... maybe because they
 ml> expect a "public key" to be easily found and they're not thinking about
 ml> restricted distribution of certain public keys...

I see.

Thunderbird does not allow to send encrypted messages to nntp server. Which is
good, I think. :)

 TK>> Content-Type: application/pgp-keys;
 TK>>  name="0x2442E762.asc"

 ml> got your key, thanks! :)

:)

'Tommi

--- Thunderbird 2.0.0.23 (OS/2/20090822)
 * Origin: *** nntp://rbb.bbs.fi *** Lake Ylo *** Finland *** (2:221/360)
SEEN-BY: 1/123 19/10 57/0 90/1 120/340 601 123/131 153/250 757 154/10
SEEN-BY: 203/0 220/70 221/0 1 6 360 226/17 30 227/51 114 702 229/101
SEEN-BY: 229/424 426 664 1014 230/0 240/5832 249/206 303 317 400 266/404
SEEN-BY: 267/800 280/464 5003 292/624 854 310/31 317/3 320/119 322/757
SEEN-BY: 340/1000 342/200 423/81 120 712/848 770/0 1 100 340 772/0
SEEN-BY: 772/1 220 230 500
PATH: 221/360 1 203/0 280/464 770/1 229/664 426