Most of the emails I send are read by users with web mail or an html-centered mua (outlook, apple mail), often on phones. Hard line breaks can make emails nearly unreadable on small screens. So I've experimented with not hard wrapping my emails. But in reading around on mail protocols, it has struck me that this may result in truncated lines (beyond 1000 characters) or perhaps worse (emails rejected or marked as spam). (My understanding of these protocols comes mainly from this helpful summary: https://stackoverflow.com/questions/25710599/content-transfer-encoding-7bit-or-8-bit.)
How do other bower users handle this challenge? Format=flowed seems long dead. I formerly used alot (https://github.com/pazz/alot), which encoded all emails as quoted-printable (originally because python 2 couldn't encode 8bit?), with equal-sign soft breaks at 76 characters. I've played around with the html filter, which is cool---but seems unnecessary/overkill for plain-text emails. All ideas are appreciated—thanks!
Most of the emails I send are read by users with web mail or an html-centered mua (outlook, apple mail), often on phones. Hard line breaks can make emails nearly unreadable on small screens. So I've experimented with not hard wrapping my emails. But in reading around on mail protocols, it has struck me that this may result in truncated lines (beyond 1000 characters) or perhaps worse (emails rejected or marked as spam). (My understanding of these protocols comes mainly from this helpful summary: https://stackoverflow.com/questions/25710599/content-transfer-encoding-7bit-or-8-bit.)
How do other bower users handle this challenge? Format=flowed seems long dead. I formerly used alot (https://github.com/pazz/alot), which encoded all emails as quoted-printable (originally because python 2 couldn't encode 8bit?), with equal-sign soft breaks at 76 characters. I've played around with the html filter, which is cool---but seems unnecessary/overkill for plain-text emails. All ideas are appreciated—thanks!