Re: [MlMt] composer window placement

2016-08-01 Thread John D. Muccigrosso
Should have added that this happens with messages I’m reading too. 
Same feeling about it.


John
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate


[MlMt] composer window placement

2016-08-01 Thread John D. Muccigrosso
New-message windows in MM2 seem to get placed a little right and lower 
than the previous one, until one gets as far right and down as possible 
and then they stay there. Makes me think they’re going off-screen. 
I’d prefer MM2 to remember where I placed one the last time and always 
use that. Or at least restart the placement (as I think Mail.app does).


Thanks.

John
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate


[MlMt] Why Is Source Code Pro An Unknown Font?

2016-08-01 Thread Hans Trygve Jensen

Dear Benny and other geniuses on the MailMate Users List,

Out of curiosity, I decided to launch MailMate via iTerm2/Terminal the 
other day. I hadn’t experienced any particular problems and just 
wanted to see if any warnings or error messages popped up.


However, something did show up. Every time I select a message, both read 
and unread, the following kind of warning appears in the command line:


MailMate[29971:472156] Warning: Unknown font “SourceCodePro”

Every line is preceded by date and time.

I do use the font “Source Code Pro” in plain text messages and have 
set the font by way of the “Fonts” panel available in the 
“Format” menu, not via any CSS files in MailMate’s folders in 
Application Support. I’ve selected “Source Code Sans” with a 
similar approach to set preferred font for the message list columns and 
the mailbox sidebar. (I’ve opted for the Widescreen layout.) And, yes, 
both fonts show up as the one’s I’ve picked.


My questions are these:

1. Why is “SourceCodePro” considered an unknown font?
2. Why is it labeled as one word (not as “Source Code Pro”)?

I’m running MailMate 1.9.4 (5234) with “Experimental 2.0 Features” 
enabled. My Mac OS X version is 10.11.6.


Nice if anyone can clarify the matter. Thanks!

--
Hans Trygve Jensen | p...@htjensen.no
Sail With The Arts | web: htjensen.no
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate


Re: [MlMt] Updating account information made MailMate (re)download *all* email

2016-08-01 Thread Sherif Soliman



On 1 Aug 2016, at 6:01, Benny Kjær Nielsen wrote:


On 28 Jul 2016, at 2:37, Sherif Soliman wrote:

[FastMail issues]

What I chose to do is to start with a fresh install of MailMate. I 
kept a copy of my keybindings file and `Tags.plist`, removed 
everything else, and set everything up from scratch. I haven't had 
any issues since.


I'm glad it works given that I didn't provide much help. Thanks for 
the updates (and warning for other users).


Now, I'll try to analyze what happened.

You wrote:

I put in the new password and changed the server names from the old 
`mail.messagingengine.com` to `.fastmail.com`.


I'm pretty sure MailMate displays a warning at this point. This is 
because you have to be absolutely sure that MailMate is still looking 
at the exact same account. Otherwise, the mapping between local emails 
and server emails might be incorrect which could, e.g., lead to 
deleting a message locally which maps to a different message on the 
server. (This is not very likely to happen due to what follows below, 
but some servers have a somewhat primitive use of `UIDVALIDITY` often 
reusing values between user accounts.)




Yes, I remember seeing that warning. I read its meaning as you just 
described it: make sure this is the same account as it was before 
because if MailMate authenticates and finds different messages than what 
it had before, it will download them and delete the old ones, and 
generally do whatever it needs to do to reflect the new reality it finds 
on that server.


Now, it looks like this should be ok with FastMail, but then it seems 
something else happened. The redownloading of emails indicate that the 
`UIDVALIDITY` value changed of each mailbox. Each email is uniquely 
identified using the `UIDVALIDITY` of the mailbox and the `UID` of the 
message. If the `UIDVALIDITY` value of a mailbox changes then MailMate 
MUST delete its local cache of emails and then fetch the “new” 
messages of the mailbox. There is no way to tell MailMate to ignore 
`UIDVALIDITY` changes.


Hmm, MailMate should also warn you when the latter happens which makes 
me think that this might be a MailMate bug after all. I have a 
FastMail test account and I'll note to test what happens when I do as 
you describe. Sorry about the inconvenience if this turns out to be a 
bug.




I did not see any other warnings besides that first one.

Sherif
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate


[MlMt] Syncing SmartBox synchronous between two hosts

2016-08-01 Thread Tobias Matthaeus

Hello everyone,



I am trying to use MailMate and I really like the SmartBox feature. But 
I have a problem: I have two machines, and would really like to have the 
SmartBoxes synchronous between this both hosts…



