What's the SOLUTION??? Watching this thread is like watching a dog chase
it's tail. The distinguished left hand keeps saying that "E-mail wasn't
designed to do this." The down and dirty right hand keeps asserting "User's
will keep using it if there is no good alternative."
Well I have news for
A couple of points. In 3) you say that you demand that message not be able
to be altered. Can that be done? I can only think that alteration is
detectable (signatures, et. al.)
Also, I would add that if a store and forward method is used, the message
must not be readable at the storage site.
Does ESMTP support the recipient being able to tell the sender to not send?
How about when I have a POP or IMAP client, and my ISP has the SMTP server?
Can I easily and transparently set an attribute for myself at the SMTP
server that instructs the sender to abort if the message is over my persona
But I can do that already, by sending an email with a huge attachment direct
to your SMTP server that has a destination with a name and IP, but no
physical site. It will stay at your site until your SMTP timeout kicks in.
This is, of course, assuming that the RFC still says all SMTP servers must
