Module SMTP and Attachments

Started by ale870, July 13, 2009, 12:48:32 AM

Previous topic - Next topic

TedWalther

#15
Quote from: "xytroxon"Yes, this legacy code from the early days of pre-internet file transfer is a mess, but it has a lot of functionality (yEnc) I still use with Windows/DOS command line Usenet postings ;)



Or do e-mail attachments not use these MIME encoding protocols???



-- xytroxon


*sigh*  I get the feeling everyone else in this thread is using the word "MIME" to mean something completely other than what the RFC's specify.



uuencoding, like base64 encoding, is merely an encoding type.  MIME can contain chunks of data of any type.  As far as detecting the MIME type of data, that is a completely different subject, although a MIME module may well want to include utility functions for doing it, just as it should include uu and base64 encoding/decoding functions.
Cavemen in bearskins invaded the ivory towers of Artificial Intelligence.  Nine months later, they left with a baby named newLISP.  The women of the ivory towers wept and wailed.  \"Abomination!\" they cried.

newdep

#16
As far as I know is MIME nothng more than a Email header addon

for the use of Base64...



Probably MIME extended over the years with other formats but it was base64

originaly.. iirc..
-- (define? (Cornflakes))

ale870

#17
Not exactly: mime-types is a convention, standard description format, to define "which kind of file we are talking about". In this way a program can decide how to manage it.

It is a required information in order to exchange data from different operating systems (which they manage data in different ways).
--

newdep

#18
Ha you read the RFC ..;-) thanks for clearing my dusty mind...;-)
-- (define? (Cornflakes))

ale870

#19
:-)



http://en.wikipedia.org/wiki/MIME_type">http://en.wikipedia.org/wiki/MIME_type



(see RFC: it was born on 1993!!!)

But you are right: mime-type was used for the first time to exchange emails! (I discovered it now). Thank you for your hint!
--

xytroxon

#20
Quote from: "ale870":-)



http://en.wikipedia.org/wiki/MIME_type">http://en.wikipedia.org/wiki/MIME_type



(see RFC: it was born on 1993!!!)

But you are right: mime-type was used for the first time to exchange emails! (I discovered it now). Thank you for your hint!


Suffering suffixes!!! ie er is not the same as ing!



I did a Google Search for: mime encoder


QuoteDid you mean: mime decoder  Top 2 results shown

#

UUDeview Home Page

The decoder automatically detects the type of encoding used, offering MIME's Base64 and BinHex as well as the popular uuencoding and the less frequently ...

fpx.de/fp/Software/UUDeview/ - Cached - Similar


I should of done a Google Search for: mime encoding


Quote
MIME - Wikipedia, the free encyclopedia

MIME also specifies rules for encoding non-ASCII characters in e-mail message headers, such as "Subject:", allowing these header fields to contain ...

en.wikipedia.org/wiki/MIME - Cached - Similar


Python has an smtplib module:

http://docs.python.org/library/smtplib.html">//http://docs.python.org/library/smtplib.html



And a higher level email module:

http://docs.python.org/library/email.html">//http://docs.python.org/library/email.html



I hope this helps ;)



-- xytroxon
\"Many computers can print only capital letters, so we shall not use lowercase letters.\"

-- Let\'s Talk Lisp (c) 1976

Kirill

#21
Just came across http://mailgun.net/">MailGun. Which is, according to the docs, a programmable email platform. It allows sending and receiving messages with HTTP API. Receiving fully parsed message via HTTP sounds cool! And sending too, for that matter.



Haven't tested yet.