Re: Warning re. obscure reformat fwd mail with attachment

On Tue, 9 Dec 2008, Eduardo Chappa wrote:

> On Tue, 9 Dec 2008, David Morris wrote:
>
> :) It looks like what happened is that Dice sent the original email as
> :) text/html with appropriate <br> tags to force new lines. When pine
> :) forwarded the mail, it retained the text/html content type, but
> :) didn't include <br> tags.
>
...
>
> In this case, what you need to do is to convince Pine that it needs to tag
> your messag as text/plain and not as text/html. There is a trick to send
> the content-type of a message when sending the mail, and you can use it to
> change the content-type to text/plain. An explanation of how to do this
> can be found in the following post in comp.mail.pine
>
> http://groups.google.com/group/comp.mail.pine/browse_thread/thread/7c187285b7d02441/
>
> Hopefully you can use that trick to change the content-type to text/plain,
> rather than (as explained in the post) to text/html.

Awesome ... I had to use:
   echo "Content-type: text/plain; charset=US-ASCII" > $2
without charset, pine added it, but inserted a new line without
leading whitespace. That broke header parsing at yahoo where I was
testing.

With "compose-send-offers-first-filter" set prompting for filter usage was
bypassed. It just ran, which is fine with me. I NEVER want a different
value.

Thanks,
   Dave Morris
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info