FW: [Python-ideas] Standard library high level support for email messages
Daniel Reis <[email protected]> Wed, 30 Jan 2013 16:08:26 +0000
| Newsgroups | gmane.comp.python.mime.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============0508372909==
Content-Type: multipart/alternative;
boundary="_4c9de6e6-3ad9-4374-a42b-e978c06d8f44_"
--_4c9de6e6-3ad9-4374-a42b-e978c06d8f44_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello all=2C
I originally posted this to the python-ideas list=2C and am reposting it he=
re following Barry Warsaw's advice:
"""
Python=2C as a "batteries included" language=2C strives to provide out of t=
he box solution for most common programming tasks.
Composing and sending email messages is a common task=2C supported by `emai=
l` and `smtplib` modules.
However=2C a programmer not familiar with MIME won't be able to create non-=
trivial email messages.
Actually=2C this proposal idea comes from the frustration of fast learning =
about MIME to get the job done=2C and later learn that some people=B4s emai=
l clients couldn't properly display the messages because I tripped in some =
details of multipart messages with Text+HTML and attachments.
You can call me a bad programmer=2C but couldn't / shouldn't this be easier=
?
Should a programmer be required to know about MIME in order to send a decen=
tly composed email with images or attachments?
The hardest part is already built in. Why not go that one step further and =
add to the email standard library an wrapper to handle common email composi=
tion without exposing the MIME details.
Something similar to http://code.activestate.com/recipes/576858-send-html-o=
r-text-email-with-or-without-attachment=2C or perhaps including a lib such =
as pyzlib.
"""
Regards
Daniel Reis =
--_4c9de6e6-3ad9-4374-a42b-e978c06d8f44_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>Hello all=2C<br><br>I originally=
posted this to the python-ideas list=2C and am reposting it here following=
Barry Warsaw's advice:<br><br>"""<br><div>Python=2C as a "batteries includ=
ed" language=2C strives to provide out of the box solution for most common =
programming tasks.<br><div dir=3D"ltr"><div><div dir=3D"ltr">Composing and =
sending email messages is a common task=2C supported by `email` and `smtpli=
b` modules.<br><br>However=2C a programmer not familiar with MIME won't be =
able to create non-trivial email messages.<br>Actually=2C this proposal ide=
a comes from the frustration of fast learning about MIME to get the job don=
e=2C and later learn that some people=B4s email clients couldn't properly d=
isplay the messages because I tripped in some details of multipart messages=
with Text+HTML and attachments.<br><br>You can call me a bad programmer=2C=
but couldn't / shouldn't this be easier?<br>Should a programmer be require=
d to know about MIME in order to send a decently composed email with images=
or attachments?<br><br>The hardest part is already built in. Why not go th=
at one step further and add to the email standard library an wrapper to han=
dle common email composition without exposing the MIME details.<br><br>Some=
thing similar to <a href=3D"http://code.activestate.com/recipes/576858-send=
-html-or-text-email-with-or-without-attachment" target=3D"_blank">http://co=
de.activestate.com/recipes/576858-send-html-or-text-email-with-or-without-a=
ttachment</a>=2C or perhaps including a lib such as pyzlib.<br>"""<br><br>R=
egards<br>Daniel Reis</div></div></div></div> </div></body>
</html>=
--_4c9de6e6-3ad9-4374-a42b-e978c06d8f44_--
--===============0508372909==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline