1996-08-19 - No Subject

Header Data

From: Alan Horowitz <alanh@infi.net>
To: N/A
Message Hash: f067e84efef4ef6909a3b2bc5ad8f0718b84e23663982943b821923fe3b6ec93
Message ID: <199608190352.XAA07594@larry.infi.net>
Reply To: N/A
UTC Datetime: 1996-08-19 06:03:06 UTC
Raw Date: Mon, 19 Aug 1996 14:03:06 +0800

Raw message

From: Alan Horowitz	<alanh@infi.net>
Date: Mon, 19 Aug 1996 14:03:06 +0800
Subject: No Subject
Message-ID: <199608190352.XAA07594@larry.infi.net>
MIME-Version: 1.0
Content-Type: text/plain


On Aug 18, 96 11:12:16 am, Joel M Snyder, Now Overwhelmed Again wrote:

> Back to the original topic: email-to-snail-mail.  That's not hard,
> technologically.  The problem as I see it is billing.  If I were to offer
> such a service, I'd want to keep my cost to the consumer low, on the order
> of $0.75 to $1.00 per message, with marginal charges for additional pages. 
> I might possibly barely be able to find some slave labor to make a profit
> at doing it, IF I HAD THE VOLUME (which I probably wouldn't), but the
> overhead of setting up a billing arrangement with every TDH who wants to do
> it would eat the profits up instantly.  
> 
> It's difficult to conceive of a setup which a technomad would use in
> sufficient volumes to be cost-effective.  


How about the sender provides a Digicash e-cash payment for the
appropriate amount with each message, kind of like a electronic postage
stamp?  A script on the receiving side could automatically check the
payment amount, bouncing the message back to sender with an
"insufficient payment" message if necessary.  Or you could use a web
page to submit messages and payments.  Either way no one needs to worry
about billing, account tracking, etc.  Payment/billing is taken care of
immediately.  Of course, there is some overhead with the fees on e-cash,
but it probably would be more cost effective than other methods.


P.S. I have an alpha version of a program which may be of interest to
technomads: it automatically executes scripts received by email from a
remote machine and then mails back the results.  The scripts (shell
scripts, perl scripts, or whatever) are encrypted and signed with PGP
before being sent to provide security and prevent unauthorized users
from executing scripts on your machine.  The program runs on unix
systems, and submissions can be from anything that runs PGP and is able
to send email.  See:

  http://www.bmen.tulane.edu/~carpente/emscrypt/emscrypt.html

for more info.


--Matt

--
mcarpent@mailhost.tcs.tulane.edu    PGP mail preferred, finger for public key.






Thread