Re: [MlMt] Notify on reply

2014-09-19 Thread Benny Kjær Nielsen

On 19 Sep 2014, at 6:14, Jeremy Cowgar wrote:

I wrote a post with instructions and screen shots showing how I 
accomplished this process.


http://jeremy.cowgar.com/2014/09/18/mailmate-waiting-on-reply/

I would be very interested in any improvements, ideas or comments on 
the process. I'll be happy to edit/update the post with the community 
making things better.


Great post!!

Here are my comments:

* Instead of `Thread-ID` you might want to use `“In-Reply-To” is in 
“Waiting on Reply” “Message-ID”`. Otherwise I think you get into 
trouble when waiting on a reply in a longer thread.
* Maybe the mailbox should be named “Received Replies” since it 
contains the replies and not the original messages.
* Note that given “Received Replies” you can easily add a counter in 
the Counters preferences pane and get a dock/menu-count or 
sound/notification when a reply arrives (sounds can also be done using 
rules and eventually notifications are also going to be available via 
rules).
* A variant of this system is to add a condition to “Waiting for 
Reply” to only display messages older than X days. This would allow 
you to see messages for which you might need to remind the recipient 
that you are still waiting for a reply (please don't use that against me 
;-) ).


Alternative idea (which might not be much better):

You can add a smart mailbox based on “Waiting for Reply” with the 
reversed condition: `“Message-ID” is in “Inbox” 
“In-Reply-To”`. Then add a rule to this mailbox with an archive 
action (no conditions). It'll always be empty, but it'll take care of 
moving waiting messages to your archive. But this breaks the “Received 
Replies” mailbox and I think the best way to fix that is to also add a 
“HasReply” tag to the archived message. Then base the other mailbox 
(Received Replies) on Inbox messages for which the parent has this tag. 
Hmm, that might require another smart mailbox -- well, I wrote this 
might not be much better :-)


--
Benny
___
mailmate mailing list
mailmate@lists.freron.com
http://lists.freron.com/listinfo/mailmate


[MlMt] Sharing my current key bindings

2014-09-19 Thread Kee Hinckley
I have a bunch of key bindings for mass selection and deletion of mail 
messages. The deletion ones can be rather dangerous, so sometimes I just 
use the selection ones and then hit delete (or file, or whatever is 
appropriate).


(I also have an action that sends me a Growl notification of the 
subjects and number of messages deleted if I delete more than a few, 
that's useful for when I accidentally go overboard. I can upload that if 
people are interested.)


The selection ones are particularly useful now that I'm using the 
recently shared modification that adds an extra pane showing the 
selected messages and (in my case) everything else with the same 
subject. It makes it far easier to see what I just selected.


Of those, I probably use t, i, s, and f most often. 'dt' is great for 
nuking a conversation you are done with. 'di' is good for deleting just 
the conversation in your inbox, but not the items you've filed already 
(e.g. you filed that useful post to MailMate, but you want to delete all 
the replies). 'ds' is good for when threading isn't capturing 
everything, or it's a bunch of automated messages with the same subject. 
And 'df' is great for email notifications from online services (a dozen 
messages from a store about new products).


In any case, here they are if anyone would like to try them. If you 
haven't modified keybindings, they go in 
`~/MailMate/Resources/KeyBindings/Kee.plist` and then you'd set your 
Custom Key Bindings in preferences to 'Kee'.


Thanks to all the other MailMate users who made it possible to build 
these. And of course, our favorite developer!


