Re: smtplib.send_message

Barry Warsaw <[email protected]> Mon, 20 Jun 2011 10:21:15 -0400
Newsgroups gmane.comp.python.mime.devel
Organization Damn Crazy Followers of the Horn
Message-ID <[email protected]>
--===============0408202533==
Content-Type: multipart/signed; micalg=PGP-SHA256;
	boundary="Sig_/JTB5KPqOjbFnJINEM7xe4TM";
	protocol="application/pgp-signature"

--Sig_/JTB5KPqOjbFnJINEM7xe4TM
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

My main concern is that whatever you decide to do, it is well documented, w=
ell
tested, and completely predictable.  We don't want to make it easy for
applications to do the wrong thing and accidentally send a message to the
wrong recipients.  Reducing functionality to ensure this is fine with me.

-Barry

--Sig_/JTB5KPqOjbFnJINEM7xe4TM
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJN/1dbAAoJEBJutWOnSwa/sTMP/RLJSAV/kZotKZtfdtgFKT9y
G2aCf84Q1jlxIkFckFnhH/3nG7PAx2hb+sxDLC5JhoEfl1zPW0r+Qj1gqLIsWp0O
TdL/aW0Zi85iF8bvolzvcnJQ+dHp0mvBD75D1URPO5bZ2mIjdVydIa3Le4PnyoSi
LBJP4B2v4p4Db2MSVUBNY2huMzkVWPlv6HTtwq7DiUmOGp0z7FthP8D8LRSlsyIf
7Dc18j9bX/t4FkHlFEYOC9qBymFwCKHntUJvBoojiTBBa/ZCi3TLDuVGqsikwDi0
MrtcBon58t894tD7VkSbOvnYrSzdVu8GsRE1FJv3FGXfI1xZiLd9Uq1bCRBc/fwc
zqOri6AzM05HGS3B8at1FhmFECA8afeis9AGfS7m/gq0EaRExrF9laDkSxDl2cdZ
RwlvvpsqPGGq+5f7Llrn1RXgWrCGLsXjJFwC2gxvuoQT1d+h5GvY1+zC5lExswP4
Oa7kFeV+kY9x6AHemCYTkigJuzBM9c5I1SjCE15goSsJRXAkH7dVSCLLiNf05IsV
zwGvKZ11uCcmYpsRvwJhuhNqBZNxVYxcqlrvsCohsiJVUPWQWE0MrF3ptWKNpGLJ
MKhlpS4mIzndBrG4KAwQb+j1xpkngWbM+R6Xdb07tmoB1iAC+n2VGFM4d13zfJrs
4djEBEBMNrBVL+7xNaAr
=S3R8
-----END PGP SIGNATURE-----

--Sig_/JTB5KPqOjbFnJINEM7xe4TM--

--===============0408202533==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline