On 26 Jan 2012, at 12:29, Ross Paterson wrote: > Not sure how this works, but have just switched to Mailmate.
Thanks for choosing MailMate. > 2 questions: > 1. I like to create subfolders to store different kinds of emails, but > that does not seem to work with the smartfolder system. e.g. emails of > a certain category kept in a subfolder. Any clues? Smart folders are not real folders. They are views of the messages in the real mailboxes in your IMAP accounts. You can create a hierarchy of real mailboxes in one your of your IMAP accounts (under SOURCES) and you can then either use drag'n'drop to move messages into them or use ??T. Personally, I just archive messages using ?Move to Archive? and the messages are then moved into an IMAP mailbox named Archive within the same account. If I need to see a special set of messages I most often search (or create a smart mailbox). With respect to smart mailboxes, it can be useful to mark messages using ?Mark as Flagged?. It is also possible to use [custom key bindings][1] to introduce other tags (there is currently no GUI for that, but IMAP keywords are supported). An advanced example of the use of a smart mailbox (and tagging) can be seen [here][2]. The example shows how to easily keep track of whether or not you have received replies to messages for which you are waiting for replies. [1]: http://manual.mailmate-app.com/custom_key_bindings#special_actions [2]: http://freron.lighthouseapp.com/projects/58672/tickets/224 > 2. I cannot get an html email (with graphics etc) to forward as that, > as all seem just plain text when forwarded. Any clues? MailMate (and I) are not so fond of HTML emails. The composer can only handle plain text although recently it also supports [Markdown][3] for generating HTML emails (but you probably knew that): [3]: http://manual.mailmate-app.com/preferences#markup_support You can ?Message ? Forward as Attachment? to forward the original message as you received it. In all other cases MailMate prefers the plain text alternative if available in the message. I have no plans to make an HTML composer, but I may introduce a HTML ? Markdown transformation to handle some use cases better. (I hope you are not too disappointed with that answer.) (Off-topic: Your message and my reply are good examples of when Markdown fails to work as intended. It is impossible to split up an auto-enumerated list in a reply without ruining the enumeration. This is one of several examples which makes it desirable to define and implement a Markdown variant designed for email usage.) -- Benny