-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Now thats uncalled for. My point was, that Mika's posts are > difficult to read as it is (because he doesn't trim them) without > all that extra "stuff" at the end. > > I haven't read all the thread yet, so bearing that in mind, I think > it is fine to sign your emails. In fact, many developers¹ do and I > can see good reason to. > > Mika: Is it possible to sign your mail *without* sending the whole > key² as well or is that another problem with enigmail? My whole key is not in signature. The key is this what is attached to this message. > Ahhh... wait a minute. .... > > "Enigmail is capable of signing, authenticating, encrypting and > decrypting email. Additionally, it supports both the inline PGP > format, as well as the PGP/MIME format as described in RFC 3156." > > If you change to the newer PGP/MIME format and see ² hopefully > that should at least halve your post content. As I have said three times in this same thread, I also use K9 Mail on phone and it doesn't support PGP/MIME. > ¹ Although most tend to use mutt which uses gnupg. > > ² If that is in fact what it is; I suggest uploading your key to a > keyserver, and just publishing the fingerprint. > I have published my key to keyserver and I have both, keyid and fingerprint mentioned in my emails in automatically added signature. Look at the third and fourth lines after this line. - -- Mika Suomalainen > gpg --keyserver pool.sks-keyservers.net --recv-keys > 4DB53CFE82A46728 Key fingerprint = 24BC 1573 B8EE D666 D10A AA65 > 4DB5 3CFE 82A4 6728 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPgUZoAAoJEE21PP6CpGcofjkP+wdKWksogsQ2nOYjOs/+pY0y WgyqMI+NmNWdQgwQOZyJ1fKsXcGpzTKPlXe6lkw8vQ9U3FcDw90zGSdSMMshkEPr CMpBft1ABSUq1bbuRiay+q1wZ5j0WsUt0EyROprA3npbQhaK4rMe56nE1NM9i5MO Fo4meUJnAXvEVtbpqGOJQW/WPk4g/gJbMfX9635YKrPPk9eOOvIXqtp3nd6DFQMw n2rrFTlCIVvCXxXkNMufup9YY9Q5gHwkqvSXpYurNNCW+NvJ4cR2Mwx1X+xbMRne df2P2OOuz3AQhSKQqEbtNDchWKT3htQ+MEE0FUZub685q2bkJHUsPkdANrUoO3// 0ej51UHWWNFdH5Up4S+6yUYpDEeg40JAPab9ghK3XL2bE/NC2hsp+DX9tPgQ+4z3 kq3Ia6LpzvIWNuvj+85QDEoM8dcClzqJ4w2UW2qHJ3s/z2hvbVxsfJ9o9ss15C0m JTboVfmsReNud/zJTgXZAiZi889XkZSMN9F8+azz549AJUFWQB2FaTxp3tp6qsxn DTVpF8KmDOupThCfRsNAt0d9H+1y+VYiBv6crimXWorxHIU0PYGV/IajZQTvrDkG ljxDzRB+DghgGu6grzvVHbDU7aOwCe5w5qXHznos5VvEqyy1oV9Gkd2u6EJOtlCo q2RkLppxkkPBboukRy1f =Pb+v -----END PGP SIGNATURE-----
Attachment:
0x82A46728.asc
Description: application/pgp-keys
Attachment:
0x82A46728.asc.sig
Description: PGP signature