Author Topic: It would be nice to be able to select plaintext when composing  (Read 225 times)

rowanthorpe

  • Newbie
  • *
  • Posts: 22
    • View Profile
It would be nice to be able to select plaintext when composing
« on: September 20, 2017, 05:15:24 pm »
It would be nice to see a button (or even just menu-item) in the compose window for selecting plaintext mode. I guess this would be low on the priority list but I expect it would be easy enough to implement, and would allow efficiency & increased security for the receiver, for those who prefer it. When in plaintext mode all formatting buttons could just be greyed out, and if CM is using some kind of multipart/MIME format (like in the SMTP world) then attachments could still be enabled (including images). For that matter, if the mail is being constructed in some kind of multipart/MIME format then it would also be good to have a setting for defaulting to displaying either plaintext or html when receiving messages with both parts present.

Mike

  • Administrator
  • Full Member
  • *****
  • Posts: 105
    • View Profile
Re: It would be nice to be able to select plaintext when composing
« Reply #1 on: September 20, 2017, 06:16:15 pm »
You would like the sender to be able to set plaintext only?

The next version of CM is going to display text-only in case of a bad signature or key collision. I am somewhat worried about an exploit in wx.RichTextCtrl being the easiest way to attack someone via CM.

You would also like the receiver to be able to set a menu option and have the double-click action default to open text only?

Right now there are three types: text, HTML, and Rich Text XML as supported by wx. The HTML is there for future compatibility, as I would like CM to use HTML for its rich text someday. At the moment there is no good editor available.

The message is a ZIP file with the text, html, and xml formats as separate files inside the ZIP.

rowanthorpe

  • Newbie
  • *
  • Posts: 22
    • View Profile
Re: It would be nice to be able to select plaintext when composing
« Reply #2 on: September 20, 2017, 07:15:05 pm »
Obviously this is just a feature-request which I suspect is probably not a very popular one, but I am a bit addicted to text-only interfaces and scriptability. I would personally love to see (in addition to the wxwindows GUI) a highly configurable/hookable TUI interface for CM (like mutt/pine/etc for email, & lynx/w3c/etc for web) come out one day. Aside from the obvious reasons (security, bandwidth-savings), I find that sticking to text-and-attachments-only as much as possible is a good technique for staying focused when working (messages load/render faster, less eye-candy to navigate in order to read the actual content, less chance of hitting bugs, etc).

You would like the sender to be able to set plaintext only?

Yes. I do that with my email clients.

The next version of CM is going to display text-only in case of a bad signature or key collision. I am somewhat worried about an exploit in wx.RichTextCtrl being the easiest way to attack someone via CM.

You would also like the receiver to be able to set a menu option and have the double-click action default to open text only?

Yes. I do that with my email clients too. Also, when I subscribe to mailing lists the first thing I do is set "text-only digests".

Right now there are three types: text, HTML, and Rich Text XML as supported by wx. The HTML is there for future compatibility, as I would like CM to use HTML for its rich text someday. At the moment there is no good editor available.

The message is a ZIP file with the text, html, and xml formats as separate files inside the ZIP.

...so are attachments handled as separate files (from the message-content) within the zip archive? I presume they are not encoded into the html/xml content itself, considering you have stated you've successfully sent/received 4GB attachments..? If attachments are entirely possible with plaintext messages, then my request is "enthusiastic". If plaintext excludes attachments then it would still be worth having as an option, but much less likely to be used often.

Mike

  • Administrator
  • Full Member
  • *****
  • Posts: 105
    • View Profile
Re: It would be nice to be able to select plaintext when composing
« Reply #3 on: September 20, 2017, 07:45:11 pm »
Yes, the attachments are files in the zip archive preceded by an underscore. The underscore is removed when you extract the attachment. It is also possible to forward a message with the original sender signature intact, by adding the message zip and sig into the outer zip. There is a spec PDF on the download page that fully explains the format and protocol. You seem to be into this stuff, so please post your opinions.

I have had an email exchange with one well-known open source guru, and that's exactly what he wanted: a scriptable toolkit. It's possible but would require something more complex than command line invocation. I am not sure what the best type of interface to provide is. CM is already divided into a client agent and a GUI, and I have several automatic clients which drive the client agent. One of those is a mailing list server, and another is a file server.

I can definitely add a "show me text by default" option, and all messages are required to contain text. HTML and XML are optional.