From hu@animalgenome.org Mon Mar 17 17:38:07 2014 From: Zhiliang To: smartlist@lists.rwth-aachen.de Subject: mail body Date: Mon, 17 Mar 2014 11:37:51 -0500 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6641972324206607241==" --===============6641972324206607241== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit 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 ................................... mail body hyper text ...................................... --_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(a)mail.iastate.edu> Content-Transfer-Encoding: base64 UEsDBBQABgAIAAAAIQAk5ahdmwEAAJYGAAATAAgCW0NvbnRlbnRfVHlwZXNdLnhtbCCiBAIooAAC AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ................. coded lines ...................... --_004_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_-- --===============6641972324206607241==-- From charlie@lofcom.com Mon Mar 17 18:04:07 2014 From: charlie@lofcom.com To: smartlist@lists.rwth-aachen.de Subject: Re: mail body Date: Mon, 17 Mar 2014 13:04:07 -0400 Message-ID: <1395075847.29636@lofcom.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3722871793473856768==" --===============3722871793473856768== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Zhiliang wrote .. > I wonder which part of the > smartlist converts mordern mails to old fashioned plain text(?), It doesn't. It treats "modern mails" the same way it treats "antique mails;" as a stream. If you want only plain-text mails in your list, you need to reject or convert multipart outside of SmartList. (Well, ok, you can call your rejection or conversion routine, like the demime perl script, from any of the rc.submit.* you want, but I mean that SmartList cannot natively change multipart to plain text. Truth is, IMHO, one of the things that makes it such an excellent tool even now is that it _doesn't_ munge the body.) > and if I > can take that part out (e.g. is it in "rc.submit"? etc). There's nothing to remove. SmartList is working exactly as-designed; passing the message on to the list mostly the way it found it (header changes notwithstanding). Charlie --===============3722871793473856768==-- From hu@animalgenome.org Mon Mar 17 20:23:49 2014 From: Zhiliang To: smartlist@lists.rwth-aachen.de Subject: Re: mail body Date: Mon, 17 Mar 2014 14:23:33 -0500 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5310329036888689088==" --===============5310329036888689088== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Charlie - Thanks for the clarification. I have been using it for plain text only. Now this is straight. Zhiliang On Mon, 17 Mar 2014, charlie(a)lofcom.com wrote: > Date: Mon, 17 Mar 2014 13:04:07 -0400 (EDT) > From: charlie(a)lofcom.com > To: smartlist(a)lists.rwth-aachen.de > Subject: Re: mail body > > Zhiliang wrote .. > >> I wonder which part of the >> smartlist converts mordern mails to old fashioned plain text(?), > > It doesn't. It treats "modern mails" the same way it treats "antique > mails;" as a stream. If you want only plain-text mails in your list, > you need to reject or convert multipart outside of SmartList. (Well, > ok, you can call your rejection or conversion routine, like the demime > perl script, from any of the rc.submit.* you want, but I mean that > SmartList cannot natively change multipart to plain text. Truth is, > IMHO, one of the things that makes it such an excellent tool even now > is that it _doesn't_ munge the body.) > >> and if I >> can take that part out (e.g. is it in "rc.submit"? etc). > > There's nothing to remove. SmartList is working exactly as-designed; > passing the message on to the list mostly the way it found it (header > changes notwithstanding). > > Charlie --===============5310329036888689088==--