--===============2129557833== Content-Type: multipart/signed; boundary="nextPart1463366.Sf3RTPTcd8"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1463366.Sf3RTPTcd8 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 19 January 2007 04:52, Anne Wilson wrote: > One reason I started using it is that some spam/virus emails substitute > addresses from an addressbook instead of the real sender. =A0I had compla= ints > that I had sent a virus and had to explain how to look at headers and > identify the sender's IP and compare it with one known to be mine. =A0This > doesn't go down well with most computer users. =A0Signing it was one way = of > giving them quick identification. =A0 Anne, This is precisely why I started signing as well. > I do, however, get some complaints that=20 > I send 'attachments' in messages, and the recipients system doesn't allow > them to view the attachment. =A0 I try to remember to use inline signatures with those people. I use my=20 verizon.net account for Linux tech lists and my gmail account for lists tha= t=20 are either non-tech or dominated by MS Outlook users. I tried to set my=20 gmail identity to use inline signatures, but it doesn't seem to work. Ingo= =20 recommended that I make the setting via the recipient's address book entry,= =20 and that works when I compose a message to an "inline recipient", but not=20 when I reply to one. For now, I have to rely on memory to check if the=20 format is correct. > I've just got used to explaining that=20 > the 'attachment' is my signature, and if they wish to ignore it, they can. I have an explanation in my tagline signature, even pointing to a web page = for=20 furher explanation, but most people don't read it. =2D-=20 _____________________________________________________________ Art Alexion PGP fingerprint: 52A4 B10C AA73 096F A661 92D2 3B65 8EAC ACC5 BA7A Keyserver: hkp://subkeys.pgp.net The attachment - signature.asc - is my electronic signature; no need for=20 alarm. Info @=20 http://mysite.verizon.net/art.alexion/encryption/signature.asc.what.html _____________________________________________________________ --nextPart1463366.Sf3RTPTcd8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iQCVAwUARbDLFkLG/oYII0YuAQIF0AQAsqqqrcvy8dMWKHhGzV2aKEUQmSdv0GXj wVeeyhmG09lCyB/inuJWjIIEuwJg0fbQr4C9Y2rE/gwQsA32SWSk95aZ8GgVBoEC fNsIVfFeTILL8T1BkF5Gi9bdzYEpgpc9XXjVvmqj8Ooui2JnW7+Wtbhy160UlSI5 MO5836kk7vI= =uWqH -----END PGP SIGNATURE----- --nextPart1463366.Sf3RTPTcd8-- --===============2129557833== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ KDE PIM users mailing list kdepim-users@kde.org https://mail.kde.org/mailman/listinfo/kdepim-users --===============2129557833==--