From tariqmi at gmail.com Mon Jun 2 16:36:19 2025 From: tariqmi at gmail.com (Tariq Magdon-Ismail) Date: Mon, 02 Jun 2025 13:36:19 -0700 Subject: [MlMt] Gmail and "Delete Immediately" Message-ID: When I use "delete immediately" to skip the trash and delete an email, it gets archived instead (still shows up in All Mail). I've tried the different Gmail IMAP settings but can't get the expected behavior. Does "delete immediately" work with Gmail for anyone else? Regards, -Tariq MailMate: Version 2.0 (6257) From info at techworkspro.com Wed Jun 4 09:36:07 2025 From: info at techworkspro.com (Henry Seiden) Date: Wed, 4 Jun 2025 13:36:07 +0000 Subject: [MlMt] MailMate 2.0(r6260) Crash reported to Feedback Message-ID: <010001973b28023e-ff453704-7945-49f6-88b2-051060a29c80-000000@email.amazonses.com> Hello All, I’ve had a continuing issue with MM Crashing in my current setup. There seems to be two distinct issues causing failure. Firstly, the crash occurred for me as a shutdown of the app triggering a MacOS Crash Report. It started in r6257 first reported on 6/1/2025, seemingly triggered when messages are received in any source account with Network Framework enabled. The MacOS Crash report identified the crash as MailMate and the error in this case as, “NameSpace, code 6…” **Troubleshooting** Benny advised me to run the debug tool in MM and send in logs. He also advised to upgrade to r6259. R6259 did not affect the failure, which continued. Then, a r6260 was recommended. Was able to get the problem to recur and a version to try later was sent by Benny (r6260). A different result was noted clearly affecting MM. Seemed more repeatable by receipt of and processing by secondary drone setup of SpamSieve on another computer, and was shown in MacOS Crash Reports as “NameSpace, code 5…” This possibly related only to spam mail processing, not Network Framework settings. However this has not been proven. The debug log was sent showing a different result. Since then, I have downgraded all machines to the last most stable setup r6256, without Network Framework enabled. It seems that unless you have a similar setup to mine, you might not be affected by this situation. However, if you are affected similarly, please report that to aid Benny in his ongoing troubleshooting efforts. Good luck, Benny. Respectfully, Henry Seiden - - Techworks Pro Co. E: infotechworksprocom W: http://techworkspro.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglist at freron.com Wed Jun 4 10:12:39 2025 From: mailinglist at freron.com (=?utf-8?q?Benny_Kj=C3=A6r_Nielsen?=) Date: Wed, 04 Jun 2025 16:12:39 +0200 Subject: [MlMt] MailMate 2.0(r6260) Crash reported to Feedback In-Reply-To: <010001973b28023e-ff453704-7945-49f6-88b2-051060a29c80-000000@email.amazonses.com> References: <010001973b28023e-ff453704-7945-49f6-88b2-051060a29c80-000000@email.amazonses.com> Message-ID: <93FFA271-9F0B-428E-88DA-6799D3D15E3B@freron.com> On 4 Jun 2025, at 15:36, Henry Seiden wrote: > It seems that unless you have a similar setup to mine, you might not be affected by this situation. However, if you are affected similarly, please report that to aid Benny in his ongoing troubleshooting efforts. Note that I removed this release from the test release branch (the one you get when holding down ⌥), but it's still available via direct download: https://updates.mailmate-app.com/archives/ -- Benny From info at techworkspro.com Wed Jun 4 11:33:26 2025 From: info at techworkspro.com (Henry Seiden) Date: Wed, 4 Jun 2025 15:33:26 +0000 Subject: [MlMt] MailMate 2.0(r6260) Crash reported to Feedback In-Reply-To: <93FFA271-9F0B-428E-88DA-6799D3D15E3B@freron.com> References: <010001973b28023e-ff453704-7945-49f6-88b2-051060a29c80-000000@email.amazonses.com> <93FFA271-9F0B-428E-88DA-6799D3D15E3B@freron.com> Message-ID: <010001973b936a52-04a44e61-cea4-4af8-9826-f2147ba4ecb4-000000@email.amazonses.com> I had different crashes effective with versions since r6256-6259 as stated, even though those seemed different and related to Network Framework. So the default set up in r6256 currently works fine for me (as noted previously, that’s what is in use here). My system: MailMate/6256/OS15.5.0/arm64/MacBookPro18,3/10 Respectfully, Henry Seiden - - Techworks Pro Co. E: infotechworksprocom W: http://techworkspro.com On 4 Jun 2025, at 10:12, Benny Kjær Nielsen wrote: > On 4 Jun 2025, at 15:36, Henry Seiden wrote: > >> It seems that unless you have a similar setup to mine, you might not >> be affected by this situation. However, if you are affected >> similarly, please report that to aid Benny in his ongoing >> troubleshooting efforts. > > Note that I removed this release from the test release branch (the one > you get when holding down ⌥), but it's still available via direct > download: https://updates.mailmate-app.com/archives/ > > -- > Benny > _______________________________________________ > mailmate mailing list > Unsubscribe: https://lists.freron.com/listinfo/mailmate -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglist at freron.com Wed Jun 4 12:01:04 2025 From: mailinglist at freron.com (=?utf-8?q?Benny_Kj=C3=A6r_Nielsen?=) Date: Wed, 04 Jun 2025 18:01:04 +0200 Subject: [MlMt] MailMate 2.0(r6260) Crash reported to Feedback In-Reply-To: <010001973b936a52-04a44e61-cea4-4af8-9826-f2147ba4ecb4-000000@email.amazonses.com> References: <010001973b28023e-ff453704-7945-49f6-88b2-051060a29c80-000000@email.amazonses.com> <93FFA271-9F0B-428E-88DA-6799D3D15E3B@freron.com> <010001973b936a52-04a44e61-cea4-4af8-9826-f2147ba4ecb4-000000@email.amazonses.com> Message-ID: On 4 Jun 2025, at 17:33, Henry Seiden wrote: > I had different crashes effective with versions since r6256-6259 as > stated, even though those seemed different and related to Network > Framework. > > So the default set up in r6256 currently works fine for me (as noted > previously, that’s what is in use here). Ok, when you have time then please also try [MailMate_r6261.tbz](https://updates.mailmate-app.com/archives/MailMate_r6261.tbz) I'm not sure it fixes the issues you have had, but some new crash reports would be helpful. -- Benny -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at techworkspro.com Wed Jun 4 13:11:43 2025 From: info at techworkspro.com (Info@techworkspro.com) Date: Wed, 4 Jun 2025 17:11:43 +0000 Subject: [MlMt] MailMate 2.0(r6260) Crash reported to Feedback In-Reply-To: References: Message-ID: <010001973bed6528-cd4b2c8b-0c03-4f1e-963b-5b480aea15b6-000000@email.amazonses.com> An HTML attachment was scrubbed... URL: From info at techworkspro.com Wed Jun 4 15:23:55 2025 From: info at techworkspro.com (Henry Seiden) Date: Wed, 4 Jun 2025 19:23:55 +0000 Subject: [MlMt] MailMate 2.0(r6260) Crash reported to Feedback In-Reply-To: <010001973b28023e-ff453704-7945-49f6-88b2-051060a29c80-000000@email.amazonses.com> References: <010001973b28023e-ff453704-7945-49f6-88b2-051060a29c80-000000@email.amazonses.com> Message-ID: <010001973c666d7b-3d86c375-d861-4758-a190-8f5b528caf8c-000000@email.amazonses.com> Benny, Seems OK for now. If the testing goes well no failures for over a day or so, will try r6261 on my drone machine to verify it doesn’t quit either. I had downgraded both since the issue was occurs both machines when running r6260. Possible that 6260 also works now with your 03JUN2025 patches noted in Release Notes? Did not try it, though. Moving forward… Respectfully, Henry Seiden - - Techworks Pro Co. E: infotechworksprocom W: http://techworkspro.com On 4 Jun 2025, at 9:36, Henry Seiden wrote: > Hello All, > > I’ve had a continuing issue with MM Crashing in my current setup. > There seems to be two distinct issues causing failure. > > Firstly, the crash occurred for me as a shutdown of the app triggering > a MacOS Crash Report. It started in r6257 first reported on 6/1/2025, > seemingly triggered when messages are received in any source account > with Network Framework enabled. > > The MacOS Crash report identified the crash as MailMate and the error > in this case as, “NameSpace, code 6…” > > **Troubleshooting** > Benny advised me to run the debug tool in MM and send in logs. He also > advised to upgrade to r6259. > > R6259 did not affect the failure, which continued. Then, a r6260 was > recommended. Was able to get the problem to recur and a version to > try later was sent by Benny (r6260). > > A different result was noted clearly affecting MM. Seemed more > repeatable by receipt of and processing by secondary drone setup of > SpamSieve on another computer, and was shown in MacOS Crash Reports as > “NameSpace, code 5…” This possibly related only to spam mail > processing, not Network Framework settings. However this has not been > proven. The debug log was sent showing a different result. > > Since then, I have downgraded all machines to the last most stable > setup r6256, without Network Framework enabled. > > It seems that unless you have a similar setup to mine, you might not > be affected by this situation. However, if you are affected similarly, > please report that to aid Benny in his ongoing troubleshooting > efforts. Good luck, Benny. > > > Respectfully, > > Henry Seiden > - - > Techworks Pro Co. > E: infotechworksprocom > W: http://techworkspro.com > _______________________________________________ > mailmate mailing list > Unsubscribe: https://lists.freron.com/listinfo/mailmate -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglist at freron.com Wed Jun 4 15:25:56 2025 From: mailinglist at freron.com (=?utf-8?q?Benny_Kj=C3=A6r_Nielsen?=) Date: Wed, 04 Jun 2025 21:25:56 +0200 Subject: [MlMt] MailMate 2.0(r6260) Crash reported to Feedback In-Reply-To: <010001973c666d7b-3d86c375-d861-4758-a190-8f5b528caf8c-000000@email.amazonses.com> References: <010001973b28023e-ff453704-7945-49f6-88b2-051060a29c80-000000@email.amazonses.com> <010001973c666d7b-3d86c375-d861-4758-a190-8f5b528caf8c-000000@email.amazonses.com> Message-ID: <5DFEA1FD-0C43-486F-AC7E-AF5BD04EE355@freron.com> On 4 Jun 2025, at 21:23, Henry Seiden wrote: > Seems OK for now. If the testing goes well no failures for over a day or so, will try r6261 on my drone machine to verify it doesn’t quit either. I had downgraded both since the issue was occurs both machines when running r6260. > > Possible that 6260 also works now with your 03JUN2025 patches noted in Release Notes? Did not try it, though. Moving forward… Neither r6260 or r6261 fixes the bug I think was the main problem (related to, e.g., an INBOX being emptied on a different machine -- which could also explain the drone-spam-detection triggering the issue). -- Benny From info at techworkspro.com Wed Jun 4 15:28:04 2025 From: info at techworkspro.com (Henry Seiden) Date: Wed, 4 Jun 2025 19:28:04 +0000 Subject: [MlMt] MailMate 2.0(r6260) Crash reported to Feedback In-Reply-To: <5DFEA1FD-0C43-486F-AC7E-AF5BD04EE355@freron.com> References: <010001973b28023e-ff453704-7945-49f6-88b2-051060a29c80-000000@email.amazonses.com> <010001973c666d7b-3d86c375-d861-4758-a190-8f5b528caf8c-000000@email.amazonses.com> <5DFEA1FD-0C43-486F-AC7E-AF5BD04EE355@freron.com> Message-ID: <010001973c6a3c2c-14ef41d2-168d-45b1-9ba6-6a01acfd5521-000000@email.amazonses.com> Got it! Will do. Respectfully, Henry Seiden - - Techworks Pro Co. E: infotechworksprocom W: http://techworkspro.com On 4 Jun 2025, at 15:25, Benny Kjær Nielsen wrote: > On 4 Jun 2025, at 21:23, Henry Seiden wrote: > >> Seems OK for now. If the testing goes well no failures for over a day >> or so, will try r6261 on my drone machine to verify it doesn’t quit >> either. I had downgraded both since the issue was occurs both >> machines when running r6260. >> >> Possible that 6260 also works now with your 03JUN2025 patches noted >> in Release Notes? Did not try it, though. Moving forward… > > Neither r6260 or r6261 fixes the bug I think was the main problem > (related to, e.g., an INBOX being emptied on a different machine -- > which could also explain the drone-spam-detection triggering the > issue). > > -- > Benny > _______________________________________________ > mailmate mailing list > Unsubscribe: https://lists.freron.com/listinfo/mailmate -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at techworkspro.com Wed Jun 4 15:33:26 2025 From: info at techworkspro.com (Henry Seiden) Date: Wed, 4 Jun 2025 19:33:26 +0000 Subject: [MlMt] MailMate 2.0(r6260) Crash reported to Feedback In-Reply-To: <010001973c6a3c2c-14ef41d2-168d-45b1-9ba6-6a01acfd5521-000000@email.amazonses.com> References: <010001973b28023e-ff453704-7945-49f6-88b2-051060a29c80-000000@email.amazonses.com> <010001973c666d7b-3d86c375-d861-4758-a190-8f5b528caf8c-000000@email.amazonses.com> <5DFEA1FD-0C43-486F-AC7E-AF5BD04EE355@freron.com> <010001973c6a3c2c-14ef41d2-168d-45b1-9ba6-6a01acfd5521-000000@email.amazonses.com> Message-ID: <010001973c6f2387-98ae76ce-73ca-4bc5-8930-bdcb576393f6-000000@email.amazonses.com> Benny, Testing now. The findings you used make sense to me, it explains the two distinct OS crash tags noted and that the debug log didn’t produce the exact failure indications you were looking for on the second go (r6260). Additional Hint: I usually run with an empty Inbox! Winner, winner, chicken dinner? My system: MailMate/6262/282BCB28-893E-51E7-891E-F3272BC540D1 15.5.0/arm64/MacBookPro18,3/10 Respectfully, Henry Seiden - - Techworks Pro Co. E: infotechworksprocom W: http://techworkspro.com On 4 Jun 2025, at 15:28, Henry Seiden wrote: > Got it! Will do. > > Respectfully, > > Henry Seiden > - - > Techworks Pro Co. > E: infotechworksprocom > W: http://techworkspro.com > > On 4 Jun 2025, at 15:25, Benny Kjær Nielsen wrote: > >> On 4 Jun 2025, at 21:23, Henry Seiden wrote: >> >>> Seems OK for now. If the testing goes well no failures for over a >>> day or so, will try r6261 on my drone machine to verify it doesn’t >>> quit either. I had downgraded both since the issue was occurs both >>> machines when running r6260. >>> >>> Possible that 6260 also works now with your 03JUN2025 patches noted >>> in Release Notes? Did not try it, though. Moving forward… >> >> Neither r6260 or r6261 fixes the bug I think was the main problem >> (related to, e.g., an INBOX being emptied on a different machine -- >> which could also explain the drone-spam-detection triggering the >> issue). >> >> -- >> Benny >> _______________________________________________ >> mailmate mailing list >> Unsubscribe: https://lists.freron.com/listinfo/mailmate > _______________________________________________ > mailmate mailing list > Unsubscribe: https://lists.freron.com/listinfo/mailmate -------------- next part -------------- An HTML attachment was scrubbed... URL: From MailMate at OmniComp.org Wed Jun 4 16:00:55 2025 From: MailMate at OmniComp.org (Alan Dobkin) Date: Wed, 04 Jun 2025 16:00:55 -0400 Subject: [MlMt] Gmail and "Delete Immediately" In-Reply-To: References: Message-ID: <855DD8AB-A9FD-4255-9068-F5B390262A82@OmniComp.org> This is a function of Gmail's IMAP behavior, not controlled by MailMate. If you delete messages from the Inbox via IMAP, they remain in All Mail. In order to get rid of it completely from MailMate, you can subscribe to the All Mail folder for that account, then delete it from there. Alan On 6/2/2025 4:36 PM, Tariq Magdon-Ismail wrote: > When I use "delete immediately" to skip the trash and delete an email, > it gets archived instead (still shows up in All Mail). I've tried the > different Gmail IMAP settings but can't get the expected behavior. > Does "delete immediately" work with Gmail for anyone else? > > Regards, > -Tariq > > MailMate: Version 2.0 (6257) > _______________________________________________ > mailmate mailing list > Unsubscribe: https://lists.freron.com/listinfo/mailmate -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at techworkspro.com Wed Jun 4 16:07:28 2025 From: info at techworkspro.com (Info@techworkspro.com) Date: Wed, 4 Jun 2025 20:07:28 +0000 Subject: [MlMt] Gmail and "Delete Immediately" In-Reply-To: <855DD8AB-A9FD-4255-9068-F5B390262A82@OmniComp.org> References: <855DD8AB-A9FD-4255-9068-F5B390262A82@OmniComp.org> Message-ID: <010001973c8e4ec3-dc1ad543-938d-452e-b211-a4248dd61329-000000@email.amazonses.com> I simply do not look at All Mail mailbox as I find it useless, as are lots of “features” in Google Mail. Henry - - Please excuse the tttapping errors... Sent from my iPhone C/T (954) 253-4125 Henry M. Seiden Techworks Pro > On Jun 4, 2025, at 16:01, Alan Dobkin wrote: > >  > This is a function of Gmail's IMAP behavior, not controlled by MailMate. If you delete messages from the Inbox via IMAP, they remain in All Mail. > > In order to get rid of it completely from MailMate, you can subscribe to the All Mail folder for that account, then delete it from there. > > Alan > > On 6/2/2025 4:36 PM, Tariq Magdon-Ismail wrote: > > When I use "delete immediately" to skip the trash and delete an email, it gets archived instead (still shows up in All Mail). I've tried the different Gmail IMAP settings but can't get the expected behavior. Does "delete immediately" work with Gmail for anyone else? > > Regards, > -Tariq > > MailMate: Version 2.0 (6257) > > mailmate mailing list > Unsubscribe: https://lists.freron.com/listinfo/mailmate > > _______________________________________________ > mailmate mailing list > Unsubscribe: https://lists.freron.com/listinfo/mailmate -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailmate2 at coopercontent.com Wed Jun 4 21:11:18 2025 From: mailmate2 at coopercontent.com (John Cooper) Date: Wed, 04 Jun 2025 18:11:18 -0700 Subject: [MlMt] Gmail and "Delete Immediately" In-Reply-To: <010001973c8e4ec3-dc1ad543-938d-452e-b211-a4248dd61329-000000@email.amazonses.com> References: <855DD8AB-A9FD-4255-9068-F5B390262A82@OmniComp.org> <010001973c8e4ec3-dc1ad543-938d-452e-b211-a4248dd61329-000000@email.amazonses.com> Message-ID: <3D6E8AEC-80D1-4F17-AD16-2E4F09666C6E@coopercontent.com> info at techworkspro.com wrote (at 1:07 PM on Wednesday, June 4, 2025): > I simply do not look at All Mail mailbox as I find it useless, as are lots of “features” in Google Mail. > > Henry Noted. However, you are not the person who asked for help, whose experience may differ. When I delete a Gmail message via MailMate, double-tapping my custom keybinding for "delete message" (x) permanently deletes the messages without my having to change mailboxes, since I typically view Gmail from a MailMate view of unread messages, or from my top-level "Google Mail" mailbox in the Sources list. The first press archives the message, which stays in the current view. The second deletes it permanently. Maybe a similar workflow would be helpful to Tariq. info at techworkspro.com wrote (at 1:07 PM on Wednesday, June 4, 2025): > I simply do not look at All Mail mailbox as I find it useless, as are lots of “features” in Google Mail. > > Henry > - - > Please excuse the tttapping errors... > Sent from my iPhone > C/T (954) 253-4125 > Henry M. Seiden > Techworks Pro > > >> On Jun 4, 2025, at 16:01, Alan Dobkin wrote: >> >>  >> This is a function of Gmail's IMAP behavior, not controlled by MailMate. If you delete messages from the Inbox via IMAP, they remain in All Mail. >> >> In order to get rid of it completely from MailMate, you can subscribe to the All Mail folder for that account, then delete it from there. >> >> Alan >> >> On 6/2/2025 4:36 PM, Tariq Magdon-Ismail wrote: >> >> When I use "delete immediately" to skip the trash and delete an email, it gets archived instead (still shows up in All Mail). I've tried the different Gmail IMAP settings but can't get the expected behavior. Does "delete immediately" work with Gmail for anyone else? >> >> Regards, >> -Tariq >> >> MailMate: Version 2.0 (6257) >> >> mailmate mailing list >> Unsubscribe: https://lists.freron.com/listinfo/mailmate >> >> _______________________________________________ >> mailmate mailing list >> Unsubscribe: https://lists.freron.com/listinfo/mailmate > _______________________________________________ > mailmate mailing list > Unsubscribe: https://lists.freron.com/listinfo/mailmate From mailmate at businessdatasystems.co.nz Wed Jun 4 21:20:33 2025 From: mailmate at businessdatasystems.co.nz (mailmate at businessdatasystems.co.nz) Date: Thu, 05 Jun 2025 09:20:33 +0800 Subject: [MlMt] Resetting the View In-Reply-To: <54708AF2-0378-4315-A423-0606FA1F5647@businessdatasystems.co.nz> References: <54708AF2-0378-4315-A423-0606FA1F5647@businessdatasystems.co.nz> Message-ID: <4EDDA85F-E076-4958-965B-7DC115253811@businessdatasystems.co.nz> Answering myself as no-one else seems to have bumped into this problem. As described below, clicking and dragging the dimpled horizontal bar does nothing - until you drag far enough. I don't know what "far enough" really means. In my case it was about 300px. Until the click-and-drag gets beyond the magical limit there is no visual feedback, and in fact, nothing happens. The window pane is not modified in any way. The application provides no support for doing the right thing. At the point that the magic limit is passed the message view window springs into view. What I am accustomed to is progressive action. If I do the something on my side, the computer program does the something on its side, and it does this progressively. If I touch the "e" key once I see "e" printed on the screen. If I hold the "e" key down, "e" is printed on the screen until I release it. Having to perform the right action in a highly specific way, instead of a highly general way, makes it extremely difficult to use the software comfortably. In this case, clicking and dragging should be sufficient to obtain a successful result. In fact, success can only be achieved by clicking and dragging until an unspecified (but fairly large) minimum distance has been travelled by the mouse. This leaves a lot of potential for failure. The fact that it's very easy to get into this situation and very hard to get out of this situation really sucks. thanks to everyone at home who is reading along. Malcolm On 29 May 2025, at 16:16, mailmate at businessdatasystems.co.nz wrote: > I read my mail in three pane view: a thin left hand column contains > mailboxes. The rest of the window is split by a horizontal divider, > with message lists at the top and the message pane at the bottom. > > Recently I've moved the divider between the message lists and the > message pane. The mailbox column and the message list are visible but > the message pane is not. I can see the divider at the bottom of the > window. It displays the characteristic dimple and when I hover my > mouse over it, the icon changes to a horizontal bar with an arrow > pointing up. Clicking and dragging does nothing. I'm not able to move > the divider to reveal the message pane. > > This is frustrating me. How do I reset the window to sensible > defaults? > > Malcolm > > _______________________________________________ > mailmate mailing list > Unsubscribe: https://lists.freron.com/listinfo/mailmate -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglist at freron.com Thu Jun 5 06:56:09 2025 From: mailinglist at freron.com (=?utf-8?q?Benny_Kj=C3=A6r_Nielsen?=) Date: Thu, 05 Jun 2025 12:56:09 +0200 Subject: [MlMt] Highlighting message headers in mailing list digests In-Reply-To: <00835EC1-6F66-46FE-A60B-CC623973CDA8@sumware.co.nz> References: <00835EC1-6F66-46FE-A60B-CC623973CDA8@sumware.co.nz> Message-ID: <9B7C726C-4DB8-48AF-A567-9DB9F481E693@freron.com> On 29 May 2025, at 0:29, Rob Russell via mailmate wrote: > I've noticed that in mailing list digests (such as this mailing list produces) that if I am dark mode, each message has alternating background colouring...at least the headers do. Well, it's not really alternating, but it looks like that because many/most emails have an HTML part which has a white background by default (MailMate still needs a feature to force these into dark mode when possible). If you get a digest of plain-text-only emails then they would all have dark backgrounds. > However, in Light mode, each message is not distinguished as clearly. Which is because most emails contain HTML. > Is this my configuration or am I adding something to Benny's long list of work? If you select multiple messages then you'll see what MailMate could do for digests as well, that is, add some margin and maybe a border. Unfortunately, an embedded message does not quite work the same way as a regular message (internally) which means that I cannot just flip a switch. So, the “missing” feature is to improve how embedded messages are handled in the message view and then that would make it easier to also improve it visually. -- Benny From mailinglist at freron.com Thu Jun 5 07:36:43 2025 From: mailinglist at freron.com (=?utf-8?q?Benny_Kj=C3=A6r_Nielsen?=) Date: Thu, 05 Jun 2025 13:36:43 +0200 Subject: [MlMt] Resetting the View In-Reply-To: <4EDDA85F-E076-4958-965B-7DC115253811@businessdatasystems.co.nz> References: <54708AF2-0378-4315-A423-0606FA1F5647@businessdatasystems.co.nz> <4EDDA85F-E076-4958-965B-7DC115253811@businessdatasystems.co.nz> Message-ID: On 5 Jun 2025, at 3:20, mailmate at businessdatasystems.co.nz wrote: > Answering myself as no-one else seems to have bumped into this problem. Sorry about the late reply. > The fact that it's very easy to get into this situation and very hard to get out of this situation really sucks. Yes, I'll decrease the minimum size of the message view to make this less likely to happen again. (In my defense, I do believe it's larger in Apple Mail.) -- Benny From mailmate at businessdatasystems.co.nz Thu Jun 5 21:58:21 2025 From: mailmate at businessdatasystems.co.nz (mailmate at businessdatasystems.co.nz) Date: Fri, 06 Jun 2025 09:58:21 +0800 Subject: [MlMt] Resetting the View In-Reply-To: References: <54708AF2-0378-4315-A423-0606FA1F5647@businessdatasystems.co.nz> <4EDDA85F-E076-4958-965B-7DC115253811@businessdatasystems.co.nz> Message-ID: On 5 Jun 2025, at 19:36, Benny Kjær Nielsen wrote: > Sorry about the late reply. > >> The fact that it's very easy to get into this situation and very hard to get out of this situation really sucks. > > Yes, I'll decrease the minimum size of the message view to make this less likely to happen again. (In my defense, I do believe it's larger in Apple Mail.) The problem that I experienced was that the message pane divider was unresponsive until I had click-dragged past the minimum height for the window. My experience from other multi-pane windows is that the divider is responsive. The user sees it moving immediately, and of course this has ramifications for minimum heights because it must be able to accept any height between zero and the window height. Malcolm