<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<style>
div.markdown { white-space: normal; }
body { font-family: sans-serif; }
h1 { font-size: 1.4em; }
h2 { font-size: 1.2em; }
h3 { font-size: 1.1em; }
blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #3983C4; color: #3983C4; }
blockquote blockquote { border-left-color: #7CBF0C; color: #7CBF0C; }
pre { margin-left: 15px; margin-right: 15px; padding: 5px; border: thin solid gray; overflow-x: auto; max-width: 90vw; }
div.footnotes li p { margin: 0.2em 0; }
</style>
</head>
<body>
<div class="markdown">
<p dir="auto">Benny,</p>
<p dir="auto">A gentle nag about a feature we discussed below.</p>
<p dir="auto">Marc</p>
<p dir="auto">On 19 Feb 2016, at 18:18, Marc ARC wrote:</p>
<blockquote>
<p dir="auto">On 16 Feb 2016, at 11:15, Benny Kjær Nielsen wrote:</p>
<blockquote>
<p dir="auto">On 12 Feb 2016, at 17:59, Marc DR wrote:</p>
<blockquote>
<p dir="auto">example:</p>
<pre><code>[From] [is in] [Info ▸ Marketing_Confirmed] [From]
[Move to Mailbox] [Info ▸ Marketing_Auto]
</code></pre>
<p dir="auto">Please do note that I do not move to the Mailbox_Source because this allows me to see what has been add recently.<br>
I think I could achieve an identical result by tagging the "fresh" mails before moving and untagging them after verification ( or vice versa ), which is "easier" for you to implement. :-))</p>
</blockquote>
<p dir="auto">I think that would also be a nicer way to handle that.</p>
<blockquote>
<p dir="auto">I think GUI-wise the "new-move" version could look like this</p>
<pre><code>[From] [is in] [Mailbox/SmartMailbox] [From]
[Generic Move to first matched Source Mailbox of] [Mailbox/SmartMailbox]
or
[Dynamic Move to first matched Source of] [Mailbox/SmartMailbox]
or
[Fuzzy Move to Source of] [Mailbox/SmartMailbox]
</code></pre>
<p dir="auto">Just some ideas and have a nice WE,</p>
</blockquote>
<p dir="auto">I think this illustrates that it's hard to make such a feature intuitive. A better (and cleaner) approach would be to make the action independent of the conditions. The action could then be something like:</p>
<pre><code>Move to Related Mailbox based on [Header] in [Mailbox]
</code></pre>
</blockquote>
<p dir="auto">Benny,</p>
<p dir="auto">When [Header] means the actual functionality we have for filtering on “header contained info” then this will be a great feature.</p>
<blockquote>
<p dir="auto">The “Mailbox” could be any smart or IMAP mailbox/account. It would trigger MailMate to look for the first message in Mailbox with the same header value. When found, the new message would be moved to the same IMAP mailbox as the found message. It would be like an IMAP mailbox variant of the Submailboxes feature for smart mailboxes.</p>
<p dir="auto">This would allow a worst case near-linear running time if a large number of messages are “moved” (linear in terms of the size of the mailbox used in the action).</p>
<p dir="auto">Note that in this case there would be no need for a condition for the rule except for maybe limiting the messages triggering the action.</p>
<p dir="auto">A somewhat related feature would allow simply creating IMAP mailboxes based on a header value:</p>
<pre><code>Move to Submailbox of [IMAP Mailbox/Account] based on [Header]
</code></pre>
</blockquote>
<p dir="auto">This would be a nice to have, and I already see some use for it.<br>
From a “what I like to have first” point-of-view this is last on my list.</p>
<p dir="auto">Thanks</p>
<p dir="auto">Marc</p>
</blockquote>
</div>
</body>
</html>