This is possible with copying the file Mailboxes.plist into ownCloud and 
symlink it to the ~/Library/Application Support/Mailboxes.plist file. 
But after changing a SmartBox the Mailboxes.plist file is a complete new 
file. The symlink will be overwritten with the new file and this ends in 
the situation that both machines are not synchronous in SmartBoxes 
anymore.



Do you have any idea for me?



Thanks and regards




Tobias
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate


Re: [MlMt] scripts/rules not taking effect...?

2016-08-01 Thread Benny Kjær Nielsen

On 28 Jul 2016, at 23:26, Seebs wrote:

So I have some rules, which appear to work. And I have other rules, 
which... don't seem to. And I am not sure what I'm missing. But I 
vaguely recall there having been an option for turning on logging so I 
could see more information about rules.


As an example, consider the script MoveMlmt.mmCommand:


This is in the resources Script folder? I'm likely to deprecate that 
eventually.



{
name= 'Move Mlmt';
events  = ( 'account.synchronized' );
select  = "subject =[c] '[MlMt]'";
actions = ( { type = moveMessage; mailbox = mlmt; },
  { type = changeFlags; enable = ( '\\Seen' ); disable = ( ); 
},

  );
}

The intent is to move things from this list automatically into a 
mailbox,
and mark them as seen. (Okay, maybe not a great plan, given that I 
presumably want to see responses to this, but it's a good example.)


:) You should click on the Inbox and use “Mailbox ▸ Edit Mailbox” 
and then switch to the Rules pane. Then setup your condition and actions 
in a rule. Then let me know if that also doesn't work. This condition is 
also more exact: “Subject ▸ Blob is "MlMt"”. Although basing it on 
the `List-ID` header would be even better. Note that creating a smart 
mailbox makes it easier to play around with conditions matching the 
expected messages.


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


Re: [MlMt] enhancement, I think

2016-08-01 Thread Benny Kjær Nielsen

On 25 Jul 2016, at 13:55, Patrik Fältström wrote:


On 25 Jul 2016, at 11:54, Mike Brasch wrote:

As long a syncing mechanism uses local folders for syncing (like 
Dropbox, Bittorrent Sync and some others) MailMate could copy the 
relevant data to such a folder. This way users can use their 
preferred syncing service.


+1

MailMate should be able to detect whether the file has changed, and in 
that case re-read its new configuration, and when saving, it just 
saves the new config waiting for the service to propagate it to other 
units.


I'll just end this thread with a couple of comments:

* The discussion quickly turned into “which cloud service”, but this 
is just a technicality (and I still think IMAP itself is the best 
choice). The challenge is not how to synchronize the mailboxes file, 
it's how to gracefully handle any order and timing of changes to this 
file on multiple machines.
* The above file oriented behavior, as described by Patrik, is 
essentially what is needed for synchronization to work.


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


Re: [MlMt] Updating account information made MailMate (re)download *all* email

2016-08-01 Thread Benny Kjær Nielsen

On 28 Jul 2016, at 2:37, Sherif Soliman wrote:

[FastMail issues]

What I chose to do is to start with a fresh install of MailMate. I 
kept a copy of my keybindings file and `Tags.plist`, removed 
everything else, and set everything up from scratch. I haven't had any 
issues since.


I'm glad it works given that I didn't provide much help. Thanks for the 
updates (and warning for other users).


Now, I'll try to analyze what happened.

You wrote:

I put in the new password and changed the server names from the old 
`mail.messagingengine.com` to `.fastmail.com`.


I'm pretty sure MailMate displays a warning at this point. This is 
because you have to be absolutely sure that MailMate is still looking at 
the exact same account. Otherwise, the mapping between local emails and 
server emails might be incorrect which could, e.g., lead to deleting a 
message locally which maps to a different message on the server. (This 
is not very likely to happen due to what follows below, but some servers 
have a somewhat primitive use of `UIDVALIDITY` often reusing values 
between user accounts.)


Now, it looks like this should be ok with FastMail, but then it seems 
something else happened. The redownloading of emails indicate that the 
`UIDVALIDITY` value changed of each mailbox. Each email is uniquely 
identified using the `UIDVALIDITY` of the mailbox and the `UID` of the 
message. If the `UIDVALIDITY` value of a mailbox changes then MailMate 
MUST delete its local cache of emails and then fetch the “new” 
messages of the mailbox. There is no way to tell MailMate to ignore 
`UIDVALIDITY` changes.


Hmm, MailMate should also warn you when the latter happens which makes 
me think that this might be a MailMate bug after all. I have a FastMail 
test account and I'll note to test what happens when I do as you 
describe. Sorry about the inconvenience if this turns out to be a bug.


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