tag:help.tenderapp.com,2008-11-12:/discussions/problems/724-dealing-with-formatflowedTender: Discussion 2012-07-20T12:23:49Ztag:help.tenderapp.com,2008-11-12:Comment/2394422009-07-09T03:04:22Z2009-07-09T03:04:22ZDealing with format=flowed<div><p>We don't do anything with it right now -- but you're right, we
should fix the TMail parsing to do that.</p>
<p>P.S. If you're ever curious about our email parsing, you browse
the source of <a href=
"http://github.com/entp/astrotrain/tree/master">http://github.com/entp/astrotrain/tree/master</a>
which is the app that receives email and passes it on to
Tender.</p>
<p>Thanks!<br>
Kyle<br></p></div>Kyle Neath (GitHub Staff) tag:help.tenderapp.com,2008-11-12:Comment/2394422009-07-09T03:05:17Z2012-07-20T15:38:18ZDealing with format=flowed<div><p>A Lighthouse ticket was created for this discussion</p></div>Systemtag:help.tenderapp.com,2008-11-12:Comment/2394422009-07-09T03:10:39Z2009-07-09T03:10:39ZDealing with format=flowed<div><p>I've known about the issue for awhile, but it wasn't a real
issue for us until we stopped running emails through the markdown
processor. We recently turned off markdown for emails (mainly so
things like stack traces and whatnot aren't messed up), and now
this issue is rearing its ugly head.</p>
<p>To be honest, it's not a big deal to me at the moment. We have
bigger email-related issues that are encoding/charset related, or
dealing with text/html-only messages. It would be nice to get
resolved though, and mikel on github has been receptive about
<a href="http://github.com/mikel/tmail/issues">my issues and
patches</a>. I'd like to tackle it, but currently working out a way
to make the reply tracking much smarter...</p></div>rick