[SpamCop-List] Re: [MEDIA] FTC deal blocks company's pop-up ads

[Paul Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Frog Prince" <me at privacy.net> writes:

> Paul, about half the post from you are totally unreadable on my end (don't
> know why, don't really care) so given that just how critical is it for me to
> know, for a fact, that a post I cannot read is from you?

Ah.  Read the same page, at the top this time.  I try to remember to
inline it instead of going by the RFCs in this newsgroup as a
workaround, but ultimately the problem is on your end.

http://kmself.home.netcom.com/Rants/gpg-signed-mail.html

You're probably reading this because you either stumbled across it at my
website, or I sent it to you in response to an email you sent me saying
you can't read my mail. The reason is that I'm using an open Internet
standard, RFC 2015 encoding, to sign, or authenticate, my mail. This
standard has existed since 1996, and can be freely implemented by any
email software author. It provides means to both authenticate, and
encrypt, email.
[...]
As to the immediate problem, the short answer is that:

* Your mailer is broken.
* This is your problem, not mine.
* File a bug report with your vendor.
* I'm going to continue signing my mail, and if you don't change your
  end of things, you're going to continue having problems reading it.

In some cases (you're cute, my mom, or you're offering sufficient
reasons per hour), I'll make exceptions, but this is on a case-by-case
basis, and I'm intentionally leaving it as a PITA manual process so that
each of us is reminded it's a bad idea: me, when I do it, you, when I
forget and you're stuck with unreadable mail from me. GET A REAL MAILER.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBEHwGUzgNqloQMwcRAqB6AJ9szIoRslSecciCxbLcadddf749RQCfQBLj
Ev5CBJeUqGpJAUQcupw5Gos=
=vezL
-----END PGP SIGNATURE-----