-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Stephen" == Stephen Gran <[EMAIL PROTECTED]> writes:
Stephen> On Mon, Jan 10, 2005 at 07:22:29PM +0300, Arkady
Stephen> V.Belousov said: [snip]
Stephen> Of course you do, somewhere, or else the ftp part of it
Stephen> wouldn't work. I assume what you have on your end is an
Stephen> intermittent uucp connection for email (and why you think
Stephen> uucp is somehow different at the transport layer than
Stephen> smtp is beyond me, but that's another argument). You
Stephen> already have a bot that makes ftp connections and sends
Stephen> you an email of the contents, right?
He's not using FTP. He's using e-mail. He doesn't have a bot. He
uses someone else's bot. From the ``Accessing the Internet by E-mail
FAQ'' (http://www.faqs.org/faqs/internet-services/access-via-email/):
FTP BY EMAIL
------------
FTP stands for "file transfer protocol", and is a means of accessing
files that are stored on remote computer systems (sites). Files at FTP
sites are typically stored in a tree-like set of directories (or nested
folders for Mac fans), each of which pertains to a different subject.
When visiting an FTP site using a "live" internet connection, one would
specify the name of the site, login with a userid & password, navigate
to the desired directory and select one or more files to be transferred
back to their local system.
Using FTP by e-mail is very similar, except that the desired site is
reached through a special "ftpmail server" which logs in to the remote
site and returns the requested files to you in response to a set of
commands in an e-mail message.
Using FTP by e-mail can be nice even for those with full Internet
access, because some popular FTP sites are heavily loaded and
interactive response can be very sluggish. So it makes sense not to
waste time and connect charges in these cases.
...
If you find an interesting FTP site in the list, send e-mail to one of
these ftpmail servers:
[EMAIL PROTECTED] (United States)
[EMAIL PROTECTED] (United States)
[EMAIL PROTECTED] (Russia) - SLOW
[EMAIL PROTECTED] (Japan)
[EMAIL PROTECTED] (Sweden)
[EMAIL PROTECTED] (Germany)
[EMAIL PROTECTED] (Ukraine)
[EMAIL PROTECTED] (Japan)
[EMAIL PROTECTED] (Hungary)
[EMAIL PROTECTED] (Belgium)
[EMAIL PROTECTED] (Ukraine)
[end excerpt]
And yes, UUCP is different from SMTP. SMTP is TCP-only whereas UUCP
can run over TCP, X.25 or dial-up lines. UUCP uses its own transport
protocols for dial-up and X.25.
Stephen> On the machine that has the ftpbot, write a short script
Stephen> that does this for you - a combination of dig (to check
Stephen> txt records to see if an update is necessary), wget (to
Stephen> fetch the files), and uuencode and mail (to actually send
Stephen> the files) is all that's necessary. The mail part should
Stephen> be transparent - if the MTA on that machine has a uucp
Stephen> route for you, it will handle getting the mail to you.
Startling as it may sound, there are still people on this planet who
do have access to the Internet but not to IP. Once one understands
that fundamental premise, Arkady's reservations about using HTTP, FTP,
wget, ncftp, Net::FTP, LWP and whatever other suggestions that the
list has provided become slightly clearer.
Ignorance of another person's environment is no excuse for denigrating
his statements.
Regards,
- -- Raju
- --
Raj Mathur [EMAIL PROTECTED] http://kandalaya.org/
GPG: 78D4 FC67 367F 40E2 0DD5 0FEF C968 D0EF CC68 D17F
It is the mind that moves
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFB4silyWjQ78xo0X8RAp1aAKCKMZWxnUefzgQAZqVPSxCqAE0h1gCeJOWn
KrgXR23LOwskUzktDDvAXKc=
=Gc6P
-----END PGP SIGNATURE-----
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
