You Might Be An Anti-Spam Kook If...

Each item in the following list was suggested by the words or actions of people who presented themselves to the IETF or elsewhere as having discovered the FUSSP. Some of the items may seem obscure to those who have not dealt with the IETF.

Almost all of those who have inspired this list mean well. In many cases, they are not in the habit of thinking critically and believe that "Star Trek" accurately depicts the creation of hardware, software, and even social or political mechanisms.

You have discovered the Final Ultimate Solution to the Spam Problem (FUSSP).

You are the first to think of the FUSSP.

You started looking for the FUSSP after observing that it is impossible to filter more than 99% of spam with fewer than 0.1% false positives by currently available mechanisms.

Despite being the inventor of the FUSSP, you are unfamiliar with false positive, false negative, UBE, tarpit, teergrube, Brightmail, Postini, SpamAssassin, DNS blacklist, HELO, RBL, or mail envelope.

You will make money by licensing the FUSSP.

You will build the FUSSP as soon as you find some investors.

Since most spammer domain names are bought with stolen credit card numbers, delay domain name activation for 30 days.

You don't plan to make a fortune from the FUSSP, but you do expect recognition as its generous and public spirited netizen inventor.

You are hurt and angry because you are not respected as spam fighter.

People don't see the value of the FUSSP because they have axes to grind, are jealous, or are too stupid to understand it.

You invented the FUSSP but thieves stole the idea. Never mind that the so called thieves talked about your idea in public and used it long before you first thought of it.

You have no solutions for the problems in the FUSSP and your implementation and deployment plan is tell to Google, but you do know that Arthur C. Clarke wrote "When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong."

You realized how to stop spam during the more than six weeks you've been fighting it.

The FUSSP assumes that your attention is so important that strangers will pay money to send you mail.

Despite having invented the FUSSP, you not only don't know the difference between the SMTP envelope and SMTP headers. You doubt there is such a thing as the SMTP envelope because email doesn't involve paper.

Despite having invented the FUSSP, your SMTP header and DSN reading skills are such that when you send a mail message to two sites and one rejects it, you can't tell that only one rejected it, not to mention which one.

You cannot name several potentially fatal flaws in the FUSSP.

All you need to do to get the FUSSP implemented and deployed is to publish an RFC or get a law passed.

You don't recognize any significant difference between deploying and implementing the FUSSP.

You plan to publish an RFC mandating the FUSSP but have never heard of RFC 2223 or RFC 2026.

Inventing the FUSSP did not require that you know the difference between RFC 821 and RFC 822 or that they have been replaced by RFC 2821 and RFC 2822.

You don't know the relevance of consensus or IESG approval to publishing RFCs.

You think all RFCs have the same standing.

Spammers won't ignore, subvert, or exploit the FUSSP if you publish it as an RFC.

Spammers can't use automation or cheap labor for puzzle solving, character recognition, or other hoops that the FUSSP requires of legitimate mail senders.

The FUSSP depends on spammers or mail recipients changing their behavior without any immediate gain.

The FUSSP won't be effective until it has been deployed at more than 60% of SMTP servers and that's not a problem.

The FUSSP will be the only spam defense used, or at least everyone will make special provisions for it.

The FUSSP is easy to implement and deploy, but you have done neither.

Your job is done after having explained the FUSSP to the IETF or The Industry.

Programmers will drop everything to implement the FUSSP.

You think that a violation of an RFC by an SMTP client or server is good and sufficient reason to reject all mail from the system's domain.

With standards, the implementation cost is about zero, so the FUSSP will be practically universally deployed within months of being documented in an RFC.

You know that SMTP has no authentication and have never heard of SMTP-AUTH, SMTP-TLS, S/MIME, or PGP.

You know that the failure of SMTP servers to authenticate the SMTP clients of strangers is a major bug in SMTP instead of an expression of a primary design goal.

Despite discovering the FUSSP, you don't know the meanings of MTA, MUA, SMTP server, SMTP client, or submission server.

The FUSSP requires a small number of central servers on the Internet to handle certificates, act as pull servers for bulk mail, account for mail charges, or whatever, and that is good thing or not a problem

The FUSSP uses central servers to manage all mailing list subscriptions on the Internet, handle digital signatures for mail, and track spam. Your impression that Google has 100% uptime shows that this problem can be solved by using a bunch of Linux systems.

The central servers required by the FUSSP to handle all mailing list subscriptions, digital signatures for mail and so forth will be run by a non-profit organization. It will be easy to find or create a non-profit organization that everyone will trust.

The FUSSP requires that anyone wanting to send mail obtain a certificate that will be checked by all SMTP servers.

The FUSSP involves certificates, but there is no barrier to spammers buying many independent certificates.

You know that certifying that a user legitimately claims a name and has never used some other name is cheap and easy.

You feel that most Internet users would be happy to pay $5/month to avoid spam and you do not know the price of anti-virus software or data.

The FUSSP involves ISPs issuing certificates to users and the ISPs that today don't terminate the accounts of spammers and don't investigate prospective customers enough to refuse service to spammers today will refuse FUSSP certificates to known spammers and revoke the certificates of new spammers.

The FUSSP involves convincing everyone to not buy anything advertised with spam.

You have never heard of RFC 2554 or RFC 2487 and the FUSSP includes fixing the lack of authentication in SMTP.

The FUSSP won't work on mobile clients such as cell phones and PDAs and that is not a problem.

The FUSSP involves replacing SMTP.

The FUSSP involves replacing TCP/IP, because you consider TCP/IP insecure, and never mind that you do not define "security."

You routinely send single reports of single examples of objectionable mail to more than two dozen addressees.

Your definition of spam differs significantly from "unsolicited bulk email."

The FUSSP cannot be described in fewer than 100,000 words.

The existence of this list is proof that the spam problem will never be solved by the people currently working on it.

You frequently use terms from math, statistics, and information theory, but have never heard of The Law of Large Numbers and think entropy is something about heat.

Nothing in this list applies to your solution to the spam problem except some entries that are neither ironic nor silly.

This list was written specifically to insult you.

With apologies to Jeff Foxworthy.

See also

Contact Vernon Schryver of Rhyolite Software, LLC at

$Date: 2016/12/27 14:46:45 $