1. A process for defeating phishers and carried out in a distributed email system having a protected email server coupled via a wide area network to a plurality of client computers executing protected email software, comprising: A) receiving an initiation message at a protected email server from a client computer executing a protected email sender process, said initiation message requesting a code in the form of a stemp for inclusion in the header of a proposed email addressed to a recipient, said initiation message including at least ID information which identifies said sender and includes secure information to which a phisher would not have access and including at least said header of said proposed email; B) using said ID information and/or said secure information to determine the identity of the sender of said initiation message by looking up the owner of a protected email micropayments account associated with said ID information and/or said secure information; C) authenticating the sender of the initiation message by determining if the purported sender of said initiation message is the owner of the protected email micropayments account determined from said ID information and/or secure information in said initiation message; D) if the sender of said initiation message is not authentic, sending a warning message and denying said request for a stemp; E) if said sender is authentic, determining if the request for a stemp from this sender is legitimate in terms of a stemp policy; and, if not, denying said request for a stemp; F) if said request for a stemp is within said stemp policy, using an encryption key to encrypt a stemp, said encrypted stemp including at least unique information which directly or indirectly identifies the sender; G) saving said encryption key, said unique information, the identity of said sender or a pointer to the identity of said sender, any Truemark, generic logo or white list source icon associated with said sender and the encrypted version of said stemp in a table or database; H) determining if said sender is on a white list of said intended recipient, and, if not, deducting a micropayment amount from a micropayments account owned by said sender; I) sending said stemp back to the sender computer which sent said initiation message along with the header of said proposed email; J) after a recipient computer receives an email purportedly from said sender computer, receiving at least the header of said email if said email had a stemp therein; K) using the encrypted version of the stemp or a transaction number decrypted using a standard key from said encrypted stemp to look up a database record or table entry that pertains to said email; L) determining the identity of the sender from said database record or table entry that pertains to said email, determining if said stemp is a valid paid-for stemp and determining if there is a source icon of a Truemark or white list variety associated with said email that should be displayed with said email when said email is displayed on said recipient computer; M) determining if the sender ID decrypted from said stemp matches the sender who purportedly sent said email; N) if said sender does not match, sending back a warning message to said recipient computer; and O) if said sender matches, sending back a message to said recipient computer indicating said sender is authenticated and sending any Truemark or white list icon to be displayed with said email or data indicating which locally stored Truemark source icon should be displayed with said protected email or that the white list icon should be displayed with said protected email.