[37897] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Possible solution? (e-mail parcel vs. FTP)

daemon@ATHENA.MIT.EDU (E.B. Dreger)
Fri May 25 12:31:27 2001

Date: Fri, 25 May 2001 15:49:54 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: nanog@nanog.org
Message-ID: <Pine.LNX.4.20.0105251542560.30647-100000@www.everquick.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu


Here are my "givens":

* Average users cannot, and will not, tolerate FTP
* HTTP and FTP are more efficient than SMTP
* New protocols (IM2000) might be nice, but we need interoperability
* Attachments are usually MIME, with a few uuencoded ones now and then.

Methinks that it's proxy time.  Why not hack the popular MTAs so that they
take attachments, spool them in a Web-accessible directory, then modify
the message.

Just like e-cards...

	ATTACHMENTS:

	1. http://some.domain.tld/path/to/sample/file.jpg
	2. http://another.place.tld/second-attachment.doc

Go to the link, receive a warning that they must save the file after
download, that it will be deleted after successful download.  Or delete it
after a few days.  Or maybe users could manage their Web spool, deleting
messages as they please.

There are some details to work out, but is the "FTP upload" not a task
that we could automatically perform for users?


Eddy

---------------------------------------------------------------------------

Brotsman & Dreger, Inc.
EverQuick Internet Division

Phone: (316) 794-8922

---------------------------------------------------------------------------

Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.

These last few lines are a trap for address-harvesting spambots.  Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.



home help back first fref pref prev next nref lref last post