[MlMt] Porting a Thunderbird bundle for SafeLinks?
Hi, My employer decided in all their wisdom to enable Outlook SafeLinks. I despise those things and would really love to have my links (and privacy) back. There is already a Thunderbird bundle that has this functionality. https://github.com/phavekes/unmangleOutlookSafelinks/blob/master/src/display.js#L2 Now I’ve not made a MailMate bundle before, but have a little coding experience. Is there someone out there who’d be able to team up with me on this? Thanks! Jeroen. ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
[MlMt] Check for Test Build
Greetings List, I’ve come to realize that my ‘Check for Test Build’ in MM hasn’t been working in some time. I have done some manual checks and have updated and am running build 6024. When I hold the option key and ‘Check for Test Build’ in the MailMate menu, I get the following message “You are Using a Prerelease 5673 is the latest release available. You have version 6024. Downgrade to 5673 | OK” This is of course the same message whether I hold the option key and “Check for Test Build” or whether I don’t and just “Check for Update”. Is anyone else experiencing this? I have updated builds a couple times recently and this is still happening. I’m not sure when it started. Any suggestions appreciated. Best regards -- Verdon Vaillancourt ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Check for Test Build
On 4 Mar 2024, at 15:53, Verdon Vaillancourt wrote: > Greetings List, > > I’ve come to realize that my ‘Check for Test Build’ in MM hasn’t been working > in some time. I have done some manual checks and have updated and am running > build 6024. When I hold the option key and ‘Check for Test Build’ in the > MailMate menu, I get the following message > > “You are Using a Prerelease 5673 is the latest release available. You have > version 6024. Downgrade to 5673 | OK” > > This is of course the same message whether I hold the option key and “Check > for Test Build” or whether I don’t and just “Check for Update”. Is anyone > else experiencing this? I have updated builds a couple times recently and > this is still happening. I’m not sure when it started. Any suggestions > appreciated. Benny values stability above anything else and only updates the "test" releases when he's happy with the builds which he tends to provide for specific problems, though anyone can use download them from the website. Personally, I can't use anything > 5964 but at lease Benny's managed to replicate the bug. I think he released 6016 around the New Year. Charlie -- Charlie Clark Sengelsweg 34 Düsseldorf D- 40489 Tel: +49-203-746000 Mobile: +49-178-782-6226 ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Check for Test Build
Hi Verdon, This is a long standing reason that the developer Benny does not want to return to previous versioning methods. Contact him for a historical reasoning of why. There are three ways to check in MailMate for new builds of what used t be varying types, but not the latest. You spoke of two (MailMate Menu>check for new builds, ⌥ + Check for New Builds). There is also from the Menu>Mailmate>Settings…>Software Update. Unfortunately, none of these will show you ALL the versions available. The [Archive web site](https://updates.mailmate-app.com/archives/) has every single version of M-M including the latest “Experimental Builds” and what I use as a relevant reference. The current version shown there is the release you apparently have found for the LKV (last known version, 1.14, r6024. It was published to the site dated 26FEB2024. They’ve been coming out regularly, sometimes a few days apart. I have a feeling therefore that a we’re due for a new one soon. So look there. Hopefully when Benny decides to move to a Test Build/Prelease/Release format of builds, then the updates will fit in to the previous plans. Meanwhile the suggestion was made here to use the archive for latest builds of a more experimental nature for the interim. Does that fill in the holes of the release numbering? Respectfully, Henry Seiden - - Techworks Pro Co. E: infotechworksprocom W: http://techworkspro.com On 4 Mar 2024, at 9:53, Verdon Vaillancourt wrote: I’ve come to realize that my ‘Check for Test Build’ in MM hasn’t been working in some time. I have done some manual checks and have updated and am running build 6024. When I hold the option key and ‘Check for Test Build’ in the MailMate menu, I get the following message “You are Using a Prerelease 5673 is the latest release available. You have version 6024. Downgrade to 5673 | OK” This is of course the same message whether I hold the option key and “Check for Test Build” or whether I don’t and just “Check for Update”. Is anyone else experiencing this? I have updated builds a couple times recently and this is still happening. I’m not sure when it started. Any suggestions appreciated.___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Check for Test Build
Thanks Henry and Charlie, I didn’t realize that was by design. I thought the “Check for Test Builds” would show me the most recent build. I’ll just visit the updates site to look for new builds, as part of my daily habit now. Best regards, V On 4 Mar 2024, at 10:17, Henry Seiden wrote: > Hi Verdon, > > This is a long standing reason that the developer Benny does not want to > return to previous versioning methods. Contact him for a historical reasoning > of why. > > There are three ways to check in MailMate for new builds of what used t be > varying types, but not the latest. You spoke of two (MailMate Menu>check for > new builds, ⌥ + Check for New Builds). > > There is also from the Menu>Mailmate>Settings…>Software Update. > Unfortunately, none of these will show you ALL the versions available. > > The [Archive web site](https://updates.mailmate-app.com/archives/) has every > single version of M-M including the latest “Experimental Builds” and what I > use as a relevant reference. The current version shown there is the release > you apparently have found for the LKV (last known version, 1.14, r6024. > > It was published to the site dated 26FEB2024. They’ve been coming out > regularly, sometimes a few days apart. I have a feeling therefore that a > we’re due for a new one soon. So look there. > > Hopefully when Benny decides to move to a Test Build/Prelease/Release format > of builds, then the updates will fit in to the previous plans. Meanwhile the > suggestion was made here to use the archive for latest builds of a more > experimental nature for the interim. Does that fill in the holes of the > release numbering? > > Respectfully, > > Henry Seiden > - - > Techworks Pro Co. > E: infotechworksprocom > W: http://techworkspro.com > > On 4 Mar 2024, at 9:53, Verdon Vaillancourt wrote: > >> I’ve come to realize that my ‘Check for Test Build’ in MM hasn’t been >> working in some time. I have done some manual checks and have updated and am >> running build 6024. When I hold the option key and ‘Check for Test Build’ in >> the MailMate menu, I get the following message >> >> “You are Using a Prerelease 5673 is the latest release available. You have >> version 6024. Downgrade to 5673 | OK” >> >> This is of course the same message whether I hold the option key and “Check >> for Test Build” or whether I don’t and just “Check for Update”. Is anyone >> else experiencing this? I have updated builds a couple times recently and >> this is still happening. I’m not sure when it started. Any suggestions >> appreciated.___ > mailmate mailing list > mailmate@lists.freron.com > https://lists.freron.com/listinfo/mailmate -- Verdon Vaillancourt ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Check for Test Build
On 4 Mar 2024, at 16:24, Verdon Vaillancourt wrote: > Thanks Henry and Charlie, > > I didn’t realize that was by design. I thought the “Check for Test Builds” > would show me the most recent build. I’ll just visit the updates site to look > for new builds, as part of my daily habit now. Okay, but make sure you have backups! Charlie -- Charlie Clark Sengelsweg 34 Düsseldorf D- 40489 Tel: +49-203-746000 Mobile: +49-178-782-6226 ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Check for Test Build
That’s the joy of the archive — you can always download a previous version. -- Steve Sent from an iDevice > On Mar 4, 2024, at 10:31 AM, Charlie Clark wrote: > > Okay, but make sure you have backups! ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Check for Test Build
I've also noticed that there is an inconsistency between the different ways to check for updates. Here are the messages I see when checking for updates: ## 1. Settings → Software Update → Check Now 5937 is the latest version available. You have version 6022. ## 2. Settings → Software Update → Check Now (holding *option*) 6016 is the latest version available. You have version 6022. ## 3. MailMate menu → Check for Update 5937 is the latest version available. You have version 6022. ## 4. MailMate menu → Check for Test Build (holding *option*) 5937 is the latest version available. You have version 6022. #2 and #4 should display the same results, but they do not. I raised this issue in October 2023 but didn't get a response. Quinn___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Thread expansion logic?
On 2024-03-01 at 16:11:57 UTC-0500 (Fri, 01 Mar 2024 16:11:57 -0500) Glenn Parker is rumored to have said: You may already know this, or it may not be your preferred UI, but you can use Option-Right_Arrow to fully expand a collapsed thread. If you prefix that with Command-A to select all messages, you will fully expand every thread in a mailbox. I sometimes use this to “get the big picture” on a mailbox. I agree that there doesn’t seem to be a predictable logic for how threads are initially expanded, but I would not want threads with no unread messages to be expanded by default. Instead, I would like all unread messages to be directly visible in expanded threads. Right, that is what I meant: expand all threads that have unread messages should be expanded to make all unread messages visible. On 28 Feb 2024, at 11:57, Bill Cole wrote: Is it just me or is the logic controlling how MM expands threads incomprehensible? I mostly read mail in per-source submailboxes of a smart mailbox that aggregates threads with unread messages across subfolders of multiple accounts, including mostly non-INBOX sources. Much of the mail is mailing lists like this one, where threads are important. I have found that recent test builds (roughly: 59xx and 6xxx) have lost any discernible pattern in how threads are expanded in relation to unread messages. Often I go into a mailbox and find some threads expanded down to the first unread message, some fully collapsed despite having unread messages one or two levels down, and some expanded to reveal all unread messages. I do not see any UI that would help tune this in any way. My ideal behavior would be to have threads expanded by default to reveal any unread messages. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate Glenn P. Parker glenn.par...@comcast.net ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Thread expansion logic?
Bill, For me the toolbar expansion of threads in a folder seems to work OK. E.G. This is exposed when clicking the thread expose tool in the tool bar and hides all threading when the other tool is used. There are parts that don’t work as they should (sorting), though and I take your point on those. You didn’t indicate on settings how you have them and/or enable the threaded mode. Respectfully, Henry Seiden - - Techworks Pro Co. E: infotechworksprocom W: http://techworkspro.com On 28 Feb 2024, at 11:57, Bill Cole wrote: Is it just me or is the logic controlling how MM expands threads incomprehensible? I mostly read mail in per-source submailboxes of a smart mailbox that aggregates threads with unread messages across subfolders of multiple accounts, including mostly non-INBOX sources. Much of the mail is mailing lists like this one, where threads are important. I have found that recent test builds (roughly: 59xx and 6xxx) have lost any discernible pattern in how threads are expanded in relation to unread messages. Often I go into a mailbox and find some threads expanded down to the first unread message, some fully collapsed despite having unread messages one or two levels down, and some expanded to reveal all unread messages. I do not see any UI that would help tune this in any way. My ideal behavior would be to have threads expanded by default to reveal any unread messages. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Thread expansion logic?
On 2024-03-04 at 16:16:13 UTC-0500 (Mon, 04 Mar 2024 16:16:13 -0500) Henry Seiden is rumored to have said: Bill, For me the toolbar expansion of threads in a folder seems to work OK. I was exclusively referring only to the way threads in a message list pane are expanded by MM when I first enter a mailbox. No toolbar involved. "Organize by Thread" always on, or the question would be insane. E.G. This is exposed when clicking the thread expose tool in the tool bar and hides all threading when the other tool is used. Your toolbar must be radically different than mine, I have nothing that is clearly a thread expand tool or anything that I would naturally consider the 'other one' but that's fine because I wasn't referring to how widgets expanded threads. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
