[37916] in North American Network Operators' Group
Re: EMAIL != FTP
daemon@ATHENA.MIT.EDU (Alexei Roudnev)
Fri May 25 16:16:29 2001
Message-ID: <03ae01c0e53e$c5169b20$9eb431c6@oemcomputer>
From: "Alexei Roudnev" <alex@relcom.EU.net>
To: "Robert Blayzor" <rblayzor@thebiz.net>,
"M. David Leonard" <mdl@equinox.shaysnet.com>
Cc: <nanog@nanog.org>
Date: Fri, 25 May 2001 10:18:51 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="windows-1251"
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
Few things are obvious:
(1) sender must be able to use simple _attach file_ feature to send a file,
without extra skills;
(2) receiver should be able to receive this file and open it as part of letter;
without extra skills.
If you want to create additional service, you can (by request) retract attachments
on the server, place them on the web (you can virus - scan them if you want and
add virus warning) and include html reference into the mail itself; but it cause
a lot of problems if customer uses something other that openlook - express. For
some cases it looks reasonable; for opthers, IMAP can solve the problem. And (of
course) you need _smart_ anty-spam filters which can be turn on / off by the
customer (and can have ON default).
My friends filter out SPAM by finding the same messages send to the hundred of the
custoimers at onse - this simple method drop the SPAM percent dramatically (just
again, it's important to allow receiving spam - it can be something except SPAM,
so they provide some way to look through removed messages, as I know). Anyway,
SPAm p[roblem and PARSEL problem are different ones.
>
