mail body

17 Mar 2014


      I have a new list, that turns all attachable parts/hyper text to plain 
text into the mail body (see lower part for an example). I did an 
experiment, using procmailrc code to only forward to a list of emails with
   ! `cat listfile`
which passes the mails with multi-parts well. I wonder which part of the 
smartlist converts mordern mails to old fashioned plain text(?), and if I 
can take that part out (e.g. is it in "rc.submit"? etc).

Thanks,
Zhiliang

-------------
-- example --
-------------

--_004_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_
Content-Type: multipart/alternative;

boundary="_000_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_"

--_000_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
......................
         mail body text
         ...........................
--_000_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" 
xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" 
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" 
xmlns=3D"http://www.w3.org/TR/REC-html40">
...................................
              mail body hyper text
             ......................................
</body>
</html>
--_000_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_--

--_004_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_
Content-Type: 
application/vnd.openxmlformats-officedocument.wordprocessingml.document;
 	name="2014 NRSP 8 Leadership.docx"
Content-Description: 2014 NRSP 8 Leadership.docx
Content-Disposition: attachment; filename="2014 NRSP 8 Leadership.docx";
 	size=19737; creation-date="Mon, 17 Mar 2014 13:42:32 GMT";
 	modification-date="Mon, 17 Mar 2014 13:42:32 GMT"
Content-ID: <814DB34A2C17E0419B28190B2C5E44B5@mail.iastate.edu>
Content-Transfer-Encoding: base64

UEsDBBQABgAIAAAAIQAk5ahdmwEAAJYGAAATAAgCW0NvbnRlbnRfVHlwZXNdLnhtbCCiBAIooAAC
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
.................
      coded lines
      ......................
--_004_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_--