<div class="markdown">
<p>On 21 Mar 2012, at 14:18, David Vereschagin wrote:</p>
<blockquote>
<blockquote>
<p>The new thing is that the <code>To</code> header is also pre-filled if there is a <code>List-Post</code> header available in the current context.</p>
<p>How to change this behavior [...]</p>
</blockquote>
<p>So, if I'm understanding this correctly, I can turn off the derivation of the "To" address by turning off the derivation of the "From" address. Since I like MailMate deriving the "From" address, and now that I have a better understanding of how this works, I'll just be a little more careful.</p>
</blockquote>
<p>I have disabled the pre-filled <code>To</code> header in the latest test version of MailMate. It can be fetched by holding down ⌥ when clicking “Check Now” in the Software Update preferences pane. <strong>Warning to everyone:</strong> It is fine to do this when asked to do so, but in general, a test version can be anything. It can be unstable, slow, write out tons of debug output, etc. It is often a version of MailMate made to debug a single issue for a single user. That said, the current version should be fine.</p>
<p>I have also disabled the existing derivation of the <code>From</code> header, but this has been replaced by something else. The main idea is to replace the black box heuristic by an explicit setting. This also makes it an opt-in feature. I would appreciate feedback on this from anyone relying on <code>From</code> header derivation. The following is the release notes of the test version. (I know the description of the new feature should be improved.):</p>
<hr>
<p>Derivation of the <code>From</code> address for replies has been changed. Until now it has been based on a heuristic using the <code>X-Original-To</code> header and others, but examples from users have shown that this approach is a dead end. This heuristic has now been disabled. The replacement is an optional account setting named “Address Pattern” which is disabled by default. The value for this option is a regular expression which describes the format of any aliases for the account. For example, I can use the following pattern for <code>freron.com</code>: <code>"mm-.*@freron\.com"</code>. When replying to a message MailMate scans various delivery related headers (such as <code>X-Original-To</code>) and if anything matches the pattern then it is used for the <code>From</code> address. This happens after checking for addresses matching any explicitly defined addresses in “Email Address(es)” in the account settings.</p>
<p>Introduced <code>makeFirstResponder:</code> for key bindings. It can be used to bind a key to directly activate a view. The identifiers for the views can be found in the layout files. Here is an example for binding <code>m</code> to activate the message view:</p>
<pre><code>"m" = ( "makeFirstResponder:", "messageView" );
</code></pre>
<p>Other changes:</p>
<ul>
<li>Improved headers editor for recipient addresses in the composer. Previously, multiple tokens were created if pasting text in the middle of an existing token or if tab'ing when the cursor was in the middle of an existing token.</li>
<li>IMAP mailbox states are now cached. This makes scrolling in the mailboxes outline smoother. (Still work in progress.)</li>
<li>Now bounces “Download” folder instead of opening it when saving an attachment.</li>
<li>Fixed “Edit ▸ Find ▸ Mailbox Search” menu item. It now works correctly when selected using the mouse (previously it switched to “All Messages”).</li>
</ul>
<hr>
<p>I won't be able to reply to messages until Sunday afternoon, so be patient if the test version does not work for you. Go back to <a href="http://updates.mailmate-app.com/archives/MailMate_r2802.tbz">r2802</a> if you have any serious problems.</p>
<hr>
<p>Benny</p>
</div>