[MlMt] Default columns not honored, asking again....

[Benny Kjær Nielsen]

On 29 Jun 2017, at 19:45, Helen Holzgrafe wrote:

> Thanks for the info. Already knew and regularly use the command line 
> you referenced. For me it only lasts about three weeks and then I have 
> to do it over again. Very annoying.

If it's any consolation I do consider this an Achilles' heel of 
MailMate. It varies a lot whether or not users are affected by the 
issues of saving/restoring mailbox column states, but those who are 
affected generally find it very annoying.

> Also, I did not know Junk mail was designed not to be readily 
> changeable. That's the one I need most to have my default columns.

Just to make sure. Note that “Use as Default Columns” tells MailMate 
what the global default should be. Changing the columns of the 
“Junk” mailbox should be sufficient to make it stick (disregarding 
bugs). It should also be automatically inherited by the submailboxes of 
Junk if no explicit changes have been made to them.

> I get more than a thousand junk mails a day. I have to hand sort them 
> to find those that are really junk and those that are from new 
> customers, or people that are in my contacts list that get their mail 
> sent to Junk randomly for some reason that particular day. That's 
> another weirdness I should ask about, but that's a different topic.

MailMate itself *only* moves messages to Junk if told to do so by 
SpamSieve (if that is installed and enabled).

> The standard columns are inadequate for fast visual scanning for 
> things like attachments. I rely heavily on "Spamsieve Score" and "Spam 
> score" also.  I am still trying to figure out why some messages with 
> very low scores still end up in Junk.

If you like then we can debug that off list. If it was server-side junk 
filtering then they shouldn't get a SpamSieve score at all unless you 
have enabled SpamSieve for more than Inbox messages. Note that the other 
“Spam Score” column is based on values added to the email by 
server-side spam identification.

> I gather that there is no way for me to get "use as default columns" 
> and "revert to default columns" as keyboard short cuts, either to make 
> dealing with this problem a bit easier.

You can probably bind keys to the following using custom key bindings:

	useAsDefaultColumns:
	revertToDefaultColumns:

But I don't promise that they'll continue to exist when I (finally) get 
around to refactoring how all of this works.

>>> Can I change the "real mailmate default columns" to be the ones I 
>>> want permanently somehow deep inside the secret command zone of 
>>> Mailmate?

Well, low-level you can, but you risk getting bitten by future changes 
to MailMate since your file is going to “shadow” the default one. 
This is the file you should copy:

	MailMate.app/Contents/Resources/standardMailboxes.plist

This is where you should put it:

	~/Library/Application\ Support/MailMate/Resources/

Then edit it and look for `defaultState` for the Junk mailbox. You can 
then change the set of columns enabled by default. You find the column 
names in the `outlineColumns.plist` file which is in the same MailMate 
folder as described above.

(I have not tested this. You probably need to clear 
`MmMailboxRelatedStates`.)

I hope this can ease some of the pain involved with column states.

-- 
Benny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freron.com/pipermail/mailmate/attachments/20170704/2736965d/attachment-0001.html>