```json
{
// r = ( replyAll:, selectAll:, decreaseQuoteLevel:, 
deselectAll:, moveToBeginningOfDocument:, insertNewline:, 
insertNewline:, moveToBeginningOfDocument: );

r = ( addTag:, HTMLReply, replyAll: );
c = collapseThread:;
e = expandThread:;
j = nextMessage:;
k = previousThread:;
n = nextUnreadMessage:;
p = previousUnreadMessage:;
J = ( markAsNotJunk:, removeTag:, \\Seen, 
moveToMailbox:,'INBOX');


// delete commands
d = {
// Delete entire thread
t = ( selectThread:, deleteMessage: );
// Delete the thread in the inbox, but leave filed items 
alone
i = ( selectWithFilter:, #thread-id = 
${#thread-id} and #source.path = 'INBOX', deleteMessage: );

// Delete thread except mail that was mine (I sent)
m = ( selectWithFilter:, #thread-id = ${#thread-id} 
and #source.path != 'Sent Messages' and #source.path != 'Sent Items', 
deleteMessage: );

// Delete thread except the stuff in inbox or sent (other)
o = ( selectWithFilter:, #thread-id = 
${#thread-id} and #source.path != 'INBOX' and #source.path != 'Sent 
Messages' and #source.path != 'Sent Items', deleteMessage: );

// Delete the subject
s = ( selectWithFilter:, subject = '${subject}', 
moveToMailbox:, trash );

// Delete by from address
f = ( selectWithFilter:, from.address = 
'${from.address}', moveToMailbox:, trash );

// Delete any mail to this recipient
r = ( selectWithFilter:, #recipient.address = 
'${#recipient.address}', moveToMailbox:, trash );

};

// select commands (good if you aren't sure what the delete in 
thread action is going to do!)

s = {
// Select an entire thread
t = selectThread:;
// Select just the items in the thread that are in my 
inbox, leaving filed messages alone
i = ( selectWithFilter:, #thread-id = 
${#thread-id} and #source.path = 'INBOX' );

// Select thread except mail that was mine (I sent)
m = ( selectWithFilter:, #thread-id = 
${#thread-id} and #source.path != 'Sent Messages' and #source.path != 
'Sent Items' );

// Select thread except the stuff in inbox or sent (other)
o = ( selectWithFilter:, #thread-id = 
${#thread-id} and #source.path != 'INBOX' and #source.path != 'Sent 
Messages' and #source.path != 'Sent Items' );

// Select the subject
s = ( selectWithFilter:, subject = '${subject}' 
);

// Select by from address
f = ( selectWithFilter:, from.address = 
'${from.address}' );
// Select any mail to this recipient (warning, I've had 
this crash MailMate)
r = ( selectWithFilter:, #recipient.address = 
'${#recipient.address}' );


//m = ( selectWithFilter:, #thread-id = 
${#thread-id} and #source.mailto !=[x] \\$SENT.source.mailto );
// m = ( selectWithFilter:, #thread-id = 
${#thread-id} and from.address !=[x] \\$SENT.from.address );


};

// FROM SOMEONE c = ( showThread:, showCorrespondence );

// Editing commands
// bold selection
@b = (selectWord:, setMark:, swapWithMark:, deleteToMark:, 
insertText:, 

Re: [MlMt] insertFormatString... ${} expansions listed somewhere?

2014-09-19 Thread Kai Großjohann

On 19 Sep 2014, at 11:21, Benny Kjær Nielsen wrote:


On 18 Sep 2014, at 21:48, Kai Großjohann wrote:

Actually, I find that the Outlook threading is better than I had 
feared.  It actually works pretty well for a linear thread like 
this one (the one I'm responding to):


I think I should add here that I was talking about the Outlook threading 
more than the message content.  I found it pretty cool that Outlook 
collapsed sequences of replies into one message, and only displayed 
extra messages on every fork.


About the content, read on...

For the record, for me top/bottom posting is not just about the 
ordering. Top posting is a “lazy” reply style in the sense that it 
encourages adding a comment to the top of the email leaving it to the 
recipient to figure out what is commented.


Yeah.  I take pains to reiterate the points, leading to things like on 
item 3.  It's not as friendly as just quoting the relevant bit of the 
email, as I'm doing here.


And don't we all love those responses that say Please see my replies 
below in orange.


Oh well.  When in Rome, it seems I try to do as the Romans do...

Kai
___
mailmate mailing list
mailmate@lists.freron.com
http://lists.freron.com/listinfo/mailmate


Re: [MlMt] insertFormatString... ${} expansions listed somewhere?

2014-09-19 Thread Kee Hinckley


 On Sep 19, 2014, at 4:20 PM, Kai Großjohann kai.grossjoh...@gmail.com wrote:
 
 And don't we all love those responses that say Please see my replies below 
 in orange.

Don't get me started. OTOH, a few times I've tried to do inline replies, and 
the had to go to someone's desk to explain which parts were mine. I assumed 
user error until I saw how badly Outlook had slaughtered them. I no longer 
blame the users.
___
mailmate mailing list
mailmate@lists.freron.com
http://lists.freron.com/listinfo/mailmate