On 3 Apr 2026, at 16:47, Robert Brenstein wrote: > I think I solved the problem. The change that worked was to give SpamSieve > full disk access rights. No idea whether this setting got lost during the > system update or was not needed before. I am not sure where I found a tip > about this either. I am just happy that MailMate works again as expected :-) > In my case Spamsieve already hd full disk access but Mailmate did not. I’ll see if that was my problem…
> Robert > > On 3 Apr 2026, at 20:02, David R. Oran wrote: > >> I’m seeing this extensively on Tahoe (26.4), Mailmate 6290 & 6292, with >> Spamsieve multiple versions (just updated to 3.3b1) and already reported it >> to Bennie along with config and activity logs. >> >> Just FYI - you can cut the beach balling short by clicking on Spamsieve to >> bring it to the foreground. My guess is the root cause is something in MACOS >> blocking or delaying cross-app data sharing. >> > _______________________________________________ > mailmate mailing list > Unsubscribe: https://lists.freron.com/listinfo/mailmate DaveO
smime.p7s
Description: S/MIME digital signature
_______________________________________________ mailmate mailing list Unsubscribe: https://lists.freron.com/listinfo/mailmate
